Core Web Vitals measure how your website feels to a real visitor: how fast the main content loads, how quickly the page responds when they tap, and whether things jump around while it loads. SEO Autopilot pulls these numbers from Google's Chrome UX Report (CrUX) - real-world data from actual Chrome users, not a single lab test on your machine. This guide shows you where to find the panel and how to read all three gauges honestly.

SEO Autopilot · Core Web Vitals · Field data (mobile) Source: CrUX · p75 LCP Largest Contentful Paint · loading 2.1s GOOD ≤ 2.5s good 2.5s - 4.0s needs work ≥ 4.0s poor INP Interaction to Next Paint · response 310ms NEEDS WORK ≤ 200ms good 200 - 500ms needs work ≥ 500ms poor CLS Cumulative Layout Shift · stability 0.04 GOOD ≤ 0.10 good 0.10 - 0.25 needs work ≥ 0.25 poor Values shown are the 75th-percentile real-user readings. Numbers are illustrative of the panel layout.
The Core Web Vitals panel in SEO Autopilot: three gauges (LCP, INP, CLS) each scored green, amber or red against Google's published thresholds, using real Chrome field data at the 75th percentile.

How to check Core Web Vitals step by step

  1. Open SEO Autopilot and load the client whose site you want to check.
  2. Make sure the business website URL is filled in on the config - the vitals check reads it to find your origin.
  3. Click Check Core Web Vitals. Autopilot queries Google's CrUX API for real mobile field data.
  4. Read the three gauges: LCP (loading), INP (responsiveness) and CLS (visual stability).
  5. Compare each value to Google's thresholds - green (good), amber (needs work) or red (poor).
  6. If you see no data yet, that means your origin doesn't have enough Chrome traffic - it isn't an error.
  7. Re-check after fixes and watch the stored history to confirm the trend is moving the right way.

What each of the three vitals actually measures

LCP (Largest Contentful Paint) is how long it takes for the biggest visible element - usually your hero image or main headline - to render. If it drags past 2.5 seconds, visitors on a phone are staring at a blank or half-built page. Good is 2.5s or under; poor is 4.0s or over.

INP (Interaction to Next Paint) replaced the old First Input Delay metric. It measures how fast the page visibly responds after someone taps a button, opens a menu or fills a form field. Good is 200ms or under; poor is 500ms or over. Heavy scripts and third-party widgets are the usual culprits when this creeps into amber.

CLS (Cumulative Layout Shift) is a stability score, not a time. It captures how much content jumps around as the page loads - the classic case is tapping a link right as an ad or banner pushes everything down. Good is 0.10 or under; poor is 0.25 or over.

Why we use field data, not a lab test

A lot of speed tools run a single test from one server and give you a lab score. That is useful for debugging, but it isn't what Google uses for page experience. Autopilot reads the Chrome UX Report, which aggregates real visits from real Chrome users over a rolling window and reports the 75th percentile - meaning 75% of your visitors had that experience or better. That is a more honest picture of what your actual customers feel, and it is the same field-data source behind Google's page-experience signal.

One consequence: brand-new or low-traffic local sites often show no data yet. CrUX only publishes an origin once it has enough Chrome traffic to form a reliable sample. We surface that plainly instead of faking a number. If you see it, keep building traffic and re-check later - it is not a bug on your site.

Want us to run and act on your vitals for you?

SEO Autopilot tracks your Core Web Vitals alongside rankings and content, so you see loading, responsiveness and stability trends in one place.

Open SEO Autopilot →Book a free call →

What to do after you read the panel

If any gauge is amber or red, don't panic-optimize everything at once. Start with the single worst metric. For LCP, compress and correctly size your hero image and cut render-blocking scripts. For INP, audit third-party tags (chat widgets, booking embeds, analytics) and remove what you don't need. For CLS, set explicit width and height on images and reserve space for anything that loads late, like ads or embedded reviews.

Then re-run the check. Because CrUX is a rolling field average, improvements show up gradually as new real-user visits accumulate - not the instant you deploy. Autopilot keeps your recent readings so you can watch the trend rather than judging off a single snapshot. Faster, steadier pages help conversions and organic rankings; we won't promise a specific position or timeline, because no honest team can.

FAQ

Where does Autopilot get the Core Web Vitals numbers?

From the Chrome UX Report (CrUX) API, which is Google's real-world field data collected from actual Chrome users on your site. It is the same page-experience data Google references, not a one-off lab test.

What are the good, needs-work and poor thresholds?

Google's boundaries are: LCP good at or under 2.5s and poor at or over 4.0s; INP good at or under 200ms and poor at or over 500ms; CLS good at or under 0.1 and poor at or over 0.25. Anything between the two boundaries is "needs work".

Why does my site show "no data yet"?

CrUX only reports origins that get enough Chrome traffic to form a reliable sample. A "no data" response means your site hasn't hit that volume yet - it is surfaced honestly rather than as an error, and it is common for newer or lower-traffic local sites.

Will good Core Web Vitals make me rank higher in the map pack?

Page experience is one of many signals and it mostly affects your website, not directly the Google Business Profile map pack. Faster, more stable pages help conversions and organic rankings, but we don't promise a specific position or timeline.

Are these numbers for mobile or desktop?

By default Autopilot checks mobile (phone) field data, since most local searches happen on phones and Google indexes mobile-first. The underlying data can be read for desktop too, but mobile is what we lead with.