Term
Brotli / Gzip Compression
Server-side compression methods that shrink text resources like HTML, CSS and JavaScript before transmission — Brotli usually delivers better ratios than Gzip today.
Brotli / Gzip Compression — explained in more detail
Both methods compress responses transparently via the HTTP Content-Encoding header. Gzip (based on Deflate, since 1992) is universally supported and delivers ~70% size reduction on text. Brotli (Google, 2015) typically achieves 15–25% better ratios than Gzip at comparable performance — largely thanks to a pre-trained dictionary for web-typical content.
Browsers advertise what they support in the Accept-Encoding header — the server then dynamically picks the best available method. In practice Brotli is preferred and Gzip serves as fallback.
Example / practical use
A 250 KB JavaScript bundle drops to ~75 KB with Gzip, ~60 KB with Brotli. Over poor mobile connections, a noticeable LCP advantage. Activation happens in the web server (Nginx: brotli on;) or at the CDN.
Distinction from related terms
Compression is lossless — no quality is lost, unlike image compression (WebP/AVIF). Brotli supports two modes: dynamic (at request time) or static (precomputed at build time, e.g. .br files) — the latter allows higher quality levels without server CPU load.
Entdecke mehr
CDN (Content Delivery Network)
A distributed server network that delivers static — and increasingly dynamic — content from the geographically nearest edge server to the user.
LexikonTechnical SEO — what Google actually has to crawl, render and index
How crawl budget, robots, sitemap, JS rendering, indexing, canonical and Core Web Vitals fit together — the full arc for production sites.
NewsGoogle Search Central Live Toronto 2026 — what Google officially said about the future of search
Information Gain as the new guideline, Google-Extended clarified, AI Mode with 93% zero-click. The key statements from Toronto.