Black Friday: 50% off. Your first year on any annual plan, until 1 December. See the dealFirst year on annual plans, until 1 December
WPClientHub V2 is live. Fewer plugins on your client sites: caching, forms and image optimization now come built into WPClientHub One. See what’s newCaching, forms and images, built in. See what’s new
Sign in Start free

← Docs  /  Sites & health score

The health score, explained

Updated 2026-10-06

Exactly how the 0–100 score is calculated, what each deduction is worth, and how to read the breakdown drawer.

Browse documentation

What it does

Every site gets one honest number from 0 to 100. 100 means nothing needs attention; the score falls as real problems stack up, each with a capped deduction so no single factor can bury the rest. Click the score on a site's header to open the health score breakdown drawer and see exactly where the points went.

How to

Read the breakdown top to bottom — the first entries are usually what's "dragging the score down". More than two negative factors show a +N more pill that opens the same drawer instead of hiding them.

Limits & defaults

FactorDeduction
WordPress core update available−10
Each plugin update available−3 each, capped at −24
Each theme update available−2 each, capped at −8
No backup has ever completed−15
Last completed backup older than 7 days−10
No offsite backup destination configured−10
Each open uptime incident−15 each, capped at −30
PHP below 8.1 (the supported minimum)−10
PHP below 7.4 (end of life)−20
Open critical/high vulnerability−10 each
Open medium/low/unknown vulnerability−4 each — vulnerabilities capped at −25 total
Each failed hardening check−3 each, capped at −12
Suspicious files from the daily file check, worst one high or critical (file integrity)−40
Suspicious files from the daily file check, medium or low only−10
Domain expired, on hold, pending delete or in redemption (domain monitoring)−10
Domain registration ends in 7 days or less−5 (no published expiry date costs nothing)

Bands: Excellent 90–100 · Good 75–89 · Needs attention 50–74 · Critical 0–49. The Sites list's "needs attention" stat counts Needs attention + Critical.

Stale scores. A score is only as current as the site's last sync. When a site is disconnected, or a connected site hasn't synced for 48 hours, the Sites list and the site header show the score greyed out as Stale instead of a green number, with the reason on hover — a site that stopped reporting is never shown as healthy.

The score recomputes the moment a contributing fact changes — a vulnerability is ignored or resolved, a backup completes, an incident opens or clears — plus a nightly reconciliation pass as a safety net, so the number on the list and the one in the drawer are always the same value.

Troubleshooting

The score didn't move after I fixed something
Most factors update the moment the underlying event is recorded (a backup finishing, a vulnerability resolving). An update you ran on the site itself needs a sync to be reflected — resync from the site's Overview tab if it doesn't appear within a minute or two.
A site is being penalized for "no offsite destination" but I do have one
The offsite penalty looks at whether your organization has a working offsite destination configured under Offsite storage — add or verify one there.