Quick Fix with Thunder
Run a benchmark, install Thunder, then test the same URLs again. Thunder improves the common Shopify bottlenecks that show up in speed tests: app scripts, render-blocking resources, image delivery, font loading, lazy-loading mistakes, and mobile Core Web Vitals.
Why Benchmark Before App Changes
Most Shopify speed debates happen after the damage is done. A merchant installs reviews, chat, subscriptions, a page builder, a pixel, or a product recommendation app, then notices the mobile score dropped. Without a baseline, nobody knows whether the app caused it, whether the theme changed, or whether the tested URL was already slow.
Benchmarking fixes that. It gives you a before picture for the exact pages shoppers use. Shopify's Web Performance Dashboard can show real user trends across Core Web Vitals, while tools such as PageSpeed Insights and Thunder's speed test help reproduce page-level diagnostics. Google Search Console also groups real-user Core Web Vitals issues when enough Chrome data is available.
The point is not to chase a perfect 100. The point is to protect revenue pages from avoidable regressions. If a new app helps conversion but adds 100 KB of JavaScript only after interaction, that may be fine. If it blocks the product page hero image and adds long tasks on mobile, you need to fix it before campaign traffic arrives.
Shopify Store Speed Test URLs to Include
A single homepage test is weak evidence. Shopify stores have different templates, different app blocks, and different revenue paths. Test pages that represent how shoppers actually enter and use the store.
| Page type | Why test it | Common bottleneck |
|---|---|---|
| Homepage | Brand traffic, navigation, campaign first impression. | Hero media, sliders, collection grids, popups, tracking. |
| Product page | Highest intent page before add to cart. | Product media, reviews, subscriptions, variants, upsells. |
| Collection page | SEO and browsing traffic. | Filters, large image grids, infinite scroll, search apps. |
| Landing page | Paid traffic and promotions. | Page builders, video, tracking pixels, duplicated sections. |
| Blog or guide | Organic traffic and informational intent. | Images, embeds, third-party widgets, unused CSS. |
For page-specific guidance, read product page speed optimization, Shopify collection page speed, and Shopify homepage speed.
Metrics to Record in a Shopify Store Speed Test
Record the score, but do not stop there. A performance score is a summary, not a diagnosis. Capture the metrics and diagnostics that tell you what changed.
- LCP: Whether the largest above-the-fold element appears within 2.5 seconds.
- INP: Whether real interactions respond within 200 milliseconds.
- CLS: Whether late-loading content shifts the page by less than 0.1.
- Total Blocking Time: A lab proxy for heavy JavaScript and main-thread work.
- Network requests: How many scripts, stylesheets, images, fonts, and API calls load.
- Transfer size: Whether the page became heavier after apps or media changes.
- LCP element: Which element is actually responsible for the main loading metric.
If the result changes every run, that is normal. Read why Shopify speed test scores vary before assuming a single test proves a fix or regression.
Simple Benchmark Template Before Installing an App
Keep the benchmark small enough that you will actually use it. The store owner, marketer, developer, or VA should be able to fill this out before and after any meaningful storefront change.
Change:
Date:
App/theme/tracking change:
URL tested:
Device: mobile
Tool:
Performance score:
LCP:
INP or TBT:
CLS:
Requests:
Transfer size:
Largest contentful element:
Top 3 diagnostics:
Notes:
Buying flow tested:
- Variant selection
- Add to cart
- Cart drawer
- Search/filter if relevant
- Checkout link
- Analytics/event checkStore these snapshots in a shared doc. When the score drops, you will have real evidence instead of guessing. This is especially important before installing high-impact apps such as reviews, search, page builders, chat, subscriptions, loyalty, upsells, and attribution pixels.
Manual Benchmark Workflow vs Thunder Workflow
| Step | Manual workflow | Thunder workflow |
|---|---|---|
| Before change | Run tests, save screenshots, export network data, write down metrics. | Run the same benchmark, then install Thunder for the first optimization pass. |
| After app install | Compare requests, scripts, CSS, app embeds, and visual changes manually. | Let Thunder optimize common app and resource-loading issues, then retest. |
| If scores drop | Disable app embeds one by one in a duplicate theme and inspect DevTools. | Use Thunder first for safe automated fixes, then isolate any remaining custom issue. |
| Long-term | Repeat the benchmark after each major change and update a performance log. | Keep Thunder active as the baseline optimization layer while monitoring key URLs. |
How to Compare Before and After Results Safely
Use the same URL, same device mode, same test tool, and same conditions where possible. Run multiple tests and compare medians instead of celebrating one lucky pass. If the first run after a deploy is slow, run again after cache warms.
More importantly, test the storefront experience. A benchmark is not successful if the score improves but variant selection, app blocks, tracking, add-to-cart, search, filters, or checkout links break. Shopify speed work has to protect the buying flow.
If you need a broader diagnostic process, use how to read your Shopify speed test results and the complete Shopify speed optimization guide. If you want to compare speed app options before acting, see the best Shopify speed apps in 2026.
When to Use Thunder After Benchmarking
Use Thunder when the benchmark shows common storefront bottlenecks: app scripts, blocking resources, heavy images, fonts, lazy loading mistakes, poor mobile LCP, poor INP, or layout shifts. Those problems are common enough that automation makes sense.
Use a developer when the benchmark points to custom theme logic, a broken app integration, a complex product configurator, or a revenue-critical cart flow. Use professional speed optimization when you need hands-on cleanup beyond app automation.
For most stores, the practical sequence is simple: benchmark, install Thunder, retest, then decide whether anything left is worth custom work. You can review Thunder pricing before you start.
FAQ
What is a Shopify store speed test?
A Shopify store speed test measures how quickly important storefront pages load, render, respond, and stay visually stable. The best benchmark includes homepage, product, collection, and landing page URLs, not just one homepage score.
When should I run a Shopify store speed test?
Run a test before installing apps, publishing a theme, launching a campaign, adding large media, changing tracking tags, and after each major fix. A baseline makes regressions obvious.
Which Shopify pages should I benchmark?
Benchmark the homepage, one top product page, one collection page, one blog or landing page, and any page used by paid ads or email campaigns. Mobile results usually matter most.
Why do Shopify speed test results vary?
Results vary because device emulation, network conditions, server timing, app requests, test location, cache state, and third-party scripts change between runs. Use repeat tests and compare trends.
Can Thunder improve my benchmark after the test?
Yes, when the benchmark shows common Shopify bottlenecks such as heavy app scripts, render-blocking files, image loading issues, font loading, lazy loading mistakes, or Core Web Vitals problems.
Is Shopify's Web Performance Dashboard enough?
It is useful for real user trends, but you still need page-level tests to reproduce a specific issue, inspect diagnostics, and compare before-and-after changes quickly.
Conclusion
A Shopify store speed test is your insurance before app changes. Benchmark the pages that matter, capture the metrics behind the score, retest after each change, and use Thunder to automate the common Shopify speed fixes before speed problems turn into conversion problems.