Tell reported render blockers from static HTML candidates
Admin ·
Use a saved runtime report to see what was reported during a run. Use the HTML source to check declarations that might contribute to a delay.
Render Blocking Resource Detector
Compare the two blockers in the saved report
Open Sample evidence and choose Load Lighthouse report. Select Detect blocking resources. The supplied PageSpeed-format sample contains Lighthouse’s render-blocking-insight audit. catalog.css appears first with a 280 ms audit estimate and 28,000 recorded bytes. catalog.js follows with 140 ms and 42,000 bytes.
The supplied network tree has a depth of three and a reported longest-chain duration of 414 ms. The font in the dependency chain is separate from the two resources listed as blockers. Request estimates can overlap, so compare rows instead of adding the times into a predicted improvement.
Chrome Render-blocking requests insightLighthouse 13 replacement audit IDsChrome network dependency tree insight
Switch to saved HTML to find the declarations
Load saved HTML sample and detect again. It has four candidates. The enabled catalog.css and the synchronous catalog.js are in the head. navigation.js declares blocking=render. The wide.css stylesheet depends on a media condition.
The deferred reviews.js and the print stylesheet are left out of this screen-oriented check. The parser resolves the relative addresses through the saved base declaration. A static row identifies code to inspect. Use a runtime report to confirm a blocker in a specific visit.
HTML standard stylesheet and media behaviorHTML standard script and render-blocking behavior
Check scope before drawing a conclusion
The supplied pass sample reports no blockers. The retry-limit sample reports Incomplete capture. The fix-suggestion sample records the plan without applying any changes.
Download the JSON to save the audit ID, link order and source notes. If you change loading order, check actual first paint and compare a new capture with the same page and device settings.
Chrome Render-blocking requests insightChrome network dependency tree insight
Common questions
Can I use older Lighthouse exports?
Yes. The detector understands render-blocking-resources and the current render-blocking-insight. It reads PageSpeed JSON when the Lighthouse report is inside lighthouseResult.
Why is the runtime font in the chain and absent from the blocker rows?
The resource list comes from the blocker audit. The dependency tree describes a related chain, with its own scope and timing.