Reviewed October 25, 2026
Redirect Chains: The Invisible Delay in Front of Your Store
Every redirect is a round trip your shopper pays before the page even starts loading. Old campaign links, domain hops, and http to https chains add up. How to find and flatten them.
A redirect is a toll booth before the road
Before your storefront can be fast, it has to be reached. A redirect tells the browser the page lives somewhere else and sends it on a fresh request, a new round trip of DNS, connection, and response. One redirect for a moved page is normal housekeeping. A chain, where the first redirect lands on a second and sometimes a third, taxes every single arrival with delays measured in hundreds of milliseconds each on mobile networks.
Chains form innocently. The store moved from http to https, then from a www address to the bare domain, then an old campaign URL was redirected to a newer one that was itself later redirected. Each hop was a reasonable decision. Together they mean a shopper tapping an old ad or a saved link waits through three toll booths before your carefully optimized page is even allowed to start.
Where chains hide in a real store
The homepage chain is the classic: an ad or social link points at an old http www address, which hops to https, which hops to the non www domain, arriving three requests later. Email links from old campaigns and printed materials with legacy URLs feed the same chains for years. QR codes are forever, and the chain behind a code printed in 2023 is still being paid by every scan.
Internal redirects matter too. Menu links and blog posts pointing at URLs that were redirected during a tidy up add a hop to everyday navigation, and a redirect that lands on another redirect inside your own link structure is pure waste. Market and language redirects layered on top, sending a visitor through a country detection hop, can extend the chain further for exactly the international shoppers with the slowest connections.
How to find and flatten them
Crawl your own store with any redirect checking tool and export every URL that does not answer 200 directly. The report separates into three useful piles: single redirects that are fine, chains of two or more that need flattening, and redirects pointing at pages that no longer exist, which are 404s wearing a disguise. Work the chains first, since they tax every visit.
Flattening means editing the first redirect to point at the final destination, so A goes directly to C instead of through B. In your platform redirect list that is a one line change per chain. For the domain level hops, the fix is choosing one canonical address, one protocol, one host form, and pointing everything, ads, socials, email templates, at it directly, so the first request is already the last one.
Keep the chains from coming back
Every future restructure recreates the risk. When you redirect a page that was itself the target of older redirects, update the older entries to point at the new final URL in the same sitting. Redirect lists are append only in most stores, which is precisely how chains grow: nobody revisits the earlier entries when the later ones are added.
Audit the list twice a year alongside checking your highest traffic landing pages in a redirect tracer. Paid landing pages deserve special discipline, since every hop also sheds a fraction of visitors and can interfere with tracking parameters. Speed work usually starts at the page. The fastest stores also check the road in front of it, because a slow arrival makes a fast page feel slow.
Related reading
If this topic is useful, these earlier guides go deeper on connected questions: Lazy Loading Images on Shopify: Speed Gains and Pitfalls, Interaction to Next Paint on Shopify: Why Taps Feel Slow, and How Third Party Apps Slow Down a Shopify Store.
Frequently asked questions
How much does one redirect actually slow a page?
On a fast desktop connection, often 50 to 150 milliseconds. On mobile networks with higher latency, a single redirect round trip can cost 300 milliseconds or more, and chains multiply it. Two unnecessary hops can add over half a second before loading begins, which is a large share of a mobile patience budget.
Are redirects bad for SEO as well as speed?
Single redirects are a normal, supported way to move pages. Long chains dilute the clarity of the move, slow crawling, and occasionally drop parameters or fail on some clients. Search engines follow chains, but they recommend keeping them short, which aligns exactly with the speed advice: point every old URL at the final one.
Can I remove the http to https redirect?
No, and you should not want to: the secure version is the destination, not a hop to eliminate. The fixable waste is everything chained around it, such as legacy www and old path redirects stacked on top. One clean hop from any legacy address straight to the final https URL is the goal.
How do I check a specific link for a chain?
Paste it into any online redirect checker or use your browser developer tools network panel with preserve log enabled and watch the sequence of requests and status codes. A healthy link shows one request with a 200. Anything that shows two or more 301 or 302 steps before the 200 is a chain worth flattening.