When to use client components in NextJS - Performance & Optimization

Performance: When to use client components

HIGH IMPACT

This affects page load speed and interaction responsiveness by deciding which parts of the page run in the browser versus on the server.

Rendering interactive UI elements in Next.js

NextJS

"use client";
import React from 'react';
export default function Button() {
  const [count, setCount] = React.useState(0);
  return <button onClick={() => setCount(count + 1)}>Clicked {count} times</button>;
}

Explicitly marking as client component loads only necessary JS for interactivity, enabling faster hydration and responsiveness.

📈 Performance GainReduces interaction delay by 200-500ms and avoids unnecessary server rendering overhead

Rendering interactive UI elements in Next.js

NextJS

export default function Button() {
  const [count, setCount] = React.useState(0);
  return <button onClick={() => setCount(count + 1)}>Clicked {count} times</button>;
}
// No 'use client' directive, so this runs as a server component

Trying to use React state in a server component causes errors or forces hydration of large JS bundles, delaying interactivity.

📉 Performance CostBlocks rendering until hydration completes, increasing INP by 200-500ms on typical devices

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Using client components only for interactive parts	Minimal, scoped to interactive elements	Single reflow on interaction	Low paint cost	[OK] Good
Marking entire page as client component unnecessarily	Large DOM with many nodes	Multiple reflows during hydration	High paint cost	[X] Bad

Rendering Pipeline

Client components are sent as JavaScript to the browser, which parses, hydrates, and runs them to enable interactivity. Server components render HTML on the server and send it directly.

→JavaScript Parsing

→Hydration

→Interaction Handling

⚠️ BottleneckHydration delays caused by large client component bundles

Core Web Vital Affected

INP

This affects page load speed and interaction responsiveness by deciding which parts of the page run in the browser versus on the server.

Optimization Tips

1Use client components only for interactive UI or browser APIs.

2Keep client components small to reduce hydration time.

3Avoid marking entire pages as client components to improve INP.

Performance Quiz - 3 Questions

What is the main reason to use a client component in Next.js?

A To enable interactivity and use browser-only APIs

B To improve server rendering speed

C To reduce JavaScript bundle size by default

D To avoid sending any JavaScript to the browser

DevTools: Performance

How to check: Record a performance profile during page load and interaction. Look for long hydration tasks and scripting time.

What to look for: Long 'Hydrate' or 'Evaluate Script' tasks indicate heavy client component load slowing interactivity.

Practice

1. Which of the following is the main reason to use a client component in Next.js?

easy

A. To make parts of the app interactive and respond to user actions

B. To improve server-side rendering speed

C. To reduce the size of the JavaScript bundle sent to the browser

D. To fetch data from the database on the server

Solution

1. Step 1: Understand client components purpose

   Client components run in the browser and handle interactivity like clicks and animations.

2. Step 2: Compare options with this purpose

   Only To make parts of the app interactive and respond to user actions matches making the app interactive and responding to user actions.

3. Final Answer:

   To make parts of the app interactive and respond to user actions -> Option A

4. Quick Check:

   Client components = interactivity [OK]

Hint: Client components run in browser for interactivity [OK]

Common Mistakes:

• Thinking client components improve server rendering
• Confusing client components with server data fetching
• Believing client components reduce bundle size

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

easy

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

B. Name the file with a .client.js extension

C. Add "use client"; at the top of the file

D. Add client: true in the component props

Solution

1. Step 1: Recall Next.js client component syntax

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

2. Step 2: Check other options

   Options A, C, and D are not valid Next.js syntax for client components.

3. Final Answer:

   Add "use client"; at the top of the file -> Option C

4. Quick Check:

   Client component marker = "use client"; [OK]

Hint: Remember: "use client"; at file top marks client component [OK]

Common Mistakes:

• Trying to use special tags to mark client components
• Using file extensions to indicate client components
• Passing props to mark client components

3. What will happen if you try to use useState in a Next.js server component without marking it as a client component?

medium

A. You will get a runtime error because hooks like useState only work in client components

B. The state will be shared across all users

C. The app will render normally without errors

D. The component will automatically become a client component

Solution

1. Step 1: Understand hook usage rules

   Hooks like useState only work in client components because they run in the browser.

2. Step 2: Check behavior in server components

   If you use useState in a server component without "use client" directive, Next.js throws a runtime error.

3. Final Answer:

   You will get a runtime error because hooks like useState only work in client components -> Option A

4. Quick Check:

   useState in server component = runtime error [OK]

Hint: Hooks need client components or error occurs [OK]

Common Mistakes:

• Assuming hooks work in server components
• Thinking state is shared globally without errors
• Believing components auto-switch to client

4. You wrote a Next.js component with "use client"; but forgot to import useState from React. What will happen?

medium

A. The component will render but state updates won't work

B. The component will work fine without errors

C. Next.js will automatically import useState for you

D. You will get a ReferenceError because useState is not defined

Solution

1. Step 1: Check import requirements for hooks

   Hooks like useState must be explicitly imported from React to be used.

2. Step 2: Analyze missing import effect

   Without importing, JavaScript throws a ReferenceError because useState is undefined.

3. Final Answer:

   You will get a ReferenceError because useState is not defined -> Option D

4. Quick Check:

   Missing import useState = ReferenceError [OK]

Hint: Always import hooks before using them [OK]

Common Mistakes:

• Assuming Next.js auto-imports React hooks
• Ignoring import errors thinking component still works
• Confusing runtime errors with silent failures

5. You have a Next.js app with a server component that fetches data and a button that updates UI state on click. How should you organize components?

hard

A. Make the whole component a client component to handle data fetching and button state

B. Keep data fetching in a server component and create a separate client component for the button with state

C. Use only server components and handle button clicks with server actions

D. Fetch data in the client component and handle button state in the server component

Solution

1. Step 1: Separate concerns for performance and interactivity

   Server components are best for data fetching; client components handle interactivity like button clicks.

2. Step 2: Organize components accordingly

   Keep data fetching in server component and create a small client component for the button with state and event handlers.

3. Final Answer:

   Keep data fetching in a server component and create a separate client component for the button with state -> Option B

4. Quick Check:

   Server fetch + client interactivity = separate components [OK]

Hint: Use server for data, client for interactivity [OK]

Common Mistakes:

• Making entire component client causing slower loads
• Trying to handle UI state in server components
• Fetching data in client causing unnecessary delays