Core Web Vitals (CWV) measure real-user loading, interactivity, and visual stability. Search Console shows CWV from field data collected through the Chrome User Experience Report (CrUX), not from a single lab test. That makes the report the right place to prioritize fixes that affect visitors Google already measured.
Where to find the report
In Search Console, open Experience > Core Web Vitals. The overview splits data by Mobile and Desktop. Google recommends starting with the platform that drives most of your search traffic, which for many sites is mobile.
If you see No data available, the property may be new in Search Console or CrUX may not yet have enough URL-level data for that device type. You can still test individual URLs with PageSpeed Insights or Lighthouse, but those tools do not replace the field-data report.
How Google assigns Poor, Need improvement, and Good
The report groups similar URLs and evaluates three metrics: LCP (Largest Contentful Paint), INP (Interaction to Next Paint), and CLS (Cumulative Layout Shift). Google publishes threshold bands. At a high level for each metric: Good meets the fastest band, Need improvement is in the middle band, and Poor exceeds the slowest threshold.
A URL group's status equals its worst metric on that device. Example: Good LCP plus Poor CLS is labeled Poor. Only indexed URLs can appear. The report shows a sample of URL groups meant to represent site-wide experience, not every indexed URL.
Prioritize by traffic, not by audit score alone
Search Console is not designed to look up one arbitrary URL's status quickly. Google directs you to external tests for that. For prioritization, open Poor or Need improvement groups, note the URL pattern (product template, blog layout, homepage), then cross-check those sections in Performance for impressions and clicks. Fix templates with both CWV problems and meaningful search visibility first.
Fix shared templates once
URL groups usually share HTML shells, CSS, fonts, tag managers, and hero images. Patching one URL while leaving the template broken wastes time. Typical mobile improvements aligned with Google's metric definitions:
- LCP: Optimize and prioritize the largest above-the-fold image or text block, improve server response time, remove render-blocking resources where safe.
- INP: Reduce long JavaScript tasks on interactive elements such as menus, carts, and filters.
- CLS: Set explicit width and height on images and embeds; avoid inserting content above existing content unless space is reserved.
Use lab tools to debug, not to rank priorities
PageSpeed Insights and Lighthouse help reproduce issues on a specific URL. Google documents important differences: CrUX groups URLs with parameters; PSI often strips parameters. A URL can look fine in lab data but Poor in field data if real users on slow networks dominate. Use lab tools after you pick a group from Search Console.
Validate after deploy on CrUX timelines
Field data rolls on a 28-day window. After shipping fixes, allow one to two weeks before expecting movement in the report, then confirm the URL group shifts toward Good. Pair with Performance to ensure clicks did not keep falling during the optimization work.