Type at least two letters.

    ↑ ↓ to moveEnter to open

    Read an audit report

    What each part of a report shows, what every status means, and what to fix first.

    Updated

    A report describes one audit run: one site, one moment, one profile. Open it from Audits, from a site’s latest result, or right after you start an audit.

    The top of the report

    • The status pill: queued, running, succeeded, partial or failed. While the run is queued or running, a notice says so and the page fills in when it is done.
    • The line under the title: the address that was read, when the run finished (or when a scheduled run starts), how long it took, and the profile.
    • Report a problem: opens the report form with this run attached. See Report a problem.
    • Run again: queues a new audit of the same site with the same selection of checks. If you had ticked the checks by hand without saving them, it opens Run audit… on Sites so you can pick them again.

    Where you stand

    The panel at the top sums up the run: the share of measured checks that passed, how many are left to fix and how many of those are high severity, and which one to start with. Checks that gave no result are left out of the share; they are never counted as failed. If the audit covered only part of the checks, the panel says so.

    Area tiles

    One tile per area: the number of checks to fix (or All good), a bar and the number that passed out of those measured, and how many could not be measured. Click a tile to jump to its checks. Areas group checks by topic: availability, security, email, performance, marketing, accessibility, privacy and technology. See The passive audit for what each area looks at.

    The checks

    To fix is selected first and lists the failed checks by area, the most severe first. All checks shows every result. Each row has the check, its status, its severity and a one-line summary of what was seen, for example the value of a header or the length of a title.

    Statuses

    Status Meaning Counts as a failure?
    To fix The check failed. Yes
    Passed The check passed. No
    No data There was nothing to check, for example no image on the page. No
    Not tested This audit cannot see it from outside, for example the TLS certificate’s expiry date or DKIM. No
    Not measured The measurement failed, not the site. No. Run again later.

    Severity

    A failed check is high, medium, low or info. Fix high first: it is the most likely to hurt visitors, mail delivery or security. Info is a note, not a problem.

    What a report is, and what it is not

    • One moment. A report shows what was visible when the run happened. Run it again after a change to verify the fix.
    • One page read. Performance findings come from reading the page once. They are not lab or real-user measurements.
    • Technical observations. Privacy findings describe what a visitor’s browser would receive. They are not legal advice or a certification.

    The same result over the API

    At the bottom of a report, the app shows the request that returns the same results. Over the API, a report is GET /audit-runs/{runId} plus GET /audit-runs/{runId}/observations; add ?status=fail for the checks to fix. See Audit runs.