AVO
Read the results
Every audit you queue lands in the same table. This topic is about reading that table precisely — where each column's number comes from, and why the things people expect to find here (a largest-images gallery, benchmark cards, a health score) are not part of this screen.
How it works
- There is no largest-images gallery —
Optimization runsis a six-column table, and this is what each column is - How to read payload, optimized, and saved — and why there are no benchmark or recommendation cards on this screen
- What a run measures, and where the rest of the engine's output is actually surfaced
Good to know
- A
FAILEDrow keeps its place in the list and the failure reason is not shown in the table - The list request returns the newest 25 runs; older runs stay in the database and are reachable only through the API
- Rows are per URL, so one domain audited on three pages produces three rows