Ayo is the founder of Why Matters, a Shopify agency based in Brighton. With over 20 years of experience in ecommerce, digital marketing, and ROI-driven growth, he has helped hundreds of Shopify brands build, launch, and scale their online stores. Why Matters is a certified Shopify, Klaviyo, and Recharge partner.
Shopify's speed score is a Google Lighthouse lab result, benchmarked against similar stores, and it is a poor guide to how your store actually performs. Google does not use Lighthouse scores for ranking. It uses Core Web Vitals field data collected from real Chrome users, which you can check in Google Search Console or in the field data section of PageSpeed Insights. Track your conversion rate, your Core Web Vitals, and the load time of the landing pages taking paid traffic. Optimise the things you control, principally your theme, your images and your app stack. Do not remove an app that earns its keep in order to move a number that does not affect your rankings or your revenue.
Shopify's built-in speed score causes more anxiety than any other number in the admin. Merchants see a score out of 100, assume anything below 80 is a problem, and start removing apps and stripping back functionality in pursuit of a higher number, often damaging their conversion rate in the process.
The score is based on Google Lighthouse, a lab simulation that does not measure how real customers experience your store. What affects your rankings and your revenue is how your store performs for real users in real conditions, and that is a different set of metrics entirely. This article covers what the score actually is, what to measure instead, and which optimisations are worth your time.
The speed report in the Online Store section of your admin shows a score out of 100 based on Google Lighthouse performance testing. Lighthouse is an open-source Google tool that runs automated simulations of page loading under controlled lab conditions. Shopify tests your homepage, a product page and a collection page, then produces a composite score.
The important detail, and the one most merchants miss, is that the score is comparative. Shopify benchmarks your store against similar Shopify stores, so a score of 50 does not mean your store is slow. It means you are performing around the median for stores like yours.
Most merchants read it as an absolute measure, assume anything under 70 is unacceptable, and start making decisions that prioritise the number over their actual business performance.
Much of what determines your Lighthouse score is decided by other people: Shopify's own infrastructure, your theme's underlying architecture, the third-party app scripts loading on every page, and the simulated network and CPU conditions Lighthouse applies during testing. You can optimise at the edges. You cannot rewrite the parts that matter most.
Run Lighthouse against the largest sites on the internet and you will find a lot of mediocre scores, including on properties owned by Google itself. This is worth doing yourself rather than taking on trust, because it takes two minutes and it recalibrates expectations permanently. Sites with heavy media, personalisation and dynamic content score badly on a metric that rewards simplicity, and a Shopify store with apps, reviews and conversion tools is in exactly that category.
We have audited stores turning over seven figures a year with speed scores below 30, and stores scoring above 80 that struggle to convert. The score measures one dimension of performance in isolation. Commercial performance depends on speed, design, trust signals, product, pricing and the whole customer journey interacting, which no single number captures.
This distinction is the most important idea in the whole page speed conversation and the one merchants are least often told about.
Lab data is generated by simulating a page load on a throttled connection in a controlled environment. It tests one scenario under artificial conditions, and results can vary noticeably between runs taken seconds apart, because the simulation cannot replicate the range of real user environments.
Field data, also called Real User Metrics, is collected from actual Chrome users visiting your site. It measures how your pages perform on real devices, real networks and real locations. Google collects this through the Chrome User Experience Report and uses it for ranking.
Google has been explicit about the difference. Core Web Vitals field data is a ranking signal. Lighthouse lab scores are not. Which means your Shopify speed score could be 25 while your Core Web Vitals pass comfortably, or 90 while they fail. The two measure different things by different methods, and only one of them is what Google ranks on.
Three metrics, all taken from real user field data.
| Metric | What It Measures | Google's "Good" Threshold |
|---|---|---|
| Largest Contentful Paint | How long the largest visible element takes to load, usually a hero image or heading | Under 2.5 seconds |
| Interaction to Next Paint | How quickly the page responds to clicks, taps and keyboard input | Under 200 milliseconds |
| Cumulative Layout Shift | Visual stability, meaning whether elements move while the page loads | Under 0.1 |
Interaction to Next Paint replaced First Input Delay as the responsiveness metric in 2024, so any advice still referring to FID predates that change and is worth treating with caution.
Check your field data in Google Search Console under Experience, then Core Web Vitals, or test a specific URL at PageSpeed Insights. PageSpeed Insights shows both the Lighthouse lab score and the real user field data, clearly separated. The field data section is the one that matters. For the wider technical picture, see our Shopify SEO guide.
Conversion rate. The metric that matters most. If it is strong and stable, your store is performing regardless of the score. If you add a reviews app, lose ten speed points and gain conversion, that is a win however the number looks.
Core Web Vitals field data. Check Search Console regularly. If they pass, Google is not penalising your store on speed. If one fails, fix that specific metric rather than chasing a general score.
Landing page load time. Pages taking paid traffic should load in under three seconds, because cold traffic from ads is far less patient than organic visitors. Test the specific URLs rather than relying on a site-wide figure.
Engagement metrics. Bounce rate, session duration and pages per session indicate whether real users are hitting friction. Performance may be the cause, but so might design, product relevance, pricing or a missing trust signal, so treat them as a prompt to investigate rather than a diagnosis.
Theme choice is the single largest lever available to most merchants, and the evidence for it is unusually clear. Across the stores we have upgraded to Online Store 2.0, mobile PageSpeed scores improved by an average of 23 points. That is a bigger swing than every image and script optimisation in this list combined, and it is one decision rather than an ongoing programme of work.
It is also a more common problem than merchants expect. Of the 265 Shopify stores we have audited, 196 were still running legacy themes predating Online Store 2.0. If you are worrying about your speed score while running a legacy theme, you are optimising the wrong layer.
Time and money spent trying to move these is wasted. Spend it on the previous section instead.
The most common mistake we see is merchants removing useful apps to lift their speed score. This is almost always counterproductive.
A reviews app that adds 0.3 seconds and lifts conversion by 10% is a clear net positive. A chat widget that adds 0.2 seconds and reduces pre-purchase hesitation is worth keeping. A loyalty app with a small performance cost that raises repeat purchase rate is generating revenue the speed score has no way of seeing.
The question is not whether an app slows your store down. Everything slows your store down. The question is whether the value it delivers outweighs what it costs in performance. For most conversion-enhancing apps the answer is yes, because the score does not correlate with revenue and conversion rate does. See our guide on how to increase Shopify conversions for what belongs on a product page.
| Tool | What It Measures | Best For |
|---|---|---|
| Google Search Console | Core Web Vitals field data across the whole site | The definitive source for how Google evaluates your speed |
| PageSpeed Insights | Field data and lab data for a specific URL, shown separately | Testing individual pages and seeing both results side by side |
| GTmetrix | Detailed waterfall analysis of page loading | Finding the specific resource that is holding a page up |
| WebPageTest | Real browser testing from multiple locations and devices | Checking how the store loads for customers in other regions |
| Shopify speed report | Lighthouse lab score benchmarked against similar stores | A rough comparative benchmark, nothing more |
Page speed matters. We are not arguing otherwise. A store taking eight seconds to load will lose customers and will rank badly. The argument is that Shopify's speed score is a poor proxy for actual performance, and that optimising for it at the expense of conversion features is one of the more expensive strategic mistakes a merchant can make.
When we audit a store we never recommend removing an app purely because of its effect on the score. We look at what the app does for conversion rate, customer experience and revenue, and recommend removal only when it is not earning its cost.
The pattern worth noticing is where the real gains sit. Of the 265 stores we have audited, 196 were on legacy themes, and the ones we moved to Online Store 2.0 gained an average of 23 points on mobile PageSpeed. Almost nobody arrives worrying about their theme. They arrive worrying about their score, which is the symptom rather than the cause.
If you are unsure whether your store's performance is genuinely costing you conversions or you are simply chasing a misleading number, our free SEO audit includes a Core Web Vitals assessment alongside a full technical and on-page review. We also offer a 3-month guarantee on development projects.
Does the Shopify speed score affect SEO?
No. Google has confirmed that Lighthouse lab scores do not directly affect search rankings. Google uses Core Web Vitals field data collected from real Chrome users as a ranking signal, not lab-based Lighthouse scores. Your Shopify speed score can be low while your Core Web Vitals pass, and your SEO is unaffected.
What is a good Shopify speed score?
The score is comparative rather than absolute, so a score of 50 means you are performing around the median for similar stores. Stores running apps and conversion tools generally score lower than a stripped-back store, which is expected rather than a fault. Your Core Web Vitals field data and your conversion rate tell you far more than the score does.
Should I remove apps to improve my speed score?
Only if an app is not earning its keep. An app that adds 0.3 seconds and increases conversion by 10% is a net positive. Judge each app by business impact rather than by its effect on a lab score. Do remove apps you are no longer using, since they often leave residual scripts running on every page.
What are Core Web Vitals and how do I check them?
Three metrics Google uses as ranking signals: Largest Contentful Paint, Interaction to Next Paint and Cumulative Layout Shift. Check them in Google Search Console under Experience, then Core Web Vitals, or test a specific URL at PageSpeed Insights and read the field data section rather than the Lighthouse lab score.
How fast should my Shopify store load?
Google treats a Largest Contentful Paint under 2.5 seconds as good. For landing pages taking paid traffic, aim for a total load under three seconds. If your Core Web Vitals pass and your conversion rate is healthy, your store is fast enough whatever the score says.
Does switching to a faster Shopify theme improve speed?
Yes, and it is the largest improvement available to most merchants. Across the stores we have moved to Online Store 2.0, mobile PageSpeed scores improved by an average of 23 points. If you are on a heavy legacy theme, the theme is almost certainly the constraint rather than your images or your apps.
Why does my speed score change every time I run the test?
Because Lighthouse is a simulation, and results vary between runs even seconds apart. The throttled network and CPU conditions are approximations, not fixed measurements. A score moving a few points between tests is normal and means nothing. This variability is another reason to prefer field data, which averages real user experience over time rather than capturing one artificial moment.
Improving your store's speed is worth doing. Chasing a perfect speed score is not. The score comes from a lab simulation, is driven substantially by factors outside your control, and does not correlate with the things that actually move your business.
Focus on what does. Make sure your Core Web Vitals field data passes. Get your landing pages loading in under three seconds. Check whether you are running a legacy theme, because that is where the largest gain usually sits. And make sure every app in your stack is earning its performance cost in measurable business value.
If your speed score is 30 but your Core Web Vitals pass and your conversion rate is strong, your store is performing well. Do not let a misleading number persuade you otherwise.