Client-side rendering sends a minimal HTML shell, then waits for the browser to download and execute JavaScript before constructing meaningful content. This all-at-once pattern can leave users staring at a blank screen or loading indicator. section 5.2.1
Evaluate client-side rendering against its delivery trade-offs:
- It can work well on fast connections and powerful devices. section 5.2.1
- It can delay visible content substantially on mobile networks and budget devices. section 5.2.1
- It may hurt user experience and SEO when important pages remain empty during JavaScript download and execution. section 5.2.1
DoorDash homepage
DoorDash found that users on mobile devices sometimes waited 10 seconds for the interface. Migrating high-traffic pages to server-side rendering with Next.js improved Largest Contentful Paint by 65% on the homepage and 67% on store pages; poor-LCP URLs fell by 95%. section 5.2.1
Table 5.1 Web rendering approaches
|
Rendering approach
|
Category
|
Waits for
|
Trade-offs
|
|
Server-Side Rendering
|
All-at-once
|
All data before sending HTML
|
Response blocked by server’s slowest data source
|
|
Client-Side Rendering
|
All-at-once
|
All JavaScript before rendering
|
User sees blank screen or loading indicator
|
|
Streaming SSR
|
Progressive
|
Nothing; sends chunks as ready
|
Added complexity
|
|
Islands
|
Progressive
|
Nothing; hydrates components independently
|
Architectural constraints
|
Compare client-side rendering with server-side rendering, streaming SSR, and islands architecture by what each approach makes users wait for. section 5.2.1




