Vitals Compliance Score

Vitals Compliance Score is the percentage of URLs that pass Google’s Core Web Vitals in real-user data. It matters because SEO teams need a portfolio-level KPI, not 5,000 individual PageSpeed screenshots.

What the score actually measures

In practice, this score usually means: passing URLs ÷ measured URLs × 100. Historically that meant passing LCP, FID, and CLS. Today, Google has replaced FID with INP as a Core Web Vital, so any glossary entry still centered on FID is outdated.

That matters. A site reporting an 85% compliance score based on LCP/FID/CLS may look healthy while failing badly on INP. Google Search Console (GSC) groups URLs into Good, Needs improvement, and Poor using Chrome UX Report data over a 28-day window. Most teams calculate the score from the URLs or URL groups marked Good.

Why SEOs use it

This is a management metric. Not a Google metric. Google does not publish an official “Vitals Compliance Score” in ranking systems documentation.

Used well, it helps you:

• Track progress across thousands of pages after template changes
• Prioritize page types with the biggest SEO upside, like product, category, or article templates
• Report performance health to stakeholders without dumping raw CrUX exports into a slide deck

Tools help, but they measure different things. GSC gives you field data. PageSpeed Insights mixes lab and field data. Lighthouse and Surfer SEO are useful for debugging, not for calculating a true compliance rate. Screaming Frog can crawl templates and surface heavy assets, but it does not replace CrUX. Ahrefs, Semrush, and Moz can support page-level audits, yet none of them are the source of truth for Core Web Vitals pass rates.

Where teams get this wrong

The big mistake is treating the score like a direct ranking lever. Google’s page experience signals are real, but they are lightweight compared with relevance, links, and content quality. Google’s John Mueller has repeatedly said versions of this for years, and that remains the practical reading in 2025: fixing CWV can help, but it rarely rescues weak pages.

Another issue: the denominator. Are you measuring all indexed URLs, only URLs with CrUX data, or GSC URL groups? Those are not interchangeable. On smaller sites, a large percentage of pages may have no usable field data at all. On enterprise sites, one broken template can drag 20,000 URLs into failure and make the score look catastrophic overnight.

How to use it properly

1. Pull GSC Core Web Vitals data by mobile and desktop separately.
2. Calculate compliance by template or directory, not just sitewide.
3. Track LCP, INP, and CLS failure counts alongside the roll-up score.
4. Validate fixes in lab tools like Lighthouse, then wait for field data to catch up over the 28-day window.

If you want a useful benchmark, aim for 90%+ of measured mobile URL groups in Good. Below 70%, you usually have a template, image, JavaScript, or ad-tech problem worth escalating.