Redirecting domain name to Cloudflare URL results in 10+ seconds of loadtime

Hello there! We own a lot (thousands) domain names, and we use the redirect service of our registrar / hosting company to redirect our domains to a cloudflare site. For instance the domain rental.eu is being redirected to https://domeinenbank.nl/forwardlanguage/?domain=rental.eu. And Domeinenbank is a domain that’s proxied to Cloudflare.

Sometimes it lasts more than 10 seconds before the resulting page is presented to visitors, when they type in the domain name. However, when we open the URL which the domain name is redirected to directly, it never disappoints and loads within a few seconds.

The registrar states that their redirect services work flawlessly and blames Cloudflare for this delay. I think it’s strange, because the pages that Cloudflare serves should be slow also when we visit them directly.

So my question: is it possible that some setting in Cloudflare can cause this amount of delay? Good to know: the redirect service doesn’t work over the HTTPS-protocol. So for instance: https://rental.eu won’t redirect and therefore it doesn’t resolve. Next to that, we got a lot of traffic from bad bots. We block them using Cloudflare, but they will also go through the redirect service, as they follow our domain names.

Please help! Thanks in advance?

Redirects can result in latency because the client needs to make an additional request to the new URL specified in the response headers. This adds an extra round trip time (RTT) as compared to directly accessing the desired resource.

There are many reasons to cause the latency:

  • Server processing: When a request for redirection is received by the server, it needs to process this information and determine where to send the user next. The server may perform several operations before issuing the redirect instruction.

  • DNS lookups: If the redirected URL involves switching domains (cross-origin redirects), resolving DNS (Domain Name System) queries might introduce additional delays as servers look up IP addresses associated with specific domain names, establishing TCP connections and TLS (SSL) handshakes. If any of these steps encounter delays or issues, it prolongs the overall time taken for serving content to users.

  • HTTP request/response cycle: Each redirected request adds extra steps in the HTTP cycle – initial request processing, response generation by server-side scripts/frameworks, transmission of response headers back to clients – leading to increased overall loading times.

  • Caching: Web browsers often cache redirects temporarily so that subsequent requests do not require contacting the original server again immediately after redirection has occurred; however, this caching behavior can cause issues when updates are made but are not recognized until cached redirects expire.