Why Your Mobile Score Is Far Worse Than Desktop
Mobile PageSpeed scores run lower than desktop because Google throttles CPU and network to simulate a mid-range phone. Here's how to diagnose and fix the gap step by step.
Your mobile PageSpeed score is lower than desktop because Google’s testing tool simulates a mid-range phone with CPU throttled to roughly a quarter of a typical laptop’s speed, running on a slow 4G connection profile — not because your site genuinely serves a broken version to phones. The fix isn’t to chase the number for its own sake; it’s to reduce the actual page weight, JavaScript execution time, and render-blocking resources that a real mid-range phone on a real mobile network would also struggle with.
This gap catches almost everyone off guard the first time they run PageSpeed Insights: desktop scores 95, mobile scores 52, same URL, same content. The instinct is to assume something is misconfigured. Usually nothing is — the test conditions are just far apart, and mobile conditions are the ones that matter for ranking and for the majority of your visitors.
What causes the gap between mobile and desktop PageSpeed scores?
PageSpeed Insights runs two separate lab tests with different throttling profiles. Desktop testing applies light throttling that roughly resembles a fast laptop on broadband. Mobile testing applies a much heavier CPU slowdown multiplier and simulates a slower, higher-latency network, modelling a mid-tier Android phone rather than a flagship device on Wi-Fi. Every millisecond your page takes to parse HTML, execute JavaScript, and paint content gets stretched further under that mobile profile.
The three biggest contributors to a wide mobile-desktop gap are usually the same three things: JavaScript that blocks the main thread longer on a slower CPU, images sized for desktop viewports that still get downloaded (even if displayed smaller) on mobile, and third-party scripts — ads, chat widgets, analytics — that execute regardless of device and hit mobile’s limited processing budget hardest.
| Test condition | Desktop (PageSpeed Insights) | Mobile (PageSpeed Insights) |
|---|---|---|
| CPU throttling | Light (roughly 1x baseline) | Heavy (roughly 4x slowdown) |
| Network profile | Minimal latency, high bandwidth | Simulated slow 4G, higher latency |
| Simulated device | Standard laptop-class | Mid-tier Android phone |
| Typical score gap | Baseline | 20-40 points lower on the same URL |
Once the test conditions are visible side by side, the score gap stops looking like a bug and starts looking like exactly what it is: the same page under a much less forgiving simulation.
How do you diagnose what’s actually slowing mobile down?
Follow this order before changing anything — fixing symptoms without a diagnosis wastes a development sprint.
- Run PageSpeed Insights on the live URL and open the “Diagnostics” section, which ranks opportunities by estimated time savings, not alphabetically.
- Check the field data panel (Chrome UX Report) if it’s populated — this tells you what real visitors on real devices experienced over the last 28 days, separate from the lab simulation.
- Open the Lighthouse trace for a waterfall view of what’s blocking the main thread — look specifically at “Reduce JavaScript execution time” and “Minimize main-thread work.”
- Cross-check Search Console’s Core Web Vitals report, which segments mobile and desktop URLs separately and shows which URL groups are failing which metric.
How do you fix a low mobile PageSpeed score?
Once you know what’s blocking the main thread, the fixes fall into a predictable order of impact.
Five fixes, ranked by typical impact
- Defer or remove non-critical JavaScript — High impact. Split code so only what’s needed for the first paint loads immediately; defer the rest.
- Compress and correctly size images — High impact. Serve WebP/AVIF at the actual display size for mobile viewports, not a downscaled desktop image.
- Eliminate render-blocking CSS/JS — Medium-high impact. Inline critical CSS, load the rest asynchronously.
- Audit and trim third-party scripts — Medium impact. Every ad network, chat widget, and tracking pixel adds main-thread work that’s identical on mobile and desktop but costs mobile more.
- Improve server response time (TTFB) — Medium impact. Caching, a CDN, and a faster host reduce the baseline before any rendering even starts.
What common mistakes make the mobile-desktop gap worse?
- Testing over Wi-Fi and assuming mobile is “fine.” A phone on office Wi-Fi doesn’t experience the throttled network condition the score is modelling — test with real network throttling in Chrome DevTools to see what the score sees.
- Loading desktop-sized hero images on mobile and relying on CSS to shrink them visually. The full file still downloads; use responsive
srcsetor a CDN that serves device-appropriate sizes. - Treating the lab score as the goal instead of the field data. A 95 lab score with poor real-user Core Web Vitals in Search Console means the lab test isn’t matching what visitors actually experience — trust the field data.
- Stacking multiple ad networks or A/B testing tools that each inject their own JavaScript, compounding main-thread work in a way that’s invisible until you check the trace.
Does the mobile score actually affect rankings?
Indirectly, but meaningfully. Google has used mobile-first indexing for years, meaning it primarily crawls and ranks the mobile version of your pages. The lab score from PageSpeed Insights isn’t itself a ranking signal, but the real-user Core Web Vitals it’s designed to predict — Largest Contentful Paint, Interaction to Next Paint, Cumulative Layout Shift — are part of Google’s page experience signals. A site that’s fast on desktop but slow on mobile is being judged, and indexed, primarily on the slow version.
Frequently asked questions
Why is my mobile PageSpeed score so much lower than desktop?
PageSpeed Insights tests mobile under a simulated mid-tier phone CPU with roughly 4x throttling and a slow 4G network profile, while desktop is tested with minimal throttling. The gap mostly reflects that simulated hardware and network difference, not two different versions of your site.
Does a low mobile PageSpeed score directly hurt rankings?
The lab score itself isn’t a ranking factor, but the real-user Core Web Vitals it’s meant to predict are part of Google’s page experience signals, and Google indexes and ranks primarily on the mobile version of your site. A slow mobile experience affects both rankings and conversion.
Should I optimise for the lab score or real user data?
Real user data from the Chrome UX Report, visible in Search Console and PageSpeed Insights, matters more because it reflects actual visitors on actual devices. Use the lab score to diagnose and prioritise fixes, but confirm improvement in the field data before declaring the problem solved.
Can I ever get a 90+ mobile PageSpeed score?
Yes, but it requires deliberate work: a lightweight page weight, minimal render-blocking JavaScript, properly sized images, and a fast server response. Sites with heavy ad stacks, large JS frameworks, or third-party widgets will find 90+ difficult without removing or deferring that weight.
Sources
- About PageSpeed Insights — Google for Developers
- Core Web Vitals: The Complete Guide
- Technical SEO: The Complete Working Guide
- How to Fix INP (Interaction to Next Paint)
- Image Dimensions and CLS: The Two-Attribute Fix
Want this done on your site?
Every PalV’s DM engagement starts with a free audit of your actual website — a 12-point
crawl covering what is blocking indexation, on-page gaps against your primary keywords, speed
findings, and the three to five fixes worth making first. Delivered in two working days. No
payment details, and the findings are yours whether you hire us or not.
