If you’ve opened Google Search Console recently, you’ve probably seen a “Core Web Vitals” report with a handful of URLs marked “Needs improvement” or “Poor,” and three unfamiliar abbreviations attached to them. Most site owners know this is supposed to matter for SEO, but not exactly what it’s measuring or what a “good” number looks like.
Core Web Vitals are a set of three metrics Google uses to measure real-world user experience on a page: how fast the main content loads, how quickly the page responds when someone interacts with it, and how visually stable it is while loading. They’re part of Google’s broader page experience signals, and while content quality and relevance still matter far more for rankings, a page with a genuinely poor experience can hold itself back.
The Three Core Web Vitals
Largest Contentful Paint (LCP) — Loading Speed
LCP measures how long it takes for the largest visible element on the page — usually a hero image, a heading, or a large text block — to fully render for the user. It’s meant to approximate when the page feels “loaded” from the visitor’s point of view, rather than measuring every last resource on the page.
What counts as good: Under 2.5 seconds. Between 2.5 and 4 seconds is “needs improvement,” and anything above 4 seconds is “poor.”
What commonly causes poor LCP: Large uncompressed images, slow server response times, render-blocking CSS or JavaScript loaded before the main content, and fonts that load in a way that delays visible text.
Interaction to Next Paint (INP) — Responsiveness
INP replaced an older metric called First Input Delay in 2024, and it measures how quickly the page responds across every interaction a user makes during their visit — not just the first click, but every tap, scroll trigger, or keypress that expects a visible response.
What counts as good: Under 200 milliseconds. 200–500ms needs improvement, and above 500ms is poor.
What commonly causes poor INP: Heavy JavaScript execution that blocks the browser’s main thread, too many third-party scripts (chat widgets, ad tags, analytics tools) competing for processing time, and large, unoptimized DOM structures.
Cumulative Layout Shift (CLS) — Visual Stability
CLS measures how much content unexpectedly shifts around while the page is loading. You’ve experienced bad CLS if you’ve ever tried to tap a button and had an ad load in above it at the last second, shoving the button down and making you click the wrong thing.
What counts as good: A CLS score under 0.1. 0.1–0.25 needs improvement, and above 0.25 is poor.
What commonly causes poor CLS: Images or ads without reserved dimensions, web fonts that swap in and change text size, and content injected dynamically above existing content.
How Google Actually Uses This Data
It’s worth being precise here: Core Web Vitals scores in Search Console are based on field data — real measurements from actual visitors using the Chrome browser over a rolling 28-day period — not a one-time lab test. That’s why a page can look fine when you personally load it but still show as “poor” in Search Console: your own test doesn’t reflect your real audience’s devices, connections, and locations.
Google has stated that page experience is one signal among many, and that it generally can’t override strong, relevant content. A page with excellent Core Web Vitals but thin or unhelpful content still won’t outrank a page that thoroughly answers the query. Treat Core Web Vitals as a tiebreaker and a user-experience issue worth fixing in its own right, not a silver bullet for rankings.
Where to Check Your Scores
- Google Search Console → Core Web Vitals report, under the “Experience” section, shows URLs grouped by status (Good/Needs improvement/Poor) using real field data.
- PageSpeed Insights shows both field data (if enough traffic exists for a page) and lab data from a simulated test, plus specific diagnostic suggestions.
- Chrome UX Report (CrUX) is the underlying public dataset that both tools draw field data from.
What “Passing” Actually Requires
A URL is considered to have “good” Core Web Vitals only when all three metrics meet the good threshold for at least 75% of page visits measured. It’s not an average — a page can have a great typical experience and still fail the report if a meaningful share of visits (say, users on slow mobile connections) have a poor experience.
FAQs
Q.1 Are Core Web Vitals a direct ranking factor?
They’re part of Google’s page experience signals, which factor into ranking, but content relevance and quality carry far more weight. Google has said good Core Web Vitals won’t help a page with weak content outrank one with strong content.
Q.2 Why does Search Console show no data for some of my pages?
Field data requires enough real-world traffic to be statistically meaningful. Low-traffic pages often show “not enough data” rather than a score.
Q.3 What replaced First Input Delay?
Interaction to Next Paint (INP) became the official responsiveness metric in March 2024, replacing First Input Delay because it measures responsiveness across the whole visit rather than just the first interaction.
Q.4 Can third-party scripts really hurt my Core Web Vitals?
Yes — chat widgets, ad networks, and tracking scripts are among the most common causes of poor INP because they consume processing time on the main thread.
Q.5 Does mobile or desktop data matter more?
Google evaluates them separately, and since indexing is mobile-first, mobile Core Web Vitals typically deserve more attention if your site’s report shows a gap between the two.
Q.6 How long does it take for a fix to show up in the report?
Since the report uses a rolling 28-day window of real user data, it can take several weeks after a fix ships before Search Console reflects the improvement.
