Avoid multiple page redirects

Redirects slow down your page load speed. Lighthouse flags pages that have multiple page redirects:

Lighthouse audit showing page doesn't avoid multiple redirects
Page doesn't avoid multiple redirects.

How this audit fails

A page fails this audit when it has 2 or more redirects.

Each PWA audit is weighted equally in the Lighthouse PWA Score, with the exception of three manual audits: Site works cross-browser, Page transitions don't feel like they block on the network, Each page has a URL. Learn more in The Progressive Web App score.


Your Lighthouse report lists resources that are being redirected. Update the links to these resources. The links should point to the current locations of the resources, so that the redirects are eliminated. It's especially important to avoid redirects in resources that are required for your Critical Rendering Path.

If you're using redirects to divert mobile users to the mobile version of your page, consider re-designing your site to use Responsive Design.

Why you should avoid multiple page redirects

When a browser requests a resource that has been redirected, the server usually returns an HTTP response like this:

HTTP/1.1 301 Moved Permanently
Location: /path/to/new/location

The browser must then make another HTTP request at the new location in order to retrieve the resource. This additional trip across the network can delay the loading of the resource by hundreds of milliseconds.

More information

Last updated: Improve article