ISR Performance Characteristics
What you'll learn: How Incremental Static Regeneration balances the strengths of SSG and SSR, and where it impacts key performance metrics.
The Performance Sweet Spot
ISR sits between pure SSG and SSR, offering a unique performance profile. Understanding its characteristics helps you decide when it's the right choice.
Time to First Byte (TTFB)
First request (cache miss): Similar to SSG—instant from CDN. The page was pre-built, so users get near-instant responses.
During revalidation: Here's the magic. While a page regenerates in the background, users still receive the stale version instantly. Your TTFB stays fast even as content updates.
Think of it like this: A restaurant displays yesterday's menu (instant) while the chef quietly updates it for tomorrow. Diners never wait.
Server Load Comparison
vs. Pure SSG: Slightly higher load. Your server rebuilds pages periodically based on revalidation intervals, not just at build time.
vs. SSR: Dramatically lower. Instead of rendering every request, you render once per revalidation period (e.g., every 60 seconds). If 10,000 users visit in that minute, the server only worked once.
CDN Caching Benefits
ISR leverages CDN edge caching beautifully. The CDN serves cached static pages globally, reducing origin server requests by 99%+. When revalidation happens, only one request hits your server to update the cache—subsequent requests serve the fresh version from the edge.
Trade-off: Content freshness is bounded by your revalidation interval. A 60-second revalidation means content could be up to 60 seconds stale.
The Practical Result
ISR delivers SSG-like speed with SSR-like freshness. You get fast TTFB, minimal server costs, and automatic content updates—without manual rebuilds.
Key Takeaway: ISR provides near-instant TTFB and excellent CDN caching like SSG, with minimal server load compared to SSR, at the cost of controlled staleness during revalidation intervals.