To monitor Core Web Vitals, verify your site in Google Search Console and open the Core Web Vitals report. The report uses real-user field data, grouped as Poor, Needs improvement or Good, for Largest Contentful Paint (LCP), Interaction to Next Paint (INP) and Cumulative Layout Shift (CLS). Drill into mobile and desktop, fix the URL groups that fail, and use PageSpeed Insights or Lighthouse when you need a lab test of a single URL.
This is about watching the official field data over time, not about chasing a one-off Lighthouse score. Our earlier article explains whether Core Web Vitals affect rankings. This guide covers how to set up the monitoring itself, using Google's report documentation and web.dev's Core Web Vitals overview.
What are you measuring?
Google's current Core Web Vitals, described on web.dev, are:
- LCP (Largest Contentful Paint): when the main content appears. The good threshold is 2.5 seconds or less at the 75th percentile.
- INP (Interaction to Next Paint): how quickly the page responds to clicks, taps and key presses. The good threshold is 200 milliseconds or less at the 75th percentile. INP replaced First Input Delay in March 2024.
- CLS (Cumulative Layout Shift): how much the layout unexpectedly moves. The good threshold is 0.1 or less at the 75th percentile.
Those thresholds are official targets, not invented house rules. A page can pass two metrics and still be Poor overall, because Search Console uses the worst of the metrics it can report.

How do you open the Search Console report?
- Set up Search Console and verify the property if you have not already.
- Open the Core Web Vitals report from the Experience or later equivalent menu. Google's Core Web Vitals report help is the official manual for this screen.
- On the overview, look at the charts for Mobile and Desktop separately. Click Open report next to a chart to drill in.
- Toggle Poor, Need improvement and Good on the performance chart.
- Use the table of issues to see URL groups that are not Good. Each example URL stands for a group of similar pages, such as a template.
- Open an example to see the failing metric, then follow the links to test a specific URL.
The report is based on the Chrome User Experience Report (CrUX) field data from real Chrome users, not on a simulated test. Google says it is not a complete list of every indexed URL, only a sample with enough data. Only indexed URLs can appear. Data is assigned to the actual URL, not the canonical URL, which is different from most other Search Console reports.
If you see "No data available", the property may be new, or there may not yet be enough CrUX data for that device type. Google says it can take a few days after you create a property for existing CrUX data to be analysed and posted. Small or new sites often have this gap. You can still test individual URLs with PageSpeed Insights or Chrome Lighthouse.






