What is Edge-Cached HTML?
Caching rendered HTML at CDN edge nodes close to visitors. Edge HTML caching cuts time to first byte for repeat views, but dynamic or personalized pages need careful keys or bypass rules to avoid serving one user’s markup to another.
Related terms
Cache-Control Headers
Response headers telling browsers and CDNs how long to reuse a file. This site serves its RSS feed with a one-hour public cache, while hashed static assets can carry far longer lifetimes because filenames change on rebuild.
CDN
A content delivery network serving static assets and cached pages from locations near the visitor. It cuts latency and TTFB globally without changing application code.
Caching
Storing responses at the browser, CDN, or edge so repeat visits skip origin work. Correct cache headers and edge caching are usually the cheapest large performance win available.
SSR Per Request
Fresh HTML rendered on the server for every request, used for personalized or frequently changing pages. Server rendering guarantees complete markup on first paint but costs compute per visit, so reserve it for dynamic routes.
CSR Shell
A minimal HTML shell that renders content in the browser after JavaScript loads. Client rendering suits authenticated dashboards behind login, where SEO matters less and interactivity starts only after scripts execute.
Hydration Cost
The JavaScript work that turns server-rendered HTML into an interactive app. Hydration replays component logic in the browser, so oversized bundles delay input readiness even when paint looks instant.