Audits
The list of a site's audits, and the four tabs every audit has.
An audit is one check-up of your site at a point in time. It crawls up to 500 pages, runs the checks on each, measures the most important pages with PageSpeed, and saves a score. Audits are snapshots: a later audit never changes an earlier one, so you can see how the site moved between them.

The audit list
A site's Audits tab has Run audit, the audit schedule, and every audit of the site, newest first, 20 to a page.
| Column | What it shows |
|---|---|
| Audited | The date and time, in UTC. A partial audit says Partial under it. |
| Pages | How many pages the audit counted. |
| Change | How the score moved since the complete audit before it. |
| Score | The site score, from 0 to 100. |
A partial audit has no change of its own, and the audit after it is compared with the last complete one instead. Partial and capped audits explains why. On a phone, Pages and Change are hidden.
Running audits on a schedule is covered in Schedules.
Preview audits
Below the list, Preview audits shows each audit of a pull request's preview deployment, newest first: what it was (the pull request, branch and commit it was started with), its score, and how that compares with production, both scored without PageSpeed. A preview still going shows its status, and one that failed says why. Preview audits are started from the API or the GitHub action, and never count as one of the site's audits.
An audit's tabs
Open an audit to see its date, its page count and four tabs:
Summary
The score, what changed, what to fix first, and how the audit ran.
To do
One row per problem, ranked by how serious it is and how much its pages matter.
Issues
Every issue, grouped by check, with filters for status, severity and area.
Pages
Every page the audit visited, with its status, issues and screenshot.
To do and Issues show a count beside their name. They're turned off when there's nothing in them, for example an audit that found no issues.
Also in this section
- How the score works
- Marking issues as intended, for problems that are on purpose
- Comparing with another audit
- Issue prompts, to hand a fix to a developer's coding agent
- CSV exports
- Sharing a summary with someone outside your organization