How Next.js renders (server-first model) - Quick Revision & Summary

Recall & Review

beginner

What does 'server-first model' mean in Next.js rendering?

It means Next.js renders pages on the server first before sending HTML to the browser. This helps with faster loading and better SEO.

intermediate

What is a Server Component in Next.js?

A Server Component is a React component that runs only on the server. It can fetch data and render HTML without sending extra JavaScript to the browser.

intermediate

How does Next.js handle client-side interactivity with server-first rendering?

Next.js sends minimal JavaScript to the browser to hydrate interactive parts. This means the page is mostly server-rendered but can become interactive on the client.

advanced

What is the role of React Server Components in Next.js's server-first model?

React Server Components let Next.js render parts of the UI on the server without sending their code to the client, reducing bundle size and improving performance.

beginner

Why is server-first rendering beneficial for SEO in Next.js?

Because the full HTML is ready on the server and sent to the browser, search engines can easily read and index the page content without running JavaScript.

In Next.js's server-first model, where is the initial HTML generated?

A On the server

B In the browser

C On a CDN

D In a database

Next.js generates the initial HTML on the server before sending it to the browser.

What is hydration in Next.js rendering?

A Fetching data from the server

B Compiling JavaScript code

C Converting server HTML into interactive React components on the client

D Caching pages on the server

Hydration means making the server-rendered HTML interactive by attaching React event handlers on the client.

Which Next.js feature helps reduce JavaScript sent to the browser?

A React Server Components

B Client Components

C Static Site Generation

D API Routes

React Server Components run only on the server, so their code is not sent to the browser, reducing JavaScript bundle size.

Why does server-first rendering improve SEO?

A It hides content from search engines

B Search engines get fully rendered HTML without needing JavaScript

C It delays page loading

D It requires user login

Server-first rendering sends complete HTML to search engines, making it easier for them to read and index content.

In Next.js, what happens after the server sends HTML to the browser?

A The page reloads automatically

B The server shuts down

C The browser ignores the HTML

D The browser hydrates the page to add interactivity

After receiving HTML, the browser runs JavaScript to hydrate the page, enabling user interactions.

Explain how Next.js uses the server-first model to render pages and why this is helpful.

Think about where the page is built and how it reaches the user.

Describe the role of React Server Components in Next.js's server-first rendering approach.

Focus on how they affect code sent to the browser.

Practice

1. What is the main reason Next.js renders pages on the server first?

easy

A. To avoid using React components

B. To run JavaScript only on the client

C. To improve page load speed and SEO

D. To prevent any HTML from being sent to the browser

Solution

1. Step 1: Understand server-first rendering purpose

   Next.js renders pages on the server to send fully formed HTML to the browser quickly.

2. Step 2: Connect server rendering to SEO and speed

   Sending ready HTML helps search engines read content and users see pages faster.

3. Final Answer:

   To improve page load speed and SEO -> Option C

4. Quick Check:

   Server-first rendering = better speed and SEO [OK]

Hint: Server rendering means faster pages and better SEO [OK]

Common Mistakes:

• Thinking server rendering delays page load
• Believing React is not used in Next.js
• Assuming HTML is not sent to the browser

2. Which Next.js function is used to fetch data on the server before rendering a page?

easy

A. getServerSideProps

B. componentDidMount

C. useEffect

D. getStaticProps

Solution

1. Step 1: Identify server-side data fetching functions

   Next.js provides getServerSideProps to fetch data on the server at request time.

2. Step 2: Differentiate from other functions

   getStaticProps runs at build time, useEffect and componentDidMount run on client side.

3. Final Answer:

   getServerSideProps -> Option A

4. Quick Check:

   Server data fetch = getServerSideProps [OK]

Hint: Server data fetch uses getServerSideProps [OK]

Common Mistakes:

• Confusing getStaticProps with server-side fetching
• Using client hooks like useEffect for server data
• Thinking componentDidMount runs on server

3. Given this Next.js page code, what will the browser initially receive?

export async function getServerSideProps() {
  return { props: { message: 'Hello from server' } };
}

export default function Page({ message }) {
  return <h1>{message}</h1>;
}

medium

A. HTML with <h1>Hello from server</h1>

B. An empty page with no content

C. JavaScript code only, no HTML

D. A JSON object with the message

Solution

1. Step 1: Understand getServerSideProps role

   This function runs on the server and passes props to the component before rendering.

2. Step 2: Determine what is sent to browser

   The browser receives fully rendered HTML with the message inside an <h1> tag.

3. Final Answer:

   HTML with <h1>Hello from server</h1> -> Option A

4. Quick Check:

   Server props produce HTML output [OK]

Hint: Server props render HTML sent to browser first [OK]

Common Mistakes:

• Expecting raw JavaScript or JSON instead of HTML
• Thinking page is empty initially
• Confusing client-side rendering with server rendering

4. What is wrong with this Next.js page code?

export async function getServerSideProps() {
  const data = await fetch('https://api.example.com/data');
  return { props: { data } };
}

export default function Page({ data }) {
  return <div>{data.title}</div>;
}

medium

A. React components cannot use props

B. getServerSideProps cannot be async

C. Props cannot be passed to components

D. fetch returns a Response object, not JSON data

Solution

1. Step 1: Check fetch usage in getServerSideProps

   fetch returns a Response object; to get JSON, .json() must be called.

2. Step 2: Identify missing JSON parsing

   Without calling await data.json(), data is not the actual JSON, causing errors in rendering.

3. Final Answer:

   fetch returns a Response object, not JSON data -> Option D

4. Quick Check:

   fetch needs .json() to get data [OK]

Hint: Always parse fetch response with .json() in server props [OK]

Common Mistakes:

• Assuming fetch returns JSON directly
• Thinking getServerSideProps can't be async
• Believing props can't be passed to components

5. You want to render a page that shows a list of users fetched from an API on every request. Which Next.js approach correctly ensures the page is server-rendered with fresh data each time?

hard

A. Use getStaticProps to fetch users at build time

B. Use getServerSideProps to fetch users on each request

C. Fetch users inside useEffect in the component

D. Hardcode the user list in the component

Solution

1. Step 1: Understand data freshness needs

   Fetching fresh data on every request requires server-side fetching at request time.

2. Step 2: Match Next.js data fetching methods

   getServerSideProps runs on each request, while getStaticProps runs once at build time.

3. Step 3: Evaluate client-side fetching

   Fetching inside useEffect delays data until after page load, hurting SEO and initial render.

4. Final Answer:

   Use getServerSideProps to fetch users on each request -> Option B

5. Quick Check:

   Fresh server data = getServerSideProps [OK]

Hint: Fresh data each request? Use getServerSideProps [OK]

Common Mistakes:

• Using getStaticProps for dynamic data
• Fetching data only on client side
• Hardcoding data instead of fetching