HTTP caching and browser media-performance prerequisites
Interpret the cache’s actual representation
A cache stores a representation under a particular key and applicable policy. Cache-Control directives determine relevant freshness and storage behavior. A max-age value specifies a freshness lifetime under its cache model, not a guarantee that the object is stored or never evicted. Private distinguishes a private-cache allowance from shared-cache storage under the directive’s actual semantics. No-cache permits storage but requires applicable validation before reuse; it is not synonymous with no-store.
Validate rather than resend unchanged data
An ETag can act as a representation validator. A relevant conditional request can receive304 Not Modified when the conditions for reuse are satisfied, avoiding retransmission of the representation body. Vary indicates request-header dimensions relevant to stored variants; it must align with how responses actually vary. Ignoring a meaningful personalization dimension can leak data, while adding irrelevant high-cardinality dimensions can fragment the cache. A tracking parameter that truly does not affect the returned bytes can be excluded under an intentionally configured model, but do not discard transformation parameters that change a Cloudinary representation.
Measure the user’s experience
TTFB, content transfer, rendering, layout shifts and interaction responsiveness describe different stages. A fast first byte does not prove the main image or page is visible. A responsive image can save bytes, yet a blocking script or unsuitable layout can still dominate perceived performance. Field measurements reflect actual populations, while controlled lab tests support repeatable comparison. Compare relevant percentiles and populations instead of hiding slow mobile users behind one combined mean.
Choose appropriate optimizations
Connection reuse and supported multiplexing can reduce selected overhead, while compression reduces eligible transferred bytes. A lower round-trip duration does not mean the protocol automatically uses fewer round trips. HTTP/2 still inherits relevant TCP loss behavior, and QUIC has different transport properties and resumption conditions. Avoid applying text compression blindly to already compressed media. When changing media, validate visual quality, accessibility, encoded size, actual cache behavior and representative loading. General web/CDN examples here are prerequisites and do not imply that another vendor’s Property Manager behavior is a Cloudinary setting. This exercise makes no HTTP request or production configuration change.