This is listed on the Pro plan page:
“Global Content Delivery Network (CDN) Improve latency and performance with location-based access to your website using our 165 data centers located around the globe.” https://www.cloudflare.com/plans/pro/
But I was told it wouldn’t due to the high bandwidth charges to Australia. https://blog.cloudflare.com/the-relative-cost-of-bandwidth-around-the-world/
I just found these 2 blog posts down below now from a quick Google search. Since caching can mean 2 different things here, I just wanted some clarification on how Cloudflare routes and fetches requests when you first set it up without static content caching at the edge nodes.
1. What this blog post down below refers to, it’s not content caching, but requests rerouting to Cloudflare’s servers (when the orange cloud is enabled in the DNS tab) which then go back to the origin to fetch all dynamic content if a static rule isn’t setup for static HTML content.
What does Cloudflare actually cache by default on standard setting? From looking at DevTools, it seems like it stores a copy of all content at 2 of CF’s IP addresses (hosts), but those IP addresses / servers then fetch content there and then from the origin, hence the double slow down there as well.
2. FULL Static HTML/CSS/JS caching with a Page Rule where requests don’t hit back to the origin? (I’ve tried several WordPress static site generators, but none are working with my Elementor.com Page Builder, so I’m relying on Cloudflare here to pull through with full static page caching).
Some more transparency around affected performance in Australia from Cloudflare would have been nice. There’s no mention of which countries are used for the Pro plan, so I’m assuming it’s all countries by that marketing play… can some CF Engineer please confirm before I decide to commit?
I’ve been using Cloudflare for 6 years, I joined with the premise of having a faster site loading experience, but it’s honestly not the case for free users in Australia or neighbouring countries for that fact.
The only real value here is free automatic SSL (which Let’s Encrypt offers too, but I haven’t had the need to set it up since I’ve always used CF) and Page Rule Redirects for www. redirections or http to https is pretty easy (and caching if it works), but that can all be done in Nginx or Apache as well if you have any server admin experience or don’t mind learning.
CF just makes it easy and puts it all in one GUI console place. Just ironic the performance isn’t there for Australians (at least on free) which is the primary reason of why people use a CDN and it isn’t warned for Australian users when they go to use it.