Glossary · Page speed

Render-blocking resources

Also called: render blocking, critical CSS, defer JavaScript

Definition

Render-blocking resources are CSS and JavaScript files the browser must download and process before it can show anything on the page.

Render-blocking resources explained

When a browser loads a page, it reads the HTML from the top. Stylesheets in the head, and scripts without the async or defer attributes, pause rendering until they have downloaded and run. On a slow connection, several large files can leave visitors looking at a blank screen.

Common fixes include:

  • Adding defer or async to scripts that aren't needed for the first view.
  • Inlining the small amount of critical CSS needed for above-the-fold content and loading the rest later.
  • Removing unused CSS and JavaScript, often left behind by themes and plugins.
  • Self-hosting fonts and loading them with a sensible font-display setting.
  • Loading third-party tags through a tag manager after the page is interactive.

PageSpeed Insights and Lighthouse list render-blocking resources, with the estimated time each costs, which makes them a practical place to start.

Example

Your theme loads a large icon library stylesheet and a slider script in the page head on every page, even where neither is used. Loading them only on pages that need them, and deferring the script, lets the page render much sooner.

Why it matters

Removing render-blocking files is often one of the biggest single improvements to how quickly a page first appears and to LCP.

Related service

Page Speed Optimization

We fix LCP, INP and CLS issues so pages load fast and respond quickly for real users.

Page speed and Core Web Vitals optimization

Published by Vidern, founded and led by Malhar Shah. Updated .

Find out what's holding your site back

Get a free SEO audit with prioritized fixes, delivered within 48 hours.