Speed conversations on Shopify tend to jump straight to tactics — compress this image, defer that script — without first establishing where the platform's stores actually stand today. This report answers that prior question with data: what share of Shopify stores currently pass Core Web Vitals, how mobile and desktop performance differ, and what measurable role themes and apps play in the outcome.
The short version: Core Web Vitals compliance across Shopify stores is inconsistent and, on mobile specifically, more often failing than passing. Third-party studies commonly report that only 33% to 48% of Shopify stores pass all three Core Web Vitals on mobile — a wide range that itself is informative, because it reflects real methodological disagreement about how to measure "speed" rather than a single clean number merchants can chase.
This report is the data companion to CROVEX's Ultimate Shopify Speed Optimization Guide, which covers the technical how-to. Here, the focus is strictly on benchmarks.
Speed also is not purely a technical concern anymore — it is a search visibility and paid media efficiency concern. Core Web Vitals are a confirmed ranking input for Google Search, and slow-loading landing pages typically carry a higher cost-per-acquisition in paid channels because ad platforms increasingly factor post-click experience into quality scoring. A merchant evaluating a speed project purely on "does the page feel fast" is underpricing the investment; the more complete framing includes organic visibility, paid efficiency, and conversion rate simultaneously.
What percentage of Shopify stores pass all Core Web Vitals?
Third-party studies commonly report a range of roughly 33% to 48% of Shopify stores passing all three Core Web Vitals on mobile, with the wide range driven by methodology differences — field data versus lab data, which pages are sampled, and device/network throttling assumptions.
Methodology and How to Read These Benchmarks
Core Web Vitals sound like a single, objective measurement, but in practice there are at least two very different ways to measure them, and studies rarely specify which one they used clearly enough for merchants to compare results.
Field data (like Google's Chrome UX Report, which powers Search Console's Core Web Vitals report) reflects real user sessions across real devices and networks, aggregated over a rolling 28-day window. Lab data (like a single Lighthouse or PageSpeed Insights run) reflects one simulated visit under fixed, throttled conditions. Field data is more representative of actual visitor experience; lab data is more reproducible and useful for debugging a specific page.
Beyond field-vs-lab, studies also differ in which pages they sample (homepage-only crawls tend to look faster than full-site crawls that include image-heavy collection and product pages), which device/network profile they throttle to, and how they define the "store universe" being measured. Each of these choices can move a reported pass rate by ten percentage points or more.
How to verify your own store
Measure your own store using both PageSpeed Insights (lab, on-demand) and Search Console's Core Web Vitals report (field, real users) rather than relying on any single third-party study as ground truth for your specific storefront.
Key Findings
- Google's "Good" Core Web Vitals thresholds are LCP ≤2.5s, INP ≤200ms, and CLS ≤0.1, measured at the 75th percentile of page loads.
- Third-party studies commonly report that 33%–48% of Shopify stores pass all three Core Web Vitals on mobile.
- Mobile median LCP is commonly reported in the 2.3–3.0 second range, often at or above the 2.5-second "Good" threshold.
- INP is disproportionately affected by app count; stores running 10+ installed apps are far more likely to fail the INP threshold.
- Images remain the largest single contributor to total page weight on ecommerce pages generally (HTTP Archive / Web Almanac).
- Shopify's own enterprise materials position the platform as faster than alternatives and cite high internal "fast storefront" figures.
Core Web Vitals: The Thresholds That Define "Fast"
Before benchmarking Shopify stores against a standard, it's worth being precise about what that standard actually is. Google defines three Core Web Vitals, each targeting a different dimension of user experience, and each is assessed independently — a store can pass two of three and still receive an overall "Needs Improvement" or "Poor" classification in Search Console because the assessment requires all three metrics to clear the "Good" threshold at the 75th percentile simultaneously.
| Metric | What it measures | Good | Needs Improvement | Poor |
|---|---|---|---|---|
| LCP (Largest Contentful Paint) | Loading speed | ≤2.5s | 2.5s – 4.0s | >4.0s |
| INP (Interaction to Next Paint) | Responsiveness | ≤200ms | 200ms – 500ms | >500ms |
| CLS (Cumulative Layout Shift) | Visual stability | ≤0.1 | 0.1 – 0.25 | >0.25 |
INP replaced First Input Delay (FID) as the official responsiveness metric, and it is the metric most sensitive to third-party app scripts, because it measures the full time from interaction to visual response — not just the delay before a browser starts processing an event.
Each metric maps to a distinct commercial risk on an ecommerce storefront. A slow LCP delays the moment a shopper actually sees your hero product image or collection grid. A high INP shows up as a sluggish "add to cart" button or a laggy variant swatch. A high CLS creates the experience of a page still settling around the user, which frequently causes mis-taps and a general sense that the site feels unfinished.
Benchmark ranges by page type
Not every template on a Shopify store carries the same performance profile. Directionally, based on aggregated public Core Web Vitals studies and typical template complexity:
| Page type | Typical LCP risk | Primary driver |
|---|---|---|
| Homepage | Moderate | Hero banners, carousels, and above-the-fold video embeds |
| Collection page | Moderate–High | Grid of product images, often with filter/sort JavaScript |
| Product detail page (PDP) | High | Large hero product image plus reviews, upsell, and personalization app scripts |
| Cart | Low–Moderate | Fewer visual assets, but frequently loaded with upsell and shipping-calculator scripts |
| Checkout | Lower (Shopify-managed) | Platform-hosted and generally more consistent, though Plus checkout extensibility can reintroduce risk |
PDP risk concentration
Product detail pages consistently emerge as the highest-risk template in public studies: they combine the largest hero image on the site with the highest concentration of third-party apps, making them the template most likely to fail both LCP and INP simultaneously.
Shopify Core Web Vitals Pass Rates: The 33–48% Range
This is the single most cited — and most misunderstood — statistic in Shopify performance discussions. Depending on methodology, third-party studies report that somewhere between 33% and 48% of Shopify storefronts pass all three Core Web Vitals simultaneously on mobile.
| Pass-rate estimate | Likely methodology driver |
|---|---|
| ~33% (lower end) | Full-site crawls including image-heavy PDP/collection pages, stricter mobile throttling |
| ~40–45% (mid-range) | Mixed page samples, moderate throttling assumptions |
| ~48% (upper end) | Homepage-weighted samples, field data from higher-traffic (often better-optimized) stores |
The actionable takeaway
More than half of Shopify stores, under almost any methodology, fail at least one Core Web Vital on mobile — meaning a majority of merchants have a genuine, measurable speed gap, not a marginal one. If your own report shows a failing metric, you are in the majority, not an outlier.
Mobile vs Desktop: Where the Gap Concentrates
Mobile and desktop Core Web Vitals rarely look the same for a given store, and the direction of the gap is consistent: mobile is harder to pass.
| Metric | Mobile (typical) | Desktop (typical) |
|---|---|---|
| Median LCP | ~2.3s – 3.0s | Typically faster, often within the "Good" range |
| INP risk | Higher — touch interactions plus JS-heavy stacks compound delay | Lower — more processing headroom |
| CLS risk | Higher — smaller viewport increases visible impact of late-loading elements | Lower — more layout headroom |
The mobile gap compounds with the conversion-rate gap documented in CROVEX's State of Shopify Conversion Optimization Report: mobile traffic is both the majority of sessions for most stores and the segment most likely to encounter a slow, unstable page.
The App and Theme Performance Cost
App count and INP
Every installed Shopify app that touches the storefront typically injects at least one script tag into the theme. Individually, many of these scripts appear lightweight in isolation. The problem is cumulative: parse time, execution time, and main-thread contention all add up, and INP — measuring the full round-trip from interaction to visual response — is the metric most sensitive to this accumulation.
Public performance analyses consistently find that stores running 10 or more installed apps are substantially more likely to fail INP thresholds than stores running a lean stack, even when no single app is individually "slow" by its own vendor's claims.
This is rarely a single-app problem, which is why single-app performance testing understates the real risk. The pattern is cumulative and often non-linear: two apps that each add 50ms of main-thread blocking time do not simply add up to 100ms of delay — they can compound through shared resource contention, competing for the same rendering thread during the critical page-load window. A store that passed comfortably at five installed apps can cross the INP failure threshold after adding just two or three more, even if each individual addition seemed reasonable in isolation.
Theme impact
Theme choice sets the performance ceiling before a single app is installed. Heavily feature-rich themes with built-in sliders, multiple font families, and animation libraries start from a higher baseline JavaScript and CSS weight than minimal, performance-first themes — meaning two stores with an identical app stack can still show meaningfully different Core Web Vitals purely based on theme foundation.
Image weight
HTTP Archive's Web Almanac and related public page-composition data consistently show that images are the largest single contributor to total page weight on ecommerce pages, ahead of JavaScript, fonts, and CSS combined in many samples. For Shopify stores specifically, this means product and collection imagery — often the least technical part of a merchant's workflow — is frequently the highest-leverage lever for LCP improvement, since LCP is very often the product image itself on PDP and collection pages.
Speed Priorities by Revenue Tier
A $10K/mo store and a $200K/mo store both benefit from passing Core Web Vitals, but the realistic path to get there — and the tools worth paying for along the way — differ significantly based on typical app-stack size and available engineering support.
| Revenue tier | Typical app count | Realistic speed priority | Tooling budget guidance |
|---|---|---|---|
| $10K/mo | 3-8 apps | Image compression and a lean theme; avoid adding apps that duplicate existing functionality | Free tools (PageSpeed Insights, Search Console) are usually sufficient; a paid image app is often the highest-ROI purchase |
| $50K/mo | 8-15 apps | A quarterly app audit against the 10-app INP threshold, paired with ongoing image and script optimization | A lightweight RUM or synthetic monitoring tool becomes worth the cost once several pages depend on multiple apps |
| $200K/mo | 12-25+ apps | A standing performance budget per template (especially PDP), with dedicated engineering time for script governance | Dedicated performance monitoring and a documented performance budget process typically pay for themselves at this scale |
App count creep applies at every tier
The 10-app INP risk threshold documented earlier in this report isn't exclusive to larger stores — a $10K/mo store can just as easily accumulate 12 apps over time as a $200K/mo store. Revenue tier changes the tooling budget available to fix it, not whether the risk applies.
What This Means for Shopify Merchants
1. A failing Core Web Vitals score is common, not exceptional
With well under half of stores passing all three metrics on mobile under most methodologies, a failing report is a normal starting point, not a sign of unusual mismanagement. Treat it as a prioritized backlog, not an emergency.
2. Mobile should be the default test environment, not an afterthought
Because mobile concentrates both more session volume and more Core Web Vitals risk, every speed audit should start on mobile field data (Search Console) rather than a desktop lab test that likely overstates real-world performance.
3. INP is a stack-management problem as much as a code problem
The fastest way to improve INP for many stores is not writing better JavaScript — it is auditing which apps are installed, whether each is still earning its performance cost, and removing or replacing the ones that are not (see CROVEX's Shopify Apps Industry Report for a full governance framework).
4. Image optimization remains underrated relative to its impact
Because LCP is frequently the hero product image, and because images are the largest page-weight contributor generally, disciplined image compression and modern format adoption often produces a larger LCP improvement than more complex JavaScript optimization work — for a fraction of the engineering effort.
5. Speed and conversion should be tracked together, not separately
Since mobile carries both the conversion gap and the speed gap, a mobile-first performance project is very likely to show up in conversion data as well as in Core Web Vitals data — making it easier to build the business case for prioritizing it.
6. Product detail pages deserve a dedicated performance budget
Because PDPs concentrate both the largest image asset and the most third-party scripts, treating them as a separate performance category — with their own app-count limit and image-size standard — is more effective than applying a single site-wide speed rule that PDPs will predictably violate first.
Actionable Recommendations
- Pull your real Core Web Vitals data from Search Console first, not just a single PageSpeed Insights run, so you are working from field data representing actual visitors.
- Audit your installed apps against the 10-app threshold. If you are running 10+ storefront-facing apps, prioritize an app audit before any code-level performance work.
- Compress and modernize product imagery (WebP/AVIF, responsive sizing, lazy-loading below the fold) as a first-pass LCP fix.
- Test mobile and desktop separately and report them separately internally — a "passing" desktop score can mask a failing mobile score.
- Re-benchmark after every theme change or major app install, since either can silently shift LCP, INP, or CLS independently of other work.
- Treat CLS fixes as trust-building, not just technical hygiene — reserve space for images, ads, and dynamically injected banners.
- Pair every speed initiative with a conversion-rate check using CROVEX's CRO benchmark report, so performance work is justified in revenue terms.
- Use the companion how-to guide for the specific technical sequence once you have identified priority gaps from this benchmark data.
A Speed Measurement Playbook
Speed work is unusually easy to measure badly — a single lab test run under ideal conditions can look great while real visitors on real networks experience something much worse. A disciplined measurement approach avoids both false confidence and false alarm.
| Signal source | What it tells you | Recommended cadence |
|---|---|---|
| Search Console Core Web Vitals report | Field data from real visitors, aggregated over a rolling 28-day window | Review monthly; this is your primary source of truth |
| PageSpeed Insights / Lighthouse | Lab data for a single simulated visit; useful for debugging a specific page | Run immediately after any theme or app change touching a key template |
| Real User Monitoring (RUM) tool | Continuous field data, often broken down by page template and device | Set up once traffic and stack complexity justify the cost (typically $50K/mo+) |
| App-level performance testing | Isolated script weight and execution time for a specific app before installing it | Run before adding any new storefront-facing app, not just after problems appear |
- Every speed claim in an internal report cites which data source (field or lab) it came from.
- Mobile and desktop are reported and reviewed separately, never blended into a single number.
- A new app or theme change gets a before/after Lighthouse comparison before going live on 100% of traffic.
- Core Web Vitals trend is reviewed on the same monthly cadence as conversion rate, not as a separate, less frequent workstream.
Don't chase a perfect Lighthouse score
A 100/100 Lighthouse score on a single lab run doesn't guarantee a passing field score for real visitors on slower networks and older devices. Treat Lighthouse as a debugging tool for specific issues, and Search Console's field data as the actual pass/fail signal that matters for Google Search and real user experience.
A 90-Day Speed Improvement Roadmap
| Days | Focus | Key actions |
|---|---|---|
| 1-7 | Baseline and diagnosis | Pull Search Console field data for mobile and desktop separately; identify which of LCP, INP, or CLS is failing and on which templates |
| 8-21 | App and theme audit | Inventory installed apps against the 10-app INP risk threshold; flag candidates for removal or replacement |
| 15-35 | Image and asset optimization | Compress and modernize product/collection imagery (WebP/AVIF, responsive sizing); this is usually the fastest LCP win available |
| 30-55 | Script governance | Remove or replace flagged apps; re-test INP after each change to isolate individual impact |
| 50-75 | PDP-specific performance budget | Set a dedicated image-size and app-count standard for product detail pages specifically, given their elevated risk profile |
| 75-90 | Re-benchmark and lock in monitoring | Confirm field data improvement in Search Console; establish the ongoing monthly review cadence from the measurement playbook |
Expect gradual field-data movement
Because Search Console's Core Web Vitals report uses a rolling 28-day window, improvements made in week 6 won't fully reflect in the field data until roughly a month later. Don't judge a fix as ineffective before the reporting window has had time to catch up.
As with the other 90-day plans in CROVEX's benchmark reports, treat this as a repeatable quarterly cycle rather than a one-time project. Themes get updated, apps get added for seasonal campaigns and never removed, and product imagery grows heavier as a catalog expands — all of which can quietly erode a passing Core Web Vitals score months after the initial fix.
Downloadable Infographic Suggestions
- Shopify Core Web Vitals Cheat Sheet (downloadable PDF, portrait) — thresholds, pass-rate range, and a 5-item quick-audit checklist.
- App Performance Cost Calculator visual (landscape infographic) — how common app categories add to script weight.
- Before/After LCP Improvement Social Carousel (4-slide square) — problem, diagnosis, fix category, expected impact range.
Frequently Asked Questions
What are Google's Core Web Vitals thresholds in 2026?
"Good" thresholds are LCP ≤2.5s, INP ≤200ms, and CLS ≤0.1, measured at the 75th percentile of page views.
What percentage of Shopify stores pass all Core Web Vitals?
Third-party studies commonly report roughly 33% to 48% passing all three on mobile, with the range driven by methodology differences in how pages are sampled and measured.
Why do more installed apps hurt Shopify speed?
Most apps inject JavaScript that adds parse, execution, and main-thread time, directly affecting INP. Stores with 10+ apps are far more likely to fail INP than lean-stack stores.
Is mobile or desktop Shopify performance worse?
Mobile is typically the harder benchmark, combining less powerful hardware with slower network conditions. Median mobile LCP commonly falls in the 2.3–3.0 second range.
What is the biggest contributor to Shopify page weight?
Public HTTP Archive data consistently shows images as the largest single contributor to ecommerce page weight, making image optimization a high-leverage speed fix.
How is this report different from CROVEX's speed optimization guide?
This report covers benchmarks — where stores stand and why. The Ultimate Shopify Speed Optimization Guide 2026 covers the step-by-step technical implementation.
Does Shopify itself claim to be fast?
Shopify's enterprise materials cite platform-level speed positioning and high internal "fast storefront" figures. These are platform claims, useful as context, but not a substitute for independent Core Web Vitals data on your specific store.
Which page template usually has the worst Core Web Vitals?
Product detail pages typically carry the highest risk, since they combine the largest hero image on the site with the highest concentration of third-party app scripts, making them the template most likely to fail both LCP and INP simultaneously.
How often should I re-check my Core Web Vitals?
At minimum monthly, using Search Console field data as the primary signal, and immediately after any theme change or new app install using a lab tool like PageSpeed Insights for a faster before/after comparison. Because field data uses a rolling 28-day window, allow roughly a month for a fix to fully reflect in your reported score.
Is a paid performance monitoring tool worth it for a smaller store?
For most stores under roughly $50K/month, free tools (Search Console and PageSpeed Insights) are usually sufficient. Paid real-user-monitoring tools become more valuable once a store has enough page templates and traffic volume to justify continuous, template-level tracking rather than periodic manual checks.
Key takeaways
- Only an estimated 33%–48% of Shopify stores pass all Core Web Vitals on mobile — a failing score is common, not exceptional.
- Mobile concentrates both more traffic and more speed risk for most stores, making it the priority test environment.
- INP failures correlate strongly with app count; auditing your app stack is often the fastest path to improvement.
- Images are the largest page-weight contributor on ecommerce pages, making image optimization a high-leverage, low-risk fix.
- Product detail pages carry the highest combined LCP and INP risk and deserve a dedicated performance budget.
Want to know exactly what is slowing your store down?
CROVEX runs technical speed audits that measure your real Core Web Vitals, isolate which apps and theme elements are costing you the most, and prioritize fixes by conversion impact.
Book Free Shopify AuditFrequently Asked Questions
Google's "Good" thresholds are Largest Contentful Paint (LCP) at 2.5 seconds or less, Interaction to Next Paint (INP) at 200 milliseconds or less, and Cumulative Layout Shift (CLS) at 0.1 or less. Passing all three at the 75th percentile of page views is required to earn a "Good" Core Web Vitals assessment for a URL or origin.
Third-party studies commonly report a range of roughly 33% to 48% of Shopify stores passing all three Core Web Vitals on mobile, with the wide range driven by methodology differences — field data versus lab data, which pages are sampled, and device/network throttling assumptions.
Most Shopify apps inject JavaScript into the storefront. Each script adds parse, execution, and often main-thread blocking time, which directly affects Interaction to Next Paint (INP). Stores running many apps simultaneously are more likely to fail INP thresholds than lean-stack stores, even if individual apps seem lightweight.
Mobile is typically the harder benchmark to pass, since it combines less powerful hardware with slower network conditions in most testing methodologies. Median mobile LCP is commonly reported in the 2.3–3.0 second range depending on the study, often close to or above the 2.5 second "Good" threshold.
Public web performance data (HTTP Archive / Web Almanac) consistently shows images as the largest single contributor to total page weight on ecommerce pages, which is why image compression, modern formats, and responsive sizing remain some of the highest-leverage speed fixes.
This report focuses on benchmarks — where Shopify stores stand today on Core Web Vitals and why. For the step-by-step technical implementation to actually fix those issues, see the companion Ultimate Shopify Speed Optimization Guide 2026.
Shopify's enterprise materials have positioned the platform as faster than alternatives and cited high "fast storefront" rates internally. These are platform-level positioning claims from Shopify, not independent benchmarks, so they're worth weighing alongside third-party Core Web Vitals studies rather than as a substitute for them.
At minimum quarterly, and immediately after any theme change, major app install, or catalog/image overhaul, since each of these can shift LCP, INP, or CLS independently of your other optimization work.