Why rendering strategy matters in NextJS - Quick Recap

Recall & Review

beginner

What is rendering strategy in Next.js?

Rendering strategy is the way Next.js decides when and how to generate the HTML for a page, either on the server, at build time, or on the client.

beginner

Why does Next.js offer multiple rendering strategies?

Because different pages have different needs: some need fresh data every time, some can be pre-built for speed, and some can load data on the client for interactivity.

intermediate

What is the difference between Server-Side Rendering (SSR) and Static Site Generation (SSG)?

SSR generates the page on each request, giving fresh data but slower response. SSG builds pages once at build time, making them very fast but less fresh.

intermediate

How does rendering strategy affect user experience?

Choosing the right strategy can make pages load faster, show up quickly on screen, and keep data up to date, which makes users happy and engaged.

intermediate

What happens if you choose the wrong rendering strategy for a page?

The page might load slowly, show outdated data, or use too much server power, which can frustrate users and increase costs.

Which Next.js rendering strategy builds pages once at build time?

A Client-Side Rendering (CSR)

B Server-Side Rendering (SSR)

C Static Site Generation (SSG)

D Incremental Static Regeneration (ISR)

SSG builds pages once during the build process, making them fast to serve.

What is a key benefit of Server-Side Rendering (SSR)?

A Pages have fresh data on every request

B Pages are pre-built and very fast

C Pages load only on the client

D Pages never update after build

SSR generates pages on each request, so data is always fresh.

Why might you choose Client-Side Rendering (CSR) in Next.js?

A To pre-build pages for speed

B To load data after the page loads for interactivity

C To generate pages on the server every time

D To avoid using JavaScript

CSR loads data in the browser after the page loads, useful for interactive content.

What does Incremental Static Regeneration (ISR) allow you to do?

A Disable caching for all pages

B Build pages only once and never update

C Render pages only on the client

D Update static pages after build without rebuilding the whole site

ISR lets you update static pages after build time, combining speed and freshness.

What is a risk of using SSR for all pages?

A Server load can increase and slow down responses

B Pages might be outdated

C Pages cannot show dynamic data

D Pages will not be SEO friendly

SSR requires the server to generate pages on every request, which can increase load and slow responses.

Explain why choosing the right rendering strategy in Next.js is important for both performance and user experience.

Think about how fast pages load and how fresh the data is for users.

Describe how Incremental Static Regeneration (ISR) combines benefits of static and dynamic rendering in Next.js.

ISR lets you update static pages without rebuilding the whole site.

Practice

1. In Next.js, why does choosing the right rendering strategy matter for your website?

easy

A. It decides which fonts are used on the page.

B. It changes the color scheme of the website automatically.

C. It controls the size of images on the page.

D. It affects how fast the page loads and how fresh the content is.

Solution

1. Step 1: Understand rendering strategy impact

   Rendering strategy determines when and how page content is created and delivered to users.

2. Step 2: Connect rendering to performance and freshness

   Choosing the right strategy affects page load speed and how up-to-date the content appears, which is important for user experience and SEO.

3. Final Answer:

   It affects how fast the page loads and how fresh the content is. -> Option D

4. Quick Check:

   Rendering strategy = speed and freshness [OK]

Hint: Rendering strategy controls speed and content freshness [OK]

Common Mistakes:

• Thinking rendering changes colors or fonts
• Confusing rendering with styling or image size
• Assuming rendering affects only visuals, not performance

2. Which Next.js page export correctly sets a page to use Static Site Generation (SSG)?

easy

A. export default function Page() { return Hello }

B. export const getServerSideProps = async () => { return { props: {} } }

C. export const getStaticProps = async () => { return { props: {} } }

D. export const getInitialProps = async () => { return { props: {} } }

Solution

1. Step 1: Identify SSG method in Next.js

   Static Site Generation uses getStaticProps to fetch data at build time.

2. Step 2: Match export to SSG

   Only getStaticProps triggers SSG; others are for server-side or legacy methods.

3. Final Answer:

   export const getStaticProps = async () => { return { props: {} } } -> Option C

4. Quick Check:

   SSG = getStaticProps [OK]

Hint: SSG uses getStaticProps export [OK]

Common Mistakes:

• Confusing getServerSideProps with SSG
• Using getInitialProps which is legacy
• Not exporting any data fetching function

3. Given this Next.js page code, what will the user see when visiting the page?

export async function getServerSideProps() {
  return { props: { time: new Date().toISOString() } };
}

export default function Page({ time }) {
  return 
Current time: {time}
;
}

medium

A. The current server time updated on every request.

B. The time when the site was built, never changes.

C. An error because getServerSideProps cannot return props.

D. A blank page because time is undefined.

Solution

1. Step 1: Understand getServerSideProps behavior

   This function runs on every request, fetching fresh data each time.

2. Step 2: Analyze returned props usage

   The page receives the current server time as a prop and displays it inside the div.

3. Final Answer:

   The current server time updated on every request. -> Option A

4. Quick Check:

   getServerSideProps = fresh data each request [OK]

Hint: getServerSideProps runs every request, shows fresh data [OK]

Common Mistakes:

• Thinking it shows build time (that's SSG)
• Assuming getServerSideProps causes errors
• Believing props are undefined without checking code

4. This Next.js page uses Static Site Generation but the data is not updating after deployment. What is the likely fix?

export async function getStaticProps() {
  const data = await fetch('https://api.example.com/data').then(res => res.json());
  return { props: { data } };
}

export default function Page({ data }) {
  return 
{data.message}
;
}

medium

A. Add revalidate property to enable Incremental Static Regeneration.

B. Change getStaticProps to getServerSideProps to fetch on every request.

C. Remove the fetch call to avoid stale data.

D. Wrap the component in React.memo to force updates.

Solution

1. Step 1: Identify SSG data freshness issue

   Static Site Generation builds pages once at build time, so data stays static unless re-built.

2. Step 2: Use revalidate for periodic updates

   Adding revalidate enables Incremental Static Regeneration, refreshing data after set seconds.

3. Final Answer:

   Add revalidate property to enable Incremental Static Regeneration. -> Option A

4. Quick Check:

   SSG + revalidate = fresh static pages [OK]

Hint: Use revalidate in getStaticProps for fresh static data [OK]

Common Mistakes:

• Switching to getServerSideProps unnecessarily
• Removing fetch which breaks data loading
• Using React.memo which doesn't affect data fetching

5. You want a Next.js page that shows user profile data that updates every 10 seconds but also loads fast initially. Which rendering strategy best fits this need?

hard

A. Use Server-side Rendering with getServerSideProps to fetch data on every request.

B. Use Static Site Generation with revalidate: 10 to update every 10 seconds.

C. Use Client-side Rendering only with useEffect to fetch data after page loads.

D. Use Static Site Generation without revalidate for fastest load.

Solution

1. Step 1: Understand the need for fast initial load and frequent updates

   Static Site Generation gives fast load by pre-building pages; revalidate allows periodic updates.

2. Step 2: Compare options for update frequency and speed

   Using revalidate: 10 updates the page every 10 seconds without slowing initial load, unlike server-side rendering which runs every request.

3. Final Answer:

   Use Static Site Generation with revalidate: 10 to update every 10 seconds. -> Option B

4. Quick Check:

   SSG + revalidate = fast + fresh [OK]

Hint: SSG with revalidate balances speed and freshness [OK]

Common Mistakes:

• Choosing server-side rendering which slows initial load
• Using client-side fetching which delays content display
• Ignoring revalidate option for periodic updates