That's it! After a while comparing Netlify and Cloudflare TTFB from France, I moved my photography site to the later.
Results are great!
Impact for users is obvious:
Cloudflare in “Faster website, more customers: Cloudflare Observatory can help your business grow”:
The generated report provides an overall performance score ranging from 1 (least performant) to 99 (most performant)
First try on my photography site: 100 🤷♂️😅
Joke aside, new tools to audit performance are always welcome!
I still don't understand why using Cloudflare in front of Netlify allows for a much better and stable Time To First Byte (TTFB) than Cloudflare Pages or Netlify alone… 🤷♂️
TTFB for static sites should always be very low.
Any idea why there's so much TTFB difference on #Netlify for main vs branch deploys?
Here is TTFB for:
If you want to run a #GitHub Action after a #Cloudflare Pages build is done, you can use @WalshyDev's Action: https://github.com/marketplace/actions/cloudflare-pages-await
I hope Cloudflare Pages will get triggers like #Netlify: https://docs.netlify.com/functions/trigger-on-events/
Why is #Dareboost reporting "7 resources has a non-consistent extension with its actual content" in this report where #Cloudinary images were proxified through #Netlify, but not on this one where they're not… 🤷♂️