← Back to overview

ISR — Incremental Static Regeneration

Uses Netlify's durable CDN cache with a 60-second TTL. After the first request, the rendered HTML is stored on the CDN. Subsequent requests within 60s get the cached version instantly. After 60s the page is served stale while a fresh render happens in the background.

StrategyISR
Rendered at

2026-03-23T18:57:08.826Z

If this timestamp stays the same across reloads, the page is being served from cache.

Expected Response Headers

Cache-Status: "Netlify Edge"; hit (or miss on first request)
Netlify-CDN-Cache-Control: public, durable, s-maxage=60, stale-while-revalidate=31536000

How it works

  • Nuxt routeRules: { isr: 60 } sets durable CDN caching
  • First request: miss → page is server-rendered and cached
  • Within 60s: hit → cached HTML served, timestamp stays frozen
  • After 60s: stale → cached version served, fresh render queued in background
  • Next request after revalidation: hit → new cached version with updated timestamp

Use cases

  • Marketing pages, blog posts, product pages
  • Content that updates occasionally but doesn't need to be real-time
  • High-traffic pages where CDN offloading matters