Core Web Vitals decide whether Google's field data labels your pages a good experience — and they move with every script, font and layout shift you ship. Guesswork fails here because perception lies: a page feels instant on your fiber connection yet stumbles for users on mid-range phones. Proper Core Web Vitals tools measure the truth across real visitors and controlled lab conditions.
The trick is knowing which kind of data you are reading. Field data reports what actual Chrome users experienced over a rolling 28-day window; lab data simulates a single visit under fixed conditions. Diagnosis needs both — field tells you there is a problem, lab tells you why.
Quick Answer: Start with PageSpeed Insights, which pairs field data from real users with a Lighthouse lab run in one free report, then monitor site-wide trends in Search Console's Core Web Vitals report.
Field Data Versus Lab Data
- Field (CrUX) — sampled from real Chrome visits and reported at the 75th percentile; requires enough traffic before any URL or origin appears at all.
- Lab (Lighthouse) — deterministic, debuggable, and available for any URL including zero-traffic ones.
- Neither replaces the other — optimizing lab scores without confirming field movement is performance theater.
What Passing Actually Means
Google assesses three metrics at the 75th percentile of visits: Largest Contentful Paint should land within 2.5 seconds, Interaction to Next Paint (INP) within 200 milliseconds, and Cumulative Layout Shift below 0.1. Miss any threshold and the URL group gets flagged as needing improvement — that flag is exactly what Search Console surfaces.
Core Web Vitals Tools Compared
| Tool | Best For | Free Option |
|---|---|---|
| PageSpeed Insights | Combined field plus lab snapshot of one URL | Yes |
| Search Console CWV Report | Site-wide field data grouped by issue type | Yes |
| CrUX Dashboards | Metric distributions and history across an origin | Yes |
| Lighthouse (DevTools) | Local lab debugging with throttled runs | Yes |
| WebPageTest | Device and location matrices with CWV timing | Yes, with limits |
Tool Breakdown
PageSpeed Insights
Both data sources in a single free report, plus diagnostic opportunities ranked by estimated savings. Grab it at pagespeed.web.dev. Limitation: it reports per URL, so sitewide patterns require other tools.
Search Console Core Web Vitals Report
Groups URLs by shared problem across the whole domain, telling you whether one template is broken or fifty. Updates slowly, but nothing prioritizes CWV work faster.
CrUX Dashboards on Looker Studio
Charts metric percentiles and month-over-month history for your origin, optionally against competitors. Free once wired to a Google account.
Lighthouse in Chrome DevTools
Runs throttled audits locally, traces slow interactions to specific code paths, and reproduces what PSI measures before anything deploys.
WebPageTest
Filmstrips and waterfalls show exactly when LCP paints across device and location combinations — invaluable for international audiences.
Workflow Tip: Fix Templates, Not Pages
Identify the worst-performing template in Search Console, reproduce its failure in Lighthouse, apply fixes, then verify in field data four-plus weeks later — the CrUX window rolls slowly by design. Celebrating a lab win that never moves field numbers is the most common trap in this discipline.
Key Takeaways
- Field data proves real-user experience; lab data explains it. Use both, never just one.
- Targets: LCP under 2.5s, INP under 200ms, CLS under 0.1 at the 75th percentile.
- Search Console groups failures by template — start where the damage concentrates.
- Expect weeks between shipping fixes and seeing field movement.