Shopify Speed Optimization.
Fixed in the Code, Not Hidden by an App.
Shopify speed optimization is usually sold as a PageSpeed score. Google and your shoppers judge something else: how fast real visitors see the main image, how quickly a tap on Add to cart responds, and whether the page jumps while it loads. We find what slows your theme down, from apps and images to fonts and leftover code. We fix it on a copy of your theme you review first, then track Core Web Vitals from real visitors until the numbers hold.
Three numbers decide whether your store counts as fast
Google's Core Web Vitals come from real Chrome visitors, measured at the 75th percentile over 28 days. A page passes when all three are in the good range.
Largest Contentful Paint
How long until the biggest thing on screen, usually the hero or product image, has loaded.
2.5 s or less
The main image set to lazy-load, oversized images, and app scripts that block rendering.
Interaction to Next Paint
How quickly the page responds when a shopper taps, clicks or types.
200 ms or less
Heavy JavaScript from review, upsell, chat and tracking apps, and bulky sliders and variant pickers.
Cumulative Layout Shift
How much the layout moves around while the page loads.
0.1 or less
Images with no set size, banners and app widgets that appear late, and web fonts swapping in.
Interaction to Next Paint replaced First Input Delay as a Core Web Vital in March 2024. Stores tuned for the old metric often fail the new one.
Six things slowing down
a normal product page.
This is a typical Shopify product page on a phone. Once it has loaded, it looks fine. Tap a marker to see what a speed audit flags, and what we change.
Linen Overshirt
$68.00 · Free shipping over $75
- What's there
- What it costs you
- What we do
Your own audit lists these against your real templates, ranked by how much load time each one costs.
Five areas we work through on every store
Every item is a change to your theme, apps or settings. You get a changelog, not a slide deck.
Audit and baseline
We record where you stand before anything changes.
- Core Web Vitals field data by page type
- Lab tests on home, collection, product and cart
- A script-by-script list of what each app loads
- Fixes ranked by impact and effort
Theme and code
Most of the load time lives in the theme itself.
- Render-blocking CSS and JavaScript deferred
- Unused sections, snippets and libraries removed
- Heavy Liquid loops and sections simplified
- Sliders and variant pickers made lighter
Images, video and fonts
The files that decide Largest Contentful Paint on most pages.
- Main image loaded first, the rest lazy-loaded
- Responsive sizes and set dimensions
- Videos that load on click, not on arrival
- Font files trimmed and preloaded
Apps and third-party scripts
Every app has to earn its load time.
- Leftover code from removed apps cleaned out
- App scripts deferred or loaded on interaction
- Lighter alternatives suggested where they exist
- Tracking tags checked in GTM and the theme
Monitoring and handover
Speed drifts back as new apps and campaigns are added.
- Field data tracked through the 28-day window
- A before and after report by page type
- A short guide to adding apps without slowing the store
- Optional monthly checks
Why we don't chase a PageSpeed score
PageSpeed Insights shows two different things. The big Performance score is a lab test. The Core Web Vitals assessment comes from real visitors, and that is the data Google uses.
Lab data (Lighthouse)
- ·One test on one simulated phone
- ·Changes from run to run
- ·Good for finding what causes a slow page
- ·Not what Google uses for Core Web Vitals
Field data (Chrome UX Report)
- ✓Real visitors on real phones and networks
- ✓Measured at the 75th percentile over 28 days
- ✓What Google uses for Core Web Vitals
- ✓What we report the project against
Some speed tools raise the lab score by holding scripts back in ways that do little for real visitors. The score goes up and shoppers see no difference. We use lab tests to find problems and real-user data to prove the fix.
Every fix logged, with the number it moves.
At handover you get a fix log: each change, where it was made, the metric it targets, and the reading before and after.
Illustrative figures, not a client store. Yours come from your own lab tests and field data.
Measure, fix, then confirm
Speed fixes go wrong when they are published straight to a live store. Every change is built on a copy of your theme and checked before it goes live.
Audit and baseline
Field data, lab tests on each page type and a full script inventory. You get the ranked fix list and your starting numbers before any code changes.
You receive: audit + baselineFixes on a duplicate theme
Theme, image, font and app fixes built on an unpublished copy of your live theme. Your storefront stays untouched while we work.
You receive: preview link + changelogReview and publish
You click through the preview, we test cart, checkout and app features with you, and we publish once you approve. The old theme stays as a rollback.
You receive: published theme + fix logField data check
Real-user data updates over a rolling 28 days. We track it until the new numbers settle and fix anything that slips.
You receive: before and after reportA speed app, a DIY pass, or a fix project
All three have a place. This is what each one changes, so you can pick what fits your store today.
| Speed booster app | DIY with a checklist | Fix project with us | |
|---|---|---|---|
| What it changes | Adds its own script to delay or preload others | Whatever you're comfortable editing | Theme code, images, fonts and how apps load |
| Leftover app code | Left in place | Hard to find without tracing scripts | Traced and removed |
| Risk to your live store | Delayed scripts can break app features | Edits often made on the live theme | Built on a duplicate theme, published after review |
| Judged on | Usually the lab score | Usually the lab score | Real-user Core Web Vitals |
| Cost | A monthly app fee | Your time | A fixed project price |
| Best for | A quick test on a small, simple store | Stores with a developer in-house | Stores where apps and theme edits have piled up |
How pricing works, and what we need to start
Speed work is a fixed-price project. Monitoring afterwards is optional.
Two ways to work with us
Fix project
A one-off, fixed price for the audit, the fixes, the review and the field data check. You get the figure after the free audit.
Monthly monitoring (optional)
A monthly check of your field data, new apps and theme changes, with fixes when a number slips.
What shapes the quote: how many apps you run, how much custom code is in the theme, and how many page templates need work.
What we need from you to start
- ✓Collaborator access to your Shopify admin
- ✓Permission to duplicate your live theme
- ✓A list of the apps you rely on, and which features matter
- ✓Google Search Console access, if you have it
- ✓GA4 or Google Tag Manager access, if your tags live there
- ✓Dates of any launches or sales we should work around
Questions store owners ask about speed
Google rates a page as good when Largest Contentful Paint is 2.5 seconds or less, Interaction to Next Paint is 200 milliseconds or less, and Cumulative Layout Shift is 0.1 or less, for at least 75% of real visits. We work to those thresholds, not to a PageSpeed number.
Core Web Vitals are part of how Google assesses page experience, but relevance and content count for more. Speed alone rarely moves rankings much. It does decide how many visitors wait for the page to load, which is why we pair it with SEO when rankings are the goal.
Not always. Many apps can load later, or only on the pages that use them. We show you what each app costs in load time and suggest removing one only where it adds little. Nothing is uninstalled without your go-ahead.
No. All work happens on a duplicate of your theme. You review it on a preview link, we publish once you approve, and your previous theme stays in the theme library as a rollback.
The score comes from one simulated lab test, so network and server timing move it from run to run. The real-user Core Web Vitals that Google uses cover 28 days of visits and are far steadier. We report both and judge the work on the real-user data.
Lab results change as soon as fixes are published. Search Console and the field data in PageSpeed Insights use a rolling 28-day window, so expect the new numbers to show in full about four weeks after launch.
Yes. The work is the same on any Shopify plan. Custom or heavily edited themes usually take longer, and that is reflected in the quote after the free audit.
What speed work usually leads to
Shopify SEO
Fast pages give your collections a fair chance to rank. SEO decides what they rank for.
View service →Shopify CRO
Once pages load quickly, testing product pages, cart and checkout turns more visits into orders.
View service →Theme customization
When the theme itself is the bottleneck, we rebuild the sections that slow it down.
View service →Want to know what's slowing your store down?
Get a free speed audit. Within 48 hours we send your Core Web Vitals, the scripts and files behind them, and the fixes ranked by impact.