Guide

Core Web Vitals and Rankings: What Actually Matters

Core Web Vitals are a real ranking input, but a small one. They rarely explain a big traffic drop on their own, so check them without letting them distract you from the real cause.

Core Web Vitals affect rankings, but modestly. They are three measurements of how fast, responsive and stable a page feels, and Google uses them as part of its page experience signals. They seldom explain a large drop by themselves. Fix them because they cost you visitors and sales, then look for the cause of the drop elsewhere.

What the three metrics measure

Core Web Vitals are three measurements of real visits to your pages.

MetricWhat it measuresGood threshold
Largest Contentful Paint (LCP)How long until the main content appears2.5 seconds or less
Interaction to Next Paint (INP)How quickly the page responds when someone taps or clicks200 milliseconds or less
Cumulative Layout Shift (CLS)How much the page jumps around while loading0.1 or less
Google's published thresholds for a Good score, measured at the 75th percentile of visits.

INP replaced First Input Delay as the responsiveness metric in 2024. If an old audit still talks about FID, it is out of date.

How much do they matter for rankings

Google has said plainly that page experience is one of many signals, and that relevance and content quality still lead. A slow, unstable page can lose to a similar page that loads well. A fast page with weak content will not beat a strong one.

So think of vitals as a way to avoid losing a close contest, and as a way to stop visitors leaving. The wider question is covered in our short answer on whether site speed affects rankings.

How to check your own vitals

Search Console

Open the Core Web Vitals report. It groups URLs by status (Poor, Needs improvement, Good) for mobile and desktop, using field data from real Chrome users. Pages with too little traffic may have no data at all.

PageSpeed Insights

Enter a single URL. You get field data where it exists and a lab test with specific suggestions. Use the lab test to find causes and the field data to judge the real situation.

Common causes

What usually makes vitals Poor

Heavy hero images

Large unoptimised images or sliders slow LCP on the pages that matter most.

Too much JavaScript

Scripts that block the main thread make taps feel slow and hurt INP.

Late loading elements

Ads, banners and embeds that appear after load push content around and raise CLS.

Slow server response

A slow first byte delays everything that follows.

Third party tags

Chat widgets, trackers and fonts from other sites add weight you do not control.

Images without sizes

No set width and height means the layout shifts when each image arrives.

Step by step: what to fix first

  1. Open the Core Web Vitals report and find the page groups marked Poor.
  2. Pick the group that covers the most traffic or revenue, such as product pages or the main article template.
  3. Run a representative URL through PageSpeed Insights and note which metric fails.
  4. Fix at the template level. One change to a template can move hundreds of URLs.
  5. Re-test, then wait. Field data is a rolling window, so improvements take time to show in Search Console.

Rendering problems that delay content can cause poor scores and indexing trouble together, which we cover in JavaScript SEO rendering problems.

Field data versus lab data

This is where most owners get confused. Field data comes from real Chrome users visiting your site over roughly the last 28 days. It is what Google uses. Lab data is one simulated test, run once, on a set connection and device. It is useful for finding causes, but it can show a green score on a page real visitors find slow.

Two practical rules follow. Judge success by the Core Web Vitals report, not by a single lab score. And test the mobile view first, because most sites have more mobile visitors and mobile scores are usually worse.

What not to chase

Do not spend weeks pushing a lab score from 90 to 100. Once a page passes the Good thresholds for real users, the ranking benefit stops growing. Time is better spent on content, links and crawl health.

Do not trust a plugin that promises a perfect score in one click. Some defer scripts in ways that break checkout forms or hide content from Google. Always re-test after a change, and check that the page still renders in the URL Inspection tool.

Vitals versus the real cause of a drop

If your traffic fell sharply, do not assume vitals are the cause because the report shows red. Check the timing. Did the drop line up with a change in vitals, a core update, a migration or a crawl problem? A site can have poor vitals for years and rank fine.

Look first at whether pages are being crawled and indexed at all. Our guide on crawl budget explains how crawling problems hide behind other symptoms. Performance work belongs inside a wider technical check, which is what our technical SEO fixes service covers.

When to call for help

Get help when the report shows Poor across the whole site and you cannot tell which template to fix, when fixes are not moving field data after several weeks, or when traffic has dropped and you need to know whether vitals are involved at all. That last one is a diagnosis question, and it is the one we answer first.

Ask for a free SEO triage and we will tell you whether Core Web Vitals are part of the cause or a side issue.

FAQ

Questions owners ask us

Do Core Web Vitals affect rankings?

Yes, they are part of the page experience signals Google uses. Google also says great content can rank well even with a weaker page experience, so treat vitals as a tiebreaker and a user experience fix, not a magic switch.

Which Core Web Vital should I fix first?

Fix whichever one Search Console marks as Poor on your most valuable page types. In practice that is often Largest Contentful Paint, because slow main content hurts both readers and the metric. Start with the template that covers the most URLs.

Why does PageSpeed Insights disagree with Search Console?

PageSpeed Insights shows a lab test of one page, plus field data when available. Search Console reports field data from real Chrome users, grouped by URL pattern. Field data is what Google uses, so trust that when they differ.

Get started

Tell us where it hurts.

Your site, what changed and when. We reply with a first read on the cause.