Want a website built and looked after for you?
We build small-business websites for £499 +VAT, then £59 +VAT a month covers hosting, support and small changes from our UK team. Tell us what you need and a real person will reply, usually within a few hours.
The audit is a score out of 100 and what to fix first, emailed within two working days.
Render-Blocking Resources Checker
What it does
The Render-Blocking Resources Checker reads a page’s HTML and lists every stylesheet, web font stylesheet and script in the head that the browser has to download before it can show anything. Each file comes with its size, how long our server took to fetch it, and the change that would stop it blocking. It is part of the SEO Suite.
Common situations
PageSpeed Insights has flagged “Eliminate render-blocking resources” and you want the list in plain terms, with the files that come from your own site separated from those added by plugins and third parties. The checker gives you that list in one run, and the size column shows which files are worth the effort.
You’ve added a cookie banner and the page now shows white for a moment before anything appears. Run the page before and after. If a new synchronous script or stylesheet has appeared in the head, it will be in the list.
A developer says the theme “already defers everything”. Check it. A WordPress site often has a dozen stylesheets queued by different plugins, and one script loaded without defer is enough to hold up the whole page.
You’re writing a brief for a site rebuild and want a baseline. Save the result for the current homepage and a typical inner page, then hold the new build to fewer blocking files.
What you need to know
When a browser receives a page, it reads the HTML from the top. Every <link rel="stylesheet"> it meets in the head has to be downloaded before the first paint, because the browser won’t draw a page it might have to restyle a moment later. Every <script src> in the head without async or defer stops the HTML parser until the script has downloaded and run. Until both are done, the visitor usually looks at a blank screen.
That delay adds to First Contentful Paint and to Largest Contentful Paint, which is a Core Web Vital. On a fast office connection the cost is small. On a phone with a weak signal, each blocking file can add a round trip of a few hundred milliseconds before the request even starts.
The checker treats these as blocking:
- stylesheets with no
mediaattribute, ormedia="all"or"screen" - scripts in the head with a
srcand none ofasync,deferortype="module" @importrules in an inline<style>block, which add a request the browser only finds after the first one arrives- Google Fonts stylesheets, flagged separately because they bring a third-party connection and, without
display=swap, invisible text while the font loads
A stylesheet with a media query such as (max-width: 600px) is listed as conditional. It blocks only on screens where the query matches. Stylesheets with media="print", files loaded with rel="preload", deferred and async scripts, and modules are counted as non-blocking and summarised under the table.
How to fix each kind
For your own scripts, defer is the safe default. Deferred scripts download in parallel and run in order once the HTML is parsed, which is what most site code expects. async suits independent scripts such as analytics, which can run whenever they arrive.
For CSS, the standard approach has two parts. Inline the small amount of CSS needed to draw the first screen into the head, then load the full stylesheet without blocking, either with rel="preload" as="style" and an onload switch to stylesheet, or with media="print" changed to all once loaded. WordPress caching plugins often call this “critical CSS” or “optimise CSS delivery”.
For fonts, add &display=swap to a Google Fonts URL so text shows in a fallback font straight away. Self-hosting the font files removes the extra connection to Google’s servers entirely.
What the checker can’t see
It reads the HTML our server receives. Files that JavaScript adds after the page loads, such as many tag manager tags and chat widgets, are not in that HTML and won’t be listed, although they can still slow the page down in other ways. Sizes come from a HEAD request, so a server that doesn’t report Content-Length shows a question mark. Times are measured from our server, not from a visitor’s phone, so treat them as a guide to which files are slow rather than as the delay a visitor sees.
Frequently asked questions
What are render-blocking resources?
Files the browser must download, and for scripts run, before it can paint the page for the first time. In practice that means stylesheets and synchronous scripts referenced in the head.
How many render-blocking resources is too many?
There is no official number. Every blocking file is a request that has to finish before the visitor sees anything, so fewer is better. One small stylesheet from your own domain is a reasonable target for most sites. Lighthouse estimates the time each one costs on a throttled connection, which is a useful second opinion.
Is all CSS render-blocking?
Stylesheets that apply to the screen are, by design. A stylesheet whose media query can’t match the current screen, such as a print stylesheet, is still downloaded but doesn’t hold up the first paint.
Should I use async or defer?
Use defer when the order scripts run in matters, or when a script needs the full HTML to exist first. Use async for scripts that stand alone. If you’re unsure, start with defer and test the page afterwards.
Do scripts at the bottom of the body block rendering?
They pause the parser when it reaches them, but by then the content above them has been parsed and can be painted. Moving scripts to the end of the body was the standard fix before defer had wide support. defer in the head achieves the same while letting the download start earlier.
Why does my result differ from PageSpeed Insights?
PageSpeed Insights loads the page in a real browser, so it also sees files added by JavaScript, and it estimates the time saved on a slow mobile connection. This checker reads the server HTML and lists what’s in the head, which makes it quicker for spotting the files you control.
Does fixing render-blocking resources improve rankings?
Indirectly. Page experience, including Core Web Vitals, is one of many signals Google uses, and it rarely outweighs relevance. The bigger gain is visitors on slow connections seeing the page sooner and leaving less often.
Common problems
Problem: A plugin’s stylesheet loads on every page, though the plugin is used on one.
Common with slider plugins, and with form plugins that only matter on the contact page. Many have a setting to load assets only where they’re used. If not, a few lines in the theme can dequeue the stylesheet everywhere else.
Problem: Adding defer broke something on the page.
An inline script further down probably calls a library, such as jQuery, before the deferred copy has run. Defer the inline script as well by moving its code into a file, or keep that one library blocking and defer everything else.
Problem: The result lists an
@import.
An @import inside CSS makes the browser fetch one file, read it, and only then discover the next. Replace it with a separate <link> in the HTML so both download at once, or combine the files.
Problem: The page has hundreds of kilobytes of inline CSS in the head.
Some optimisation plugins inline the whole stylesheet instead of the part needed for the first screen. That removes a request but makes every HTML download heavier and can’t be cached between pages. Inline the first-screen CSS only.
Tips
- Check a typical inner page as well as the homepage. Templates often load different files.
- Third-party files are the hardest to control. Ask whether each one needs to be in the head at all.
- After a change, re-run the check and then a Page SEO Audit to make sure nothing else moved.
- The HTTP Headers Inspector shows whether a slow file is being cached and compressed.
Related tools in this suite
Render-blocking files are one part of a slow first paint. TTFB & Server Response Time measures the server side, before any file is requested, and the Image Weight Audit covers the images that usually decide Largest Contentful Paint.
Take it further
If the list is long because plugins have piled up over years, removing a few won’t fix a theme that depends on them. Our guide to planning a website redesign covers setting performance targets before a rebuild starts. If you want a second pair of eyes on the result, send us the page and we’ll tell you which fixes are worth doing first.