Why rendering strategy matters in NextJS - Visual Breakdown

Concept Flow - Why rendering strategy matters

User requests page

↓

Choose rendering strategy

↓

Server Render

↓

Send HTML

↓

Page loads fast

↓

User experience varies

This flow shows how a page request leads to choosing a rendering strategy, affecting load speed and interactivity.

Execution Sample

NextJS

export default function Page() {
  return <h1>Hello from Next.js!</h1>
}

// Rendering strategy: Server-side or Client-side

A simple Next.js page component that can be rendered on server or client, showing how strategy affects output.

Execution Table

Step	Action	Rendering Strategy	Result	User Experience
1	User requests page	N/A	Request received	Waiting for response
2	Next.js chooses rendering	Server-side	Render HTML on server	Page loads fast with content
3	Send response	Server-side	HTML sent to browser	User sees content immediately
4	User interacts	Server-side	Hydration happens	Page becomes interactive
5	User requests page	N/A	Request received	Waiting for response
6	Next.js chooses rendering	Client-side	Send JS bundle	Page loads blank initially
7	Send response	Client-side	JS bundle sent	User waits for JS to load
8	JS runs	Client-side	Render content in browser	Page becomes visible and interactive
9	Exit	N/A	Rendering complete	User experience depends on strategy

💡 Rendering completes after sending content and user sees page; speed and interactivity depend on strategy.

Variable Tracker

Variable	Start	After Step 2	After Step 3	After Step 6	After Step 8	Final
Page Content	undefined	<h1>Hello from Next.js!</h1> (server)	<h1>Hello from Next.js!</h1> (sent)	undefined (no HTML yet)	<h1>Hello from Next.js!</h1> (rendered client)	<h1>Hello from Next.js!</h1> (visible)
User Experience	Waiting	Loading fast	Content visible	Blank screen	Content appears	Interactive page

Key Moments - 3 Insights

Why does server-side rendering show content faster than client-side?

Because server-side rendering sends ready HTML, so the browser can display content immediately (see execution_table rows 2-4). Client-side waits for JavaScript to load and run first.

Why might client-side rendering show a blank page initially?

Because the browser receives only JavaScript and no HTML content initially, so it must run JS to build the page (see execution_table rows 6-8).

What happens during hydration in server-side rendering?

Hydration attaches JavaScript behavior to the already loaded HTML, making the page interactive without reloading content (see execution_table row 4).

Visual Quiz - 3 Questions

Look at the execution table, at which step does the user first see the page content in server-side rendering?

A Step 3

B Step 6

C Step 7

D Step 8

💡 Hint

Check the 'Result' and 'User Experience' columns for server-side rendering steps.

According to the variable tracker, what is the 'Page Content' value after step 6 in client-side rendering?

A "<h1>Hello from Next.js!</h1> (server)"

B "<h1>Hello from Next.js!</h1> (rendered client)"

C "undefined (no HTML yet)"

D "<h1>Hello from Next.js!</h1> (sent)"

💡 Hint

Look at the 'Page Content' row and the value after step 6.

If the rendering strategy changed to client-side only, how would the user experience at step 3 change?

A User sees content immediately

B User waits for JS to load with blank screen

C Page becomes interactive instantly

D Hydration happens at step 3

💡 Hint

Refer to execution_table rows 3 and 7 for differences between server and client rendering.

Concept Snapshot

Next.js rendering strategy affects how and when page content appears.
Server-side rendering sends ready HTML for fast initial load.
Client-side rendering sends JavaScript first, delaying content display.
Hydration makes server-rendered pages interactive.
Choosing the right strategy improves user experience and performance.

Full Transcript

When a user requests a page in Next.js, the framework chooses a rendering strategy: server-side or client-side. Server-side rendering builds the HTML on the server and sends it immediately, so the user sees content fast. Then hydration adds interactivity. Client-side rendering sends JavaScript first, so the user sees a blank page until the JS runs and renders content. This affects how quickly the page loads and becomes interactive. Understanding this flow helps developers pick the best strategy for user experience.