Client component boundaries in NextJS - Performance & Optimization

Performance: Client component boundaries

HIGH IMPACT

This affects how much JavaScript is sent to the browser and how fast the page becomes interactive.

Separating interactive UI parts from static content

NextJS

import React from 'react';
import Counter from './Counter';

export default function Page() {
  return (
    <div>
      <h1>Welcome</h1>
      <Counter />
      <p>Static content here</p>
    </div>
  );
}

// Counter.tsx
'use client';
import React from 'react';
function Counter() {
  const [count, setCount] = React.useState(0);
  return <button onClick={() => setCount(count + 1)}>Count: {count}</button>;
}

export default Counter;

Only the interactive Counter is a client component, so less JS is sent and hydration is faster.

📈 Performance GainSaves 40-80kb in main bundle, reduces hydration time, improves INP

Separating interactive UI parts from static content

NextJS

'use client';

import React from 'react';

export default function Page() {
  // Entire page is a client component
  const [count, setCount] = React.useState(0);
  return (
    <div>
      <h1>Welcome</h1>
      <button onClick={() => setCount(count + 1)}>Count: {count}</button>
      <p>Static content here</p>
    </div>
  );
}

The whole page is a client component, so all JavaScript for interactivity is sent and run even for static parts.

📉 Performance CostAdds 50-100kb to client bundle, delays hydration, blocks interaction until JS loads

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Whole page as client component	High (all nodes hydrated)	Multiple reflows during hydration	High paint cost due to JS execution	[X] Bad
Small isolated client components	Low (only interactive parts hydrated)	Single reflow per component	Lower paint cost, faster interaction	[OK] Good

Rendering Pipeline

Client components require JavaScript to hydrate and become interactive, affecting the hydration and interaction phases.

→JavaScript Parsing

→Hydration

→Interaction

⚠️ BottleneckHydration blocking interaction until JS loads and runs

Core Web Vital Affected

INP

This affects how much JavaScript is sent to the browser and how fast the page becomes interactive.

Optimization Tips

1Only mark components as client if they need interactivity.

2Keep client components as small and focused as possible.

3Use server components for static content to reduce JS sent.

Performance Quiz - 3 Questions

What is the main performance benefit of limiting client components to small interactive parts?

A Increases server rendering time

B Reduces JavaScript bundle size and speeds up hydration

C Improves CSS loading speed

D Reduces image download size

DevTools: Performance

How to check: Record a page load and interaction; look for long hydration tasks and JS parsing times.

What to look for: Long blocking time before first input responsiveness indicates large client components.

Practice

1. What is the purpose of marking a component with "use client"; in Next.js?

easy

A. To optimize the component for server-side rendering.

B. To make the component run only on the server.

C. To disable the component from rendering.

D. To tell Next.js this component should run in the browser.

Solution

1. Step 1: Understand client component marking

   Adding "use client"; at the top of a file tells Next.js this component runs in the browser, enabling interactivity.

2. Step 2: Differentiate from server components

   Server components run on the server and do not have this directive. Marking a component as client enables browser-only features.

3. Final Answer:

   To tell Next.js this component should run in the browser. -> Option D

4. Quick Check:

   Client components = "use client" [OK]

Hint: Look for "use client" to identify browser-run components [OK]

Common Mistakes:

• Thinking "use client" makes component server-only
• Confusing client components with disabling rendering
• Assuming it optimizes server rendering

2. Which of the following is the correct way to mark a React component as a client component in Next.js?

easy

A. Add "use client"; at the top of the component file.

B. Wrap the component in <Client></Client> tags.

C. Add client: true in the component props.

D. Import the component from a special client folder.

Solution

1. Step 1: Recall client component syntax

   Next.js requires "use client"; at the very top of the file to mark it as a client component.

2. Step 2: Evaluate other options

   Wrapping in tags, adding props, or importing from folders are not valid Next.js client component patterns.

3. Final Answer:

   Add "use client"; at the top of the component file. -> Option A

4. Quick Check:

   Client component syntax = "use client" [OK]

Hint: Always place "use client" as the first line in the file [OK]

Common Mistakes:

• Trying to mark client components via props or wrappers
• Placing "use client" inside the component function
• Assuming folder structure controls client behavior

3. Given this Next.js component file content:

"use client";
import { useState } from 'react';

export default function Counter() {
  const [count, setCount] = useState(0);
  return (
    <button onClick={() => setCount(count + 1)}>Clicked {count} times</button>
  );
}

What will happen when this component is rendered in a Next.js app?

medium

A. The component will throw an error because useState is not allowed.

B. The button will display and update the count on clicks in the browser.

C. The button will render but clicks will not update the count.

D. The component will only render on the server and not be interactive.

Solution

1. Step 1: Identify client component usage

   The file starts with "use client" so it runs in the browser and can use hooks like useState.

2. Step 2: Understand interactivity

   The button uses onClick to update state, so clicks will increase the count and re-render the button text.

3. Final Answer:

   The button will display and update the count on clicks in the browser. -> Option B

4. Quick Check:

   Client component + useState = interactive button [OK]

Hint: Client components can use useState and handle events [OK]

Common Mistakes:

• Thinking useState is disallowed in client components
• Assuming server components handle clicks
• Believing the button won't update without extra code

4. Consider this Next.js component file:

import { useState } from 'react';

export default function Clicker() {
  const [count, setCount] = useState(0);
  return (
    <button onClick={() => setCount(count + 1)}>Clicked {count} times</button>
  );
}

What is the problem with this component regarding client boundaries?

medium

A. It lacks the "use client"; directive, so useState will cause an error.

B. It uses useState incorrectly inside a server component.

C. The onClick handler syntax is invalid in Next.js.

D. The component should be wrapped in a <Client> tag.

Solution

1. Step 1: Check for client directive

   The component uses useState, which requires the component to be a client component marked by "use client".

2. Step 2: Identify missing directive effect

   Without "use client", Next.js treats this as a server component, causing an error when using useState.

3. Final Answer:

   It lacks the "use client"; directive, so useState will cause an error. -> Option A

4. Quick Check:

   useState needs "use client" [OK]

Hint: useState requires "use client" at file top [OK]

Common Mistakes:

• Assuming useState works without "use client"
• Thinking onClick syntax is invalid
• Trying to wrap component in tags for client behavior

5. You have a Next.js app with a server component Profile that fetches user data and a client component EditButton that allows editing the profile. How should you correctly use these components together?

hard

A. Import Profile inside EditButton and mark both with "use client";.

B. Mark Profile with "use client"; and import EditButton without any directive.

C. Import EditButton inside Profile and mark EditButton with "use client"; at its top.

D. Wrap EditButton inside Profile without marking either as client.

Solution

1. Step 1: Understand component boundaries

   Server components can import client components, but client components cannot import server components.

2. Step 2: Apply correct marking

   The EditButton must have "use client" at the top to run in the browser, while Profile remains a server component.

3. Step 3: Correct usage

   Import EditButton inside Profile and mark EditButton with "use client"; this keeps boundaries correct and enables interactivity.

4. Final Answer:

   Import EditButton inside Profile and mark EditButton with "use client"; at its top. -> Option C

5. Quick Check:

   Server imports client; client marked "use client" [OK]

Hint: Server components import client components marked "use client" [OK]

Common Mistakes:

• Marking server components as client unnecessarily
• Trying to import server components inside client components
• Not marking client components with "use client"