Products SEO & GEO Agent Paid Ads Agent Website Agent Conversion Agent
How it works Pricing FAQ Blog Book a call

Core Web Vitals monitoring: track LCP, INP and CLS over time

Updated · 6 min read

Short answer Check Search Console's Core Web Vitals report once a month: it uses real Chrome visitors, updates daily, and keeps three months of history. For a longer trend, CrUX Vis shows 40 weeks. Every number is a rolling 28-day average, so a fix takes about four weeks to show. INP replaced FID in March 2024.

Want help applying this to your business? Talk it through on a free 30-minute call.

Book a call

How to monitor Core Web Vitals: which tool shows what

Use Search Console for the monthly check, CrUX Vis for the long trend, and PageSpeed Insights to test one page. All three read the same source: the Chrome UX Report (CrUX), Google's record of how real Chrome visitors experienced your pages. Google Analytics shows nothing about Core Web Vitals until a developer adds code.

ToolShowsUpdatesHistory
Search Console, Core Web Vitals reportYour pages in groups, mobile and desktop apartDaily, 28-day averageThree months
CrUX Vis (free, no setup)Your site or one busy page as a trend lineWeekly, on Mondays40 weeks
PageSpeed InsightsOne page today, plus a lab testDaily, 28-day averageNone
CrUX History APISame data as CrUX Vis, for your own sheet or reportWeekly40 weeks
GA4 with the web-vitals codeEvery visit, any page, any browser that supports itAs visits happenYour GA4 data

Sources: Chrome for Developers (CrUX tools; CrUX History API). The History API is free but needs a Google Cloud API key.

Skip the old CrUX Dashboard in Looker Studio. Chrome's team announced in September 2025 that it would be retired after November 2025 and pointed users to CrUX Vis instead (Chrome for Developers: CrUX Dashboard deprecation).

What changed: INP replaced FID

The three metrics are now LCP, INP and CLS. FID (First Input Delay) is retired.

"INP will officially become a Core Web Vital and replace FID on March 12 of this year" (web.dev, 2024)

FID left Search Console that same day. A dashboard, plugin or checklist still tracking FID is measuring the wrong thing.

MetricPlain meaningGoodPoor
LCP, Largest Contentful PaintTime until the main image or text shows2.5 seconds or lessOver 4 seconds
INP, Interaction to Next PaintTime the page takes to react to a tap, click or key200 milliseconds or lessOver 500 milliseconds
CLS, Cumulative Layout ShiftHow much the page jumps while loading0.1 or lessOver 0.25

Thresholds: Search Console Help (Core Web Vitals report). In between is "Need improvement." Whether these numbers move your rankings is covered in Core Web Vitals and Google ranking.

INP needs real people tapping, so lab tests often can't report it. Google's web.dev says "The best way to measure your website's INP is by gathering metrics from actual users in the field," and suggests Total Blocking Time as a rough lab stand-in.

A 15-minute monthly check in Search Console

  1. Open Search Console, then the Core Web Vitals report. Look at the mobile chart first.
  2. Compare the Poor, Need improvement and Good counts with last month. Note them in a sheet. The chart only keeps three months, so your sheet is your long-term record. The Export button also saves the chart and table.
  3. Open any Poor row. Each example URL stands for a group of similar pages, and the group takes the status of its worst metric.
  4. Fix Poor first, then the issues touching the most pages or your most important ones. That's the order Search Console Help recommends.
  5. Run the example URL in PageSpeed Insights to see what to fix.

Pages appear only once there's enough data. Search Console Help says a group with too little data rolls up into one group for your whole site, and with less than that you see "No data available." That's normal for a small site. If you hit it, test your top two or three pages in PageSpeed Insights each month instead.

Why your numbers don't move right after a fix

Every Google tool here averages the last 28 days. A fix made today shares the window with three weeks of old visits, so the line bends slowly.

Search Console lets you track this. After a fix, open the issue and click Start Tracking (on some screens, Validate fix):

"Click Start Tracking to start a 28-day monitoring session to check for instances of this issue in your site." (Search Console Help: Core Web Vitals report)

It doesn't speed anything up. Google says it "does not trigger re-indexing or any other active behavior." If any page still shows the issue, validation fails; fix it and start a new one.

Status changed, but you changed nothing

That happens. Search Console Help explains that pages sitting near a line can tip over after a site-wide event: a spike in traffic, a slower image host, a big browser update, or more visitors on slow networks. Data from every country is combined, so a wave of visitors on slow connections pulls the whole site down.

What to check, in order:

  • Did you add anything site-wide: a chat widget, booking embed, tracking tag or new theme?
  • Did traffic jump, for example from an ad campaign?
  • Are the group's numbers just over a line, like an LCP of 2.6 seconds? Then a small fix brings it back.

Tracking Core Web Vitals in GA4

GA4 doesn't collect them out of the box. Google's free web-vitals code library, about 3 KB, measures LCP, INP and CLS on each visit and sends them to GA4 as events (GoogleChrome/web-vitals on GitHub). The library's own guide notes that GA4's built-in reports can't show how the values are spread across visits. Google's web.dev guide sends the data to BigQuery, Google's data warehouse, for the analysis.

Worth it when:

  • Your site is too small for Search Console or CrUX Vis to show anything.
  • You need to know which page, device or traffic source is slow.
  • A developer already maintains your GA4 setup.

Not worth it when Search Console already shows your pages as Good. For most owners, the free monthly check is enough.

Example

Illustrative cases, not measured results.

A roofer's mobile pages turn Poor

The March check shows 40 mobile pages Poor on LCP. The example page loads a 3 MB photo at the top. The web designer compresses it and the roofer clicks Start Tracking. About four weeks later validation passes and the chart shows the pages as Good.

A dental office sees "No data available"

Too few Chrome visitors for field data. Each month the office runs its home page and booking page in PageSpeed Insights and writes the lab LCP and Total Blocking Time in a sheet. After it removes an unused chat script, Total Blocking Time drops.

An accounting firm's INP slips in tax season

Nothing changed on the site, but traffic tripled in April and a new booking widget went live in March. CrUX Vis shows INP rising over eight weeks, from the week the widget launched. The firm loads the widget only on the booking page.

FAQ

How often should I check Core Web Vitals?

Monthly is enough for most small sites, plus four weeks after any redesign, new theme or new widget. Google sets no schedule; the data moves slowly because it's a 28-day average.

Why is my site not in the Core Web Vitals report?

Too few Chrome visitors for Google to report on. Use PageSpeed Insights' lab test on your main pages instead.

Does Google Analytics show Core Web Vitals?

Not by default. A developer has to add Google's web-vitals code to send them, and deeper analysis needs BigQuery.

Should I still track FID?

No. INP replaced it on March 12, 2024, and Search Console dropped it that day. Update any tool or report that still shows FID.

Do PageSpeed Insights and Search Console disagree?

Often. PageSpeed Insights usually reports one page; Search Console reports groups of similar pages, and Google notes one page can be an outlier in its group.

Different for you?

Keep learning

NextImprove Core Web Vitals: Advanced Fixes for LCP, INP and CLSDeveloper fixes for each Core Web Vital: split LCP into its four parts, INP into three phases, find the CLS culprit, and skip the advice that backfires.

Do it yourself

Crawlability checklist: make every page reachable by GoogleA crawlability checklist for a small business site: find orphan pages, robots.txt blocks, broken links, redirect chains and server errors, with free tools.

Ask us one question

One line is enough. We reply by email.

Sources

  1. Search Console Help: Core Web Vitals report
  2. Chrome for Developers: CrUX tools
  3. Chrome for Developers: CrUX History API
  4. Chrome for Developers: CrUX Dashboard deprecation (September 9, 2025)
  5. CrUX Vis
  6. PageSpeed Insights: About PageSpeed Insights
  7. web.dev: Interaction to Next Paint becomes a Core Web Vital on March 12
  8. web.dev: Interaction to Next Paint (INP)
  9. web.dev: Measure and debug performance with Google Analytics 4 and BigQuery
  10. GoogleChrome/web-vitals library on GitHub
  11. Google Search Central: Understanding Core Web Vitals and Google search results