Core Web Vitals: Technical SEO Guide

Core Web Vitals are the three field metrics Google uses to describe how a page feels to a real visitor: how fast the main content loads, how quickly the page responds to a tap or click, and how much the layout jumps around while it settles. They are part of Google's ranking systems, and unlike most SEO signals you can measure and fix them yourself. This guide explains what each metric means, how to audit them with free tools, and the specific changes that move the numbers.

What Core Web Vitals actually measure

Core Web Vitals are a subset of a wider set of page-experience signals. They exist because raw "page speed" is too blunt to describe what a person notices. Each vital targets a distinct moment in the experience: seeing the page, using the page, and trusting that it will not shift under your finger.

• Largest Contentful Paint (LCP) measures loading. It marks the moment the largest visible element, usually a hero image, heading, or block of text, finishes rendering. A good LCP is 2.5 seconds or less.
• Interaction to Next Paint (INP) measures responsiveness. It looks at how long the page takes to visually respond after a user interacts, across the whole visit rather than just the first tap. A good INP is 200 milliseconds or less.
• Cumulative Layout Shift (CLS) measures visual stability. It scores how much visible content moves unexpectedly while the page loads. A good CLS is 0.1 or less.

According to web.dev, a page passes only when it hits the "good" threshold for all three metrics at the 75th percentile of page loads. That percentile matters: it means three out of four of your real visitors need a good experience, so a fast test on your own laptop is not proof of anything.

Field data versus lab data

There are two ways to measure these metrics, and confusing them is the most common mistake in a Core Web Vitals audit.

Field data (also called real user monitoring) comes from actual Chrome users and is aggregated in the Chrome User Experience Report, or CrUX. This is the data Google uses for ranking. INP and the pass or fail verdict in Search Console come from the field.

Lab data comes from a single simulated load in a controlled environment, such as the Lighthouse run inside PageSpeed Insights. Lab data is repeatable and great for debugging, but it cannot produce a real INP score because there is no human interacting with the page.

How to audit your Core Web Vitals for free

You do not need a paid platform to get an accurate picture. Three free Google tools cover the whole workflow, and using them is a core part of any honest SEO audit routine.

1. PageSpeed Insights gives you both field and lab data for a single URL, plus a prioritised list of opportunities. Start here for any individual page.
2. The Search Console Core Web Vitals report groups every URL on your site into "good", "needs improvement", and "poor" buckets by mobile and desktop. Google's own Core Web Vitals documentation points you here to see performance at scale.
3. Chrome DevTools and the web-vitals JavaScript library let you reproduce and debug specific interactions, which is essential for chasing down a bad INP.

Work from the report to the page: let Search Console tell you which template is failing, then load a representative URL into PageSpeed Insights to see why.

Fixing Largest Contentful Paint

Slow LCP almost always traces back to the resource that renders the largest element. Common causes and fixes:

• A slow server response. Reduce time to first byte with caching, a content delivery network, and a faster host. LCP cannot beat the time it takes to deliver the HTML.
• Render-blocking CSS and JavaScript. Inline only the critical CSS your theme needs and defer the rest so the browser can paint sooner.
• Unoptimised hero images. Serve modern formats such as WebP or AVIF, size the image to the space it occupies, and add a high fetch priority so the browser loads it first.
• Lazy-loading the wrong image. Never lazy-load the element that is your LCP candidate. That guarantees a slow score.

Fixing Interaction to Next Paint

INP is usually a JavaScript problem. The browser runs your scripts on a single main thread, and while it is busy it cannot respond to a tap. To improve INP:

• Break up long tasks so the browser can respond between chunks of work.
• Remove or defer third-party scripts you do not truly need, especially heavy tag managers, chat widgets, and ad code.
• Avoid doing expensive work inside an interaction handler; show a quick visual response first, then finish the work.
• Reserve heavy rendering for when it is actually visible instead of building large hidden components up front.

Fixing Cumulative Layout Shift

CLS is often the quickest win because the causes are predictable:

• Images and videos without dimensions. Always set width and height attributes or a CSS aspect ratio so the browser reserves the space before the media loads.
• Ads, embeds, and iframes. Reserve a fixed slot for anything injected after load so it does not push content down.
• Web fonts. A late-swapping font can reflow a whole paragraph. Preload key fonts and use a sensible font-display strategy.
• Content inserted above existing content. Cookie banners and notification bars should overlay the page or occupy reserved space rather than shove everything down.

Where Core Web Vitals fit in technical SEO

Core Web Vitals are a real ranking signal, but a modest one, and they are a tiebreaker rather than a magic lever. Google has been clear that relevant, helpful content still comes first: a fast page with weak content will not outrank a slow page that answers the query better. Treat vitals as part of a broader technical SEO program that also covers crawlability, indexing, and internal links, all of which sit inside a healthy overall SEO strategy.

The practical payoff of good vitals is often bigger for users than for rankings. Faster, more stable pages convert better and bounce less, so the effort pays for itself even before any ranking change. Once your vitals are green, keep an eye on them the same way you watch broken links or ranking drops: run a periodic check with a ranking checker and a broader SEO checker so a regression on one template does not go unnoticed.

Frequently asked questions

What are the three Core Web Vitals?

The three Core Web Vitals are Largest Contentful Paint (LCP), which measures loading; Interaction to Next Paint (INP), which measures responsiveness; and Cumulative Layout Shift (CLS), which measures visual stability. A page is considered good when it meets the target for all three.

What are the good thresholds for Core Web Vitals?

Google's "good" thresholds are an LCP of 2.5 seconds or less, an INP of 200 milliseconds or less, and a CLS of 0.1 or less. A page needs to meet each threshold at the 75th percentile of real visits, meaning most visitors get a good experience.

Did INP replace FID?

Yes. Interaction to Next Paint became a stable Core Web Vital in 2024, replacing First Input Delay. INP is a better measure because it looks at the responsiveness of interactions across the whole visit rather than only the first one, so guidance written around FID is now outdated.

Do Core Web Vitals affect Google rankings?

Yes, but modestly. Core Web Vitals are part of Google's page-experience signals and can act as a tiebreaker between pages of similar relevance. They will not push weak or irrelevant content to the top, so they should complement good content rather than replace it.

What is the difference between field data and lab data?

Field data comes from real Chrome users and is what Google uses for ranking; it is the source of your INP score and your Search Console verdict. Lab data comes from a single simulated load and is ideal for debugging, but it cannot measure real interactions. Use lab data to find causes and field data to confirm fixes.

Which free tools measure Core Web Vitals?

PageSpeed Insights shows both field and lab data for a single URL, the Search Console Core Web Vitals report groups every page on your site by status, and Chrome DevTools with the web-vitals library helps you debug specific interactions. Together they cover a full audit without any paid tooling.