How to Run a Shopify Theme Speed Test

A Shopify theme speed test tells you how fast your storefront loads for a real shopper, not how fast your homepage loads for you on a fast office connection. The short version: test your product page and your collection page (not just the homepage), test on mobile, use Google PageSpeed Insights plus Shopify's built-in Theme Inspector, and run the test more than once before you trust the number. Below is the full step-by-step process, how to read the results, and what actually moves the needle once you know your score.

Why the Homepage Test Is Misleading

Most merchants test speed by running their homepage through a tool once and calling it done. That is the least useful page to test. Homepages are usually the lightest, most cached page on a Shopify store — a handful of hero images and maybe a slideshow. Product pages carry the real weight: variant images, size charts, reviews widgets, recommended-product carousels, and often two or three apps injecting their own scripts. Collection pages carry a different kind of weight: dozens of product images and thumbnails loading at once, plus filter and sort logic. If you only test the homepage, you are testing the best-case scenario and missing the pages your paid traffic actually lands on.

Step 1: Pick the Right Pages to Test

Before opening any tool, decide what you are testing. At minimum, test three URLs:

• Your best-selling product page — the one with the most variants, images, and app widgets, since that is your worst case
• A collection page with a realistic number of products (not an empty or near-empty one)
• The homepage, mostly as a baseline rather than the main signal

If you sell across a few different categories, it is worth testing one product page per category, since apps and image counts can vary a lot page to page. A store selling both simple and highly-configured products (frames with several lens options, for example) should test both product types separately.

Step 2: Run Google PageSpeed Insights on Mobile

Go to Google's PageSpeed Insights tool and paste in the live URL of the product page you picked (not a password-protected preview link — the tool needs to load the page the way a real visitor would). Run it and look at the mobile tab first, not desktop. The large majority of ecommerce traffic is mobile, and mobile scores are almost always lower than desktop because of slower processors and network conditions, so mobile is the number that reflects your actual audience.

PageSpeed Insights gives you two kinds of data: lab data (a simulated run done right then) and, if your store gets enough traffic, field data (real Chrome user measurements from the past 28 days, labeled Core Web Vitals). Field data is more trustworthy when it is available, because it reflects real devices and real network conditions rather than one simulated run. Pay attention to three metrics in particular: Largest Contentful Paint (LCP) — how long the biggest visible element takes to render, Cumulative Layout Shift (CLS) — how much the page jumps around as it loads, and Interaction to Next Paint (INP) — how responsive the page feels once a shopper starts clicking or tapping.

Step 3: Run It More Than Once

A single run of any speed test tool is a sample, not a verdict. Server response times, third-party ad or analytics scripts, and even the testing service's own network conditions vary run to run. Run PageSpeed Insights three to five times on the same URL and look at the range rather than a single score. If your LCP bounces between 2.1s and 4.8s across runs, that instability is itself useful information — it usually points to a slow or inconsistent third-party script rather than the theme's own markup.

Step 4: Use Shopify's Built-In Theme Inspector

PageSpeed Insights tells you the outcome; Shopify's Theme Inspector (available in Shopify CLI, and as a browser extension) tells you which part of the theme caused it. It breaks down render time by section and by Liquid template, which matters because on Shopify your theme is assembled from sections and snippets — a single slow app-injected section or an oversized custom snippet can drag down an otherwise well-built page. If your PageSpeed score is unexpectedly low, this is the tool that tells you whether the culprit is a theme section, an app embed, or genuinely heavy image weight.

Step 5: Check Image Weight and Format Separately

Images are the single most common cause of a slow Shopify product or collection page, so it is worth checking them directly rather than only reading the tool's summary. In your browser's developer tools, open the Network tab, filter by "Img", reload the page, and sort by size. Look for two problems: images served far larger than their display size (a 4000px-wide photo being shown in a 600px box), and images not served as WebP or AVIF. A well-built theme should lazy-load offscreen images and serve responsive image sizes automatically — that is theme-level behavior you should not have to configure by hand, and it is one of the things worth checking for before you commit to a theme.

Step 6: Isolate Apps From the Theme

Before blaming a slow score entirely on the theme, rule out apps. Each installed app that injects a script into your storefront — reviews widgets, upsell popups, live chat, tracking pixels — adds its own load time on top of the theme. A fast way to check: temporarily disable an app (or use its theme-editor toggle if it has one) and re-run PageSpeed Insights on the same URL. If the score jumps noticeably, that app is a meaningful part of your load time, and you can decide whether it is worth the tradeoff or whether a lighter alternative exists. Doing this one app at a time is tedious but it is the only reliable way to separate "theme problem" from "app problem" instead of guessing.

What a Good Score Actually Looks Like

Google's general guidance for Core Web Vitals is to aim for an LCP under 2.5 seconds, a CLS under 0.1, and an INP under 200 milliseconds, measured on mobile. Treat these as directional targets rather than pass/fail gates — a store with a large, image-heavy catalog and several merchandising apps installed will naturally sit a bit higher than a small, minimal storefront, and that is a normal tradeoff rather than a failure. What matters more in practice is the trend: is your product page speed roughly stable release over release, or does every new app and content addition quietly push it worse without anyone noticing?

Building the Speed Test Into How You Choose a Theme

The most useful time to run this whole process is before you commit to a theme, not after your store is fully built out with months of content and apps. Most theme marketplaces host a live demo store — run the same PageSpeed Insights and Network-tab checks against a demo's product and collection pages that you would run on your own store. Look specifically at whether images are served responsively and lazy-loaded by default, since that is largely out of your control once you are relying on a specific theme's templates. Our Shopify theme catalog is built with exactly this in mind — themes designed to keep collection grids and product galleries fast by default, so speed is not something you have to fight for after launch.

If you are choosing between a general-purpose theme and a niche-specific one for a category with heavier product pages — multiple lens or fit options, comparison tables, spec sheets — it is worth testing a niche theme's demo product page specifically, since those templates tend to carry more markup by design. For example, our Optics Shopify theme is built around eyewear's heavier option layouts while still keeping galleries lazy-loaded and collection grids lightweight, which is the kind of balance worth testing for rather than assuming.

A Simple Repeatable Checklist

1. Pick a real product page (your heaviest one), a real collection page, and the homepage as a baseline
2. Run each through PageSpeed Insights on the mobile tab, three to five times
3. Note the LCP, CLS, and INP ranges, not just one run
4. Run Shopify's Theme Inspector on the same product page to see which section or template is slowest
5. Check the Network tab's image requests for oversized files or missing WebP/AVIF
6. Disable apps one at a time and re-test to isolate their impact
7. Re-run the same checklist after any theme, app, or major content change so you catch regressions early

Frequently Asked Questions

Is PageSpeed Insights the only tool I need?

It is a strong starting point because it is free, widely trusted, and reports both simulated and real-user data. Pairing it with Shopify's own Theme Inspector gets you further, since PageSpeed tells you the outcome while Theme Inspector tells you which section or template is responsible. Third-party tools built on the same underlying engine can add convenience, like scheduled monitoring, but are not required to get an accurate first read.

Why does my score change every time I test?

Some variation is normal because a lab test is a single simulated run affected by network conditions and third-party scripts at that moment. Large swings between runs usually point to an inconsistent script — often a third-party app or ad tag — rather than the theme itself, which is exactly why running the test several times matters more than trusting one result.

Does more apps always mean a slower store?

Generally yes, since every app that injects a storefront script adds some load time, but the impact varies enormously by app and by how well it is built. The only reliable way to know an individual app's cost is to test with it disabled and re-enabled, rather than assuming based on the app's category or price.

Can a theme alone fix a slow store?

A well-built theme removes a lot of the common causes of slowness — unoptimized image handling, heavy unnecessary markup, poor lazy-loading — but it cannot fix a slow score caused by too many heavy apps or unoptimized uploaded images. Think of the theme as the ceiling on how fast your store can be, and your app choices and content as what determines how close you get to it. Browsing our Shopify themes with a speed test already in hand is the best way to judge that ceiling honestly before you build on top of it.