Free tool · Redirect speed test
How fast is **your redirect?**
Test one URL: see how fast it answers, where it finally lands, and how it ranks against every redirect tested here in the last 7 days.
Frequently asked questions
Every URL tested here in the last 7 days counts once, with its latest median time to first byte. A test runs from all three locations by default, and its average is compared with the average of every URL measured from all three. Pick one location and your result is compared only with URLs tested from there. “Faster than 82%” means 82% of them took longer than yours. The ranking starts once 30 URLs have been measured.
The timing covers the first response only, so a slow destination page does not count against the redirect. The chain is then followed to the page it lands on: every hop with its status code, and what to fix, such as a temporary redirect, extra hops or a hop over plain HTTP.
From Vercel Functions in three regions: Washington, D.C. (iad1), Frankfurt (fra1) and Tokyo (hnd1). By default all three run at once, and you see their average and the result for each location. Pick one to test from there only.
Add a second URL and both get the same number of runs from the same location, alternating A, B, A, B, each on a fresh connection, and we report the median. The test runs on Vercel, not on RedirHub's network, and the curl command lets you check it from your own machine.
Every test has its own page, such as /redirect-speed-test/example.com, with the chart, the chain and a share image. Anyone with the link sees the latest result, and it is measured again when it is more than 7 days old.
Distance to the server, your connection and DNS caching all change the numbers. Compare the gap between URLs, or against the average, not the absolute values.