How do I check whether a redirect chain is slowing my site?
Tracing the path
A redirect chain happens when one address sends visitors to a second address, which then sends them to a third. Each hop adds a round trip before the page loads. A redirect checker lists every step with its status code, which makes it easy to spot a loop or an unnecessary extra hop.
- Enter the original address, not the final page
- Note the status code for each step
- Look for loops or repeated hops back to the same address
Fixing long chains
Update old links, such as those in menus or emails, so they point straight to the final address. Combine rules where possible, for example by sending a whole old domain to the new one in a single step. Test each change after saving, since rules sometimes interact in unexpected ways.
Measuring the difference
After you shorten a chain, run the check again and compare the number of steps. You can also look at page load timing in your browser's developer tools. Small gains add up on mobile connections, where each round trip costs more time.
Common mistakes
- Checking only the first address and missing a second redirect later in the chain.
- Fixing the chain in the server config while old links elsewhere still use the long path.
- Creating a redirect loop by sending the new address back to the old one.
