---
title: "Discussion on \"Brotli compression is on: why is PageSpeed / LCP still slow?\" | Hashnode"
description: "Discussion on \"Brotli compression is on: why is PageSpeed / LCP still slow?\". A green compression toggle is not an LCP fix. Confirm Content-Encoding on the critical path, then check the LCP element and Time to First Byte that still dominate the lab run."
url: "https://hashnode.com/posts/brotli-compression-on-pagespeed-lcp-still-slow/6acc9a9d3cc4806c8bbfe53a"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Brotli compression is on: why is PageSpeed / LCP still slow?](https://devlog.apogeewatcher.com/brotli-compression-on-pagespeed-lcp-still-slow?utm_source=hashnode&utm_medium=feed)

A green compression toggle is not an LCP fix. Confirm Content-Encoding on the critical path, then check the LCP element and Time to First Byte that still dominate the lab run.

Oct 12 · 8 min read · devlog.apogeewatcher.com  
Read the article

-   [#webperf](https://hashnode.com/tag/webperf)
-   [#core-web-vitals](https://hashnode.com/tag/core-web-vitals)
-   [#pagespeed](https://hashnode.com/tag/pagespeed)
-   [#lighthouse](https://hashnode.com/tag/lighthouse)
-   [#webdevelopment](https://hashnode.com/tag/webdevelopment)

## Written by

[Apogee Watcher](https://hashnode.com/@apogeewatcher)

@apogeewatcher · Greece

  
[View profile](https://hashnode.com/@apogeewatcher)

Solving web performance monitoring for agencies and solopreneurs

Apogee Information Systems operates at the intersection of digital transformation for international organisations, innovative e-learning, public service automation, and specialised commercial solutions. Currently building Apogee Watcher, a web performance tool for agencies and solopreneurs.

## Responses 1

Markdown supported · ⌘↵ to post

[CDN Edge Ops](https://hashnode.com/@cdnedgeops)

[6d ago](https://hashnode.com/posts/brotli-compression-on-pagespeed-lcp-still-slow/6acc9a9d3cc4806c8bbfe53a/comment/6af254103b80eabe017b449e)

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.
