Is Site Speed a Google Ranking Factor?

Yes, site speed is a confirmed Google ranking factor, on the record since 2010 on desktop and 2018 on mobile. In 2026 it is formalized through the Page Experience system, with Core Web Vitals (LCP, INP, CLS) as the specific measurable inputs. Google describes it as a tiebreaker between pages of similar quality. The weight is small per URL but consistent, and it matters most in competitive verticals where everything else is close. Speed will not outrank stronger content, but it will decide close fights and stop you from being held back behind faster competitors.

Google has been explicit about this on the record:

• April 2010: Google announced that site speed would be incorporated as a signal in its search ranking algorithms for desktop search. The original blog post by Amit Singhal and Matt Cutts is still online.
• January 2018: The 'Speed Update' rolled out, making page speed a ranking factor for mobile search. Google was clear that the update affected the slowest pages most.
• June 2021: The Page Experience update launched, combining Core Web Vitals (LCP, FID, CLS), HTTPS, mobile usability, and intrusive interstitial rules into a composite signal. This formalized the speed input through field measured metrics.
• March 2024: FID was replaced by INP, a more demanding responsiveness metric. INP measures every interaction across the page lifecycle, including the slowest one.
• 2026: Page Experience and Core Web Vitals remain ranking inputs, with the same CrUX field data methodology.

This is not speculation, leaked patent reading, or correlation analysis. It is documented Google policy. The only honest debate is about weight, not existence.

The terms 'site speed' and 'page speed' are often used interchangeably, but they have slightly different meanings:

• Site speed describes how fast your site is on average across all pages and users. It is a useful overview metric for monitoring and reporting.
• Page speed describes how fast a specific URL loads for a specific user on a specific device. It is the unit Google actually measures and ranks on.

For SEO purposes, page speed is the more accurate term, because Google evaluates Core Web Vitals at the URL level (with origin level fallback when there is not enough URL data). A site can have great average page speed and still have specific URL templates that fail Core Web Vitals and get held back in search.

In casual usage, 'site speed and SEO' and 'page speed and SEO' refer to the same topic: how the speed of your site affects search rankings. The distinction matters when you start diagnosing problems, because the answer to 'is my site fast' depends on which template, which device, and which user.

Google does not publish the exact weight of each ranking factor, but several patterns are clear from public statements and observed behavior:

• Speed is one signal among hundreds. Content relevance, link authority, freshness, intent match, and entity understanding all carry more direct weight.
• Speed is part of Page Experience, which itself is one composite ranking input. Page Experience also includes mobile usability, HTTPS, and intrusive interstitials.
• Page Experience is documented as a tiebreaker. Google has repeatedly described it as a way to choose between pages of similar quality, not as a way to override content quality.
• Speed is mobile first. Google uses the mobile version of your page for indexing and ranking, so mobile Core Web Vitals are what affect your rankings.

For the full breakdown of the Page Experience system, see the [Google Page Experience guide.

The honest answer is that Google has never published a number, and external estimates are speculative. What we can say with confidence:

• The direct weight per URL is small. A single passing Core Web Vitals score will not vault you from page two to position one.
• The cumulative weight across a site is larger. If every URL template passes CWV, you benefit consistently across the long tail of queries.
• The effective weight in competitive search is larger than the raw weight, because most ranking battles are between similar pages where small inputs decide outcomes.
• The indirect weight through engagement signals (bounce, conversion, pogo sticking) is often larger than the direct ranking signal.

Our 2026 study of 37,000 ranking pages sizes the effect directly: page-one Google results pass Core Web Vitals 47.6% of the time versus 44.2% on page two, and among competitive, high-traffic sites the gap widens to 7.6 points. A reasonable mental model: think of speed as worth 1 to 3 positions of movement in close ranking battles, with the effect compounding when combined with strong content. In a vertical where every result already has comprehensive content and credible links, those 1 to 3 positions decide who gets the click.

If you are deciding how much time to invest in speed:

1. If you have weak content or thin pages, fix those first. Speed will not help if the underlying page is not competitive on relevance and quality.
2. If you have strong content but failing Core Web Vitals, speed work has high payoff. You are leaving rankings on the table that you have already earned through content.
3. If you have strong content and passing CWV, additional speed work pays back through conversion lift and engagement, not through additional ranking gains.
4. If you are in a competitive vertical, treat passing CWV on mobile as table stakes. Every serious competitor will be at or near passing, and being slower puts you on the wrong side of the tiebreaker.

For the full how to on each Core Web Vital, see the complete Core Web Vitals guide. If you want a team that owns the diagnosis and the fixes, our Core Web Vitals optimization service handles speed work end to end.