HTTP Caching
PerformanceHTTP Caching is a performance technique where browsers, CDNs, and proxy servers store copies of HTTP responses and reuse them for later requests. By controlling cache behavior with headers like Cache-Control, Expires, ETag, and Last-Modified, sites reduce latency, bandwidth, and server load. Proper caching balances speed with freshness so users receive up-to-date content without unnecessary re-downloads.
How It Works
When a client requests a resource (HTML, CSS, JavaScript, images, fonts, API responses), an HTTP cache may save the response and serve it again on subsequent requests. Caches exist at multiple layers: the browser cache on the user device, shared caches such as corporate proxies, and edge caches in a CDN. Whether a response can be cached, for how long, and by whom is determined primarily by response headers.
The main controls are Cache-Control directives (for example, max-age, s-maxage, public, private, no-store, no-cache, must-revalidate). Fresh responses can be served directly from cache until they expire. After expiration, caches may revalidate using validators like ETag or Last-Modified via conditional requests (If-None-Match / If-Modified-Since). If unchanged, the origin returns 304 Not Modified, saving transfer time and bandwidth while keeping content current.
Why It Matters for Web Hosting
HTTP caching affects how much work your hosting plan must do per visitor. Strong caching reduces CPU usage, disk reads, and outbound bandwidth from the origin server, which can let a smaller plan handle more traffic and improve Core Web Vitals. When comparing hosting options, look for support for CDN integration, correct header configuration (via Nginx/Apache rules or app settings), and tooling to purge or version cached assets during deployments.
Common Use Cases
- Caching static assets (images, CSS, JS, fonts) with long max-age and versioned filenames
- Using a CDN to cache public pages and reduce origin requests during traffic spikes
- Revalidating dynamic content (news pages, product listings) with ETag/Last-Modified to avoid full downloads
- Caching API responses for short periods to smooth load and improve perceived responsiveness
- Preventing caching of sensitive or user-specific pages with private or no-store directives
HTTP Caching vs Server-Side Page Caching
HTTP caching relies on clients and intermediaries honoring HTTP headers to reuse responses, often reducing network round trips and origin bandwidth. Server-side page caching stores rendered output on the origin (or an application cache) and speeds up generation even when the response is not cacheable by shared caches (for example, personalized pages). Many sites use both: server-side caching to reduce compute, and HTTP/CDN caching to reduce latency and offload traffic from the host.