Understand website ordering in the Health Report
Learn why lower-scoring websites appear first.
Last checked 20 August 2026
TechDash orders Health Report rows by current Health Score from lowest to highest. Because a lower score represents more weighted open-incident pressure, the numerically least healthy website appears first.
When two websites have the same score, TechDash sorts them alphabetically by website name using the computer's locale-aware text ordering.
What determines the order
Each website's live score uses:
- its number of enabled monitored pages
- current open Advisory incidents, weighted 1 each
- current open Warning incidents, weighted 4 each
- current open Critical incidents, weighted 10 each
The score is the rounded result of:
100 × enabled pages / (enabled pages + weighted issues)
This means ordering is not based on raw incident count. A site with one Critical incident can rank below a site with several Advisory incidents. The number of enabled pages also changes the relative impact, so two sites with the same open incidents can receive different scores.
Select View calculation on each row to compare the exact inputs.
Why rows move
A row can move when anything changes an input to the score. Common causes include:
- a new issue opens
- an open issue recovers
- you mark an issue resolved
- an ignored-check rule changes which issues are relevant
- an issue's effective severity changes
- a monitored page is enabled, disabled, added, or removed
The current report is cached for up to five minutes. Incident and relevant website changes cause the page to request an updated report, but the cached result may briefly remain. Do not assume an action failed solely because a row does not move immediately.
The Days, Months, and Years controls do not affect ordering. They change chart aggregation only. Rows always use the current live score, not the average score shown for a historical period.
Use ordering for triage, not prioritization
The first row is a sensible starting point for technical review, but it is not automatically the highest business priority. The formula does not know:
- revenue or lead value
- traffic and ranking importance
- whether the affected URL is a homepage or a minor page
- the cost of remediation
- whether a change was intentional
- contractual or launch deadlines
A strategically important site with a score of 80 may require action before a low-value test site with a score of 40.
Use the order as the first pass:
- Review the lowest-scoring row.
- Select View calculation to identify the weighted severity mix.
- Open Incidents and filter to that website.
- Check affected URLs, evidence, and business impact.
- Repeat for important sites even if they appear lower in the list.
Interpret close and equal scores carefully
Scores are rounded to whole numbers. Two sites can display the same score even when their unrounded ratios differ slightly, then use name order as the tie-breaker. Conversely, a one-point difference does not necessarily represent a meaningful difference in impact.
The score is also relative to monitored coverage. A site with many enabled pages can absorb the same weighted incident total with a smaller score reduction than a small monitored set. Keep page count in view when comparing sites.
If a website has no enabled pages and no open incidents, it receives 100 and normally appears near the bottom. If an open issue exists despite no enabled pages, TechDash uses one page in the calculation so that the issue still reduces the score.
For portfolio review, combine row order with your own site importance, then investigate the underlying incidents rather than managing only the number.