Chase a vanity score
We will not strip functionality your business needs so a synthetic number goes green.
MEASURED ON REAL DEVICES
Shopify speed optimization and Core Web Vitals
App bloat stripped, scripts deferred, images sized properly, and LCP, CLS and INP measured on real devices rather than a lab score. Most Shopify stores carry more third-party JavaScript than first-party, and that is usually where the wins are.
IN SHORT
- Most Shopify stores load more third-party JavaScript than first-party code — that is where the largest wins usually are.
- Core Web Vitals are LCP (loading, good at 2.5s or under), CLS (visual stability, 0.1 or under) and INP (responsiveness, 200ms or under).
- The speed score in your Shopify admin is a lab score. Google ranks on field data, which is what appears in Search Console.
- The most common single fix is an oversized, late-loading hero image pushing LCP past the threshold.
- Speed work is finite — unlike CRO, it has an end state, which is why it usually pays back first.
Why Shopify stores get slow
Rarely the theme. Almost always accumulation. An app trialled during Black Friday and never removed. A tracking pixel for a campaign that ended. A review widget, a chat widget, a popup tool, a loyalty script, a heatmap recorder — each one justified on its own, and each one loading before your product image does.
The revealing number on most audits is that a store loads more third-party JavaScript than first-party. The theme your agency built is a minority of the payload, and the majority is code nobody in the building can name.
Which is good news: the largest wins usually cost nothing to ship, because they are deletions.
The three metrics that matter
Core Web Vitals, in plain terms
LCP — Largest Contentful Paint. How long until the biggest thing on screen appears, usually your hero image or headline. Good is 2.5 seconds or under.
CLS — Cumulative Layout Shift. How much the page jumps around while loading. The reason you tap the wrong thing when an image loads late. Good is 0.1 or under.
INP — Interaction to Next Paint. How quickly the page responds when someone taps. Replaced First Input Delay as a Core Web Vital in March 2024. Good is 200 milliseconds or under.
Google assesses all three at the 75th percentile of real visits — so you are being judged on your slower quarter, not your average.
Lab score against field data
| Lab score | Field data | |
|---|---|---|
| Where you see it | Shopify admin, Lighthouse, PageSpeed | Search Console, Chrome UX Report |
| What it is | A simulated load on a throttled device | Real visits from real customers |
| Updates | Instantly, every run | Over weeks, as data accumulates |
| Used for ranking | No | Yes |
| Good for | Debugging a specific page | Knowing whether you actually have a problem |
Both are useful. The mistake is optimising the lab number — chasing 90+ in the admin while the experience of a real customer on a mid-range Android on mobile data stays unchanged.
How the work runs
Six stages. The first is measurement, and the last is measurement again, weeks later.
- 01
Measure the real thing
We start with field data from Search Console and the Chrome UX Report rather than a Lighthouse run, because a lab score on a fast laptop is not what your customers experience or what Google ranks on.
- 02
Audit every third-party script
Each script is listed with what it costs in bytes and blocking time, and whether anyone still uses it. Stores routinely carry tags for tools they stopped paying for two years ago.
- 03
Clear the critical path
Render-blocking CSS and JavaScript moved out of the way, non-critical scripts deferred, and anything that can load after interaction made to do so.
- 04
Fix LCP
Usually the hero. Correct image dimensions and formats, preloading the LCP element, removing what delays it, and making sure it is not waiting behind a font or a script.
- 05
Fix CLS and INP
Reserved space for images, ads and embeds to stop layout shift, and heavy main-thread work broken up so interactions respond inside the INP threshold.
- 06
Re-measure in the field
Field data takes weeks to update, so we track it after launch rather than declaring victory on a lab score the same afternoon.
What usually comes out
- Scripts from apps that were uninstalled months ago but left their tags behind
- Duplicate JavaScript libraries, loaded twice because two apps each brought their own
- Hero images at full desktop resolution being served to phones
- Fonts blocking render because nothing told the browser how to behave while they load
- Third-party tags in the critical path that could load after interaction
- Carousels and embeds with no reserved space, causing layout shift on every load
What we do not do
Install a speed app
Adding a script to fix a script problem. Speed apps help at the margins and cost you a dependency.
Promise a number
Anyone quoting a specific score before auditing your app stack is guessing at your store.
Declare victory early
Field data takes weeks to move. We report when the real numbers change, not on launch day.
Brands we do this for
Mighty Jaxx
Speed work is part of every maintenance retainer we run, because stores decay through accumulation and a one-off clean-up drifts back within a year.
Speed questions
Why is my Shopify speed score low?
Almost always third-party apps and tracking scripts loading before the page renders, plus oversized hero imagery. Theme code is rarely the largest factor on its own.
Does the Shopify speed score affect rankings?
Core Web Vitals are a ranking signal, but the number in your Shopify admin is a lab score. Field data in Search Console is what Google actually uses.
What are good Core Web Vitals scores?
Largest Contentful Paint at 2.5 seconds or under, Cumulative Layout Shift at 0.1 or under, and Interaction to Next Paint at 200 milliseconds or under. Google assesses these at the 75th percentile of real visits, so the goal is the experience of your slower quarter, not your average.
Why is my Shopify speed score low but the site feels fast?
Because the admin score is a synthetic lab test on a throttled connection, and you are browsing on a fast device with things cached. Neither is wrong — they measure different things. Field data in Search Console is the one that affects rankings.
Will removing apps break my store?
Removing an app you use would. The audit separates apps that earn their cost from scripts left behind by apps already uninstalled — the second category is pure dead weight and comes out with no functional change at all.
Related
Conversion Rate Optimization
Research, hypothesis, test, ship — a continuous programme rather than a one-off redesign.
UX & Checkout Audit
A senior engineer walks your storefront, theme and checkout and sends back a prioritised list of fixes.
Landing Page Production
Campaign and launch pages built to a section library, so marketing ships without a dev queue.
NEXT STEP
Free store audit
A senior engineer reviews your storefront, theme performance and checkout, then sends a prioritised list of fixes. No pitch deck, no obligation.