‘Delay Competing Low Priority Requests’ Could Speed Up Web Pages on Chrome

Google Chrome is preparing to add a new feature that will delay completing low priority requests. This will help pages render faster.

Delay Competing Low Priority Requests

Have you heard of Lazy Loading Images?

Chrome now supports native lazy loading of images. For example, assume that you are on a long page with a lot of images. Chrome will load images that that you need in the beginning of the page. It will load remaining images only when you start scrolling further.

This new feature is not very similar but achieves similar results.

Low Priority Requests

If you look at this this guide from Google for developers, you will see them encouraging “priority hints”.

“As performance becomes increasingly important, it’s exciting to see browsers implement new features which give developers more control over resource loading. Resource Hints such as rel=preload and rel=preconnect give developers more control over resource loading and connections to cross-origin servers, respectively. “

Priority Requests

Rendering is the process that turns the code (HTML, and images etc) into a webpage. What if Chrome delays rendering low priority resources?

Chrome Flag

Google Chrome will soon get a new experimental flag to test this possibility.

Delay Competing Low Priority Requests: Low priority requests will be delayed if they would otherwise compete with a high priority request.”

The feature request bug also reiterates the same message:

“This is an umbrella bug for the implementation work to delay competing low priority requests in the renderer process.”

The design document for this new feature, however, is private. Hence, we do not know more than what this flag gives out at this point.


It will take a while before this flag shows up in Chrome for us to test. However, this sounds like a feature that could speed up page loading on Google Chrome.

I won’t be surprised if Edge also picks up this feature at some point.

Questions, thoughts? Let us know in the comments section.

Source: Gerrit and bugs.chromium.org.

Leave a Reply

Your email address will not be published.