Stay organized with collections
Save and categorize content based on your preferences.
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.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2024-09-03 UTC."],[[["\u003cp\u003eThis PageSpeed Insights rule flags pages with multiple redirects, as they negatively impact performance by adding extra HTTP request-response cycles and delaying page rendering.\u003c/p\u003e\n"],["\u003cp\u003eRedirects can significantly slow down a website, especially on mobile devices, by introducing additional roundtrips for DNS lookups, TCP handshakes, and TLS negotiations.\u003c/p\u003e\n"],["\u003cp\u003eResponsive web design is recommended to avoid redirects and provide a seamless multi-device experience.\u003c/p\u003e\n"],["\u003cp\u003eIf redirects are necessary, follow guidelines for proper implementation and user-agent detection.\u003c/p\u003e\n"],["\u003cp\u003eThis 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.\u003c/p\u003e\n"]]],["The content explains that multiple redirects slow down page rendering due to added HTTP request-response cycles and potential DNS lookups, TCP handshakes, and TLS negotiations. It recommends minimizing redirects and using responsive design to avoid them. When redirects are required, users should consult guidelines on redirects and user-agent detection. The document also notes that PageSpeed Insights version 4 is deprecated, and version 5 should be used instead. Lastly, it guides users to Stack Overflow and a mailing list for feedback.\n"],null,[]]
