PerformanceResourceTiming: renderBlockingStatus property

Limited availability

This feature is not Baseline because it does not work in some of the most widely-used browsers.

Note: This feature is available in Web Workers.

The renderBlockingStatus read-only property returns the render-blocking status of the resource.

It is useful to determine resources that:

  • weren't render-blocking and therefore could be delayed, or
  • were render-blocking and therefore could be preloaded.

Description

Render-blocking resources are static files, such as fonts, CSS, and JavaScript that block or delay the browser from rendering page content to the screen. The browser determines these blocking resources automatically and doesn't render any pixel to the screen before all stylesheets and synchronous scripts are loaded and evaluated. This prevents Flash of Unstyled Contents ("FOUC").

In addition to the automatic render-blocking mechanism, blocking="render" can be provided as an attribute and value to <script>, <style> or <link> elements to specify explicit render-blocking. For example:

html
<script blocking="render" src="important.js" defer></script>

Value

The renderBlockingStatus property can have the following values:

"blocking"

The resource might potentially block rendering.

"non-blocking"

The resource does not block rendering.

Examples

Logging resources that block rendering

The renderBlockingStatus property can be used to see resources that block rendering.

Example using a PerformanceObserver, which notifies of new resource performance entries as they are recorded in the browser's performance timeline. Use the buffered option to access entries from before the observer creation.

js
const observer = new PerformanceObserver((list) => {
  list.getEntries().forEach((entry) => {
    if (entry.renderBlockingStatus === "blocking") {
      console.log(`${entry.name} is render-blocking.`);
    }
  });
});

observer.observe({ type: "resource", buffered: true });

Example using Performance.getEntriesByType(), which only shows resource performance entries present in the browser's performance timeline at the time you call this method:

js
const resources = performance.getEntriesByType("resource");
resources.forEach((entry) => {
  if (entry.renderBlockingStatus === "blocking") {
    console.log(`${entry.name} is render-blocking.`);
  }
});

Specifications

Specification
Resource Timing
# dom-performanceresourcetiming-renderblockingstatus

Browser compatibility

desktop mobile server
Chrome
Edge
Firefox
Opera
Safari
Chrome Android
Firefox for Android
Opera Android
Safari on iOS
Samsung Internet
WebView Android
WebView on iOS
Deno
Node.js
renderBlockingStatus
Chrome – Full support
Chrome 107 (Release date: 2022-10-25)
footnote Full support
Edge – Full support
Edge 107 (Release date: 2022-10-27)
footnote Full support
Firefox – No support
Firefox
footnote No support
Opera – Full support
Opera 93 (Release date: 2022-11-17)
footnote Full support
Safari – No support
Safari
footnote No support
Chrome Android – Full support
Chrome Android 107 (Release date: 2022-10-25)
footnote Full support
Firefox for Android – No support
Firefox for Android
footnote No support
Opera Android – Full support
Opera Android 73 (Release date: 2023-01-17)
footnote Full support
Safari on iOS – No support
Safari on iOS
footnote No support
Samsung Internet – Full support
Samsung Internet 21 (Release date: 2023-05-19)
footnote Full support
WebView Android – Full support
WebView Android 107 (Release date: 2022-10-25)
footnote Full support
WebView on iOS – No support
WebView on iOS
footnote No support
Deno – No support
Deno
footnote No support
Node.js – No support
Node.js
footnote No support

Legend

Tip: you can click/tap on a cell for more information.

Full support
Full support
No support
No support