Free tool · Redirect speed test

redirhub.com/bl or bit.ly/apple: which redirect is faster?

Measuring now. The result appears below in a few seconds.

Enter a redirect and press Test. Results appear here in a few seconds.

Reproduce it

Run the same test yourself

Copy this into a terminal on macOS or Linux. It already holds your URL, so paste it and press Enter. Only curl is needed.

Your numbers will differ from ours: they depend on where you run it and your network.

bash · 5 runs per URL

for u in 'https://redirhub.com/bl' 'https://bit.ly/apple'; do
  for i in $(seq 5); do
    curl -s -o /dev/null --max-redirs 0 --max-time 10 \
      -w '%{time_namelookup} %{time_connect} %{time_appconnect} %{time_starttransfer} %{http_code}\n' "$u"
  done | sort -n -k4 | awk -v u="$u" '{r[NR]=$0} END{split(r[int((NR+1)/2)],m," ");
    printf "%-28s %s  DNS %4.0f  connect %4.0f  TLS %4.0f  first byte %4.0f ms\n", u, m[5], m[1]*1000, (m[2]-m[1])*1000, (m[3]>0?m[3]-m[2]:0)*1000, m[4]*1000}'
done

The benchmark

How “faster than X%” is worked out

The number comes from the redirects people test on this page, plus a fixed list of well-known redirects measured every day, so each location always has a baseline.

1

Every test is kept for 7 days

Each URL tested here stores its median first-byte time and test location. One entry per URL, so testing the same link ten times doesn't tilt the result.

2

Compared like for like

By default your result is the average of all three locations, ranked against every URL measured from all three. Test from one location and it is ranked only against URLs tested from there, so Tokyo is never compared with Washington, D.C.

3

Your rank is a percentile

“Faster than 82%” means 82% of the URLs tested in the last 7 days took longer than yours.

By provider

How fast is each redirect provider?

As of 2026-10-20, 25 providers were measured from Washington, D.C., Frankfurt and Tokyo (average) over the last 7 days. Fastly was the fastest, at a median 11 ms. Every provider with at least one tested URL is listed with its median first byte. Open one for its locations, rank and where its time goes.

Method

What the test measures

DNS

Looking up the redirect's domain.

Connect

Opening a TCP connection to the closest server.

TLS

The HTTPS handshake and certificate check.

Server wait

Until the 301 and its Location header arrive.

Only the redirect response is timed, not the destination page, so a slow destination does not count against the redirect. Hops are counted separately. The tool runs on Vercel Functions in Washington, D.C., Frankfurt and Tokyo, not on our redirect network, and alternates A and B on every run.

The benchmark figures are free to reuse: credit RedirHub and link to this page. CC BY 4.0

FAQ

Frequently asked questions

How is “faster than X%” worked out?

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.

Does it follow the whole redirect chain?

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.

Where is the test run from?

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.

Is a comparison fair to both redirects?

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.

Can I share a result?

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.

Why do my curl results differ?

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.

Related free tools

Redirect checkerSee every hop and status code of a URL.URL expanderReveal where a short link really goes.Redirect uptime monitorLive uptime and response time of redirect services.