Does your page load many blocking files?
It counts resources marked as blocking the initial render.
What Check Engine measures
Successful pages are scanned for resources whose saved render-blocking flag is true. A page enters the finding when it has at least 5 such resources. Qualifying pages are sorted by count, and the report gives the worst count with a limited URL sample. It does not time each request or decide that every script and stylesheet should be delayed regardless of its role. For example, a page with exactly 5 blocking resources qualifies for this finding.
The check uses the crawler's recorded blocking-resource types on successful pages. It cannot measure every file's effect on display time. Review which files the first view needs before delaying them.
How to read the result
The finding is medium severity. A blocking resource can be necessary for initial display, so the count points to a review rather than proving that every listed file is wasteful.
Why it matters
Resources needed before a page can paint occupy a different place in loading from optional enhancements. The check makes that distinction visible through saved flags, while the correct loading order still depends on what the page needs to show.
How to fix it
Inspect the files and identify which are required for the first useful view. Defer scripts and delay nonessential styles only where the page continues to work correctly. Combine files when that is useful, then test loading and interaction. Measure the browser result separately instead of translating a lower count into an invented time saving.
How to fix render-blocking resources
What we found in field audits
Problems in Speed & Core Web Vitals were found on 13 of the 14 sites we audited. These are area totals. Read the field-audit method.
Method note
backend/seo_engine/checks/performance.py, render_blocking, revision 0bb8e8d3.
Common questions
How many blocking files trigger the resource-count finding?
At least 5 blocking resources on a successful page qualifies. Saved flags determine which files enter that count.
Does a blocking-resource finding mean every listed file should be delayed?
No. Some blocking files are needed for initial display. Review the first useful view before changing their loading order.
Does the blocking-file check time the delay from each request?
No. Display time is not measured for each file. The medium result uses saved blocking flags as a review prompt.