Skip to content

How to eliminate render-blocking resources

Speed1 min readFixes check render-blocking-resources

CSS and synchronous scripts in the head stop the browser from painting anything until they arrive. Inline the critical CSS, defer the rest and every paint metric improves.

Step by step, with screenshots: Critical CSS: is it still worth doing in 2026? →

Check your own site

Runs this check and the other 186, free, in about 45 seconds.

What a passing site looks like

  • No render-blocking resources delay the first paintwarning · −4 ptseffort M

Render-blocking files

Why it matters. Stylesheets and scripts in <head> stop the browser from drawing anything until they have downloaded. Each one adds a round trip before the visitor sees the page.

How to fix it.
  1. Add defer or async to scripts that are not needed before the first paint, or move them to the end of <body>.
  2. Inline the CSS needed for the first screen and load the rest asynchronously (WordPress: "Optimize CSS delivery" in WP Rocket / LiteSpeed Cache).
  3. Remove unused plugin CSS/JS from pages that do not need it.

Filed under Speed & Core Web Vitals. Copy is generated from the same catalogue that scores every report, so what you read here is what the report says.