A slow Shopify store needs an investigation, not an immediate promise to remove apps or produce a perfect score. The home page, collection page and product page may load different resources and expose different problems. A useful review starts by deciding what to measure and which features must keep working.
This checklist explains how to prepare and interpret a storefront performance review. It does not claim a measured client result.
Choose representative shopping pages
Do not rely on the home page alone. Include important collection and product pages, especially those with required app features or more complex interactions.
Record the exact URLs and any conditions that affect the page. Product media, consent tools, reviews, subscriptions or variant behaviour may create different performance costs. The sample should reflect the experience being investigated rather than the easiest page to test.
Record a baseline and the test conditions
Write down when the check was performed, the tool, the device or simulation, and relevant conditions. Repeat lab checks where appropriate because individual runs can vary.
Do not compare a desktop result with a mobile result and call it improvement. A meaningful follow-up uses comparable settings and the same page types. Even then, interpret the result alongside visitor experience and functionality.
Separate lab tests from field experience
Lab tools help identify bottlenecks under controlled conditions. Field data reflects actual visitors and their devices, networks and interactions. They answer related but different questions.
Core Web Vitals cover loading, responsiveness and visual stability. The good thresholds are LCP at or below 2.5 seconds, INP at or below 200 milliseconds and CLS at or below 0.1, assessed at the 75th percentile of field visits. Google web.dev: Web Vitals and field thresholds
A lab score is not a measurement of every visitor's experience. Low-traffic pages may not have enough public field data, and that should be reported as missing data—not converted into a pass or a fail.
Review image loading and important content
Large or poorly prioritised images can delay visible content. Review image sizing, responsive sources and whether the main visible image is being lazy-loaded unnecessarily. Image dimensions can also help prevent layout shifts.
Shopify recommends using its image filters appropriately and avoiding lazy-loading the LCP image. The right fix depends on the actual theme and page, not a blanket rule to lazy-load every image. Shopify: theme performance best practices
Identify scripts and dependencies
Review theme scripts as well as installed-app resources. Third-party scripts are not automatically the only problem: first-party code can also block rendering or interaction.
Decide which resources are necessary at page load and which can be deferred or loaded when required. Shopify's performance guidance recommends reducing unnecessary JavaScript and reviewing render-blocking dependencies. Changes must account for execution order and functional requirements. Shopify: theme performance best practices
Do not remove revenue-critical or required functionality without the merchant's agreement. A useful finding explains both the performance cost and the trade-off.
Prioritise work by evidence and control
Separate issues the theme developer can fix from work that depends on an app vendor or another provider. Explain what is in scope, what needs approval and what cannot be changed directly.
Avoid a long list of generic recommendations that have not been tied to the store. The value of the review is in identifying the issues that actually affect the agreed pages and a practical order for addressing them.
For the service scope, see Shopify speed optimization.
Test functionality after performance changes
Recheck product selection, navigation, cart behaviour and required apps. A faster test result is not a successful intervention if the shopping journey stops working.
Record remaining limitations and any future dependency. If a provider controls an unresolved script or feature, make that clear in the handoff rather than implying every performance issue has been solved.
Report results without exaggeration
A responsible before-and-after report identifies the pages, conditions, method, baseline, follow-up and changes made. Distinguish lab results from field results.
A better performance score does not prove higher sales. Business outcomes need their own measurement and attribution. Likewise, speed work described as ongoing is not a completed success story. The existing Daily Belts and THOME case studies make this limitation explicit.
Prepare a performance-review brief
Share the affected storefront URLs, what visitors or your team are experiencing, any existing reports and the apps/features that must remain. Include relevant recent changes and release constraints.
If you want help reviewing the store, discuss a Shopify performance project. Begin with a baseline and an agreed scope—not a guaranteed score.