How to Measure Core Web Vitals: A Complete Guide to PageSpeed Insights, Lighthouse, CrUX & Search Console

A page can score a perfect 100 in Lighthouse and still fail Core Web Vitals where it actually counts. That contradiction confuses more site owners than almost anything else in technical SEO, and it comes down to a single distinction: lab data versus field data. Here is how PageSpeed Insights, Lighthouse, CrUX, and Search Console actually measure Core Web Vitals, and which one to trust for what.

Google uses exactly one data source to decide whether your Core Web Vitals pass for ranking purposes: real-user field data from the Chrome User Experience Report, known as CrUX. Everything else, including Lighthouse's polished 0-100 score, is a diagnostic tool, not the scoreboard.

We covered each individual metric in our guides to LCP, INP, and CLS. This article covers where to actually check the numbers.

Field Data vs. Lab Data: The Distinction That Explains Everything

Every measurement tool falls into one of two categories, and confusing them is the single biggest source of confusion in Core Web Vitals reporting.

What Each Core Web Vitals Tool Actually Does

Why Lighthouse and CrUX Can Disagree Completely

This is the exact contradiction that confuses so many site owners. Tap through both explanations.

PageSpeed Insights vs. Lighthouse vs. CrUX vs. Search Console

How to Check Core Web Vitals in Google Search Console

Open the Core Web Vitals report under the Experience section in Search Console to check your site's Core Web Vitals status. The dashboard splits results by mobile and desktop, showing URLs grouped into Poor, Needs Improvement, and Good categories.

According to Google's official Search Console help documentation, the report is designed to show overall site performance trends rather than the status of one specific URL, since it groups similar pages together by template or URL pattern.

If your property is new, it can take a few days for CrUX data to populate, since the underlying dataset gathers information independently of when a Search Console property was created.

How to Run a PageSpeed Insights Check

Visit pagespeed.web.dev and enter any URL. According to Matthew Edgar's guide to measuring Core Web Vitals, the report returns field data when available, alongside a Lighthouse-based lab score and a prioritized list of specific fixes for that page.

This makes PageSpeed Insights the most practical starting point for diagnosing a single underperforming URL, since it pairs the real-world number with concrete next steps rather than just a pass or fail verdict.

Using Chrome DevTools for Live, Real-Time Metrics

According to Carson Digital's 2026 guide to checking Core Web Vitals, opening Chrome DevTools and navigating to the Performance panel shows a Live Metrics view with real-time LCP and CLS as you browse, with INP appearing once you start interacting with the page.

The same panel can run a full Lighthouse audit, generating a shareable report useful for client updates or internal documentation without needing any separate tool or login.

How Lighthouse and CrUX Fit Into a Development Workflow

Most experienced teams do not choose one tool over the others. They use each one at the stage where it actually adds value, rather than treating any single report as the complete picture.

According to MarketingAid's guide to performance measurement tools, Lighthouse fits naturally into a development or staging environment, catching regressions before a change ever reaches real visitors.

CrUX and Search Console, by contrast, only reflect what has already shipped, since they depend on actual traffic accumulating over the 28-day window.

This means a healthy workflow checks Lighthouse before deployment and checks Search Console after, closing the loop between what was intended and what real users actually experienced.

Common Mistakes When Interpreting These Tools

The most common mistake is treating a single Lighthouse run as definitive proof a page is fast. According to Duda's comparison of Lighthouse and Core Web Vitals, real-world aggregated field data is consistently a better indicator of actual performance than a single point-in-time lab test.

A second mistake is panicking over a temporary dip in Search Console without checking whether it reflects a genuine regression or simply a small sample size on a low-traffic page.

Field data needs sufficient visits to be statistically meaningful, and results on lower-traffic URLs can swing more than the underlying reality actually changed.

FAQs on Measuring Core Web Vitals