![[Chrome for Developers]](https://www.gstatic.com/devrel-devsite/prod/v0f3a5b8b76e4a120372a69044e02756e703b6140f9f1812c6e4a0407b19864b7/chrome/images/lockup.svg){kind=link}
![[Connor Clark]](https://web.dev/images/authors/cjamcl.jpg){kind=link}
Published: Oct 8, 2025
Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
How to pass this insight
This insight only fails if a critical request is not discoverable early in the page. A request is considered critical if it is potentially render-blocking or high priority.
Some strategies for minimizing the impact of long request chains:
- Minimize the number of critical resources, for example, eliminate them, defer their download, mark them as async.
- Optimize the number of critical bytes to reduce the download time (number of round trips).
- Optimize the order in which the remaining critical resources are loaded: download all critical assets as early as possible to shorten the critical path length.
Learn more about optimizing your images, JavaScript, CSS, and web fonts.
Stack-specific guidance
This insight also offers stack-specific guidance for pages using the following technologies:
Magento
If you are not bundling your JavaScript assets, consider using baler.