Hello! AWS' Cloudfront CDN has 44 PoPs in Asia alone, while Fastly's CDN only has 11 (and three of those are in Singapore).
Some of us have Asia-only audiences and paying 2.3x a month just to get servers closer to 99.99% of our users is quite hard to swallow (especially when our websites are not businesses/e-commerce). For example, we are a 501(c)3 non-profit and we don't need any of the "Business" plan features--except for a CDN that exists in the same country as our users (Malaysia). Fastly never joined the MyIX (Malaysian Internet Exchange), while Cloudflare and AWS Cloudfront both did join and thus provide far faster & more reliable caching.
We would gladly pay $26/month (CMS pricing + $10/month) for all the CMS plan restrictions + AWS Cloudfront hosting. This pill is harder to swallow since the only alternatives are impossible: Cloudflare's CDN does not work with Webflow & code export (via a Lite Account Plan) is $16 additional to the $16 on the CMS plan.
Please, Webflow, do consider this. Our audience is stuck on Fastly's few, non-ideal CDNs. We'd give up all caching in Europe/Africa/South America just to get our major content cached in Asian CDNs near our users.
You might try a workaround.
Create your own Cloudfront distribution and add your mydomain.webflow.io domain as an origin. Keep the Custom Domain option so that Webflow doesn't reject traffic with that domain header. Then point your www.mydomain.com to your Cloudfront distribution (might test it with another custom domain first such as test.mydomain.com).
You also need to add this code in the Head Code of each page in the Custom Code section of your site settings:
document.documentElement.dataset.wfDomain = 'www.dabblewriter.com';
I had to do that to remove a badge that pops up I believe. It's been a while.
I am using Cloudfront so that I can use other origins like /api/* pointing to a backend API server on my www domain. It's been working great for over a year. You'll have to control how long the cache holds it for.
Attachments Open full size