How Fast Should a Shopify Store Load:
What 128 Product Pages Show and How to Measure Yours

In our scan of 128 US Shopify product pages, the median page fired the browser load event at 10.4 seconds and made 231 requests. That was one cold desktop test per page with an empty cache. It is a lab number and a relative signal, not what your shoppers wait. The request count is the part you control.

This post is part of our Shopify store benchmarks for 2026. It covers what we found, which number you should actually target, how to measure your store properly, and a cleanup plan for apps and tags.

How slow were the product pages we checked?

We loaded each page once in headless Chrome at 1200x900 with an empty cache. We recorded when the browser's load event fired and how many requests the page made.

Of the product pages we checked, 52% (66 of 128) took more than 10 seconds to reach the load event in this test. And 16% (20 of 128) made more than 300 requests.

Is 10.4 seconds what shoppers actually wait?

No. The load event fires when the page and everything it pulled in have finished loading: images, scripts, fonts, iframes. A shopper usually sees the product, price and button well before that.

Our test also used a cold cache. Real shoppers on a warm cache, returning to your store, get many files from their own browser and see faster pages. So do not quote 10.4 seconds as "Shopify stores take 10 seconds to load."

What the number does tell you is how much work a page asks the browser to do. A page that needs 300 requests to settle will usually feel heavier than one that needs 120, on any device. Use it to compare your pages against each other and against our sample, not as a shopper experience score.

So how fast should a Shopify store load?

Target Largest Contentful Paint (LCP), measured on real visits. LCP is when the largest image or text block in view finishes rendering. Google's web.dev LCP guide sets "good" at 2.5 seconds or less and "poor" above 4.0 seconds. It says to measure at the 75th percentile of page loads, split by mobile and desktop.

Shopify uses the same lines in its Web performance reports:

So the short answer: LCP at or under 2.5 seconds for 75% of real visits, on mobile and on desktop. Our 10.4 second load event and your LCP are different metrics. Do not compare them directly.

Why it matters: Deloitte's Milliseconds Make Millions study, commissioned by Google, tracked mobile sites over 4 weeks. A 0.1 second speed improvement went with 8.4% more retail conversions and 9.2% higher retail average order value. That is a correlation across the brands studied, not a promise for your store.

What drives 231 requests on a product page?

Our scan counted requests. It did not split them by source, so we cannot say which tool caused how many. What we can show is how common the usual suspects were. These shares come from scripts loaded on 226 homepages.

Each tag or app script typically pulls in more files: a library, a config, sometimes its own fonts, images or iframes. The common sources of request bloat on Shopify product pages are:

• Apps. Reviews, upsells, bundles, popups, chat and wishlists each load their own scripts. Shopify's speed guide says "Too many apps loading assets on your storefront can slow performance."
• Leftover app code. The same guide warns: "Uninstalling an app doesn't automatically remove its code from your theme."
• Ad and analytics tags. Several pixels, sometimes loaded twice (once in theme code, once through Google Tag Manager).
• Images. Large galleries and review photos. Shopify notes that "Pages with numerous high-quality images can load slowly."
• Video. A YouTube or Vimeo embed loads a player and its scripts. Only 12 of 128 product pages (9%) in our sample had product video, but each one adds weight.
• Fonts. Every family and weight is a separate file. Three families in four weights each is 12 font files before any content.

How do you measure your own Shopify store properly?

Use field data first and lab tests second. Field data is what real shoppers experienced. Lab tests are for finding causes.

1. Shopify's Web performance dashboard. In Shopify admin, go to Online Store to see the summary. For full reports, go to Analytics > Reports and search "contentful" (LCP), "next" (INP) or "cumulative" (CLS). Shopify says the summary uses real user data from the past 30 days, reports the 75th percentile, and lags by up to 36 hours. The Over Time charts mark app installs and theme changes as numbered lines, so you can see which change moved LCP.

2. PageSpeed Insights. Run a product URL, not only your homepage, at pagespeed.web.dev. The top section shows real Chrome user data when Google has enough of it. The lower section is a Lighthouse lab run with a list of slow scripts and large files. That data comes from the Chrome UX Report, which only covers pages and origins with "a large enough number of visitors" to be statistically significant. Smaller stores often see lab data only.

3. Chrome DevTools for requests. Open a product page, press F12, open the Network tab, check "Disable cache" and reload. The bottom bar shows the request count and the load time. This is the closest match to how we tested. Sort by domain to see which third parties make the most calls.

Test your top 3 product pages, a collection page and the homepage. Product pages usually carry the most apps.

What is the app and tag cleanup plan?

Run this once a quarter, on a duplicate theme first.

1. List every app and tag. Export your installed apps. Then list every tag in theme code, in Google Tag Manager and in Shopify's Customer events (Settings > Customer events).
2. Mark each one keep, cut or merge. Keep what drives revenue or data you actually use. Cut duplicates: two review apps, two popup tools, a pixel loaded both in the theme and in GTM.
3. Uninstall, then clean the theme. Turn off the app's embed in the theme editor (Online Store > Themes > Customize > App embeds). Then search theme.liquid and snippets for the app's name and remove leftover code. Do this on a duplicate theme first.
4. Audit the tag manager. Shopify's guide says to "remove any unused or low-value tags." Old campaign pixels and test tags are common.
5. Fix media. Use a poster image that loads the video player on click instead of on page load. Cap product galleries at the images that sell. Let the theme serve resized images rather than uploading 5,000px files.
6. Cut font files. Use 1 or 2 families and only the weights you show. A system font stack costs zero requests.
7. Re-measure. Check DevTools request counts the same day. Check the Shopify dashboard after 7 and 30 days, using the event markers.

For theme level fixes (lazy loading, preloading the main image, render blocking scripts), see our Shopify page speed optimization guide.

How we measured

We drew 360 US Shopify storefronts at random from StoreLeads on Oct 21 to 22 2026. 226 homepages loaded and on 128 we loaded a product page (the first linked product that was not a gift card). Each page was loaded once in headless Chrome, desktop viewport 1200x900, empty cache, from a data center in Mumbai, India (so load times include the distance to US servers and run higher than a US shopper would see; a rerun from the US is in progress). Load time is the browser load event in this cold test, not a Core Web Vitals field measurement, and real shoppers on a warm cache will see faster pages. The full method and limits are in the pillar report.

What should you fix first?

Speed work pays off most on the pages where buying happens. Our product page benchmarks show what else those pages are missing, and our post on review stars in Google covers a fix that adds no weight at all. For a full prioritized list, see our Shopify CRO guide.

You can run the same checks on your store. If you want a team to do the cleanup, Sorted has worked with 100+ D2C brands since 2017. Talk to us.