Overall page-experience verdict
also called Overall CWV grade
Definition
A single good, needs improvement or poor verdict presented for page experience as a whole.
How it's calculated
Set to the grade of the performance vital, and nothing else. In code the overall field is assigned directly from the performance vital's bucket, both in the base scoring pass and again after the summary values replace the page-derived ones.
Scope, grain and dimensions
- Grain
- One verdict per date range, optionally one per device.
- Dimensions
- device
- Required filters
- date_range
- Aggregation
- Not an aggregation across vitals. Rendering time, responsiveness and layout shift do not enter it at all.
- Metric type
- derived metric · one of good, needs-improvement, poor
Data sources
Where you'll see this
Named reports that normally include this metric.
Skills and analyses that use it
Skills carry the judgment; the analysis verbs do the reading.
Analysis verbs
site_health_cwv_check
Method rungs and levers
This sits on the bottom rung: if it reads badly, every measurement above it is unreliable.
levers L1 Technical & crawl health
Ask Quattr
- "Is our page experience healthy?" Simulate this →
- "What is our overall Core Web Vitals grade?" Simulate this →
How to read it
Read it as the performance vital's grade under a broader name, because that is what it is. A site can be graded good overall while failing responsiveness or layout shift outright, so the per-vital grades belong beside it whenever the verdict is quoted.
Caveats, freshness and failure modes
The name says overall; the derivation uses the performance vital alone. Rendering time, responsiveness and layout shift are graded separately and are excluded from this verdict.
That makes a good overall verdict compatible with a failing Core Web Vital, which is the opposite of what the label suggests.
Never present this as a Core Web Vitals pass or fail, pair it with the per-vital grades.
It inherits the performance vital's caveats, including that vital's own snapshot rule: the verdict follows the latest day on which the product's four score families were all populated, so it can be anchored to a different day from the three Core Web Vitals sitting beside it, which stay on period aggregates.
It inherits the rest too: lab measurement, varying collection cadence, thresholds pending product-specific confirmation.
- Freshness
- varies by site, priority URLs can run nightly; most pages far less often. The collection date rides on the card rather than being assumed.
Common failure modes
- Quoting the overall verdict as a Core Web Vitals summary and missing a failing vital underneath it.
- Reporting an improvement in the overall verdict when only the performance score moved.
Not the same as
The confusions that cause the most wrong decisions.
Overall page-experience verdict Performance score Compare definitions →
Score versus verdict: one is the numeric average, the other is its band. They are the same underlying vital, which is precisely why the verdict must not be read as covering the others.
Overall page-experience verdict Vital grade Compare definitions →
The per-vital grade covers whichever vital it names; the overall verdict covers performance only despite its name.
Watch this metric read in a real run
All runs →
Related metrics and workflows
Verification
A definition is the smallest part of this.
The measurement matters because something acts on it. Here is the rest of the showcase, in the order most people find useful.