Course contentsShow
← Web Development
Lesson 1726 of 2,98232. Server-Side Rendering ConceptsFree lesson

Subsequent Navigation Patterns

Understanding how client-side routing, full page loads, and prefetching differ by approach.

Subsequent Navigation Patterns

You'll learn: How different rendering strategies (CSR, SSR, SSG) handle navigation after the initial page load—and why it matters for user experience.

How Navigation Differs After First Load

Once your application has loaded, the way users move between pages varies dramatically depending on your rendering approach:

Client-Side Rendering (CSR)

After the initial load, navigation is instant. JavaScript intercepts link clicks, updates the URL, swaps out components, and fetches only the necessary data. The browser never performs a full page reload. Think of it like rearranging furniture in a room—the room (HTML shell) stays the same, only the contents change.

Server-Side Rendering (SSR)

By default, each navigation triggers a new request to the server, which renders fresh HTML and sends it back. However, modern SSR frameworks often use "hydration" to enable CSR-style navigation after the first page loads—giving you the best of both worlds.

Static Site Generation (SSG)

Navigation typically means fetching a pre-built HTML file from a CDN. It's faster than SSR (no server processing), but slower than CSR (still requires a document request). Some SSG frameworks add client-side routing through JavaScript to eliminate full reloads.

The Impact on User Experience

CSR: Fastest subsequent navigation—no white flash, instant transitions. But each route may need data fetching.

SSR (traditional): Full page reloads can feel slower and cause screen flicker, though each page arrives with complete HTML.

SSG: Fast static file delivery, but still experiences page reloads unless enhanced with client-side routing.

Key Takeaway: CSR offers the smoothest navigation experience after initial load, while SSR and SSG traditionally require full page requests—though modern frameworks often blend these approaches to provide CSR-like navigation benefits after the first render.