Render Blocking Resource Detector
Analyze saved Lighthouse, PageSpeed, Resource Timing, diagnostics logs or HTML. Check reported resource delays, transfer sizes, chain evidence and HTML candidates.
Paste a saved report, diagnostics log or HTML source. The detector reads captured evidence on this device.
Sample evidence
Render Blocking Resource Detector: how to use it
- Paste diagnostics or open a saved UTF-8 report, log or HTML file. Choose the evidence type or let the tool detect it.
- Detect blocking resources. Compare ranked audit findings, request-chain values or static HTML candidates. Review notes about missing or incomplete capture evidence.
- Download the JSON report to keep the findings. Use a new capture to check whether changes improve first paint.
Limits and notes
Up to 2,000,000 UTF-16 code units, 4 MB files and 500 result rows. Saved HTML lists static head candidates. Saved Lighthouse evidence comes from supported render-blocking audit IDs. The detector reads addresses as text without visiting them.
How your privacy works →Render Blocking Resource Detector: common questions
Why are elapsed time and audit delay shown separately?
Elapsed time is the captured request duration. A Lighthouse delay estimate comes from the audit. Several requests can overlap, so their values are not additive savings.
Does saved HTML prove a request delayed paint?
Saved HTML provides candidates based on head tags and attributes. Use a runtime report to see whether a specific capture listed the request as blocking.
What does Incomplete capture mean?
The saved report or diagnostics contain a failed run or retry-limit marker, or the supplied data lacks readable blocker rows. Inspect any retained findings and use a fresh capture for coverage.