Why speed matters for a store
A shopper on a phone decides within a few seconds whether a page is worth waiting for. Slow pages lose visitors before the product even appears, and Google uses loading speed, through its Core Web Vitals, as one of the signals for ranking. A faster store gets more out of the traffic you already pay for.
Measure first, properly
- Use PageSpeed Insights on your home page, a collection page and a product page. Those three templates carry most of your traffic and they are usually slow for different reasons.
- Look at the mobile result. Most shoppers are on phones, and the mobile test runs on a slower device and network, which is where problems show.
- Focus on Largest Contentful Paint (LCP), the time until the main image or heading appears. Google’s target is under 2.5 seconds.
- If your store has enough visitors, the “real users” section at the top shows field data from Chrome users. That is what Google actually ranks on.
- Write the numbers down. Without a before, you cannot prove an after.
The usual causes
| Cause | What it does | The fix |
|---|---|---|
| Too many apps | Each app can inject its own JavaScript and CSS on every page, even pages where it does nothing. | Remove apps you no longer use, and check their leftover code is gone from the theme. Replace small apps with a few lines of theme code. |
| Oversized images | A 4,000-pixel product photo sent to a phone screen that shows it at 400 pixels. | Use Shopify’s image sizes and srcset so each device gets the right size, and lazy-load images below the fold. |
| Lazy-loaded hero image | The most important image on the page waits until the browser decides it is needed. | Load the first image eagerly with high fetch priority; lazy-load everything after it. |
| Sliders and videos at the top | Heavy JavaScript and large files delay the first thing the shopper sees. | Use one strong static image, or load the video only after the page is interactive. |
| Extra fonts | Several font families and weights, each a separate download, block text from showing. | Use one or two weights, preload the main one, and set font-display so text shows straight away. |
| Old theme code | Years of edits, unused sections and scripts that run on every page. | Move to a current Online Store 2.0 theme, or clean the existing one section by section. |
A real example: 11.6 seconds to about 1 second
My own site had the same problem in a different form. The portfolio runs a 3D scene and an animated loader, which is fine for people who come to see my work, but my service pages loaded all of it too. On a mobile test, the main content of those pages took 11.6 seconds to appear.
The fix was not clever. I gave the service pages a light layout that skips the 3D scene and the loader entirely, so the text and first image are in the HTML from the start and nothing heavy runs before them. The same measurement then came in at about 1 second.
The lesson carries straight over to Shopify: find the heavy thing that runs before your content, and stop it running on the pages that need to sell. On stores that is usually an app script, a slider or a video, not the platform.
What not to do
- Don’t install a “speed booster” app. Adding another app to fix the cost of apps rarely ends well, and some only improve the test score, not the real experience.
- Don’t chase a perfect 100. A product page that loads in 2 seconds and sells is better than a stripped page that scores 100.
- Don’t delete an app before checking what still depends on it, like reviews shown in Google results or a subscription checkout.
A quick checklist
- Test the home, collection and product pages on mobile and write the numbers down.
- List every installed app and what it is for. Remove what you don’t use.
- Check the hero image is not lazy-loaded and is served at the right size.
- Cut fonts to one family and one or two weights.
- Replace sliders and autoplay videos at the top of the page.
- Test again and compare.