What Is Google PageSpeed Insights?
Google PageSpeed Insights (PSI) is a free tool at pagespeed.web.dev that analyzes the performance of any web page. Enter a URL, and it returns a performance score (0–100) along with detailed metrics, diagnostics, and recommendations.
For Shopify merchants, PSI is especially important because it's the same engine behind your Shopify admin speed score. Understanding PSI means understanding what's really happening with your store's performance — and what to fix first.
PSI provides two types of data: field data from real Chrome users visiting your site, and lab data from a simulated Lighthouse test. Both are useful, but they measure different things — and understanding the difference is crucial for making smart optimization decisions.
How PSI Works: Lab Data vs Field Data
This is the most important concept to understand about Google PageSpeed Insights. PSI shows two completely different datasets:
🔬 Lab Data (Lighthouse)
- • Simulated test on a controlled device
- • Emulates a Moto G Power on throttled 4G
- • CPU throttled to 4× slower than normal
- • Single test run — results vary each time
- • Produces the 0–100 performance score
- • Shows: FCP, LCP, TBT, CLS, Speed Index
Best for: Debugging specific issues, testing changes, comparing before/after
👥 Field Data (CrUX)
- • Real data from Chrome users visiting your site
- • Mix of all devices, connections, and locations
- • 28-day rolling average — very stable
- • Only available for sites with enough traffic
- • No single score — shows pass/fail per metric
- • Shows: LCP, INP, CLS (the Core Web Vitals)
Best for: Understanding real user experience, SEO impact assessment
💡 Key insight: Google uses field data for search rankings — not the lab score. A store with a lab score of 40 but passing field Core Web Vitals won't be penalized in search. However, lab data is still valuable for diagnosing specific issues and measuring the impact of optimizations.
Every PSI Metric Explained for Shopify
PSI's lab test measures six metrics. Here's what each one means specifically for Shopify stores, and what typically causes poor scores:
First Contentful Paint (FCP)
When the browser renders the first piece of content
Shopify context: FCP is delayed by render-blocking CSS and JavaScript in the <head>. Every Shopify app that injects a stylesheet or synchronous script pushes FCP later. Most Shopify stores have 3–8 render-blocking resources.
Fix: Inline critical CSS, defer non-critical JavaScript. Thunder does both automatically.
Largest Contentful Paint (LCP)
When the largest visible element finishes rendering
Shopify context: LCP on Shopify is usually the hero image or a large heading. It's affected by: render-blocking resources delaying the start, slow image loading (large files, no preloading), and Shopify's server response time (TTFB). For a deep dive, see our LCP optimization guide.
Fix: Preload hero image, inline critical CSS, defer render-blocking JS. Thunder handles all three.
Total Blocking Time (TBT)
How long the main thread is blocked by JavaScript
Shopify context: TBT is the single biggest factor in your PageSpeed score (30% weight). On Shopify, it's almost entirely caused by third-party app scripts — Klaviyo, Judge.me, chat widgets, upsell apps, and analytics tools all execute JavaScript that blocks the main thread. The simulated 4× CPU throttle makes this dramatically worse.
Fix: Defer all non-critical JavaScript so it doesn't block the main thread. This is Thunder's primary optimization — it defers app scripts while maintaining their functionality.
Cumulative Layout Shift (CLS)
How much visible elements move while the page loads
Shopify context: CLS on Shopify is commonly caused by: images without width/height attributes, web fonts loading late and changing text size, dynamically injected app content (popups, banners, review widgets), and slideshow/carousel transitions.
Fix: Set image dimensions, use font-display: swap, reserve space for dynamic content. Thunder's font optimization helps with font-related CLS.
Speed Index (SI)
How quickly visible content fills the viewport
Shopify context: Speed Index measures the overall visual loading experience. It's affected by everything — render-blocking resources, image loading order, CSS delivery, and JavaScript execution. Think of it as a "composite" metric.
Fix: Improving FCP and LCP automatically improves Speed Index. No separate action needed.
How to Read Your Shopify PSI Report
When you run your Shopify store through PageSpeed Insights, you'll see several sections. Here's how to read each one — or if you want a quick baseline first, test your store's performance with our free Shopify speed test:
Step 1: Check Field Data First
At the top of the PSI report, look for "Discover what your real users are experiencing." If your store has enough traffic, you'll see real Core Web Vitals (LCP, INP, CLS). Green checkmarks mean you're passing Google's ranking threshold — this is what matters most for SEO. If you don't have field data, your store doesn't have enough Chrome traffic yet.
Step 2: Look at the Performance Score
The big number (0–100) is the lab score. Remember: this is a simulated test on a throttled mobile device, not your real users' experience. It's useful for benchmarking and debugging, but don't obsess over it. For context, most Shopify stores score 20–50 on mobile.
Step 3: Check Which Metrics Are Red
The six metrics are color-coded. Focus on the red ones first — they have the most room for improvement. For most Shopify stores, TBT and LCP are the worst offenders. TBT is 30% of your score, so fixing it yields the biggest point gain.
Step 4: Review Opportunities & Diagnostics
Scroll down to "Opportunities" (things that save load time) and "Diagnostics" (structural issues). PSI estimates the time savings for each opportunity. Focus on items with the highest savings — typically "Eliminate render-blocking resources" and "Reduce unused JavaScript."
Step 5: Don't Chase Every Issue
PSI often flags 15–20 issues. Many have minimal impact (saving 50ms doesn't matter when TBT is 3,000ms). Focus on the top 3–5 opportunities with the highest estimated savings. That's where 80% of your improvement will come from.
The Easy Fix: Improve Your PSI Score by 27+ Points
After analyzing hundreds of Shopify PSI reports, we've found that 60–80% of the available improvement comes from just three optimizations: deferring render-blocking JavaScript, inlining critical CSS, and optimizing font loading. These are exactly what Thunder Page Speed Optimizer automates.
How Thunder fixes the most common PSI issues:
"Eliminate render-blocking resources"
Thunder defers all render-blocking JS and CSS, including third-party app scripts you can't control manually. Typical savings: 1–3 seconds.
"Reduce unused JavaScript"
Thunder defers non-critical JavaScript so it doesn't block the main thread, effectively removing it from the critical rendering path.
"Reduce unused CSS"
Thunder inlines only the critical CSS needed for above-the-fold content and loads the rest asynchronously.
"Ensure text remains visible during webfont load"
Thunder adds font-display: swap and preloads critical fonts automatically.
"Reduce the impact of third-party code"
Thunder controls when and how third-party scripts execute, reducing their impact on TBT.
Average improvement: +27 PageSpeed points
One-click install. No code changes. No theme modifications. Works with all Shopify themes and apps.
Free plan available · No credit card required · 30-second install · See Thunder pricing
Common Shopify Issues in PageSpeed Insights
Here are the PSI issues that Shopify stores encounter most frequently, ranked by typical impact:
"Eliminate render-blocking resources"
High Impact What it means: JavaScript and CSS files in your <head> prevent the browser from rendering anything until they download. On Shopify, these are mostly from apps — not your theme.
Typical savings: 1,000–4,000ms
Manual fix: Add defer to script tags, but this risks breaking app functionality. See our render-blocking resources guide. Thunder fix: Automatic — defers all scripts with dependency mapping.
"Reduce unused JavaScript"
High ImpactWhat it means: JavaScript files are loaded but not all code is used on the current page. Apps often load their full script bundle even when only a fraction is needed.
Typical savings: 500–3,000ms
Manual fix: You can't tree-shake third-party app code. Remove unused apps entirely. For a full walkthrough of all optimization techniques, see our complete speed optimization guide. Thunder fix: Defers unused scripts so they load after the page is interactive.
"Properly size images"
Medium ImpactWhat it means: Images are served at a larger resolution than displayed. A 4000×4000px product image displayed at 400×400px wastes 99% of the data.
Typical savings: 200–2,000ms
Manual fix: Use Shopify's image_url filter with width parameters. See our image optimization guide. Thunder fix: Partial — Thunder lazy-loads offscreen images but doesn't resize them.
"Reduce the impact of third-party code"
Medium ImpactWhat it means: Third-party scripts (analytics, chat, reviews, etc.) contribute significantly to TBT. PSI lists each domain and how much main thread time it consumes.
Manual fix: Remove apps or delay their loading with custom JavaScript. Complex and risky. Read our third-party scripts guide. Thunder fix: Automatic — manages all third-party script execution timing.
"Avoid an excessive DOM size"
Low-Medium ImpactWhat it means: Your page has too many HTML elements (over 1,500). Page builders like GemPages and PageFly often generate 3,000–6,000+ elements.
Manual fix: Simplify page structure, reduce sections, consider native theme sections over page builders. Thunder fix: Not applicable — this is a structural issue.
Why Mobile PageSpeed Scores Are Always Lower
Most Shopify merchants see a 20–40 point gap between their mobile and desktop PSI scores. This isn't a bug — it's by design. The mobile test is intentionally harsher:
📱 Mobile Test Conditions
- • Emulated Moto G Power (mid-tier phone)
- • CPU throttled to 4× slower
- • Simulated slow 4G connection
- • Viewport: 412×823px
- • Much harsher scoring thresholds
💻 Desktop Test Conditions
- • No specific device emulation
- • No CPU throttling
- • No network throttling
- • Viewport: 1350×940px
- • More lenient scoring thresholds
Which one matters more? Focus on mobile. Google uses mobile-first indexing, and the mobile test more closely reflects the conditions many of your customers experience. If your mobile score is good, your desktop score will almost certainly be good too.
PSI Score vs Shopify Admin Speed Score
Both use Google Lighthouse, but they differ in important ways:
| Factor | PageSpeed Insights | Shopify Admin Score |
|---|---|---|
| Pages tested | Any URL you choose | Homepage only |
| Number of runs | Single test | Averaged over multiple runs |
| Includes field data | Yes (if available) | No |
| Update frequency | On-demand | Periodic (varies) |
| Comparison | Absolute score | Compared to similar stores |
Differences of 5–15 points between the two are normal. Neither is "wrong" — they're just different measurement contexts. For optimization work, use PSI directly since it gives you detailed diagnostics and lets you test any page.
What Google Actually Uses for Search Rankings
Here's the truth most speed optimization articles skip: Google does NOT use your PageSpeed Insights lab score for rankings.
Google uses field data from the Chrome User Experience Report (CrUX) — real metrics from real Chrome users visiting your site. Specifically, Google looks at three Core Web Vitals:
LCP
Largest Contentful Paint
≤ 2.5s to pass
INP
Interaction to Next Paint
≤ 200ms to pass
CLS
Cumulative Layout Shift
≤ 0.1 to pass
To pass Core Web Vitals, at least 75% of your real users need to have "good" experiences for all three metrics. You can check your field data at the top of any PSI report, or in Google Search Console under Core Web Vitals.
💡 Practical takeaway: If your PSI report shows passing field data (green checks at the top), your speed is fine for SEO — even if the lab score looks scary. If you don't have field data yet, improving your lab score is still worthwhile because it correlates with better real user experiences.
Frequently Asked Questions
What is Google PageSpeed Insights?
Google PageSpeed Insights (PSI) is a free tool by Google that analyzes page performance and provides both lab data (simulated tests via Lighthouse) and field data (real user metrics from the Chrome User Experience Report). It scores pages 0–100 and measures Core Web Vitals like LCP, CLS, and TBT. For Shopify stores, it's the same engine behind the speed score in your Shopify admin.
What is a good PageSpeed Insights score for Shopify?
A score of 90–100 is 'good' (green), 50–89 is 'needs improvement' (orange), and 0–49 is 'poor' (red). Most Shopify stores score 20–50 on mobile due to third-party apps and scripts. A realistic target for most merchants is 60–80. Thunder users typically reach 70–90+ without manual code changes.
Why does my Shopify PageSpeed score differ from the Shopify admin speed score?
Both use Google Lighthouse, but with different test conditions. Shopify runs the test on your homepage using specific server settings and averages multiple runs. PageSpeed Insights lets you test any page and shows a single run. Differences of 5–15 points are normal. Neither is 'wrong' — they're just different measurement contexts.
Does Google PageSpeed Insights score affect SEO?
The score itself is not a direct ranking factor, but the Core Web Vitals it measures (LCP, CLS, INP) are confirmed Google ranking signals. Google uses field data from real users — not the lab score — for rankings. However, improving your lab score typically improves field data too, so optimizing for PSI indirectly helps your SEO.
Why is my Shopify mobile PageSpeed score so much lower than desktop?
PSI's mobile test simulates a mid-tier phone (Moto G Power) on a throttled 4G connection with a 4× CPU slowdown. This is dramatically harsher than the desktop test, which uses an unthrottled connection and faster CPU. JavaScript-heavy Shopify stores are hit hardest because the throttled CPU takes much longer to parse and execute scripts. Most stores score 20–40 points lower on mobile than desktop.
How often should I run PageSpeed Insights on my Shopify store?
Run PSI after any major change (new app install, theme update, content change). For routine monitoring, weekly is sufficient — but always average 3–5 runs since individual results vary. Thunder includes daily automated monitoring that tracks your score over time, which is more reliable than manual spot checks.
Can Thunder fix the issues PageSpeed Insights finds?
Yes, Thunder automatically fixes the most common and impactful PSI issues for Shopify: render-blocking resources, unused JavaScript, unoptimized CSS delivery, font loading issues, and third-party script impact. These typically account for 60–80% of the available improvement. Issues like image optimization and DOM size require manual work or additional tools.