HTTP Caching Explained: How max-age and ETags Affect What Users See

HTTP caching controls how browsers and intermediary systems store and reuse web resources, reducing load times by eliminating unnecessary network requests. A Cache-Control header with max-age=31536000 instructs browsers to serve a file locally for up to one year, meaning updates deployed to the server may not reach users until that period expires. This creates a practical dilemma: while caching dramatically improves performance — cutting repeat-visit load times to near zero — it also prevents browsers from fetching corrected files like updated stylesheets. Developers must distinguish between shared and private caching directives, as misconfigured headers on personalised pages can expose user-specific data through shared caches like CDNs or proxy servers. The article uses a fictional plant shop called PlantPal to illustrate how roughly 40 separate requests make up a typical homepage load, and why eliminating unnecessary requests entirely is the most effective performance gain.