One second of load time.
$210,000 of
recoverable revenue.

Your Shopify store is probably losing over $200,000 a year to a problem that doesn't show up in any marketing report. No campaign failure. No product issue. No team mistake. Just a page that loads one or two seconds slower than it should — and a conversion rate that quietly pays the penalty every single day.

Most merchants treat speed as a technical problem. Something for a developer to fix eventually, in a future sprint, after the more urgent things get handled. That framing is wrong. Speed is a revenue problem. And unlike acquisition spend, fixing it doesn't require more budget — it just requires understanding where the money is going. It's also inseparable from your app stack decisions — every app you add is adding load time, which means the app audit and the speed audit should be run together.

The math your
speed score
doesn't show you.

A 1-second delay in page load time reduces conversion rates by approximately 7%. That stat has been validated across millions of sessions and is consistent enough to build a business case around. So let's build one.

Take a Shopify store doing $3M in annual revenue. If that store currently loads in 3.5 seconds and can be reduced to 2.5 seconds — one second — the math looks like this: 7% of $3M is $210,000 in recoverable annual revenue. Not from a single campaign. Not from a price increase or a new product launch. From pages that load faster.

That $210,000 requires zero additional ad spend. The traffic is already there. The acquisition cost has already been paid. You're just converting more of what you paid to bring in.

The reason merchants don't think about it this way is that slow load times don't generate a Shopify notification. There's no alert that says "you lost $17,500 this month because your homepage took 4 seconds to load." The revenue just quietly doesn't arrive. Shoppers bounce. They don't come back. You spend more on acquisition to compensate, which compounds the problem rather than solving it. This shows up directly in your cohort LTV data as lower-than-expected second purchase rates from paid channels.

Where the 7%
actually comes from.

The figure is directional, not a guarantee — no single study will replicate exactly on your store. But the direction and magnitude are consistent across independent research covering hundreds of millions of sessions.

The most cited source: a Google-commissioned study by Deloitte and 55, examining 37 leading brand sites across Europe and North America with data from over 30 million user sessions. The finding: a 0.1-second improvement in mobile load time increased conversions by 8.4% in retail and boosted average order value by 9.2%. Not 0.1 seconds less than your target. Just 100 milliseconds.

Shopify's own published data on store speed and conversion shows a consistent relationship: faster stores convert at higher rates across every store size and category. The correlation is strongest on mobile, where Shopify data shows speed has approximately 70% more impact on conversion than the same speed improvement would have on desktop. The reason is simple. Mobile users are browsing on slower connections, with lower patience thresholds, and often with a thumb rather than a cursor — every extra second of waiting costs more patience than it would on desktop.

The conversion rate by load time data is directional but useful as a benchmark:

Vodafone documented a 31% LCP improvement that resulted in an 8% increase in sales. Rakuten 24 found that achieving good LCP scores led to a 53% increase in revenue per visitor and a 33% increase in conversion rate — an extreme outlier, but directionally consistent with the research. These aren't small companies with unusual traffic patterns. The pattern holds at scale.

One more number that should focus attention: as mobile page load time increases from 1 second to 5 seconds, bounce probability increases by 90%. Those are visitors who never even see your product. No product photography, no reviews, no offer — just a loading screen they didn't wait for.

What to measure
before you start
fixing anything.

Before touching a single app or image, you need a baseline. Most merchants haven't looked at their actual load time with any rigor — they rely on gut feel ("seems fast enough") or a Shopify speed score that doesn't tell the complete story. Here are the four measurement tools that matter, in order of how to use them.

Shopify's Built-In Speed Score

Find it in your Shopify admin under Online Store > Themes. Scores run 1–100. Below 50 is a problem. Above 70 is solid. The score also compares you to similar stores, which gives useful competitive context. What it doesn't tell you: specific Core Web Vital scores, which are what actually correlate with conversion and SEO rankings.

Google PageSpeed Insights

Go to pagespeed.web.dev and enter your URL. This gives you the Core Web Vitals breakdown: LCP (Largest Contentful Paint), FID (First Input Delay), and CLS (Cumulative Layout Shift). LCP under 2.5 seconds is the target for the "Good" threshold — this is what Google uses for search ranking signals and what the conversion research is built around. Run it on mobile, not just desktop. Mobile scores are almost always worse, and mobile is where the majority of your traffic is.

GTmetrix

More technically detailed than PageSpeed Insights. GTmetrix shows a waterfall breakdown of every resource loading on your page — scripts, stylesheets, fonts, images — with timing data for each. This is where you identify the specific culprits: which app script is adding 800 milliseconds, which image is 2.4MB when it should be 200KB. Start here when you're ready to move from measurement to fixing.

Real User Monitoring

Synthetic tests (PageSpeed Insights, GTmetrix) run from controlled environments. Real User Monitoring shows you actual load times from real visitors on real devices and connections. Triple Whale, Google Analytics 4, and several Shopify-native analytics apps surface this data by device type. It's the most accurate picture of what your customers are actually experiencing — and it often shows mobile performance materially worse than synthetic tests suggest.

Run all four. Build a baseline doc with your current Shopify speed score, your LCP on mobile from PageSpeed Insights, and the top three script/resource offenders from GTmetrix. That's your starting point.

The four things
slowing most
Shopify stores.

After working with dozens of Shopify merchants across a wide revenue range, the same culprits appear in almost every slow store. Not exotic edge cases. The same four things, in roughly the same order of frequency and impact.

The image problem alone accounts for 40–60% of total page weight on most Shopify stores. A product photo uploaded at 4,000 pixels wide and 3MB is being served to a mobile browser that displays it at 375px. The browser downloads three megabytes to show the visitor a product image roughly the size of their thumb. Every product page, every collection page, on every visit.

The app script problem is structural. Each Shopify app that injects JavaScript executes on every page your visitor loads — regardless of whether that app does anything on that page. A loyalty program widget that only renders on the account page still loads its script on the homepage, the product page, and checkout. A review app loads everywhere. A bundle builder loads everywhere. Twenty apps with page-level scripts adds between 800 milliseconds and 2.5 seconds to load time before a single product image renders.

Third-party scripts compound the app script problem. A live chat widget, an exit-intent pop-up service, three ad tracking pixels, an affiliate attribution script — each one adds HTTP requests and load time. The question with each script is whether its value exceeds its speed cost. Some clearly do. Some clearly don't. Most merchants haven't done that math.

Five fixes, ranked by
how fast they
pay back.

Not every speed fix has the same ROI. The goal is to get the most conversion improvement from the least development investment. Here are the five highest-impact fixes in order of effort-to-impact ratio.

Making the business
case before you
spend a dollar.

Speed optimization work costs money. Development time, app subscriptions, an image processing tool. Before committing to any of it, build the business case. This takes 20 minutes and tells you whether the investment is worth prioritizing over other CRO projects.

Here's how that plays out at two different store sizes.

Store A — $500K/month, 2.8% conversion rate, 3.5-second mobile LCP: The gap to 2.5 seconds is 1 second. At 7% per second, that's a 7% potential conversion lift. 7% of $500K is $35,000 in potential monthly recoverable revenue. Against a $5,000–$15,000 development investment, the payback period is under a month. Even if the actual improvement lands at half the theoretical estimate, it pays back in 2 months.

Store B — $150K/month, 1.8% conversion rate, 5.0-second mobile LCP: The gap to 2.5 seconds is 2.5 seconds. At 7% per second, that's a 17.5% potential conversion lift — but apply a conservative 40% discount for the theoretical vs. actual gap: 10.5% realistic estimate. 10.5% of $150K is $15,750/month. The image optimization and app audit work costs 6–10 hours of internal time. Payback: immediate.

The key discipline: do the measurement first, build the business case, then prioritize fixes in order of effort-to-impact ratio. Don't start with developer-level work when the image library hasn't been touched. Don't hire a speed optimization agency when the app audit hasn't been run. The highest-ROI work is almost always the simplest to execute — and it should come first.

Speed is one of the few CRO levers that improves conversion rates, bounce rates, and SEO rankings simultaneously. Better LCP scores correlate with higher organic rankings. Lower bounce rates improve your site quality signals. Higher conversion rates improve the economics of every acquisition channel you're running. The same fix pays back across three dimensions at once.

Most merchants reading this have a store loading over 3 seconds on mobile. If that's you, run PageSpeed Insights on your top product page right now. The number you see is a revenue figure waiting to be recovered.