7 parts · 2 checkpoints · 2 free / 5 member parts →
Shopify performance and app audit: what to check first
This audit route fixes the page, template, device, market, and time window before separating installed, enabled, actually loaded, and leftover theme or app resources. The PetNest case tests one variable in a preview theme, replays reviews, add to cart, subscriptions, support, and key events, and does not turn one score change into a site-wide speed claim or deletion approval.
What this lesson answers
Continues from: Shopify Markets: check the customer path before changing prices
From market path to page evidence
The market path is aligned; we still need to confirm what the page actually loads. On the PetNest path, read installed status separately from actually loaded evidence on the page. Page speed alone does not prove the cause. The page path is now defined. The current decision is whether to keep, freeze, or validate in a copy.
Once the path is defined, confirm what the page actually loads
LCP: largest-contentful-paint time. INP: interaction responsiveness. TBT: total blocking time (lab proxy). P75: 75th percentile. CrUX: Google real-user data. RUM: real-user monitoring. LCP: good ≤2.5s, poor >4.0s. INP: good ≤200ms, poor >500ms. Choose a candidate resource to practise “fix the scope, then read the evidence,” not to vote on which app to delete. Fix one candidate to one PetNest page and device condition, then read its load evidence, customer function, and recovery point. If the proposed test changes the theme, app, cache, and copy together, the scope is too large and should return to one candidate.
When reading the table, do not stop at whether the variant median improved. First confirm that the observations share page, market, device, cache, and feature conditions; then ask whether the change moved with the candidate resource; finally replay add-to-cart, reviews, subscription, or chat on the variant page. Even an improvement permits only continued bounded observation. It does not prove store-wide speed, search, checkout, or conversion improved.
Copying or downloading creates a record of entered evidence, unknowns, and next steps. It supports operational transfer, but cannot replace authorized report reads, theme-copy testing, or a formal change record.
Classify resource state before reading performance
Installed, enabled, loaded, and actual impact are four different questions. Installed means the resource exists; enabled means it may be allowed to run; loaded requires page or network evidence; actual impact must connect to a specific page task, customer action, or event. Collapsing these layers into “this app is slow” invites deletion before the cause is located.
That is why this lesson does not turn performance into one score. The conclusion records what was observed for which market, page, device, and time window; which resource appeared with the symptom; which functional replay is still missing; and whether the next move is keep, freeze, validate in a copy, or pause cleanup.
Connect the symptom to an owner
Check the theme or somewhere else first?
Self-check not answered
PetNest example: what is still missing between installed and actual impact
Here is a PetNest record that can be filled into the audit sheet. Everything in square brackets is a placeholder, not an Admin readback, screenshot, or test result. This example is not connected to a live store; an authorized owner must replace it with same-scope evidence.
Try it first
The error is substituting one score for customer-path, business-value, and recovery evidence. Correction: fix the copy and device first, then read load evidence, customer function, and the recovery point.
The error is merging lab conditions, real-user distribution, and metric boundaries into one fact. Correction: record the Lighthouse conditions and the RUM window separately.
The error is checking install state only. Correction: check app blocks, embeds, theme code, snippets, and the actual runtime request.
The error is reading "no console error" as accessibility passing. Correction: replay keyboard, focus, tap targets, and a customer task.
Free account to read · Parts 3-7 · 5 parts
Members: full exercises and records
This part includes
- Read real users before theme work
- A lab score is not experience
- Confirm features before removal
An account is free; sign in to read this part.
Checking your membership…
No checkpoint finished in this lesson yet. Start with “Go to the exercise”.
Self-check not answered
FAQ
- Why should I not uninstall an app as soon as a page feels slow?
The app may still provide reviews, subscriptions, chat, or a key event. Removing it first can break a customer path without fixing the real loading issue. Record whether the object is installed, enabled, loaded, or suspected residue, then validate one object at a time in a theme copy.
- What is the difference between installed, enabled, and actually loaded?
Installed means the app or configuration entry remains in admin. Enabled means an App block, App embed, or theme setting has an active entry. Actually loaded requires an observed request or execution on a named page, device, and time window. None of the three alone proves the object should be removed.