What Is Page Speed?

How Page Speed Works

Page speed describes how quickly a page loads and becomes usable — but “loads” hides a chain of events, and page speed really covers all of them. The browser has to reach the server and get the first byte back (Time to First Byte), download and parse the HTML, fetch the CSS, images, and scripts it references, render content to the screen, and finally become responsive to taps and clicks. A page can be slow at any link in that chain, and “page speed” is the catch-all for the visitor’s total experience of waiting.

Because it spans so much, page speed isn’t one number. It is measured two different ways. Lab data comes from a simulated load in a controlled tool like Lighthouse — repeatable and great for debugging, but run on one machine under set conditions. Field data comes from real Chrome users on their real devices and networks, aggregated in the Chrome UX Report. The two often disagree, and it matters which you trust: Google’s ranking systems use field data, because that is what real people actually experienced.

This is also where page speed and Core Web Vitals connect. Core Web Vitals are Google’s attempt to pin the fuzzy idea of “speed and smoothness” to three concrete, thresholded metrics: LCP for loading, INP for responsiveness, and CLS for stability. Page speed is the concept; Core Web Vitals are the measuring instruments.

Example of Page Speed

The best-documented moment for page speed as a ranking factor is Google’s Speed Update, which rolled out to all users on July 9, 2018. Before it, Google had used speed as a ranking signal only for desktop search. The Speed Update was the first time mobile page speed officially entered the mobile ranking algorithm.

What Google said about the update is as instructive as the update itself, and it corrects a lot of hype. Three points from the announcement:

• It only affected the slowest pages — the ones delivering the worst experience to users — and left the vast majority of sites untouched.
• It affected only a small percentage of queries.
• Query intent remained a very strong signal. In Google’s own words, a slow page can still rank highly if it has great, relevant content.

In other words, the Speed Update was a floor, not a leaderboard. It demoted genuinely frustrating experiences rather than rewarding incremental speed gains, and it never let speed override relevance. That posture has carried straight through to Core Web Vitals and page experience: fast pages don’t outrank relevant ones; speed breaks ties and keeps the worst offenders from ranking on experience alone.

The lesson generalizes to how you should spend effort. Because the ranking benefit concentrates at the slow end and intent dominates, the highest-value work is finding and fixing your slowest important templates — measured against real-user field data — rather than optimizing a page that already loads fine into an even greener lab score. Speed is worth doing for users regardless of rankings; abandonment climbs with every extra second. But as an SEO lever specifically, it is a “don’t be slow” requirement, not a “be fastest” competition.

Page Speed vs Core Web Vitals

The two terms get used interchangeably, but they operate at different levels: one is the goal, the other is the ruler.

The practical takeaway: when someone asks you to “improve page speed,” the concrete, measurable version of that request is “pass Core Web Vitals against real-user data.” Core Web Vitals are simply how the abstract goal of page speed became a set of numbers you can actually target — and, at the slow end, the numbers Google’s page experience systems act on.

Frequently Asked Questions

The Bottom Line

Page speed is the plain-language goal — pages that load fast and feel responsive — while Core Web Vitals are the measuring stick Google built to grade it. Speed matters for rankings mainly at the slow end, where it demotes frustrating experiences, and it matters everywhere for keeping users from leaving. Measure it against real visitors, and clear the bar rather than chasing a perfect score.