Page Speed and Core Web Vitals: How They Affect Rankings

Page speed affects rankings because Google uses Core Web Vitals as part of its page experience signals, and slow pages frustrate users into leaving. The three vitals measure loading, interactivity, and visual stability. Improving them lifts both your search position and your conversion rate. This guide explains each metric and the fixes that move the numbers.

Key Takeaways

Core Web Vitals are three specific metrics Google uses to judge real-world page experience, and they feed directly into ranking.
Largest Contentful Paint measures how fast the main content loads, and it should land under 2.5 seconds.
Interaction to Next Paint replaced First Input Delay in 2024 and measures responsiveness, targeting under 200 milliseconds.
Cumulative Layout Shift measures unexpected movement of page elements and should stay below 0.1.
Speed is a tie-breaker rather than an override, so it rarely beats strong content but often separates similar pages.
Field data from real users matters more than lab scores, because Google grades you on what visitors actually experience.

Why Speed Became a Ranking Factor

Google confirmed page experience as a ranking signal because slow, unstable pages drive users away. When a result loads quickly and behaves predictably, people stay, and Google reads that as a satisfied searcher.

The business case is blunt. Google research found that as page load time rises from one second to three seconds, the probability of a bounce increases by 32 percent, and by five seconds the probability climbs to 90 percent.

Speed as a Tie-Breaker

Google has been clear that content relevance still leads. Speed acts as a differentiator when two pages are otherwise comparable in quality and authority.

That framing matters for prioritisation. If your content is weak, fixing speed alone will not rescue rankings, which is why a broader SEO content audit should run alongside performance work.

The User Experience Payoff

Even setting rankings aside, speed pays for itself in conversions. Deloitte research across retail and travel sites found that a 0.1 second improvement in load time increased retail conversions by 8.4 percent and average order value by 9.2 percent.

That is a direct revenue lever. Faster pages sell more, regardless of what Google does with the signal.

The Three Core Web Vitals Explained

Core Web Vitals distil page experience into three measurable metrics. Each targets a different moment in how a page feels to use.

Largest Contentful Paint

LCP measures how long it takes for the largest visible element, usually a hero image or headline block, to render. It answers the question: has the main content appeared yet?

The thresholds are:

Good: under 2.5 seconds
Needs improvement: 2.5 to 4 seconds
Poor: over 4 seconds

Slow LCP usually traces back to server response time, render-blocking resources, or heavy unoptimised images.

Interaction to Next Paint

INP replaced First Input Delay in March 2024. It measures how quickly the page responds visually after a user interacts, across the whole visit rather than just the first tap.

The thresholds are:

Good: under 200 milliseconds
Needs improvement: 200 to 500 milliseconds
Poor: over 500 milliseconds

Poor INP almost always points to heavy JavaScript blocking the main thread when a user clicks or types.

Cumulative Layout Shift

CLS measures how much visible content moves unexpectedly while the page loads. The classic offender is a button that jumps just as you go to tap it.

The table below summarises all three vitals and their targets.

Metric	Measures	Good threshold
LCP	Loading of main content	Under 2.5 seconds
INP	Responsiveness to input	Under 200 milliseconds
CLS	Visual stability	Under 0.1

Google grades a page as passing only when the 75th percentile of real visits meets the good threshold on all three.

Measure Before You Optimise

You cannot fix what you have not measured, and there are two kinds of data that tell very different stories. Knowing which one Google uses keeps you focused.

Lab Data Versus Field Data

Lab data comes from a controlled test in a tool like Lighthouse, run once under fixed conditions. Field data comes from real Chrome users and lives in the Chrome User Experience Report.

Google ranks on field data. Lab tests are useful for diagnosis and repeatable debugging, but the grade that affects your position reflects genuine visitor experiences.

Tools Worth Using

Use these together for a full picture:

PageSpeed Insights shows both lab and field data for a single URL.
Search Console Core Web Vitals report groups your whole site by status.
Chrome DevTools lets you profile interactions and spot main-thread blocking.

Start with the Search Console report, because it surfaces which URL groups fail and how many pages sit in each bucket. That prioritises your effort across the site rather than one page at a time.

Practical Fixes for Each Vital

Each vital responds to a specific set of fixes. Working through them in order of impact avoids wasted effort on marginal gains.

Improving LCP

The biggest LCP wins usually come from images and server response:

Serve images in modern formats such as WebP or AVIF and size them correctly for their container.
Preload the LCP image so the browser fetches it early.
Reduce server response time with caching and a content delivery network.
Remove render-blocking CSS and JavaScript from the critical path.

Image handling is often the single largest factor. Our image SEO guide covers compression and format choices in more depth.

Improving INP

INP problems are JavaScript problems. Reduce the work the main thread does when users interact:

Break long tasks into smaller chunks so the browser can respond between them.
Defer or lazy-load non-essential scripts, including third-party tags.
Audit analytics, chat widgets, and ad scripts, which frequently cause the worst delays.

Third-party scripts are the usual culprit. Each one you add competes for the same main thread your users need for interactions.

Improving CLS

CLS fixes are mostly about reserving space before content loads:

Set explicit width and height attributes on images and video.
Reserve space for ads and embeds so they do not push content down.
Avoid inserting content above existing content unless a user triggers it.
Use font-display strategies that prevent large layout shifts when web fonts load.

These changes are low-risk and high-reward, because they rarely affect functionality while directly stabilising the layout.

Build Speed Into Your Workflow

One-off optimisation decays. New images, plugins, and scripts creep in over time, so speed needs to be a habit rather than a project.

Set a Performance Budget

A performance budget is a hard limit on page weight, script count, or load time that every new addition must respect. When a proposed feature blows the budget, someone has to justify or trim it.

Budgets turn speed from an afterthought into a gate. They stop the slow, invisible bloat that erodes vitals month after month.

Audit Regularly

Schedule a monthly review of the Search Console vitals report. Watch for URL groups slipping from good into needs improvement, which is your early warning before rankings react.

Pair this with your wider technical checks. If you run WordPress, the steps in our WordPress SEO checklist include several performance items worth folding into the same routine.

Do Not Over-Optimise at Content's Expense

Stripping every script can harm the experience you were trying to protect. A chat widget that drives leads may be worth a small INP cost.

Weigh each element against its business value. The goal is a fast page that still does its job, not a hollow page that scores well and converts nobody.

Frequently Asked Questions

Are Core Web Vitals a major ranking factor?

They are a genuine but modest factor. Google has described page experience, including Core Web Vitals, as a tie-breaker between pages of similar relevance and quality. Strong content on a slower page will usually still outrank thin content on a fast one, so treat vitals as important but secondary to substance.

What is the difference between INP and the old First Input Delay?

First Input Delay measured only the delay before the browser began processing the first interaction. Interaction to Next Paint measures the full response time across all interactions during a visit, including the visual update. INP is a stricter, more representative metric, which is why Google replaced FID with it in March 2024.

Should I trust my Lighthouse score or my Search Console data?

Search Console field data reflects real users and is what Google ranks on, so trust it for your grade. Lighthouse lab data is best for diagnosing problems in a controlled, repeatable way. Use Lighthouse to find and fix issues, then confirm the improvement in field data over the following weeks.

How quickly will fixing speed improve my rankings?

Field data updates on a rolling 28-day window, so improvements take several weeks to register fully in the Chrome User Experience Report. Any ranking effect follows after that. Expect a lag of one to two months before you can fairly judge whether the work moved your position.

Does mobile or desktop speed matter more?

Mobile matters more, because Google uses mobile-first indexing and most searches happen on phones. Mobile devices also tend to have slower processors and connections, so they expose performance problems that desktop hides. Always test and optimise for mobile first.