Comparing audits

Each audit is compared with the previous comparable audit of the same address. Damdit compares issue by issue, rule by rule.

Change	Meaning
New	Found for the first time.
Resolved	Found before, not found now, on pages the audit could check.
Reappeared	Found again after an audit confirmed it absent.
Inconclusive	Can’t be compared. The reason is shown.
Still detected	Found in both audits. Not a change.

Why a change is Inconclusive

• The check was updated between the two audits. A different method can find more or less, so Damdit doesn’t count it as a change of the website.
• The earlier audit did not assess this issue.
• One of the audits could not check every affected page.

When every difference between two audits comes from updated checks, Damdit says so instead of listing changes. The next audit compares normally.

What isn’t compared

• Audits of different addresses of a project: production, staging and local each have their own history.
• Audits measured with different audit engines, for example one saved by an earlier version of Damdit.
• Audits saved before Damdit kept issue history.
• Scores across a change of the scoring method, the audited address, the modules or the coverage. History marks these changes.