Gzip
PerformanceGzip is a lossless compression method that reduces the size of text-based web assets such as HTML, CSS, JavaScript, JSON, and SVG before they are sent from a server to a browser. By shrinking payloads in transit, it lowers bandwidth usage and speeds up page loads, especially on slower connections. It is commonly enabled at the web server or reverse proxy layer.
How It Works
Gzip compression is applied to HTTP responses when a client indicates support via the Accept-Encoding request header (for example, "gzip"). If enabled, the server compresses eligible content and returns it with the Content-Encoding: gzip response header. The browser then decompresses the content automatically before rendering it. This process is transparent to users and typically requires no changes to site code.
In hosting environments, Gzip is usually configured in Apache (mod_deflate), Nginx (gzip directives), or at a reverse proxy/CDN edge. Administrators choose which MIME types to compress (text/*, application/javascript, application/json, image/svg+xml) and set thresholds and compression levels. Already-compressed formats like JPEG, PNG, WebP, MP4, and most PDFs see little benefit and can waste CPU if recompressed. Proper caching headers and Vary: Accept-Encoding help ensure caches store the correct compressed and uncompressed variants.
Why It Matters for Web Hosting
Gzip affects real-world performance by reducing transfer size, which can improve Core Web Vitals and lower bandwidth consumption. When comparing hosting plans, look for easy access to server configuration (or a control panel toggle), support for modern compression options, and enough CPU headroom to compress responses under load. On very small plans, aggressive compression can trade bandwidth savings for higher CPU usage, so sensible defaults and the ability to tune settings matter.
Common Use Cases
- Compressing HTML output for dynamic sites (CMS pages, product listings, search results)
- Reducing CSS and JavaScript payloads for faster first render on mobile networks
- Compressing API responses such as JSON for web apps and headless CMS setups
- Optimizing delivery of SVG icons and inline vector assets
- Improving performance behind a reverse proxy or CDN by enabling compression at the edge
Gzip vs Brotli
Gzip is widely supported and simple to enable across most hosting stacks, making it a safe default for compatibility. Brotli is a newer compression algorithm that often achieves smaller file sizes for text assets, especially at higher compression levels, but may require specific server support and configuration. Many sites use Brotli for HTTPS traffic when supported and fall back to Gzip for older clients, balancing compression efficiency with broad compatibility.