Shopify Speed Optimisation
Slow storefronts lose sales before a customer ever reaches the checkout.
- check_circle
Core Web Vitals audited against real field data, not a one-off lab score
- check_circle
App bloat and render-blocking scripts identified and removed
- check_circle
Image, font, and Liquid rendering tuned where it actually matters
Field Data
Real Users, Not Lab Scores
Core Web Vitals
LCP, INP, and CLS
App Audit
Bloat Identified and Removed
Measured
Before and After, Documented
Why your Shopify store got slow
Almost no store is slow on launch day. It gets slow gradually — an app here, a tracking pixel there, a hero image nobody compressed, a font loaded from a third domain. Each addition seemed harmless. The cumulative effect is a storefront that takes four seconds to become useful, on the mobile connections most of your customers are actually using.
Apps injecting scripts everywhere
Every installed app can add JavaScript to every page, including pages where it does nothing. This is the single most common cause of a slow Shopify store.
Oversized images
Hero images uploaded at print resolution and scaled down in the browser, so the customer downloads several megabytes to see one banner.
Render-blocking resources
Fonts and stylesheets loaded in a way that leaves the page blank until they arrive, delaying the moment anything becomes visible.
Optimising for the wrong number
Chasing a Lighthouse score on a desktop connection while real customers on mobile networks experience something quite different.
What a performance engagement covers
We start from field data — what real visitors on real connections experience — because that is what Google measures and what your customers actually feel.
Field data audit
Core Web Vitals from real users via Chrome UX Report and Search Console, not a single lab run on a fast connection.
App impact analysis
Every installed app measured for its actual cost, so you can decide what earns its place and what quietly leaves behind orphaned scripts.
Image and font optimisation
Correct formats and sizes, responsive image handling, lazy loading below the fold, and fonts served without blocking rendering.
Liquid and theme tuning
Inefficient loops, oversized section rendering, and unnecessary API calls in the theme identified and rewritten.
Critical path optimisation
Above-the-fold content prioritised so the page becomes useful quickly, with non-essential scripts deferred.
Before-and-after documentation
Measured results showing what changed and by how much, so the work is verifiable rather than asserted.
What changes after performance work
Before
- close
Four seconds before the page becomes useful on mobile
- close
Twelve apps loading scripts, three of them unused
- close
Hero images downloading at several megabytes
- close
Layout jumping as fonts and banners load in
- close
Core Web Vitals failing in Search Console
After
- check_circle
Above-the-fold content visible quickly on mobile data
- check_circle
Only apps that earn their place, orphaned scripts removed
- check_circle
Responsive images sized to the device requesting them
- check_circle
Stable layout with space reserved before content loads
- check_circle
Core Web Vitals passing on field data
How we approach performance
Measure real users
We pull field data from Chrome UX Report and Search Console to see what actual visitors experience, then reproduce the worst cases on throttled mobile connections.
Find what actually costs
Apps, scripts, images, and theme code profiled individually. Most stores have two or three changes worth more than everything else combined.
Fix in priority order
Highest-impact changes first, each measured after the change so we know it helped rather than assuming it did.
Verify on field data
Field metrics take a few weeks to reflect changes, so we check back once real-user data has caught up rather than declaring victory on a lab score.
Shopify performance questions
Why is our Shopify store slow when Shopify is supposed to be fast?expand_more
Shopify's own infrastructure is fast. What slows a store down is almost always what has been added on top — apps injecting scripts, oversized images, third-party tracking, and theme code doing more work than it needs to. The platform is rarely the constraint; the accumulated additions usually are.
What are Core Web Vitals and do they affect rankings?expand_more
They are three measures Google uses for page experience: LCP (how quickly the main content appears), INP (how quickly the page responds to interaction), and CLS (how much the layout shifts while loading). They are a genuine ranking signal, though a modest one — relevance matters more. The stronger argument is commercial: slow pages lose customers before checkout.
Will removing apps break our store?expand_more
We audit before removing anything, and the recommendation is always yours to accept. Often the finding is that an app was uninstalled months ago but left scripts behind in the theme — that is free performance. Where a slow app is genuinely needed, we look at whether its function can be built more efficiently instead.
How much faster will our store get?expand_more
It depends entirely on what is wrong, and we will not quote a number before measuring. A store carrying years of unremoved app scripts and uncompressed images can improve dramatically. One that is already reasonably built may see modest gains. The audit tells you what is achievable before you commit to the work.
Do you optimise for the Lighthouse score?expand_more
Not as the goal. Lighthouse is a lab test on a simulated connection and is useful for diagnosis, but it is not what Google uses for ranking and it is not what your customers experience. We optimise against field data from real users, which is what Search Console reports.
Is a headless build the answer to a slow store?expand_more
Usually not. Headless can be faster, but it is a substantial engineering commitment and most slow stores are slow for reasons a headless rebuild would not fix — the same apps, images, and tracking would still be there. We would rather fix the actual causes first, and will tell you honestly if headless is genuinely warranted.
Performance is one part of what we do
Speed problems often trace back to how the theme was built or how many apps are covering gaps in it. See the full picture, or read about the pieces next to this one.
Also see: Shopify theme development · Custom Shopify app development