Pre-rendering and Edge Distribution
You'll learn how to maximize page load speeds by building pages ahead of time and distributing them globally through edge networks.
What is Pre-rendering?
Pre-rendering means generating your complete HTML pages during the build process rather than when users request them. Instead of a server constructing each page on-demand, the pages already exist as static files before anyone visits your site. This is the foundation of SSG approaches you've already studied.
Edge Distribution Explained
Once your pages are pre-rendered, they're copied to edge servers—data centers scattered across the globe in locations like Tokyo, London, São Paulo, and Sydney. When a user in Germany visits your site, they receive files from the nearest edge server (likely Frankfurt) rather than from a single origin server in, say, Virginia.
Analogy: Think of it like McDonald's. Instead of one kitchen in Chicago shipping hamburgers worldwide, they have restaurants everywhere. Your burger is "pre-rendered" using the same recipe, but served locally for instant delivery.
The Performance Impact
This combination delivers two critical benefits:
- No server processing time - Pages are already built, so there's no waiting for a server to generate HTML
- Minimal network latency - Files travel shorter physical distances, reducing Time to First Byte (TTFB)
The result? Pages often load in under 100ms globally. Compare this to SSR, where every request needs server processing plus network travel time.
How CDNs Enable This
Content Delivery Networks (CDNs) handle the edge distribution. When you deploy to platforms like Netlify, Vercel, or Cloudflare Pages, they automatically distribute your pre-rendered files to hundreds of edge locations. Users always hit the nearest cache.
Key Takeaway: Pre-rendering at build time combined with edge distribution through CDNs eliminates both server processing delays and geographic latency, creating the fastest possible page loads for users worldwide.