Why Does My Website Take an Extra Second to Even Start Loading? Redirect Chains Explained
If your audit flagged a "redirect chain," here's the part that's easy to miss: this delay happens before your page even starts loading. Not a slow homepage - a slow detour the visitor's browser is forced through first, bouncing between two or three different addresses before it even requests the page you actually built.
What a redirect chain actually is
A single redirect is normal and harmless - visiting http and landing on https, for example, is expected on almost every site today. A chain is what happens when a visitor's browser has to follow two or more of these hops back to back before it reaches the real page: type the bare domain, get redirected to the www version, get redirected again to https, get redirected a third time to the current homepage URL. Every arrow in that sequence is a full round trip to your server - request, wait, read the new address, request again - before a single byte of your actual content arrives.
Why one extra hop costs more than it looks like
A redirect isn't a free instruction the browser applies instantly. Each hop is its own separate connection and response cycle, and on a phone over a real mobile network - not a fast office WiFi connection - that round trip routinely costs 300 to 500 milliseconds. A chain of two hops can add close to a full second before the browser even sends the request for the page that has your content, on top of whatever your server response time and page weight already cost separately. It's also compounding: every metric downstream - Largest Contentful Paint, time to first byte, how "instant" your site feels - starts its clock later because of this delay, not because anything about the actual page changed.
The three causes we see most in audits
www and non-www both configured, redirecting separately
The www version of a domain redirects to https, and the non-www version redirects to https separately too, instead of one of them pointing straight at the other's final URL. A visitor who lands on whichever one isn't the canonical choice pays for two redirects instead of one - and old links, bookmarks, and business cards printed years ago often point at whichever version fell out of favor.
An old URL structure left over from a redesign or CMS switch
A site migration, redesign, or platform switch changes the URL structure, and rather than pointing the old URLs directly at their new destinations, they get redirected to an intermediate "old homepage" URL that itself redirects again. Every backlink, bookmark, and social share built up over the site's history keeps paying that extra hop indefinitely unless someone goes back and fixes the target.
Marketing and tracking links stacking a redirect on top of the site's own
Link shorteners, ad-platform click-tracking URLs, and affiliate links each add their own redirect hop before handing off to the actual site - which then applies whatever redirects the site itself already has. A paid ad's tracked link landing on a www-and-https chain can mean three hops total before the page a visitor clicked an ad specifically to see actually starts loading.
Not the same as fixing the underlying problem by removing redirects
A single redirect - http to https, or one canonical domain choice - is expected and not something to eliminate; browsers and search engines both treat it as completely normal. The fix for a chain is collapsing multiple hops into one, not chasing a zero-redirect ideal: point the old or non-canonical URL directly at the final destination, so a visitor (or Googlebot, which spends its own limited crawl budget following the same hops) reaches it in a single jump instead of two or three.
How to check your own site
Unlike some audit findings, this one is checkable with a single command. Open a terminal and run:
curl -IL https://yoursite.com
Each block of response headers in the output is one hop. A healthy site shows a single redirect (or none) before a final "200 OK." If you see two or more "301" or "302" blocks stacked before that final 200, that's a real chain - and a free online redirect-checker tool works the same way if you'd rather not use a terminal.
How the free audit catches this
Redirect chains are one of the checks in our free audit, run alongside the rest of the causes in why your website is slow and our full website audit checklist. The report names the exact chain and how much time it's estimated to be costing, not just a generic warning.
Frequently asked questions
What is a redirect chain?
A redirect chain is when a visitor's browser has to bounce through two or more URLs before it reaches the page that actually loads - for example, typing your domain lands on the www version, which redirects to https, which redirects to the current homepage URL. Each arrow in that chain is a full round trip to your server before a single byte of the real page arrives.
Why does one redirect cost so much time?
A redirect isn't free - the browser has to open a connection, wait for the server's response, read the new address, and start over. On a fast wired connection that might only add 100-200ms per hop, but on a mobile connection with real-world latency it's routinely 300-500ms per hop, and chains of two or three hops are common. That's up to a full second gone before the browser even requests the page that actually has your content.
What usually causes a redirect chain?
The three most common real-world causes: (1) www and non-www both configured, and both redirecting to https, so a visitor hits two separate redirects instead of one; (2) an old permalink or URL structure left in place after a site migration, redesign, or CMS switch, so links from years-old backlinks, bookmarks, and social posts still point at a URL that has to redirect to the new one; (3) marketing tools - link shorteners, ad-tracking URLs, affiliate links - that add their own redirect hop on top of whatever the site itself already has.
Is fixing a redirect chain the same as removing redirects entirely?
No - a single redirect (say, http to https, or www to non-www) is normal, expected, and not a problem on its own. The fix for a chain is collapsing multiple hops into one: pointing the old URL directly at the final destination instead of at an intermediate redirect. The goal is one hop maximum, not zero.
How do I check my own site for redirect chains?
Open a terminal and run curl -IL https://yoursite.com (or use a free online redirect-checker tool if you're not comfortable with a terminal). Each block of headers in the output is one hop; a healthy result shows just one redirect (or none) before a final 200 OK. Two or more 301/302 blocks before that final 200 is a real chain the free audit will also flag automatically, along with which specific URL is causing it.
The cheapest way to find out
Run the free audit below. We check speed - including this exact redirect-chain test - alongside SEO, accessibility, and security, using the same tooling Google itself uses, and email you a plain-English report the moment something's wrong. If something needs fixing, it's a flat $149 for your fixable speed/image/SEO/broken-link issue, or $299 for everything, with before-and-after proof once it's done.