Field Data vs Lab Data: Which Matters More?
When you run a speed test on PageSpeed Insights or our free Shopify speed test, you'll see two distinct sections. Understanding the difference is the single most important thing about reading speed test results.
📊 Field Data (Real Users)
Data from real Chrome users who visited your site over the past 28 days. Collected via the Chrome User Experience Report (CrUX).
- Reflects actual user experience across devices, networks, and locations
- This is what Google uses for rankings
- Updated monthly with 28-day rolling window
- May show "Not enough data" for low-traffic pages
🔬 Lab Data (Simulated Test)
Data from a simulated test run right now with controlled conditions (specific device speed, network, location).
- Instant results — shows improvements immediately after changes
- More detailed diagnostics and recommendations
- Scores vary between runs (5–10 point fluctuations are normal)
- Does not directly affect SEO rankings
Bottom line: Field data is the truth. Lab data is the debugger. Use field data (Google Search Console → Core Web Vitals report) to track what Google sees. Use lab data (PageSpeed Insights diagnostics) to identify specific issues to fix. When field and lab disagree, trust field data — it represents what real visitors actually experience.
The 3 Core Web Vitals That Affect Your Shopify Rankings
These three metrics are what Google uses as ranking signals. Everything else in the speed test is secondary. Your goal: get all three into the "good" (green) range.
LCP — Largest Contentful Paint
Measures how fast the main content loads. On Shopify, this is usually the hero image (homepage), product image (product pages), or collection banner (collection pages).
If yours is red: Read our complete LCP fix guide. The most common causes are render-blocking scripts, unoptimized hero images, and lazy-loaded above-the-fold content.
CLS — Cumulative Layout Shift
Measures how much content jumps around while the page loads. High CLS means elements shift position unexpectedly — frustrating visitors and causing misclicks.
If yours is red: Read our complete CLS fix guide. Common causes: images without width/height, late-loading app widgets, font swaps, and slideshows.
INP — Interaction to Next Paint
Measures how fast your page responds to user interactions (clicks, taps, key presses). INP replaced FID (First Input Delay) as a Core Web Vital in March 2024 and is harder to pass.
If yours is red: Read our complete INP fix guide. Common causes: heavy JavaScript event handlers, third-party app scripts, and large DOM sizes.
Other Shopify Speed Test Metrics Explained
Beyond Core Web Vitals, your speed test report shows several additional metrics. These aren't direct ranking signals but they help diagnose performance issues and contribute to the overall performance score.
First Contentful Paint (FCP)
How long before the browser renders any content (text, image, or background). Good: under 1.8s. FCP shows how quickly your page starts appearing — even before the main content (LCP) loads. A high FCP usually means render-blocking resources are preventing anything from showing.
Total Blocking Time (TBT)
Total time the main thread was blocked by long JavaScript tasks (over 50ms each) between FCP and Time to Interactive. Good: under 200ms. TBT is the lab equivalent of INP — it measures how much JavaScript is hogging the browser. High TBT = sluggish interactions. This is the most impactful lab metric for your overall speed score.
Speed Index (SI)
How quickly the visible area of the page fills in during loading. Good: under 3.4s. Speed Index measures the visual progression — a page that renders top-to-bottom smoothly scores better than one that stays blank then pops in all at once. It's useful for visual rendering optimization but not a ranking signal.
Time to First Byte (TTFB)
How long the server takes to respond. Good: under 800ms. On Shopify, TTFB is typically 200–800ms and largely depends on Shopify's infrastructure. You can influence it by simplifying Liquid templates and reducing metafield lookups, but you can't change the underlying server.
The Performance Score: What It Means (and Doesn't Mean)
The big number at the top of your PageSpeed Insights report (0–100) is the Lighthouse Performance Score. It's a weighted average of multiple metrics:
| Metric | Weight | Impact on Score |
|---|---|---|
| Total Blocking Time (TBT) | 30% | Highest — reducing JavaScript blocking time has the biggest score impact |
| Largest Contentful Paint (LCP) | 25% | Critical — speed of main content appearing |
| Cumulative Layout Shift (CLS) | 25% | Important — visual stability during loading |
| First Contentful Paint (FCP) | 10% | Moderate — speed of first visible content |
| Speed Index (SI) | 10% | Moderate — visual loading progression |
Key insight: TBT (30%) has the biggest impact on your score. Reducing JavaScript blocking time — by deferring render-blocking scripts — is the single most effective way to improve both your performance score and real-world INP. This is exactly what Thunder automates.
What the score doesn't mean: A higher score doesn't automatically mean better rankings. Google uses field Core Web Vitals (LCP, CLS, INP) for rankings, not the lab-based performance score. A store with a 65 score but passing field CWV will rank better (all else equal) than a store with an 85 score but failing field CWV. Don't chase a perfect 100 — focus on getting Core Web Vitals into the green range. For more context, see what's a good Shopify speed score. If your TBT is high, a speed optimization app like Thunder can dramatically reduce it — check plans to see which fits your store.
Reading the Diagnostics Section
Below the metrics, PageSpeed Insights shows Diagnostics — specific issues identified on your page. These are sorted by potential impact. Here are the most common Shopify diagnostics and what they mean:
"Reduce unused JavaScript"
Third-party app scripts that load on every page but aren't used on this specific page. Solution: remove unused apps, or use a script optimizer to defer non-critical scripts. See our guide on third-party script impact.
"Eliminate render-blocking resources"
CSS and JavaScript files blocking the browser from rendering content. The #1 LCP killer on Shopify. Read our render-blocking resources fix guide.
"Largest Contentful Paint image was lazily loaded"
Your hero image has loading="lazy" — remove it and add fetchpriority="high" instead. See our LCP fix guide.
"Serve images in next-gen formats"
Images are in JPEG/PNG instead of WebP/AVIF. If you use Shopify's image_url filter, WebP is served automatically. Custom images uploaded to the content area may not benefit from this. See our image optimization guide.
"Avoid large layout shifts"
Lists specific elements that shifted during loading. Click to see each element and its shift contribution. Fix by adding image dimensions, reserving space for dynamic content, and optimizing fonts. See our CLS fix guide.
"Reduce the impact of third-party code"
Shows which third-party scripts (apps, analytics, chat widgets) are affecting your score and how much they contribute to blocking time. Use this to decide which apps are worth keeping.
Shopify's Speed Score vs PageSpeed Insights
Your Shopify admin shows a speed score under Online Store → Themes → Speed. This score is not the same as PageSpeed Insights, and here's why they differ:
| Feature | Shopify Speed Score | PageSpeed Insights |
|---|---|---|
| What it tests | Random sample of pages from your store | The specific URL you enter |
| Comparison basis | Other Shopify stores on similar themes | Absolute performance thresholds |
| Update frequency | Periodically (not real-time) | Live test each time you run it |
| Used for SEO rankings | No | Indirectly (via field CWV data) |
Which should you care about? For SEO, focus on PageSpeed Insights (field data) and Google Search Console's Core Web Vitals report. Shopify's built-in score is useful as a general comparison against other Shopify stores, but it's not what Google uses. For more detail, see Shopify speed score vs PageSpeed Insights.
What to Fix First: Your Priority Order
After reading your speed test, follow this priority order for maximum impact:
Move "Needs Improvement" CWV to "Good" (orange → green)
These are borderline — a small improvement gets you into the green zone where the ranking boost applies
Reduce Total Blocking Time
TBT has the highest score weight (30%) and correlates with real-world INP. Defer scripts and remove unused apps.
Address high-impact diagnostics
Work through the diagnostics list from top to bottom — they're sorted by potential impact. Focus on the items with red/orange indicators.
The Fastest Path: Fix Most Issues in 30 Seconds
If your main issues are render-blocking scripts, unoptimized images, and CSS delivery (they usually are), Thunder handles all three automatically. Install it, run your speed test again, and see how many diagnostics disappear.
Free plan available · No credit card · See results instantly
Frequently Asked Questions
What is a good Shopify speed test score?
On mobile, a PageSpeed Insights score of 50–70 is average for Shopify stores, 70–85 is good, and 85+ is excellent. On desktop, scores of 80+ are typical and 90+ is good. Focus less on the overall score number and more on passing all three Core Web Vitals (LCP under 2.5s, CLS under 0.1, INP under 200ms) — these are what Google actually uses for rankings.
Why does my speed score change every time I test?
Lab-based speed tests simulate loading your page and are affected by network conditions, server load at the moment of testing, and background processes. Variations of 5–10 points between tests are completely normal. For reliable results, run the test 3–5 times and look at the median score, or rely on field data (CrUX) which averages real user experiences over 28 days. Read more in our guide on why speed scores vary.
What's the difference between field data and lab data?
Field data comes from real Chrome users visiting your store over the past 28 days — it's what Google uses for rankings. Lab data is from a simulated test run right now with controlled conditions (specific device, network, and location). Field data is more trustworthy for SEO decisions; lab data is more useful for debugging because you can see detailed diagnostics and timing breakdowns.
Which metrics should I fix first?
Prioritize the three Core Web Vitals that are in red or orange: LCP (Largest Contentful Paint), CLS (Cumulative Layout Shift), and INP (Interaction to Next Paint). Among these, fix whichever is furthest from the 'good' threshold first. If all three pass, look at Total Blocking Time and Speed Index for additional improvements. Don't chase a perfect 100 score — passing Core Web Vitals matters far more for SEO and user experience.
How do I test my Shopify store speed from different locations?
Use WebPageTest (webpagetest.org) to run speed tests from servers in specific countries — useful if your customers are global. GTmetrix also lets you pick test locations. For Shopify specifically, our free speed test at thunderpagespeed.com/tools/speed-test uses Google's PageSpeed Insights API to test your store. Always test on mobile with 4G throttling enabled, as that's how most shoppers experience your store and how Google evaluates Core Web Vitals.
Does Shopify's built-in speed score differ from PageSpeed Insights?
Yes. Shopify's speed score in the admin dashboard uses Lighthouse (the same engine as PageSpeed Insights) but tests a random sample of your pages and compares results against other Shopify stores on similar themes. PageSpeed Insights tests a specific URL with Google's standard configuration. The scores will usually differ. For SEO purposes, focus on PageSpeed Insights and Google Search Console — those reflect what Google actually uses.