PageSpeed refers to a web page’s loading speed — more precisely: how quickly content becomes visible and usable for visitors. The term established itself via Google’s analysis tool of the same name, “PageSpeed Insights”, as an umbrella term for web performance and today covers far more than the pure load time in seconds: it stands for a bundle of metrics describing how smooth a page feels.
Why PageSpeed counts
Two reasons make loading speed one of a website’s most important technical quality attributes:
- User behaviour: the longer a page loads, the more visitors bounce before seeing any content at all, even more pronounced on mobile devices than on desktop. That costs enquiries and revenue, entirely independent of search engines.
- Ranking: Google evaluates the user experience via the Core Web Vitals as a ranking signal, above all in mobile search. A slow page competes against faster rivals with the handbrake on.
The most important metrics
At the centre stand the three Core Web Vitals, each with its own glossary entry:
- Largest Contentful Paint (LCP) — how fast the largest visible content loads (target: under 2.5 seconds)
- Interaction to Next Paint (INP) — how fast the page reacts to input
- Cumulative Layout Shift (CLS) — how stable the layout stays while loading
Supporting values follow, such as time to first byte (server response time) and first contentful paint, as well as the four Lighthouse categories performance, SEO, accessibility and best practices, which many tools output as scores from 0 to 100.
Lab and field data
In PageSpeed measurement, two data worlds meet. Lab data comes from simulated measurement runs under controlled conditions, with Lighthouse, for instance. It’s immediately available and reproducible but doesn’t reflect every real usage situation. Field data is collected by Google via the Chrome User Experience Report from real visitors; it’s the basis of the ranking evaluation but appears aggregated over a 28-day window and thus heavily delayed. For practice that means: lab data for diagnosing and monitoring, field data for validating.
Measuring and monitoring PageSpeed
For spot measurements, PageSpeed Insights and Lighthouse (in the Chrome DevTools) are the standard, complemented by the Core Web Vitals reports in Google Search Console. The blind spot of all these tools: they only measure on demand or with weeks of delay.
Since websites change continuously (updates, new content, additional scripts), values typically degrade gradually and unnoticed. Serious performance work therefore includes continuous monitoring that measures automatically and alerts on regressions. How that works is described on our PageSpeed monitoring page; with SiteSentry we provide a free tool for it that builds on the official Google PageSpeed API.
Typical PageSpeed brakes
The most common causes of poor values are astonishingly constant: unoptimised images in outdated formats, render-blocking CSS and JavaScript, a sprawling plugin and tracking stack, missing caching and sluggish server response times. Web fonts shifting the layout as they load additionally worsen CLS.
Conclusion
PageSpeed isn’t a state to be reached once but a property that must be actively maintained, built technically clean, measured regularly and monitored permanently. We support you with analysis and implementation as part of our PageSpeed optimisation or in a free first conversation.