Understand how Health Score is calculated
Learn how page count and weighted open incidents produce a score out of 100.
Last checked 20 August 2026
Health Score summarizes the current open incidents for one website as a number from 0 to 100. A higher score is healthier. The calculation gives serious incidents more influence while accounting for the number of enabled monitored pages.
The score is a triage aid, not a percentage of checks passed. It does not measure traffic, rankings, uptime over a period, or the business importance of a website.
The exact formula
TechDash first assigns each current open incident a weight:
- Advisory weight: 1
- Warning weight: 4
- Critical weight: 10
It multiplies the number of open incidents at each level by that weight, then adds the results:
weighted issues = Advisory + (Warning × 4) + (Critical × 10)
It then calculates:
Health Score = round(100 × enabled pages / (enabled pages + weighted issues))
The result is constrained to the 0-100 range. For example, a website with 10 enabled pages, three Advisory incidents, one Warning, and two Critical incidents has 27 weighted issues:
3 + (1 × 4) + (2 × 10) = 27
Its score is:
round(100 × 10 / (10 + 27)) = 27
Select View calculation in the Health Score card to see the page count, incident counts, weighted subtotals, total weight, and formula for that website. This is the best way to verify why the displayed number has changed.
How page count changes the result
The page count is the number of enabled monitored pages for the website. Disabled pages are not included. A given incident total has a larger effect on a small monitored set than on a large one. For example, one Critical incident gives a score of 50 with 10 enabled pages, but 91 with 100 enabled pages.
This scaling prevents the same raw incident count from being treated identically for every site. It also means scores should be interpreted within the context of each site's monitored coverage. Adding low-value pages solely to raise a score would make the number less useful and is not a valid remediation.
If there are no enabled pages and no open incidents, the score is 100. If an open incident remains when there are no enabled pages, the calculation uses one page so that the incident still affects the score.
Which incidents count
The live score counts current open issues by their built-in severity. Repeated alert notifications for the same issue do not each become another open incident. Recovering or resolving an issue removes it from the open set. Ignoring a check can also change which issues are included, depending on the ignored scope.
Historical incident openings shown in the chart are different. Those lines count opening events on each local calendar day. The live score card uses the current open set, so it can remain low on a day with no new openings.
Score colors and refresh timing
The radial score uses these bands:
- 80-100: green
- 50-79: amber
- 0-49: red
These colors summarize the calculated score. They do not change incident severity.
The Health Report is cached for up to five minutes. Incident and website changes invalidate derived data and prompt the page to reload, but a cached report can briefly remain visible. If a fix, recovery, resolution, ignore action, or page enablement change is not reflected immediately, allow up to five minutes and reopen or refresh the report.
Use the score to decide where to investigate, then use the incident evidence and business context to decide what to fix.