How to Track Core Web Vitals for SEO Success and Analysis Fast Today
What Are Core Web Vitals and Why Do They Matter?
Core Web Vitals are Google’s measurements of how fast a page’s main content appears, how quickly the page reacts to input, and how much its layout jumps around, and they are built from data on real visitors. The current set is Largest Contentful Paint (LCP), Interaction to Next Paint (INP), and Cumulative Layout Shift (CLS).
The scores come from opted-in Chrome users, and each metric is judged at the 75th percentile of visits, so a page needs most of its audience to have a decent experience, not just the average visitor. Scoring also splits by device. According to Ahrefs, mobile signals have counted for ranking since May 2021, and desktop signals followed in February 2022.
The list of vitals is not fixed. INP took over from First Input Delay on March 12, 2024, so any checklist should be treated as a snapshot. On the weight of these signals, Google’s Gary Illyes spoke about them at Pubcon in September 2023, and Ahrefs notes that Google representatives have called Core Web Vitals tiny factors or tiebreakers among over 200 ranking factors.
What Scores Do the Core Web Vitals Metrics Need to Hit?
A page meets Google’s targets when LCP is 2.5 seconds or less, INP is 200 milliseconds or less, and CLS is 0.1 or less.
Those limits cover three metrics: LCP tracks loading performance, INP tracks responsiveness, and CLS tracks visual stability. Before INP arrived, First Input Delay stood for interactivity, and Seobility cites a good FID as under 100 milliseconds.
Search Console and Ahrefs publish the same grid of bands, summarized in the table. A metric slides from Good into Needs improvement past the first limit and into Poor past the second: 500 milliseconds for INP and 0.25 for CLS, with LCP crossing at 4 seconds.
| Metric | Measures | Good | Needs improvement | Poor |
| LCP | Loading | 2.5 seconds or less | Up to 4 seconds | Over 4 seconds |
| INP | Reactions to input | 200 milliseconds or less | Up to 500 milliseconds | Over 500 milliseconds |
| CLS | Layout steadiness | 0.1 or less | Up to 0.25 | Over 0.25 |
Judging happens by the weakest result. Search Console labels a page group with its worst-performing metric, so strong LCP and CLS scores cannot rescue a failing INP.
What Is Largest Contentful Paint and How Do You Speed It Up?
Largest Contentful Paint (LCP) is the time a page takes to render its single largest visible element, and Ahrefs rates it the hardest Core Web Vital to improve.
Two supporting measurements help explain a slow LCP: Time to First Byte shows how long the server takes to send the first byte, and First Contentful Paint marks when the first piece of content appears. Seobility lists PageSpeed Insights and the Chrome Web Vitals extension among the tools for analyzing Core Web Vitals, so either is a sensible first stop when LCP looks slow.
Ahrefs lists five levers for LCP:
- Prioritize the loading of key resources.
- Make files smaller.
- Serve files closer to users, the usual job of a CDN.
- Host resources on the same server.
- Use caching.
Search Console’s advice for non-technical users is to keep a page and all its resources under 500KB and to limit a page to 50 resources, a guideline aimed at phones. Ahrefs also points out that Cloudflare has rolled out Early Hints and other features meant to make sites faster.
What Is Interaction to Next Paint and Why Did It Replace First Input Delay?
Interaction to Next Paint (INP) is the time between a user’s action and the next frame the browser paints in response, and it replaced First Input Delay (FID) as a Core Web Vital.
INP gives a truer picture of real-world user experience because it observes every interaction in a visit, while FID only timed the first one. A slow reaction is also a separate problem from the unintentional clicks that layout shifts cause, which belong to CLS.
FID has no lab data counterpart, because a simulated environment has no visitor to interact with the page. Seobility suggests pairing Time to Interactive with Total Blocking Time as a stand-in, and teams that want real feedback can collect Real User Monitoring data from their own audience.
Ahrefs lists ways to relieve the delays behind weak interaction scores: send less script, load it later, break up long jobs, and lean on web workers, server-side rendering, or prerendering.
What Is Cumulative Layout Shift and How Do You Spot It?
Cumulative Layout Shift (CLS) is the sum of all individual layout shift scores on a page, where zero means nothing moved and larger numbers mean more movement.
In Google’s page-testing tool, the Diagnostics section names the LCP element, usually a featured image or an H1 tag but possibly a video, a background image, or large text blocks. Checking whether that same element moves is a quick way to link a loading problem to a shifting one, though that is practitioner advice rather than a documented rule.
A layout shift above the fold, inside the viewport, is where a link can jump just as someone reaches for it; Ahrefs describes ending up on an ad instead of the intended page. Ahrefs also lists making pages eligible for bfcache among the CLS fixes.
Which Tools Measure Core Web Vitals, and Where Does the Data Come From?
Core Web Vitals are measured with tools that read either real-visitor records or controlled test runs, and the official numbers come from Chrome’s user-experience dataset rather than from any single dashboard.
INP is built on the Event Timing API, which watches interactions across a whole visit, and CLS is limited to the five-second time frame where the most shifting happens. For hunting shifts, WebPageTest offers a Filmstrip View that highlights them, and Smashing Magazine once outlined every element with a 3px red line and filmed the page loading.
Search Console users can break performance down by country with BigQuery, and AMP pages get a live test through the AMP Page Experience Guide. Coverage is limited: Ahrefs studied over 42 million pages and found only 11.4% had metrics, and John Mueller has said signals from a section or the whole site may stand in when a page lacks data.
One related change affects news publishers: with these metrics in place, AMP was dropped as a requirement for the Top Stories feature, per Ahrefs.
What Does the Search Console Core Web Vitals Report Show?
The Core Web Vitals report in Search Console shows how a site’s pages perform using field data from CrUX, with each page group’s status taken from its worst metric.
In the report, LCP counts from the moment a user requests the URL, while INP covers every click, tap, and keyboard interaction and reports the longest interaction, ignoring outliers. Search Console applies the same status benchmarks as the grid above.
For a second opinion on a page, the report links out to testing tools, and the in-browser Lighthouse test is one option. SpeedVitals reads from the same CrUX source as Google’s own tools, and its history reaches back up to 12 months for a whole website.
Do not be alarmed when the chart total is smaller than the table total; the FAQ further down explains why.
How Do You Fix and Verify Core Web Vitals Problems?
Fixing Core Web Vitals means tackling the specific cause behind each failing metric and then confirming the repair in Search Console’s tracking window.
The causes Ahrefs names are clustered by metric, as the table shows.
| Metric | Common cause | Direction of the fix |
| CLS | Images without dimensions, plus ads, embeds and iframes without set sizes | Reserve space for each |
| CLS | Injecting content with scripts and late fonts | Optimize how fonts load |
| INP | JavaScript tasks hogging the main thread | Break up long tasks and load scripts later |
Search Console advises fixing the worst-rated URLs first. Within a group, URLs are ordered by impressions, descending, so the ones at the top move the group’s status most.
After shipping a fix, click Start Tracking to begin 28-day monitoring; the issue counts as fixed only if it appears on no URL during that window. The business case is softer: Ahrefs says better scores may support more conversions, though recording more analytics data could explain part of it.
Do Core Web Vitals Really Affect Search Rankings?
Core Web Vitals influence search results only lightly: Google says good scores align with what its core ranking systems seek to reward, yet Ahrefs calls them a minor ranking factor.
Seobility dates the metrics to 2020, and web.dev frames them as quality signals for user experience; Google’s documentation places them alongside other page experience aspects. Seobility adds that page speed had been a ranking factor for years before the vitals existed.
In practice, teams that treat the metrics as a user-experience project rather than a ranking tactic tend to get more from the effort, which is an observation, not a measured result. Ahrefs advises working with developers and, if you are on your own, relying on a plugin such as WP Rocket or Autoptimize, while platforms are rolling out features such as HTTP/3.
Why Does the Chart Show Fewer URLs Than the Table?
The chart shows fewer URLs than the table because the chart places each URL under only its worst problem, while the table lists a URL under every problem that affects it.
A URL with two different problems therefore shows up once in the chart but in two table rows. Each row stands for one of the URL groups of similar pages, and an origin group steps in when a group lacks enough data. Only indexed URLs appear, and the details table stops at 200 rows. Rows also carry a sparkline and a validation state of Pending, Passed, or Failed.
Why Did My Status Change When I Didn’t Change Anything?
A site’s Core Web Vitals status can change without any edit because pages sitting in a borderline status are easily nudged across a line by a site-wide event.
A jump in site traffic, or a change in latency from the service delivering your image files, can be enough. Less likely, a widely adopted browser version update or a wave of visitors on a slower network moves the numbers. Check your logs for browser, device, or location changes that line up with the shift.
Judge the size of the swing carefully: a URL is counted once in the chart under its slowest issue, while the table lists every issue, so compare like with like.