Brotli at the edge cuts transfer size, but LCP still stalls when the critical document or LCP image is a MISS, blocked by a long origin path, or served under a cache key that fragments every viewer. Prefer Brotli on text assets with a stable content-hashed key, keep the LCP image on a short path with warm POP coverage, and strip cookies from that asset behaviour so compression savings are not erased by a cache bypass.
Ops prove-out after enabling Brotli: fetch the same CSS or JS twice and confirm Content-Encoding is br with a HIT on the second request, then measure the LCP asset Age and status across two POPs. If transfer size drops while LCP stays flat, look at document TTFB, render-blocking chains, and whether the LCP URL still BYPASS — lengthening edge TTL on a privately keyed object will not move LCP. Under a deploy, purge only the document shell and confirm hashed Brotli assets stay warm.