Google PageSpeed Insights scores a page out of 100 by loading it in a test lab, and on the mobile tab that lab pretends to be a mid range phone on a slow mobile connection. That is why the same site can score 95 on desktop and 60 on mobile without anything being wrong with the test. The score is a summary of a few timings, it moves a few points from run to run, and on its own it is not what Google ranks you on. The measurements underneath it are the part worth understanding.
Two tests, not one
The desktop test loads your page on a fast machine over a fast connection. The mobile test slows the processor down several times over and throttles the network to something like a weak 4G signal.
That handicap is deliberate. Most people who find a local business do it on a phone, and plenty of those phones are a few years old. A page that is fine on an office computer can take several seconds to become usable in someone's hand.
So compare mobile with mobile and desktop with desktop. A gap between the two is normal. A mobile score in the 50s or 60s next to a desktop score in the 90s is common, and it almost always means the page is asking the browser to do too much work.
The measurements behind the number
Largest Contentful Paint is how long until the biggest thing on the screen, usually a heading or a main image, has appeared. Google's line for good is two and a half seconds.
Total Blocking Time is how long the page is too busy running code to respond to a tap. It is the lab's stand in for how responsive the page feels.
Cumulative Layout Shift is how much the page jumps around while it loads. Under 0.1 is good, and zero is achievable.
First Contentful Paint and Speed Index describe how soon something appears and how quickly the rest fills in. They carry less weight in the score, but a slow first paint is usually the first thing a visitor notices.
Lab scores and real visitors
Above the lab test, PageSpeed sometimes shows a second section about what your real users are experiencing. That comes from Chrome users who actually visited the page over the previous 28 days.
It only appears once a site gets enough traffic, which many small business sites do not. When it is there, it matters more than the lab score, because it is what happened rather than what a test predicts. Those real visitor measurements are the Core Web Vitals that Google uses in search.
The two can disagree. A page can score 100 in the lab and still fail with real visitors whose phones and connections are worse than the test assumes.
Why the score changes every time
Each run loads the page again on a shared machine over a real network, and small differences in timing move the result. A page that scores 96 once may score 92 the next time with nothing changed.
Run it three times and look at the spread before drawing any conclusion. One bad run is noise. Three runs in the same range is the number.
What usually drags a mobile score down
Too much JavaScript doing work before the page can respond. Animation libraries, sliders, chat widgets and tracking scripts all compete for the same slow processor.
A main image or heading that waits for something before it can appear: a script, a font, or an animation that starts from invisible.
Images far larger than the screen they are shown on.
When we fixed our own site, most of the gain came from the first two. The mobile score went from 60 and 75 across two runs to 97 the same evening, and the only thing a visitor lost was an animation on phones.
Questions people ask
- Does my PageSpeed score affect my Google ranking?
- Not the score itself. Google uses Core Web Vitals measured from real visitors as one signal among many, and relevance still outweighs speed. A slow page costs you more through the visitors who leave before it loads than through the ranking.
- Do I need a score of 100?
- No. Anything in the 90s is in good shape, and chasing the last few points rarely changes anything a visitor would notice. What matters more is getting mobile out of the orange and the real visitor measurements into the green.
- Why is my mobile score so much lower than desktop?
- Because the mobile test simulates a slower phone on a slower connection. A big gap usually points at JavaScript: the page is asking a phone's processor to do more than it comfortably can before it becomes usable.
We do this
If you would rather have it done than do it, this is the part of what we offer that covers it.