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… 🤷♂️
TIL: Configure an apex domain on #Netlify
the apex domain can’t take advantage of direct DNS routing on a global CDN like @Netlify’s
I guess I now understand why my photography site was slow from France…
TIL: #Cloudflare doesn't support the Vary HTTP header, which means the origin server can't do any content negotiation, for example send WebP or AVIF for a JPEG request…
https://developers.cloudflare.com/cache/about/cache-control/#other
#Fastly supports it, just saying… 😅