Next.js 15 PPR in Production — Real-World Partial Prerendering Impact Partial Prerendering (PPR) is a stable feature in Next.js 15 that lets static and dynamic content live on the same page without forcing the whole route into one rendering model. Here is what that looks like in production, based on a real deployment. ## PPR Core Concept - Static shell delivered first: The page shell (header, footer, layout) is sent immediately

• Dynamic regions stream in: Personalized and real-time data are rendered progressively through Suspense
• Result: Static-level TTFB with the flexibility of dynamic content ```tsx

// app/products/[id]/page.tsx export const experimental_ppr = true export default function Page({ params }) { return (

- TTFB: 480ms (waiting for server data fetching to complete)
- FCP: 620ms
- LCP: 1.2s ### After PPR Migration
- TTFB: 85ms (static shell served immediately)
- FCP: 210ms
- LCP: 980ms (after the recommendations region finished streaming) **82% TTFB improvement**, with all Core Web Vitals moving into the green zone. ## Caching Strategy PPR caches the static portion at the CDN while keeping dynamic regions uncached. Next.js handles this split automatically: ```tsx
// Static — prerendered at build time, cached permanently
function StaticProductInfo({ id }) { const product = getStaticProduct(id) // fetch + revalidate return <ProductCard {...product} />
} // Dynamic — executed on every request
async function DynamicRecommendations({ userId }) { const items = await getPersonalized(userId, { cache: "no-store" }) return <List items={items} />
}

1. 1Watch for headers() / cookies(): These calls automatically switch the route to dynamic mode. Keep them out of the static shell
2. 2Increased build time: More routes are prerendered, so build time typically grows by 20–30%
3. 3dynamic imports: Heavy use of dynamic imports inside static regions can prevent the shell from being generated properly ## CF Pages + PPR Combo PPR is fully supported on Cloudflare Pages with @opennextjs/cloudflare 2.x.

• Static shell: served instantly from the CF CDN
• Dynamic regions: streamed through CF Workers
• Leverages all 330 global PoPs ## Comparison: PPR vs ISR vs SSR | Rendering | First Byte | Dynamic Data | Cache Strategy |