5
Components in the finished document
Competitor Technical Benchmark
The same technical measurements taken across named competitors, so the site's position is quantified rather than assumed.
Where This Sits
3
Measured directly, not asserted
1
Pieces that carry my judgment
This is a Diagnostics deliverable, which means it establishes what is true about the site now. It is the unit of scope: it can be commissioned on its own, priced on its own, and accepted on its own, whether or not anything else is bought alongside it.
It is not a package and not a retainer. It is one document with 5 components, and the list below is the whole of it.
What Is Inside It
Every component is listed with the one sentence that says what it is. They are grouped by how each one is produced, because the difference between a number a tool gave me and a number I decided matters more than most reports admit.
Measured
Pulled straight from tools and logs. No interpretation, so you can re-run any of it yourself and get the same numbers.
- Competitor comparison table
- The same measurements taken across named competitors, so the gap is quantified rather than described.
- Core Web Vitals field table
- Real-user LCP, INP and CLS by template and device, from field data rather than lab runs.
- Template inventory
- The finite set of page templates the site actually uses, which is what any fix gets applied to.
Computed
Built by combining the measurements above. Every figure states the inputs it came from.
- Schema coverage matrix
- Which schema types appear on which templates, and which are missing.
Judged
My reading of the evidence. This is the part you are actually paying for, and the part you are entitled to argue with.
- Method and scope statement
- What was examined, what was deliberately not, and with which tools and data ranges.