Sure, the page rule I have is this:
Forwarding URL (Status Code: 301 - Permanent Redirect, Url:
The only reason for this redirect is to go from all non-WWW and non-HTTPS, directly to WWW-HTTPS. E.g.
I know it’s weird, but my web host can’t configure this on NGINX, and they prefer to leave as this:
https://www.example.com. It’s minimal latency for the redirect, but I just don’t like it
In any case, the cache is being hit without issues (I think), because in all the relevant Headers, I am seeing
CF-Cache-Status: HIT. Attached a screenshot for reference:
So, Cloudflare helps me fix this very easily with that page rule, for ALL pages with the one redirect.
Regarding the paid option of Polish: thanks, I will look into that… It does make me question though why anyone would then even consider using Cloudflare (free version) with a setup I’ve described in that WebP images are being served where possible.
Since I am literally just starting out, would you suggest that it’s best to DISABLE WebP files entirely > keep Cloudflare on for ‘free’ caching > see how we go until I’ve scaled a little? I’m running a Stock photo website so not images overload anyway!