Slow mobile pages cost a Shopify store conversions on every visit, and the published research puts the effect at meaningful sizes: Portent’s 2019 study found conversion rates drop an average of 4.42% for each additional second of load time in the first five seconds. The biggest causes on Shopify are almost always third-party app scripts (including leftovers from apps you already removed), oversized hero images and video, too many font files and theme bloat. Fix product pages first, remove before you optimize, and judge results on real-visitor field data, not a single lab score.
Speed is one of the few conversion levers that is mostly technical. You do not need a new campaign or a new offer. You need to know what is loading, why, and what can go. This guide explains how speed is measured, what usually slows Shopify stores down, the order we fix things in, and a worked example of what slow pages might be costing.
What the research says about speed and conversion
Two studies get cited most often, and both are worth knowing.
- Portent (2019): conversion rates dropped an average of 4.42% for each additional second of load time, between zero and five seconds.
- Deloitte and 55 for Google, “Milliseconds Make Millions” (2020): a 0.1-second improvement in mobile site speed was associated with an 8.4% increase in retail conversions. The case study is summarized on web.dev.
Neither study is a forecast for your store. They measured patterns across many sites, and your results depend on your audience, products and starting point. But both point in the same direction, and the direction is not in dispute: faster mobile pages convert better.
How speed is measured: Core Web Vitals
Google’s Core Web Vitals are the standard measures. Each has a “good” threshold, and a page passes when at least 75% of real visits (the 75th percentile) meet it.
| Metric | What it measures | Good | Typical Shopify culprit |
|---|---|---|---|
| Largest Contentful Paint (LCP) | How long until the main content, usually the hero or product image, appears | 2.5 seconds or less | Oversized hero images, autoplay video, render-blocking app scripts |
| Interaction to Next Paint (INP) | How quickly the page responds when someone taps, such as choosing a variant or adding to cart | 200 milliseconds or less | Heavy JavaScript from apps and theme features |
| Cumulative Layout Shift (CLS) | How much the page jumps around while loading | 0.1 or less | Late-loading banners, pop-ups, review stars and images without set dimensions |
Lab data vs. field data
When you run a page through PageSpeed Insights, you see two kinds of results, and mixing them up leads to bad decisions.
- Lab data is a single simulated test: one page load on a throttled device and connection, run by Google’s tools at that moment. It is useful for diagnosing problems and checking a fix immediately. It changes from run to run and does not reflect what your actual visitors experience.
- Field data comes from the Chrome User Experience Report (CrUX), which collects real measurements from Chrome users visiting your site. It appears at the top of PageSpeed Insights as what your real users are experiencing, when your site has enough traffic. It is a rolling 28-day window, so fixes take time to show up.
The lab score, the big number out of 100, is what people screenshot. The field data is what matters for your customers and for how Google evaluates the page. A store can score 40 in the lab and pass Core Web Vitals in the field, or score 80 and fail. Make decisions on field data, and use lab tests to find causes and confirm fixes.
The biggest causes of slow Shopify pages
Third-party app scripts
This is the cause we find most often. Reviews, loyalty, chat, upsells, pop-ups, analytics, personalization and subscription widgets each load their own JavaScript, often on every page, whether or not that page uses the feature. On a phone, those scripts compete for the same limited processing power, which delays the main image and makes taps feel slow.
Leftovers from uninstalled apps
Removing an app does not always remove its code. Older apps in particular leave snippets in the theme or script tags that keep loading after the app is gone. We regularly find scripts from apps that were uninstalled long ago, still loading on every page, sometimes throwing errors. You pay the speed cost with none of the benefit.
Oversized hero images and video
A full-width hero image exported straight from a design tool can be several times larger than any phone needs. Autoplay background video is worse. Shopify’s image service can resize images on the fly, but only if the theme requests the right sizes. The hero and the main product image are usually what LCP measures, so they deserve the most attention.
Fonts
Each weight and style of a custom font is a separate file. A theme using two typefaces with regular, medium, bold and italic versions can load many font files before text appears correctly. Fonts that swap in late also cause layout shift.
Theme bloat
Feature-heavy themes ship sliders, animations, mega menus, quick-view pop-ups and sections you may not use. Years of edits by different developers add more. Each piece adds code that every visitor downloads.
What to fix first
The order matters more than the individual fixes. This is how we approach it.
- Start with field data. Check the field data in PageSpeed Insights for your product pages, collection pages and home page, and look at the Core Web Vitals report in Google Search Console. Note which metric fails and on which page types. That tells you where to focus.
- Work on product pages first. Product pages are where the buying decision happens and where most paid traffic lands. A gain on the product page template applies to every product at once. The home page matters, but it is rarely where most revenue is decided.
- Remove before you optimize. List every script loading on the product page and match each to an app or feature. Uninstall apps you do not need, remove leftovers from apps already gone, and turn off app embeds on pages that do not use them. Removing a script is always faster than optimizing one.
- Fix the main image. Make sure the hero and main product image are served at sizes that fit phones, in modern formats, and loaded early rather than lazily. Replace autoplay hero video on mobile with a still image unless the video earns its cost.
- Trim fonts. Use fewer weights, load only what the page shows and set fonts to display fallback text immediately.
- Reduce theme code. Remove unused sections and features, and set dimensions on images and embeds so the page does not jump.
- Re-test, then wait for the field. Confirm each change in a lab test right away, then watch field data over the following weeks. Because CrUX uses a 28-day window, the full effect takes about a month to appear.
Worked example: what one second might be worth
Take a store doing $300,000 a month in mobile revenue whose product pages load about one second slower than they reasonably could.
Applying Portent’s average of 4.42% per additional second: $300,000 × 4.42% = $13,260 a month, or $13,260 × 12 = $159,120 a year in revenue that a one-second improvement might recover.
Treat that number as directional, not a promise. Portent’s figure is an average across many sites, the relationship between speed and conversion is not perfectly linear, and your store’s results depend on traffic mix and product. What the example does show is the order of magnitude: for a store at this size, a real speed improvement is usually worth far more than the cost of the work. Run your own numbers in the Shopify speed calculator.
Speed is also not always the biggest problem. A store with fast pages can still lose sales to a confusing product page, broken tracking or an email program that is not doing its job. Measure first, then spend effort where the evidence points. Sometimes that is speed, sometimes it is not.
For a quick, free first look at your own store, start with the store report. A full review of speed alongside apps and tracking is part of the Commerce Tech Audit ($5,000 fixed, two weeks).
Frequently asked questions
How fast should a Shopify store load on mobile?
Aim to pass Google’s Core Web Vitals on real visitors: Largest Contentful Paint of 2.5 seconds or less, Interaction to Next Paint of 200 milliseconds or less and Cumulative Layout Shift of 0.1 or less, measured at the 75th percentile of visits.
Why is my PageSpeed Insights score low when my store feels fast?
The headline score comes from a single simulated lab test on a throttled phone and connection. Check the field data section, which reflects real Chrome visitors over the last 28 days. If field data passes Core Web Vitals, your visitors are mostly getting a good experience even if the lab score looks poor.
Do Shopify apps slow down my store?
Many do, especially apps that add widgets or scripts to the storefront. The effect adds up across apps, and code left behind by uninstalled apps can keep slowing pages. Review which scripts load on your product pages and remove any you do not need.
How much revenue does a one-second delay cost?
Portent’s 2019 study found conversion rates fall an average of 4.42% per additional second of load time between zero and five seconds. For a store with $300,000 a month in mobile revenue, that suggests roughly $13,260 a month per second. Treat it as a directional estimate, not a forecast.
How long does it take to see speed improvements in Google’s data?
Lab tests show changes immediately. Field data from the Chrome User Experience Report covers a rolling 28-day period, so it takes about four weeks for a fix to be fully reflected.
Scott founded Broke Hold. He works hands-on across ecommerce operations, automation, cloud infrastructure, and integrations, works as the fractional CTO for Shopify brands, and builds and runs Broke Hold's own software, including VPS Snaps and DingPack. He served in the U.S. Navy Reserve.