{
  "slug": "cwv-overall-verdict",
  "name": "Overall page-experience verdict",
  "aliases": [
    "Overall CWV grade"
  ],
  "definition": "A single good, needs improvement or poor verdict presented for page experience as a whole.",
  "category": "Page experience",
  "type": "derived metric",
  "unit": "one of good, needs-improvement, poor",
  "direction": "higher-better",
  "verification": "verified",
  "calculation": "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.",
  "aggregation": "Not an aggregation across vitals. Rendering time, responsiveness and layout shift do not enter it at all.",
  "grain": "One verdict per date range, optionally one per device.",
  "dimensions": [
    "device"
  ],
  "requiredFilters": [
    "date_range"
  ],
  "sources": [
    "lighthouse"
  ],
  "reports": [
    "core-web-vitals-report"
  ],
  "skills": [
    "cwv-regression-watch",
    "technical-health-audit"
  ],
  "verbs": [
    "site_health_cwv_check"
  ],
  "rungs": [
    "R1"
  ],
  "levers": [
    "L1"
  ],
  "questions": [
    "Is our page experience healthy?",
    "What is our overall Core Web Vitals grade?"
  ],
  "interpretation": "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": [
    "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.",
  "failureModes": [
    "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."
  ],
  "notSameAs": [
    {
      "slug": "performance-score",
      "why": "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."
    },
    {
      "slug": "cwv-vital-grade",
      "why": "The per-vital grade covers whichever vital it names; the overall verdict covers performance only despite its name."
    }
  ],
  "related": [
    "performance-score",
    "cwv-vital-grade",
    "cwv-weakest-vital"
  ],
  "workflows": [],
  "lastVerified": "2026-08-04"
}