Skip to main content
Web Vitals runs Lighthouse audits against individual URLs and stores each result, so you can watch page performance over time.

Running a check

Click Run Check beside the page title. In the panel that opens, enter a page — example.com/pricing works; https:// is added if you leave it off. The page must be on your project’s domain or one of its subdomains — a check uses one of your site audit pages, which are for your own site. Choose Mobile (the default) or Desktop, then click Run Check at the bottom of the panel. The check runs in the background and appears in the list when it completes. Checks are per URL, not per site. Your home page performing well says nothing about a heavy product template — check the pages that matter individually. Checks are also per device — a URL measured on mobile and on desktop are separate checks, and mobile is usually the worse and more important of the two. Each check in the list is labelled with its device, and re-running one uses the same device.
Each web vitals check uses one page of your monthly site audit pages allowance — a Lighthouse run is a crawl of one page. See Usage and limits. There’s also a one-at-a-time guard: starting a check while one is already running for the project is refused rather than queued.

Performance score

Each completed check shows a performance score gauge — the Lighthouse score from 0 to 100. It’s a weighted composite of the metrics below, not a separate measurement.

Metrics

A completed check records seven metrics, all straight from Lighthouse: Times are in milliseconds; CLS is a unitless score. Any metric Lighthouse couldn’t measure comes back null and displays as —. LCP, INP, and CLS are the three Core Web Vitals — the ones Google uses as a ranking signal. The other four are diagnostics that explain them. Surnex stores the raw values rather than a pass/fail grade. For reference, Google’s own thresholds are LCP ≤ 2.5 s, INP ≤ 200 ms, and CLS ≤ 0.1 for “good”.

Reading the diagnostics

The four supporting metrics tell you why a Core Web Vital is failing, which is what makes them worth having:
  • High TTFB with high LCP — the problem is server-side. No amount of front-end optimization fixes a slow origin; look at hosting, caching, and database queries.
  • Low TTFB but high LCP — the server is fine and the page is heavy. Look at image sizes and render-blocking resources.
  • High TBT with poor INP — JavaScript is monopolizing the main thread. Split bundles, defer what isn’t needed for first paint.
  • High SI with acceptable LCP — content arrives in stages and the page feels slow even though the headline metric passes.

Opportunities

Completed checks list Opportunities — specific fixes Lighthouse identified, each with a description and the estimated time saving in milliseconds. Sort your effort by the savings figure, but sanity-check it: a 400 ms saving on a page with a 4-second LCP is worth more than a 400 ms saving on one already passing.

History

Every check is stored, so the list is a performance record for the URL. Re-check after a deploy and compare against the previous run to confirm the change helped. To re-check a URL, click the refresh icon on its row. A re-check uses one site audit page, so it asks first: the confirm says it runs the same check again, that it uses 1 site audit page, and how many you have left this month. Click Refresh in the confirm to start.

Lab data, not field data

These are lab measurements — a single synthetic load under controlled conditions — not what your real visitors experienced. That means results are reproducible and good for comparing before and after a change, but they won’t match Chrome User Experience Report figures or Search Console. Real users are on slower devices and worse networks, so field data is typically worse than lab data. Use these numbers to diagnose and to measure improvement, not to predict what Google sees.

Relationship to site audits

Both touch performance and they don’t measure the same thing: Use an audit to find which pages are slow across the site, then web vitals to work out why on the worst offenders.