Shopify's own theme performance table still shows median pass rates in the 80–97% range for LCP, INP, CLS, and “all Core Web Vitals.” Open a multi-page Lighthouse sample on a real storefront and the story often flips: mobile Performance scores cluster near 50, lab LCP averages stretch well past Google's 2.5 s “good” line, and unused JavaScript shows up on almost every domain. Both views can be true. Theme-level CrUX aggregates describe shops that look like a given theme under field conditions. Portfolio monitoring needs URL-level and multi-page evidence, because apps, media, and collection templates decide what shoppers feel.
What follows separates those clocks, publishes a reproducible sample from Shopify leads we analyse in Apogee Watcher, and points at the tuning work that actually moves scores. For store-level fixes after you read the numbers, pair this with Shopify Speed Optimization: Core Web Vitals Guide for E-Commerce.
For Core Web Vitals, the strongest public field source remains the Chrome UX Report (CrUX). Google's methodology is clear about inclusion: pages and origins must be publicly discoverable and popular enough, data comes from eligible Chrome users, and thresholds are read at the 75th percentile over a rolling window. That is why Search Console and the field section of PageSpeed Insights matter for ranking and real-user claims, while a single Lighthouse run remains a diagnostic tool.
Google's published thresholds are unchanged for the three metrics:
| Metric | Good (p75) | Needs improvement | Poor |
|---|
| LCP | ≤ 2.5 s | 2.5 s – 4.0 s | > 4.0 s |
| INP | ≤ 200 ms | 200 ms – 500 ms | > 500 ms |
| CLS | ≤ 0.1 | 0.1 – 0.25 | > 0.25 |
An origin or URL group passes Core Web Vitals when all three sit in the good bucket at p75. A Lighthouse Performance score is a different artefact: it blends lab timings under a throttled environment and is useful for regression detection, not as a substitute for CrUX pass/fail. If you need a refresher on the three metrics themselves, start with What Are Core Web Vitals? A Practical Guide for 2026.
A useful Shopify benchmark therefore states four things up front: which clock (CrUX field versus Lighthouse lab), which URLs (homepage only versus collections, PDPs, cart), how scores are aggregated (single URL versus median or mean across pages), and the collection window. Platform marketing often quotes theme or “average store” figures without that scaffolding. Agencies managing twenty Shopify clients need the scaffolding more than another green screenshot.
Sources:
Shopify theme-level CrUX context from public data
Shopify's Performance team publishes aggregated Core Web Vitals performance by theme so merchants can compare popular themes under real Chrome traffic rather than a single lab screenshot. As of the 18 Aug 2026 update on their theme table, the median theme-level pass rates across listed themes were:
| Metric | Median % of shops passing (theme table) |
|---|
| Largest Contentful Paint (LCP) | 90.3% |
| Cumulative Layout Shift (CLS) | 93.4% |
| Interaction to Next Paint (INP) | 97.1% |
| Views passing all CWVs | 82.0% |
Those figures combine devices, cover recent theme versions with enough eligible shops, and still describe theme-level cohorts, not “every live Shopify store with every app enabled.” The same table shows wide floors and ceilings: all-CWV pass rates range from roughly 37% to 95% depending on the theme row, which is the first warning that platform averages do not replace store-specific monitoring.
Third-party research often cites a lower all-CWV pass rate for Shopify as a whole (for example ~45% in vendor CrUX summaries). The gap between ~45% store-wide claims and ~82% median theme-level “all CWVs” is not a mystery if samples, devices, and theme filters differ, so treat both as orientation and do not merge them into one scorecard column.
Source: Aggregated Core Web Vitals performance by Shopify Theme
Multi-page lab sample from Watcher's Shopify users
We keep Shopify-tagged storefronts in Watcher and run multi-page PageSpeed Insights analyses that store both Lighthouse lab metrics and CrUX field payloads when Google returns them. For this snapshot we took the latest domain report per Shopify-tagged lead with an aggregated payload (n = 64 stores; reports generated between April and September 2026). Each report averages Lighthouse metrics across the URLs selected for that domain (median 17 analysed pages per store; 1,070 page runs in total). Values below are store-level averages of lab runs, not single-URL CrUX p75s.
Mobile and desktop Lighthouse Performance
| Slice | Mobile Performance (avg) | Desktop Performance (avg) |
|---|
| Minimum | 26 | 35 |
| 25th percentile | 37 | 57 |
| Median | 51 | 69 |
| 75th percentile | 62 | 83 |
| Maximum | 86 | 99 |
| Mean | 51 | 69 |
Half of the sample sits at or below a mobile Performance average of about 51. Only 32 of 64 stores clear a mobile average of 50, and 9 of 64 clear 70; none of the 64 store averages reached 90 on mobile. Desktop is kinder in the same runs (median about 69), which matches what agencies see when a client forwards a desktop-only screenshot and assumes the site is fine.
Mobile lab Core Web Vitals timings (store averages)
| Metric | Median | 75th percentile | Notes in this sample |
|---|
| LCP (s) | 9.8 | 14.5 | 0 / 64 store averages ≤ 2.5 s |
| INP (s) | 0.30 | 0.41 | 15 / 64 store averages ≤ 0.20 s |
| CLS | 0.02 | 0.07 | 55 / 64 store averages ≤ 0.1 |
CLS is the bright spot: layout stability is often already in a good lab band even when LCP is not. LCP is the structural problem. Multi-page mobile averages in the 8–15 s range do not mean every URL fails CrUX at that severity, but they do mean Lighthouse is consistently flagging heavy LCP candidates across templates. That is the signal agencies should take into a remediation backlog before arguing about a two-point Performance score change.
CrUX origin categories when field data exists
Not every lead has origin-level CrUX on the report. Where mobile origin overall category was present (n = 27), we saw 14 FAST, 8 AVERAGE, and 5 SLOW. Origin LCP was FAST on 22 of those stores, INP FAST on 22, and CLS FAST on 23. Field data is often healthier than multi-page lab averages on the same domains, especially for INP and CLS, because lab throttling and averaging across many templates punish media-heavy PDPs that may still pass origin-level CrUX when popular URLs are lighter.
Recurring Lighthouse opportunities
Across the 64 latest reports, the most common mobile opportunities were:
| Opportunity | Stores where it appeared |
|---|
| Reduce unused JavaScript | 61 / 64 |
| Reduce unused CSS | 52 / 64 |
| Avoid multiple page redirects | 26 / 64 |
| Minify JavaScript | 17 / 64 |
| Minify CSS | 10 / 64 |
Unused JavaScript is effectively the default Shopify finding in this sample. Theme code, app scripts, analytics, and personalisation layers compete for the same main thread that INP and Total Blocking Time care about. For ecommerce metric priorities beyond the three Core Web Vitals, see Performance Monitoring for E-Commerce: What Metrics Matter Most.
Two shops on the same theme can land in different buckets for reasons that never appear in a theme marketing page:
App footprint. Review widgets, loyalty, chat, upsell drawers, and A/B tools add script weight on collection and PDP templates.
Media strategy. Hero video, large product galleries, and unprioritised LCP images dominate mobile LCP in lab runs.
Template mix. A clean homepage can hide a slow cart drawer or a script-heavy collection grid when you only test one URL.
Headless versus online store. Hydrogen or other custom storefronts change what source-level theme IDs reveal and how caching works.
Traffic shape and geography. CrUX inclusion and p75 values move with real visitor mix; lab runs do not.
Platform-level medians help set expectations in a roadmap review. They do not replace scheduled checks on the URLs that drive revenue. That is why we treat theme tables as context and multi-page samples as the operating view.
We also tracked a public high-visibility cohort tagged shopify-benchmark in Watcher (Allbirds, SKIMS, Kylie Cosmetics, Fashion Nova, Brooklinen, ColourPop, Steve Madden, Glossier, Netflix Shop, Mattel Creations). Six of those domains had multi-page Watcher lab reports in the lead pull above. On 7 Sep 2026 we also pulled mobile origin Chrome UX Report field data for the cohort via PageSpeed Insights (originLoadingExperience), so lab and field sit in separate tables rather than one mixed scorecard.
Lab multi-page averages (Watcher reports)
| Brand | Domain | Mobile Performance (avg) | Desktop Performance (avg) | Mobile LCP avg (s) | Mobile CLS avg |
|---|
| Fashion Nova | fashionnova.com | 37 | 60 | 8.6 | 0.05 |
| Allbirds | allbirds.com | 34 | 53 | 15.6 | 0.02 |
| SKIMS | skims.com | 33 | 52 | 9.1 | 0.04 |
| Brooklinen | brooklinen.com | 29 | 45 | 31.1 | 0.15 |
| Kylie Cosmetics | kyliecosmetics.com | 26 | 36 | 26.8 | 0.22 |
| Netflix Shop | netflix.shop | 26 | 41 | 15.7 | 0.15 |
These lab averages punish product-heavy template sets under throttling. They are not claims that every shopper sees a Performance score in the mid-20s.
Mobile CrUX at origin (PageSpeed Insights, Sep 2026)
Origin metrics are Chrome UX Report p75 values for phone traffic across the origin. CLS is shown on the usual 0–1 scale (PSI returns hundredths). “Passes all CWVs” means LCP, INP, and CLS are all in the good (FAST) bucket at p75.
| Brand | Domain | Origin overall | LCP p75 | INP p75 | CLS p75 | Passes all CWVs? |
|---|
| Allbirds | allbirds.com | Good | 1.49 s (Good) | 176 ms (Good) | 0.00 (Good) | Yes |
| ColourPop | colourpop.com | Needs improvement | 1.66 s (Good) | 212 ms (Needs improvement) | 0.15 (Needs improvement) | No |
| Kylie Cosmetics | kyliecosmetics.com | Needs improvement | 2.02 s (Good) | 319 ms (Needs improvement) | 0.04 (Good) | No |
| Netflix Shop | netflix.shop | Needs improvement | 2.06 s (Good) | 221 ms (Needs improvement) | 0.13 (Needs improvement) | No |
| Steve Madden | stevemadden.com | Needs improvement | 2.09 s (Good) | 245 ms (Needs improvement) | 0.10 (Good) | No |
| Mattel Creations | creations.mattel.com | Needs improvement | 2.10 s (Good) | 314 ms (Needs improvement) | 0.02 (Good) | No |
| Glossier | glossier.com | Needs improvement | 2.17 s (Good) | 239 ms (Needs improvement) | 0.09 (Good) | No |
| Fashion Nova | fashionnova.com | Needs improvement | 2.52 s (Needs improvement) | 360 ms (Needs improvement) | 0.20 (Needs improvement) | No |
| SKIMS | skims.com | Poor | 2.64 s (Needs improvement) | 204 ms (Needs improvement) | 0.32 (Poor) | No |
| Brooklinen | brooklinen.com | Needs improvement | 3.49 s (Needs improvement) | 287 ms (Needs improvement) | 0.13 (Needs improvement) | No |
Homepage URL-level field rows can differ from origin (for example Fashion Nova’s homepage LCP was Good while origin LCP was Needs improvement), so use origin for brand-level scorecards and URL groups for template work.
Allbirds is the clearest split in this cohort: Watcher multi-page lab Performance averaged about 34, with lab LCP around 16 s, while mobile origin CrUX passed all three Core Web Vitals. Brand scale does not guarantee a field pass either, because only Allbirds cleared all three origin metrics in this snapshot and INP (and sometimes CLS) kept most of the other famous stores out of the good bucket even when LCP looked acceptable. If a client asks “are we slower than the big Shopify brands?”, compare their CrUX origin or Search Console URL groups to this table, and keep Lighthouse for regression hunting on the same money-path templates.
At the other end of our wider Watcher sample, smaller or carefully trimmed storefronts can clear mobile lab averages in the mid-70s to mid-80s (for example Beauty Connections, Valmont Wear, and Bäckerei Matzker in this pull). Those shops still run on Shopify. The gap versus the famous lab cohort is mostly implementation load: fewer competing scripts, lighter heroes, and fewer template surprises across the multi-page set.
Use both clocks without mixing them in one column:
| Question | Prefer |
|---|
| Does Google’s page experience view look healthy? | CrUX / Search Console / PSI field (p75) |
| Did last week’s theme or app change regress templates? | Scheduled Lighthouse (lab), same URL set |
| Are we comparing to Shopify’s theme table? | Theme CrUX aggregates (device mix, theme filter) |
| Are we comparing agency client A to client B? | Same tool, same URL roles, same aggregation |
Watcher domain reports already separate lab score cards from field methodology notes (median of URL-level p75s where present, origin badge when available). Keep that separation in client decks. A green origin badge with a mobile Performance average of 40 is not a contradiction; it is a prompt to inspect which templates the lab average is punishing. For portfolio monitoring design, see Core Web Vitals Monitoring Checklist for Agencies and How to Set Up Automated PageSpeed Monitoring.
When unused JavaScript appears on nearly every store, a useful remediation order is usually:
Measure the money paths: homepage, top collections, top PDPs, cart, and checkout-adjacent templates, not a single marketing URL.
Cut or defer app scripts that are not required for first paint or first interaction on those templates.
Fix LCP candidates explicitly (image dimensions, priority hints, hero media weight) before chasing a Performance score vanity target.
Re-check CLS when banners, consent UI, or late-injected reviews shift layout after load.
Re-run the same URL set on a schedule so you can tell a real regression from run noise.
The detailed Shopify playbook for those steps lives in Shopify Speed Optimization: Core Web Vitals Guide for E-Commerce. Benchmark numbers stay honest when prioritisation stops here and the how-to lives in that companion post.
A fixed process keeps each monthly refresh comparable:
Scope: mobile-first; LCP, INP, CLS; optional Lighthouse Performance as a lab companion metric.
URL roles: same template set each month (home, collection, PDP, cart at minimum).
Aggregation: decide in advance whether you report origin CrUX, URL-level field, or multi-page lab averages, and never mix them in one table column.
Guardrails: mark insufficient CrUX explicitly; record tool, date, and page count.
Reporting: publish median cohort values, share of stores passing field CWV when available, top gains and regressions, and hypotheses (apps, media, theme) labelled as hypotheses.
You can start wi
