This rule triggers when PageSpeed Insights detects that you have more than one redirect
from the given url to the final landing page.
Overview
Redirects trigger an additional HTTP request-response cycle and delay page rendering. In the best
case, each redirect will add a single roundtrip (HTTP request-response), and in the worst it may
result in multiple additional roundtrips to perform the DNS lookup, TCP handshake, and TLS
negotiation in addition to the additional HTTP request-response cycle. As a result, you should
minimize use of redirects to improve site performance.
Here are some examples of redirect patterns:
example.com uses responsive web design, no redirects are needed - fast and optimal!
example.com → m.example.com/home - multi-roundtrip penalty for mobile users.
example.com → www.example.com → m.example.com - very slow mobile experience.
[null,null,["Last updated 2024-09-03 UTC."],[[["This PageSpeed Insights rule flags pages with multiple redirects, as they negatively impact performance by adding extra HTTP request-response cycles and delaying page rendering."],["Redirects can significantly slow down a website, especially on mobile devices, by introducing additional roundtrips for DNS lookups, TCP handshakes, and TLS negotiations."],["Responsive web design is recommended to avoid redirects and provide a seamless multi-device experience."],["If redirects are necessary, follow guidelines for proper implementation and user-agent detection."],["This documentation refers to a deprecated version of the PageSpeed Insights API; the latest version (v5) offers real-world and lab data for more comprehensive insights."]]],[]]
