Static Generation Cache vs. Server‑Side Rendering: Choosing the Right Caching Approach for Nuxt 3 Pages

Answer the exact question first

For a page that updates rarely but must show the latest data within hours, the optimal strategy is to use Incremental Static Regeneration (ISR) with a TTL of about 2–3 hours, or Stale‑While‑Revalidate (SWR) if ISR isn’t supported on your host.

Why ISR (or SWR) is preferable to pure static generation

• Performance – the page is served from the CDN cache, delivering fast responses.
• Freshness – after the TTL the next request triggers a background rebuild, so subsequent visitors receive up‑to‑date content.
• Low overhead – no manual rebuilds or cache‑purge steps are required.

Recommended cache duration

Set the expiration to 7200–10800 seconds (2–3 hours). This keeps the page fresh for most use‑cases while still allowing aggressive CDN caching.

Can ISR be configured on your current hosting environment?

It depends on the platform:

• Vercel, Netlify, Cloudflare Pages, AWS Amplify – support ISR out of the box; no extra infrastructure needed.
• Self‑hosted Nitro – requires a storage driver (Redis, KV, or file system) for ISR state; add the service if you don’t already have it.
• Static‑only hosts (GitHub Pages, Firebase Hosting without functions) – ISR is not available; you must use a longer static TTL or add serverless functions.

How to configure ISR in Nuxt 3

1. Open nuxt.config.ts and add a route rule for the page, e.g. routeRules: { '/my-page/**': { isr: { expiration: 7200 } } }.
2. Deploy to a platform that supports ISR. The first request after the TTL triggers a background rebuild while serving the stale copy.
3. Verify by inspecting response headers (e.g., x-vercel-cache: REVALIDATED on Vercel or cf-cache-status: HIT with a revalidation flag on Cloudflare).

Alternative: Stale‑While‑Revalidate (SWR)

If ISR isn’t available, use SWR with the same TTL:

routeRules: { '/my-page/**': { swr: 7200 } }

SWR serves the stale page immediately and revalidates in the background after the TTL.

What’s missing?

To give a definitive recommendation, please confirm which hosting platform you are using, as ISR implementation details differ across Vercel, Netlify, Cloudflare, and self‑hosted Nitro.