Something is very Bad with the Performance at Cloudflare.
I have disabled for specific URL’s Path the Routes to Workers.
The Request once hit the Cloudflare POP should go direct to my Origin as i serve for this specific url’s dynamic content and there is no need to use any workers.
When i check now the Time to Forst Byte for this route the Performance is Very Very Bad even the request should go direct to my Origin it looks like in most cases it is delayed by Cloudflare by around half a second before anything happens.
See here very Bad Cloudflare Performance for Requests that should go direct to Origin:
When i disable the Cloudflare CDN and instead all request go direct to my Origin without the CDN
the Performance increases dramaticaly and proves that Cloudflare is slowing Down Requests to the Origin very Bad !
Ofc… now it is, after I run the tests it will hit in cache, for all second requests. You can not test my pages since I did not clear the cache for you to hit a first request.
Both on the same server?
All I can say is: it’s not a Cloudflare problem and I think I have proven it, since it then must be reproducable on my sites aswell. Since I have all plans of Cloudflare I can run multiple tests to see is there is a problem somewhere. ATM there are no problems.
If this is the website/domain of one of your clients then actually you should be able to figure out where the problem lies. Not a Cloudflare problem anymore. Q. E. D.
Yes need to figure out this problem.
You dont have this problems with ttf.
Thank you very much for proving that.
It helps me a lot to isolate the problem more.
It is very strange when i bypass Cloudflare that this problem with very high TTFB goes away.
So ISP could be not the Problem when testing the TTFB without Cloudflare.
Webserver is also not the Problem when testing TTFB without Cloudflare.
Only leaves out that there is a Problem with the ISP in combination with Cloudflare.
Will open a ticket and see if there is some kind of problem between Cloudflare and the isp.
Just wanted report that i could reproduce the very bad Cloudflare Performance
with a another new unused domain at Cloudflare that just print dynamicly 1 line with php.
It uses HTTP and not HTTPS to prevent any possible problems realted to SSL
One time it makes a request to a test.php script with Cloudflare Proxy CDN Enabled and has a very bad TTFB Performance.
And one time it makes a request to the same test.php script with Cloudflare Proxy CDN Disabled and has the good TTFB values.
Here the very Bad test Results with Enabled Cloudflare CDN Proxy
I’ve seen issues like this caused by some small-scale datacenter providers throttling the traffic from certain Cloudflare IP’s. This results in traffic for domains proxied through Cloudflare having a higher TTFB and overall slower speeds.
Not sure if thats the issue but it’s a guess as to why you’d be having a high TTFB when but a low TTFB when . It may not be the datacenter itself but could also be the ISP of the datacenter throttling it.
Can you setup a vhost or alias for https://throwaway-domain-6789.xyz/ on your same Switzerland server, and put a simple index.html file to serve. I’ll setup a test.
I just setup a vhost on the same server for the domain http://throwaway-domain-6789.xyz/
Its not a https but only http to avoid create ssl certificates and additional problems.
You only need to make a A DNS record now and you should be able to access the following files
index.html
index.php
test.php
The php file are just 1 liner print commands that prints simple text and exit.
(
(
. It may not be the datacenter itself but could also be the ISP of the datacenter throttling it.
