This translation has not been editorially reviewed yet. The German version is authoritative. Deutsche Fassung →
Redirects: every hop costs something
The check follows every redirect and counts the hops between the entered address and the final one. A page that responds directly is better than one reached via two or three stops.
- Chains build up historically: first from HTTP to HTTPS, then from the non-www version to the www one, then from the old address structure to the new one. Each rule is correct on its own; together they add up to three hops.
- Every hop is its own server request with its own response time — it hits the server response value in the Core Web Vitals audit area directly.
- The fix is usually to consolidate the rules: from every old version straight to the final one, instead of in stages. It also matters that internal links point straight to the final address.
FAQ
How many redirects are acceptable?
For the address being checked, a direct response is the goal. A single redirect is unremarkable in practice; a chain of several isn't.
Is 301 or 302 correct?
301 means "permanently moved", 302 means "temporary". For a final move, 301 is the correct statement; marking a permanent redirect as 302 keeps the old address artificially alive.