Does page speed affect Google rankings?

What Google says about speed and ranking, what it does not say, and how to treat speed: a real but modest factor next to relevance and content.

BeginnerExplainer5 min readUpdated October 29, 2026

In this guide
  1. What Google says
  2. What it means in practice
  3. The reasons to care that do not depend on Google
  4. What to do about it
  5. Myths to ignore
  6. Check your own page
  7. Sources

What Google says

Google's Search documentation is the place to look, and over the last few years it has said the same things in several ways:

Read together, these statements say that speed is a signal, and that it is not a trump card.

What it means in practice

A fast page with weak content will not rank for a search it does not answer. Speed does not make a page relevant. If the page does not give the searcher what they came for, nothing in this guide will fix that.

When many pages answer a search about equally well, experience can help. This is the case Google describes. In competitive searches, where several pages are similar in what they offer, being easy to use is one of the things that can separate them.

Failing the Core Web Vitals is worth fixing, and it is not a penalty box. A page that does not pass is missing one signal that Google says it uses. That is a reason to improve it, not evidence that the page will be hidden.

Nobody outside Google knows how large the effect is. Google does not publish the weight of each signal, and it changes its systems often. Treat claims such as "speed is the most important ranking factor" or "speed is irrelevant to SEO" with the same suspicion: neither is supported by what Google says.

The reasons to care that do not depend on Google

The most certain reason to speed a site up is the visitor. A slow page is harder to use, a page that jumps or ignores taps is frustrating, and visitors who are frustrated leave. That is true whatever the ranking effect turns out to be.

How much faster pages are worth in leads or sales depends on the site. You can find out for your own business instead of guessing:

  1. Pick a group of pages that matter, such as the services pages or the product pages.
  2. Record a baseline for a few weeks: the real-user Core Web Vitals, and from your analytics the number of visitors who contact you or buy.
  3. Fix the failing metric on those pages.
  4. Compare after four to six weeks, remembering that the real-user data takes about four weeks to catch up. Allow for the season and for anything else that changed.

This will not give you a precise number, but it will tell you whether speed was holding that group of pages back.

What to do about it

  1. Check your field data first. Open the Core Web Vitals report in Search Console, or PageSpeed Insights for one page, and see whether your important pages pass. The measuring guide shows where each number comes from.
  2. Fix the failing metric on the pages that matter most. Start where visitors and revenue are, not where the report is longest.
  3. Do not chase a perfect lab score. The lab score is a summary of one test. Google judges real visits.
  4. Keep investing in content. The best speed work cannot make up for a page that does not answer the search.
  5. Check again every few months. Sites get slower as plugins, scripts and large images are added.

Myths to ignore

Check your own page

Run the free audit and see whether your page passes the Core Web Vitals for real visitors, mobile and desktop. If it passes, keep an eye on it. If it fails, the report shows which metric to start with, and the guides linked from it show how to fix it.

Sources

Start here

Free website audit

Live Google data for any public page: mobile and desktop.

Mobile + desktop · Lighthouse lab test · Real-user Chrome data when Google has it

Rather have this done for you? Core Web Vitals · Book a call

Related guides

All guides →