Cloudflare TTFB (latency) not good for Asia

ErawanArifNugroho

Comparation from a Free Cloudflare user with server located in Indonesia

fl=4f409
h=www.mydomain.com
ts=1587878447.32
visit_scheme=http
uag=Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/81.0.4044.96 YaBrowser/20.4.0.1458 Yowser/2.5 Safari/537.36
colo=SJC
http=http/1.1
loc=ID
tls=off
sni=off
warp=off

With Lowendbox :

fl=35f493
h=lowendbox.com
ts=1587878503.863
visit_scheme=http
uag=Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/81.0.4044.96 YaBrowser/20.4.0.1458 Yowser/2.5 Safari/537.36
colo=SIN
http=http/1.1
loc=ID
tls=off
sni=off
warp=off

SplitIce

@ErawanArifNugroho Confirmation

pbx

yokowasis said: But the timeout that bothers me. timeout means you will be disconnected while downloading asset. It impacts website load significantly. 30 seconds could begone 300 seconds.

Then ditch CF and configure well your server in the US so that it can handle the load (nginx, varnish...). If you are with a decent provider load time should be pretty good for static files.

pbx

eva2000 said: From my experience with Cloudflare my sites on free, pro, business and enterprise plans to optimise for origins:

For Australia/Indonesia, need at least CF Pro plan
For India, need at least CF Business plan

While true I think it's important that everybody keep in mind what's really needed for a fast page loading experience: people tend to believe that their website will load really slow if it's not served from very close. In most cases that's not true. If you improve your setup as much as you can on the origin and end up serving gziped static files it's in many cases enough to serve your static assets from the closest CF Pop, even on the free plan (SG is enough for most locations in the area). If your page take 600ms or more of php+mysql then it doesn't matter where it's hosted and how good or bad your CDN is: load time will be bad. Of course more and closest POPs won't hurt (unless there is too many and the site is too small as this would create more MISS), but they are not necessarily needed for all websites/setups.

tl;dr while you need this to get the fastest experience with CF, having your stuff delivered from a few ms more won't hurt in many cases if your site is well thought and you sent the web page quickly on the origin or use full page caching.

eva2000

pbx said: tl;dr while you need this to get the fastest experience with CF, having your stuff delivered from a few ms more won't hurt in many cases if your site is well thought and you sent the web page quickly on the origin or use full page caching.

+1 in most cases completely true and CF has other features worth using like WAF/Firewall and CF Workers.

isunbejo

test acess 2 locations with same domain (CF plan free)

1. Access from IP LA (Los Angles)

fl=4f227
h=***
ip=***
ts=1587909477.408
visit_scheme=https
uag=Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:75.0) Gecko/20100101 Firefox/75.0
colo=SJC
http=http/1.1
loc=US
tls=off
sni=off
warp=off

2. Access from IP ID (Indonesia)

fl=35f272
h=***
ip=***
ts=1587909807.323
visit_scheme=https
uag=Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:75.0) Gecko/20100101 Firefox/75.0
colo=SIN
http=http/2
loc=ID
tls=TLSv1.3
sni=plaintext
warp=off

adamus007p

@isunbejo said:
test acess 2 locations with same domain (CF plan free)

1. Access from IP LA (Los Angles)

> fl=4f227
> h=***
> ip=***
> ts=1587909477.408
> visit_scheme=https
> uag=Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:75.0) Gecko/20100101 Firefox/75.0
> colo=SJC
> http=http/1.1
> loc=US
> tls=off
> sni=off
> warp=off
> 

2. Access from IP ID (Indonesia)

> fl=35f272
> h=***
> ip=***
> ts=1587909807.323
> visit_scheme=https
> uag=Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:75.0) Gecko/20100101 Firefox/75.0
> colo=SIN
> http=http/2
> loc=ID
> tls=TLSv1.3
> sni=plaintext
> warp=off
> 

How to read this or make a similar test?

NanoG6

That's literally in the first post of this thread.
Anyway, you can also using curl -I

curl -I https://lowendbox.com
HTTP/2 200
date: Mon, 27 Apr 2020 00:13:32 GMT
content-type: text/html; charset=UTF-8
set-cookie: __cfduid=d385e57f3a737d7b73705353226909d701587946411; expires=Wed, 27-May-20 00:13:31 GMT; path=/; domain=.lowendbox.com; HttpOnly; SameSite=Lax
x-litespeed-cache: hit
cf-cache-status: DYNAMIC
expect-ct: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
server: cloudflare
cf-ray: 58a45692998cc368-SIN
cf-request-id: 025a946f9c0000c368ddae1200000001

isunbejo

@adamus007p said:

@isunbejo said:
test acess 2 locations with same domain (CF plan free)

1. Access from IP LA (Los Angles)

> > fl=4f227
> > h=***
> > ip=***
> > ts=1587909477.408
> > visit_scheme=https
> > uag=Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:75.0) Gecko/20100101 Firefox/75.0
> > colo=SJC
> > http=http/1.1
> > loc=US
> > tls=off
> > sni=off
> > warp=off
> > 

2. Access from IP ID (Indonesia)

> > fl=35f272
> > h=***
> > ip=***
> > ts=1587909807.323
> > visit_scheme=https
> > uag=Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:75.0) Gecko/20100101 Firefox/75.0
> > colo=SIN
> > http=http/2
> > loc=ID
> > tls=TLSv1.3
> > sni=plaintext
> > warp=off
> > 

How to read this or make a similar test?

just create domain + cf and test with different ip access, fresh account cf plan free

just test with fresh domain freenom:

from my homebox (ID);

from api-proxy (LA)

eva2000

adamus007p said: How to read this or make a similar test?

All cloudflare protected domains get a trace feature for diagnostic troubleshooting you access via https://yourdomain.com/cdn-cgi/trace

example for LET would be at https://www.lowendtalk.com/cdn-cgi/trace

note it reveals the visitor/your IP address too so if you don't want that publicly shown, remove it when you post publicly

vld

https://cloudflare-test.judge.sh/