Vitals Compliance Score

Vitals Compliance Score is a site-level metric: the share of URLs with Core Web Vitals data that fall into Google's “good” range at the 75th percentile. In plain terms, it tells you how much of your site is actually passing, not how many individual pages looked fine in a lab test.

That matters because SEO teams need one number leadership can follow. A homepage Lighthouse 95 means very little if 62% of product URLs still fail INP in Chrome UX Report data.

What counts in the score

The usual definition is simple: good URLs ÷ URLs with enough field data × 100. The thresholds are Google's standard Core Web Vitals benchmarks: LCP at 2.5 seconds or less, CLS at 0.1 or less, and INP at 200 milliseconds or less.

Use Google Search Console first. Its Core Web Vitals report groups URLs by issue pattern and reflects Chrome field data, which is what matters for this kind of score. If you want page-level debugging, pair it with PageSpeed Insights, CrUX, or a RUM tool like SpeedCurve. Screaming Frog can help map issue groups back to templates, but it does not calculate field-based CWV on its own.

Why SEOs use it

It gives you a portfolio KPI that is harder to game than lab scores. Useful for reporting. Better for prioritization.

• Template triage: If article pages sit at 91% compliance and product pages sit at 44%, the backlog writes itself.
• Traffic weighting: A 10-point lift on URLs driving 70% of organic sessions matters more than cleaning up orphaned pages nobody visits.
• Cross-team accountability: Product, engineering, and SEO can all work from the same number instead of arguing over isolated Lighthouse screenshots.

How to calculate it properly

At minimum, segment by template type, device class, and market. Mobile usually tells the truth faster than desktop. For most sites, a weekly or monthly trendline is enough because CrUX-based reporting lags and smooths data over time.

A practical benchmark: many mid-size sites should aim for 80%+ compliance overall and 90%+ on revenue-driving templates. Below 60%, you probably have systemic front-end or server issues, not a few bad pages.

Tools like Looker Studio, BigQuery, and GSC exports make this easy to operationalize. Ahrefs, Semrush, and Moz are useful for correlating performance work with rankings and traffic, but they are not your source of truth for Vitals Compliance Score.

The caveat most teams miss

This score is only as good as the underlying field data. Low-traffic URLs often have no usable CrUX sample, so they disappear from the denominator. That can make a weak site look healthier than it is.

Also, passing Core Web Vitals does not guarantee ranking gains. Google's John Mueller has repeated for years that page experience is not a tie-breaker you can bank on page by page. In practice, Vitals Compliance Score is best treated as a risk and UX metric with SEO upside, not a direct ranking lever.

Use it. Just don't worship it. If your pages are thin, duplicated, or poorly linked internally, a 95% compliance score will not save them.