STATUS IS UPWEBSITE READINESS

Readiness check · Accelerate lane · weight 5

No render-blocking scripts in <head>

Every external script in the document head uses async, defer or type="module".

Observed on
48%

of 28,750 measured sites

Top 1K sites
55%

285 measured

Top 1M band
45%

4,665 measured

Not measured
11,345

blocked, challenged or not applicable

Why it matters

A plain <script src> in the head stops the browser from showing anything until that file has downloaded and run.

How to fix it

Add defer to scripts that need the DOM, async to independent ones such as analytics, or move them to the end of the body.

How we check

Every external script in the document head uses async, defer or type="module".

Observed: Head scripts load without blocking.

Not observed: One or more head scripts block rendering.

Limit: Based on the homepage HTML delivered to an automated client; scripts that run later were not executed.

Stack-specific steps

  • Next.js: Use the next/script component with an appropriate loading strategy.
  • WordPress: Since WordPress 6.3, scripts can be registered with a defer or async loading strategy.

By popularity band

Chrome UX Report bandObservedMeasured
Top 1K55%285
Top 5K53%1,306
Top 10K50%1,645
Top 50K48%12,839
Top 100K46%3,893
Top 500K46%4,117
Top 1M45%4,665

Categories most likely to do this

Categories least likely

By stack

By provider

Popular sites where we observed this

Sources and guides