Read incident trends and Health Score charts
Interpret daily average openings and score movement over time.
Last checked 20 August 2026
Each website on Health Report has one chart that combines incident-opening activity with Health Score history. These are related measures, but they are not the same measure.
Identify the four lines
The solid colored lines represent new incident openings:
- Advisory uses the Advisory color.
- Warning uses the Warning color.
- Critical uses the Critical color.
These lines use the left axis. TechDash counts fail events by their configured severity. Multiple duplicate opening events for the same website, URL, rule, and local calendar day are merged into one opening for the chart. A recovery event remains separate.
The dashed foreground line represents Health Score and uses the right axis, fixed at 0, 25, 50, 75, and 100. It summarizes the weighted open incident set for that day. Because the chart has two axes, a Critical line at the same visual height as Health Score does not mean the values are equal.
Hover a point to read the values for its date, month, or year.
Understand what each range aggregates
The labels Days, Months, and Years change both the time window and the chart bucket:
- Days shows up to 30 local calendar days. Each incident value is that day's opening count. The score is that day's score.
- Months shows up to 12 calendar months. Incident values are the total openings in the month divided by the number of relevant days, rounded to one decimal place. Health Score is the whole-number average of available daily scores.
- Years shows up to five calendar years. It uses the same daily-average incident and average-score method across each year.
For a partial current month or year, the divisor includes only days through today. For the first visible bucket, days before the website existed are excluded. The chart also omits complete buckets that end before the website's available history begins.
Today's Health Score point uses the current live score. If a day has no stored snapshot, TechDash fills incident openings with zero and carries forward the previous Health Score. This keeps the time series continuous without claiming that an incident opened on the missing day.
Interpret common patterns
An incident spike means several issues opened during that period. It does not necessarily mean they are still open. Check the current Incidents list to see which ones recovered or were resolved.
A low Health Score with flat incident lines usually means existing incidents remain open even though few or no new incidents are opening. Conversely, a brief opening spike can coexist with a high current score if those issues recovered quickly.
A score that falls after a small Critical spike is expected because Critical incidents have 10 times the weight of Advisory incidents. Warning incidents have four times the Advisory weight. Page count also scales the score, so two websites can respond differently to the same opening count.
Look for:
- a spike aligned with a deployment or content release
- repeated spikes on the same cadence, which can indicate unstable output
- a score that remains depressed after opening activity stops
- gradual recovery as open incidents close
- a change immediately after monitoring coverage or enabled pages changed
Move from a trend to evidence
The chart is designed for pattern recognition. It does not list rule names, affected URLs, expected values, actual values, or individual check runs.
After finding a suspicious period, open Incidents and filter to the website. Review current evidence and use the incident history to distinguish an ongoing problem from one that recovered. If you fixed a current issue, use Check & Verify where available, then allow the Health Report cache up to five minutes to update.
Do not infer SEO impact from line height alone. Severity, affected pages, business importance, and whether the change was intentional all matter.