Back to all dispatches

Frontend·Sep 28, 2026·6 min read

Next.js 15 Partial Prerendering: sub-100ms e-commerce at scale

Why choosing between static generation and server-side rendering is finally a false dichotomy, and how we reduced TTFB by 48%.

Bikram S.

Bikram S.

Full-Stack Lead, Teklin

Next.js 15 Partial Prerendering: sub-100ms e-commerce at scale

In traditional e-commerce architectures, you had to choose: pre-render static HTML for lightning-fast CDN delivery, or run dynamic server rendering to show real-time cart counts and user location.

Next.js Partial Prerendering (PPR) flips this paradigm. The page shell, navigation, product titles, and hero images are served statically from the nearest cloud edge in 18ms. Meanwhile, user-specific inventory badges stream in parallel via React Suspense.

We implemented this pattern for regional marketplace clients and observed an immediate 48% drop in Time-to-First-Byte.

Teklin Architecture Standard

“Write code so clean that any senior engineer can onboard in 24 hours. The best performance optimization is deleting code you didn’t need to write.”