Why Do Redirects Make WordPress Sites Slow?

Every redirect is a detour. The visitor’s browser asks for a page, gets told to go somewhere else, asks for that page, and so on until it reaches the real destination. Each detour takes time. On a WordPress site that has accumulated years of permalink changes and plugin configurations, these detours can stack into a real speed problem.

What is a redirect and why does each one add time?

When you visit a URL, your browser sends a request to the server and waits for a response. A redirect is a response that says “the page you want is actually over here.” The browser then makes a second request to the new address.

Each round trip between the browser and the server takes time. On a fast connection, one redirect adds roughly 100 to 200 milliseconds. On a slow mobile connection, it can add 300 to 600 milliseconds. A chain of three or four redirects adds up before any content starts loading.

This is pure waiting time. The browser is not downloading anything useful. It is just following directions from one address to another.

How do redirect chains build up on WordPress sites?

Redirect chains rarely happen on purpose. They accumulate through ordinary site management decisions that each seemed reasonable at the time.

HTTP to HTTPS migration. When a site adds an SSL certificate and moves from http:// to https://, the old URLs need to redirect. If the migration was done in stages, there may be redirects from http:// to https://, from the non-www version to the www version, and from an old path structure to a new one, all chained together.

Permalink changes. WordPress allows you to change your permalink structure. Example.com/p=123 becomes example.com/2022/blog-post, then becomes example.com/blog-post. Each change can create a new layer of redirects on top of the existing ones.

Content moved by plugins. SEO plugins, page builders, and content management plugins sometimes move content to new URLs and create redirects automatically. If those plugins are changed or the content is moved again, the chains extend.

Trailing slash rules. WordPress has its own rules about trailing slashes in URLs. Example.com/about and example.com/about/ are treated as different URLs. An external link to one version gets redirected to the other. If another redirect is already in place on that URL, the chain grows.

Domain name changes. A business that changes its domain name often ends up with a redirect from the old domain to the new one. If the new site then restructures its URLs, visitors from old links follow two redirects to reach any page.

How to find redirect chains on your site

Redirect Detective (redirectdetective.com) is a free tool. Enter any URL from your site and it shows every hop in the redirect path with the status code at each step.

httpstatus.io is another free option. It shows the full redirect chain for multiple URLs at once and is useful for checking a batch of your most important pages.

Your main homepage, your most important service pages, and any pages you know have changed their URLs are the best places to check.

What you can do today

1. Check your homepage first. Enter your domain in Redirect Detective. Count the hops. More than two is worth fixing.
2. Check your most linked pages. Any page that receives external links is worth checking. Redirect chains on those pages waste the link value.
3. Consolidate http and https. If your site still has any http:// to https:// redirect steps, update those at the server level to eliminate the hop.
4. Remove redundant redirect rules. If your SEO plugin has a redirect manager, review the list. Look for chains where redirect A points to redirect B, which points to the final URL. Change redirect A to point directly to the final URL.
5. Set www preference in one place. Decide whether your site uses www or not, and configure it consistently in WordPress settings and your hosting panel. This prevents the www vs. non-www redirect from adding a step.

Why redirects accumulate and keep accumulating

Redirects are the archaeological record of every URL decision a site has ever made. Every change leaves a layer. Over years, the layers stack.

This is not a sign of poor management. It is the natural result of a site that grows and changes. The problem is that the browser does not know the history. It follows every step.

Keeping redirects clean requires periodic audits and consolidation. Like database cleanup and image compression, it is recurring maintenance rather than a one-time fix.

Basalt moves small business websites off WordPress to a platform with nothing to hack and nothing to update. The move is free. Part of that migration is a clean, consolidated URL structure with no inherited redirect chains. If you are curious what the transition looks like, see how to leave WordPress without losing your site.

Find out what is wrong in 60 seconds

Or skip all this. Enter your web address and we will tell you exactly what is wrong with your site. Free, 60 seconds, no account needed.