Core Web Vitals: a practical guide
Your page loads, but something feels off. The heading shows up, then an ad banner drops in and pushes everything down, so you tap the wrong link. That small annoyance has a name, a number, and an audience: Google is measuring it.
Core Web Vitals are three metrics Google uses to measure how a page feels to load and use: Largest Contentful Paint for loading, Interaction to Next Paint for responsiveness, and Cumulative Layout Shift for visual stability. The targets are LCP under 2.5 seconds, INP under 200 milliseconds, and CLS below 0.1.
What each Core Web Vitals metric measures
Each metric maps to a moment in the page experience. LCP marks when the biggest visible thing, usually a hero image or headline, finishes rendering. INP tracks the delay between a tap or click and the screen actually responding, across the whole visit. CLS adds up how much the layout jumps around while things load. A page can score well on one and badly on another, so you treat them separately.
How to check your scores
Start with field data, because that reflects real visitors on real devices. The Core Web Vitals report inside Google Search Console groups your URLs into good, needs improvement, and poor, based on the last 28 days of Chrome traffic. For a single page and a list of fixes, run it through PageSpeed Insights. Lab tools like Lighthouse are fine for debugging, but the field numbers are what Google counts.
Fixing a slow LCP
Slow LCP almost always comes down to the hero image or a render-blocking resource. Compress and correctly size that lead image, serve it in a modern format, and add a preload hint so the browser fetches it early. Cut down blocking CSS and JavaScript in the head, and put a cache or CDN in front of your server so the first byte arrives quickly. These moves sit near the top of any technical SEO checklist.
Fixing sluggish INP
Poor INP means the main thread is busy when someone interacts. Heavy JavaScript is the usual culprit. Break long tasks into smaller chunks, defer scripts you do not need right away, and remove third-party tags that no longer earn their keep. Every analytics pixel and chat widget runs code, and each one competes for the same thread your buttons need.
Fixing layout shift
CLS comes from elements that arrive without a reserved spot. Set width and height attributes on images and video so the browser holds space before they load. Reserve room for ads and embeds instead of letting them push content down. Load web fonts in a way that avoids a late swap that reflows your text. Most CLS problems disappear once nothing loads into empty, unmeasured space.
Test on mobile first
Google evaluates Core Web Vitals per device type, and most sites fail on mobile long before desktop. Phones have slower processors and patchier networks, so a page that feels instant on your laptop can crawl on a mid-range Android on 4G. Throttle your testing to a slower device profile, and judge the page by that experience rather than your office fibre connection. The gap can be dramatic, and a page that passes on desktop but fails on mobile still counts as failing where most of your visitors are. Check both device tabs in Search Console rather than assuming one speaks for the other.
Common mistakes that quietly hurt your scores
The pattern I see most is teams optimising the homepage and ignoring templates. Your product pages, blog posts, and category pages each have their own vitals, and they often share a bloated component that tanks every URL at once. Fix the template, not the single page. Watch out for oversized hero images uploaded at 4000 pixels wide, autoplaying video, and a stack of marketing tags nobody has audited in a year.
Do Core Web Vitals actually move rankings?
Yes, but modestly, and mainly as a tie-breaker. Google treats page experience as a light ranking signal, so great vitals will not rescue thin content, and a fast page with a strong match to search intent tends to win. I think of Core Web Vitals as table stakes: fix them so speed stops holding you back, then spend your real energy on content and links. If you want to see where you stand today, our free SEO tools flag the pages dragging your scores down, and a free site audit pairs those numbers with the fixes that matter first.
Where this fits in your wider SEO work
Core Web Vitals belong to the technical layer, alongside crawlability and indexing. Once they are green, work through a full SEO audit and tighten your on-page SEO so the fast page also answers the query well. Speed gets people to stay; content and relevance get you ranked. Measure the change in SEO ROI over a quarter, not a week, because vitals improvements show up gradually as Google recrawls.
Frequently asked questions
What are good Core Web Vitals scores?
Aim for Largest Contentful Paint under 2.5 seconds, Interaction to Next Paint under 200 milliseconds, and Cumulative Layout Shift below 0.1. Google measures these at the 75th percentile of your real visitors, so a few slow sessions will not sink you, but the typical experience needs to clear the bar.
Are Core Web Vitals a ranking factor?
Yes, but a light one. Google uses page experience, including Core Web Vitals, as a tie-breaker rather than a heavy signal. Great scores will not outrank genuinely better content, and poor scores rarely sink a page that answers the query well. Fix them so speed stops holding you back, then focus on content.
What is the difference between field data and lab data?
Field data comes from real Chrome users who visited your site over the past 28 days, and it is what Google uses for ranking. Lab data comes from a simulated test on a single device, useful for debugging but not for judging real performance. When the two disagree, trust the field data.
Why did INP replace First Input Delay?
Google swapped First Input Delay for Interaction to Next Paint in 2024 because FID only measured the first interaction and the delay before processing began. INP measures every interaction across the whole visit and the full time until the screen updates, so it reflects real responsiveness far more honestly than FID ever did.
How long do Core Web Vitals fixes take to show up?
The field data in Search Console runs on a rolling 28-day window, so improvements appear gradually rather than overnight. Expect two to four weeks before your scores fully reflect a fix, and longer for Google to recrawl and re-evaluate every affected page across a large site. Patience beats refreshing the report daily.
Want this done for your site?
Run a free audit and see exactly what to fix for Google and AI search.