Skip to content
PageVital
← All guides

What Is a Website Health Score? Read the Evidence Behind the Grade

Learn what a website health score summarizes, how PageVital weights its standard score, and why coverage matters as much as the letter grade.

Published Updated

A website health score summarizes a tool's selected checks. It can help you decide where to look first, but it is not a universal rating of a business, a security guarantee, or a prediction of search traffic.

Two questions matter more than the letter: what contributed to this score, and what was not measured?

What PageVital's standard score includes

PageVital's standard scoring model gives performance a 30% weight, security 25%, SEO 25%, and technology 20%. These are PageVital's product choices, not weights published by Google or an industry standard. Other profiles can use different weights, so confirm the profile when comparing reports.

Within a category, the model weights checks by assigned severity: critical 3, high 2, medium 1, and low 0.5. The numeric result summarizes those checks. It does not know how much a particular page contributes to your revenue or which visitor journey is most important.

A purely illustrative calculation makes the distinction clear:

Performance 85 × 0.30 = 25.50
Security    90 × 0.25 = 22.50
SEO         75 × 0.25 = 18.75
Technology  95 × 0.20 = 19.00
Total                  85.75 → 86

That result maps to B. The current bands are A at 90 or above, B at 80, C at 70, D at 60, and F below 60. An A says the measured checks scored highly. It does not say there are no urgent issues outside those checks.

Check coverage before comparing totals

When a category is unavailable, the standard overall calculation excludes it and normalizes the remaining category weights. That makes the coverage note essential: two similar totals can describe different sets of evidence.

Imagine a report with all categories measured and a later attempt with performance unavailable. Even if the second overall number is higher, that is not evidence that performance improved. Compare completed checks and keep the missing measurement visible.

Individual error states also need inspection. A low category score may include a measurement problem. Read the check status and evidence before turning it into a repair ticket.

Translate the score into a decision

Use this sequence for a weekly review:

  1. Confirm the URL, profile, timestamp, and completed checks.
  2. Inspect changes in individual findings.
  3. Confirm the consequence for a visitor or operator.
  4. Assign a repair or record why no change is appropriate.
  5. Recheck the same scope after the repair.

The number helps organize attention. A human still decides whether an issue is consequential. A lower-severity item on a critical purchase step can deserve attention before a higher-weight check on an unused page.

Keep other measurements separate

A Lighthouse performance score uses its own model. Google's Lighthouse scoring documentation explains how metric values are converted and weighted. A PageVital grade and a Lighthouse score are not interchangeable.

Neither metric establishes conversion rate, accessibility conformance, or whether a form successfully reached its destination. Those require evidence suited to those questions.

Inspect a free snapshot, then use the guide to conflicting website grades if two reports appear to disagree.

These guides explain public-page checks and maintenance decisions. Examples are illustrative unless identified otherwise. Source links accompany technical guidance; an automated result does not establish security, compliance, or a business outcome.