Speed is one of those things every store owner nods along to and then quietly ignores until sales dip. It shouldn’t be. A slow store loses shoppers before they ever see your products, and it costs you ground in Google search results at the same time. That is a bad trade for a problem that is usually very fixable.
This is a practical look at Shopify speed optimisation: what actually slows a store down, what you can check yourself this afternoon, and what genuinely needs a developer.
Why slow quietly costs you money
Shoppers are impatient, and mobile shoppers most of all. If a page takes several seconds to become useful, a chunk of people give up before it finishes. They don’t email to complain. They just leave, and you never see them in your analytics as a lost sale.
Google folds page experience into how it ranks results, measured through Core Web Vitals. So a sluggish store gets hit twice: fewer people stick around, and fewer people find you in the first place. Speed is one of the few levers that helps conversion and SEO in the same move.
What Core Web Vitals actually measure
Core Web Vitals sound technical, but they map onto three plain questions about a real page load.
- Largest Contentful Paint (LCP) asks: how long until the main thing on screen appears? Usually your hero image or product photo. Aim for under 2.5 seconds.
- Interaction to Next Paint (INP) asks: when someone taps or clicks, how quickly does the page respond? This replaced the older First Input Delay metric in 2024. Aim for under 200 milliseconds.
- Cumulative Layout Shift (CLS) asks: does the page jump around while it loads? You want it stable, under 0.1. If a button shifts just as someone goes to tap it, that is CLS at work.
For most retailers, LCP and CLS are where the wins are. INP matters more on heavily interactive pages, filtered collections, variant pickers, that sort of thing. If you only look at two numbers, look at LCP on your product and collection pages on mobile.
The usual culprits
Slow Shopify stores are slow for a remarkably short list of reasons. We see the same offenders constantly.
- Oversized images. A 4000px hero image squeezed into a 600px slot is dead weight. This is the single most common cause of a poor LCP.
- Too many apps. Every app can inject scripts and styles that load on every page, whether you use that app on that page or not. Stores accumulate them like junk in a drawer.
- Heavy themes. Some themes ship with sliders, video backgrounds and animation libraries you may never use, all loading anyway.
- Third-party scripts. Reviews widgets, chat bubbles, pop-ups, analytics and pixels. Each one is a request to someone else’s server, and you don’t control how fast they answer.
- Render-blocking code. CSS and JavaScript that the browser must download and process before it can show anything. This is what makes a page sit blank for a beat too long.
What you can check yourself
You don’t need to be technical to get a clear picture.
- Run PageSpeed Insights on your homepage, a collection page and a product page. Use the mobile scores, since that is where most of your traffic is. Read the “Opportunities” section in plain English rather than fixating on the overall number.
- Test on a real phone on mobile data, not your office wifi. It is sobering and honest.
- Audit your apps. Open your app list and be ruthless. Anything you installed to trial and never used should go. Uninstalling is not always enough, which we will come to, but it is the right first step.
- Check your biggest images. If your hero images are several megabytes each, that is a problem you can see without any tools.
This will not fix anything on its own, but it tells you where the weight is and stops you paying a developer to find out what you could have spotted yourself.
What needs a developer
Some of this lives in the theme code, and that is where our team usually earns its keep.
- Resizing and lazy-loading images properly, so the browser loads the right size and only fetches what is below the fold when it is needed.
- Deferring non-critical scripts so chat widgets and trackers load after the page is usable, not before.
- Removing leftover app code. Uninstalling an app in Shopify often leaves fragments of its code behind in your theme. Someone has to go in and clean those out by hand.
- Trimming render-blocking CSS and JavaScript and prioritising what the browser needs to paint the page.
This is careful work, not a switch you flip. Done badly it breaks things, so it is worth having someone who knows Liquid do it on a copy of your theme first.
Realistic expectations
A word of honesty, because the marketing around this gets silly. Shopify’s own hosting is genuinely fast, so a lot of the platform-level work is already done for you. You are unlikely to hit a perfect 100 score, and you shouldn’t try. Mobile scores are always lower than desktop, and there are diminishing returns once you are past the obvious problems.
The goal is not a screenshot of a green number. It is a page that becomes useful quickly on a mid-range phone on a patchy connection. Fix the images, prune the apps, tidy the scripts, and most stores feel noticeably quicker for it.
Speed is rarely one dramatic fix. It is a handful of sensible ones, done properly and kept in check as you add things over time.
If you would like us to take a look at where your store is losing time, get in touch and we will give you an honest read.