Post #1740739

Replies (1)

• @xavier@pony.social 2026-04-28 09:09

  @elena@aseachange.com when loading your page, the browser loads data from two domains: https://elenarossini.com: Hostinger proxy -> Wordpresss, for the "dynamic" page contenthttps://elenawp.b-cdn.net: Bunny CDN -> (probably Hostinger proxy?) -> Wordpress, for the "static" assets. For this one, cache invalidation is not an issue because the urls have a ?ver= parameter, for what we call "cache busting": instead of purging the cache, we generate a new URL that will bypass the existing cache For the main domain, you cannot use the "cache busting" technique, so there's three options for cache invalidation: the simple "cache for 1 hour, fetch afterwards" cache-control: max-age header: simple to setup, but page changes don't propagate quicklythe more complex "cache indefinitely, setup the CRM to signal changes to the cache": needs a plugin and can be hard to debugthe simple "cache indefinitely, manually go in the CDN config to purge caches", viable when changes are infrequent Looking at https://blog.elenarossini.com/, we can see cf-cache-status: HIT and cache-control public, max-age=0 headers on the main HTML, which is option 2. I've seen too many people struggle with option 2 on wordpress and don't have the wordpress voodoo skills to guide you through it, but if the website is an infrequently updated one, option 3 could be the least painful to setup? You'd need to have https://elenarossini.com also go through BunnyCDN (or another) and set it's config to always cache pages (except the admin, of course), then find out how to manually purge (or build a small script to do so).

  Open ##1740738