What are Core Web Vitals in Google Search Console?

Q: What are Core Web Vitals in Google Search Console?

Core Web Vitals measure loading, responsiveness and visual stability for real Chrome users. Here is how Search Console rates your URLs and what to fix.

Core Web Vitals are three measures of what real visitors experience: Largest Contentful Paint (loading), Interaction to Next Paint (responsiveness) and Cumulative Layout Shift (visual stability). Search Console's Core Web Vitals report takes them from the Chrome UX Report, which collects anonymised timings from real Chrome users, and rates groups of similar URLs as Good, Needs improvement or Poor, separately for mobile and desktop.

The thresholds

Metric	Good	Needs improvement	Poor
LCP: time until the largest visible element renders	2.5 s or less	up to 4 s	over 4 s
INP: delay before the page responds to clicks, taps and keys	200 ms or less	up to 500 ms	over 500 ms
CLS: how much the layout jumps unexpectedly	0.1 or less	up to 0.25	over 0.25

A rating describes 75% of visits: a group is Good for LCP when three-quarters of its visits reach LCP within 2.5 seconds.

How the report rates your pages

URLs are grouped with similar pages, and the whole group shares one status.
The worst metric wins. A group that is Good for LCP and CLS but Poor for INP is Poor.
Data covers the last 28 days, so a fix takes up to four weeks to show fully.
Only indexed URLs appear, and only a sample of them.
Thin data falls back to the origin. If a group lacks enough visits, the status comes from the whole site's origin.
No data means either a new property, where data can take a few days, or too little Chrome traffic for that device type.

Do Core Web Vitals affect rankings?

Yes, within limits. Google states that Core Web Vitals are used by its ranking systems and highly recommends achieving good ones. It also says there is no single page experience signal, and that Search always seeks to show the most relevant content even when its page experience is weaker. In other words, good scores help a relevant page compete; they do not rescue an irrelevant one.

How to fix and validate

Open the Core Web Vitals report from the left-hand menu, choose mobile or desktop, and open the issue with the most URLs.
Take an example URL from the group and test it in PageSpeed Insights, which shows the same field data next to a lab test you can repeat.
Fix the cause in the template the group shares: usually the hero image or server response for LCP, heavy JavaScript for INP, and images or embeds without reserved space for CLS.
Choose Start tracking (validation). Google watches the group for 28 days, and the issue passes when it is absent from all its URLs for that whole window. Starting validation does not make Google recrawl anything.

What each metric measures in detail is in LCP, INP and CLS explained; common fixes are in fixing poor Core Web Vitals.

How AutoPSEO helps

Search Console shows how many URLs are in each status, not how the metrics themselves are trending. AutoPSEO's Core Web Vitals report reads the Chrome UX Report History API: weekly 75th-percentile values for LCP, INP and CLS, plus First Contentful Paint and Time to First Byte, for about the last 25 weeks, for your whole origin or a single URL, on phones, desktops, tablets or all devices together. You can see a regression the week it starts rather than when a group changes status.

Sources: Google's Core Web Vitals report help, Core Web Vitals and Google Search and page experience guide.