Sign inCreate a free account
Theme

Anatomy of a report

What every part of the report page is telling you.

A report is one page, analysed once, at one moment. It has a permanent address of the form /r/xRqeRgaHlR4i, so you can bookmark it or send it to whoever owns the fix without either of you signing in.

What is on the page

The top of a report: score, grade, finding counts, and the category panels below.

It reads top to bottom in order of what you need to know first.

PartWhat it tells you
Score and gradeOne number out of 100 and its letter. The summary, and the least useful thing on the page on its own. Scores and grades
Finding countsHow many critical, recommended and optional findings there are, and how many checks passed. This is the honest summary. Findings
Category panelsFive groups, each with its own score, each expandable into the individual checks that produced it.
The findings themselvesEvery check, with what was found, the evidence for it, and what to do.

The header

The URL shown is the one we finished at, not necessarily the one you typed. If the page redirected, the header says so and the redirect itself is a finding, because a chain of hops is something a crawler pays for on every visit.

Beside it is when the analysis ran. Reports are not live: the numbers describe the page as it was served at that moment. Change the page and analyse it again to get a new one.

The five category panels

Each category has its own score and its own findings. A page can be excellent at one and failing another, and the overall score would hide that, so the panels are where the actual work is.

CategoryChecksPage
Indexability and crawling73 vectorsReference
On-page content and structure63 vectorsReference
Core Web Vitals21 vectorsReference
Schema and rich snippets7 vectorsReference
Media and links28 vectorsReference

Why passing checks are shown

Most reports show only problems. We list every check, including the ones that passed, because the absence of a warning is ambiguous: it could mean the page is fine, or it could mean nobody looked. Seeing that we checked your canonical tag and found it self-referencing is worth something on its own, and it is what makes the failures believable.

Some checks report as skipped rather than passed or failed. That means we could not get the information rather than that the page failed: field vitals need enough real traffic to exist, and the security headers cannot be read if the connection itself failed. A skip is never counted against the score.

Sharing and exporting

The report URL is public to anyone holding it and is not listed anywhere. On a paid plan you can export the same report as PDF or CSV, and put your own logo on the PDF. See Exports and Branding.

Type to search. Try a check name from your report, an endpoint, or what you are trying to do.

↑↓ to move ↵ to open Esc to close