Inlining critical CSS: Crawl Audit check 88

Short answer: critical CSS means putting the styles for the first screen directly in the HTML, so the page can paint without waiting for a stylesheet, and loading the rest later. It can help, but Google calls it an advanced technique most sites don't need. Check 88 is a low-impact check: it passes if the page has any inline <style>, and warns if it has none.

What Crawl Audit checks

• Pass: at least one <style> element in the HTML.
• Warning: none.

It's a simple test. Any inline style passes, whether or not it's the critical CSS, and a fast site with one small stylesheet still gets a warning. Read it alongside check 86 and your FCP (check 75).

What Google says

• web.dev: "Critical CSS is a technique that extracts the CSS for above-the-fold content in order to render content to the user as fast as possible."
• "To minimize the number of roundtrips to first render, aim to keep above-the-fold content under 14 KB (compressed)."
• "if you inline a large amount of CSS, it delays the transmission of the rest of the HTML document. If everything is prioritized then nothing is."
• Chrome's Lighthouse 13 guidance: "Most sites should be able to achieve all of our recommended performance targets without implementing this technique."

On devmarde.com

Our homepage has no inline <style>, so it gets this warning. It loads one stylesheet and its FCP was 1.1 seconds on mobile (3 October), so we're leaving it.

When it's worth doing

• Your FCP or LCP is slow, and render-blocking CSS is the main cause.
• You have a build tool that extracts and inlines it automatically, so it stays in step with your design.

Sources

• web.dev, Extract critical CSS, checked 3 October 2026.
• Chrome for Developers, Render-blocking requests insight (8 October 2025).