Render-blocking stylesheets: Crawl Audit check 86

Short answer: before showing anything, the browser waits for every stylesheet that applies to the screen, so the page doesn't flash unstyled. Each extra stylesheet can add to that wait. Check 86 warns when PageSpeed finds render-blocking resources, or, without PageSpeed, when the page links more than three stylesheets.

What Crawl Audit checks

• Full report: PageSpeed's render-blocking result, with the possible saving.
• Free check: a count of <link rel="stylesheet"> elements. Pass at three or fewer; warning above that.

What Google says

• Lighthouse flags a stylesheet unless it's disabled or its media attribute rules it out for the visitor's device. "media="all" is considered render-blocking."
• "When loading a page, the browser only blocks the first paint to retrieve the stylesheets that match the user's device".
• Lighthouse 13 turned this into the "Render-blocking requests" insight: "Deferring or inlining can move these network requests out of the critical path."

On devmarde.com

Our homepage links one stylesheet. PageSpeed estimated the render-blocking cost at about 70ms on 3 October.

Ways to reduce it

• Combine and trim. Fewer, smaller stylesheets (check 84).
• Use media for CSS that only applies sometimes, such as media="print", so it doesn't block the screen.
• Load third-party CSS (fonts, widgets) only where it's used.
• Inline critical CSS only if you need to (check 88). Google calls it "an advanced performance technique" that can "lead to bugs if not implemented properly".

Sources

• Chrome for Developers, Eliminate render-blocking resources and Render-blocking requests insight (8 October 2025), checked 3 October 2026.