How to use it
- 1
Paste a public URL and choose mobile or desktop.
- 2
Run the provider check through the WebDiag backend.
- 3
Review the audit score, provider display value, estimated savings, and returned rows.
What the tool can do
- Reads only the audit with the render-blocking-resources ID and does not infer results from CSS or JavaScript.
- Shows up to 20 normalized rows with known bytes and estimated wasted time.
- Removes query strings and fragments from resource URLs before responding to the frontend.
Common use cases
- Check for provider-confirmed blocking resources before optimizing the critical path.
- Compare mobile and desktop audits for one page.
- Record an unavailable state when the Lighthouse contract changes without producing a false green result.
How it works inside
The backend accepts only a public URL, calls PageSpeed, and returns a strict DTO.
A missing audit is distinct from an available audit with no returned item rows.
Questions and answers
Why can the audit be unavailable?
The provider payload depends on the Lighthouse version and selected insights. WebDiag requires the exact ID and does not substitute its own classification.
Do zero rows mean there are no issues?
Not necessarily. Check audit availability and score; missing item rows alone are not universal proof.