Why client components handle interactivity in NextJS - Performance Evidence

Performance: Why client components handle interactivity

HIGH IMPACT

This affects how fast the page becomes interactive and how smoothly user inputs are handled.

Adding interactive features to a Next.js app

NextJS

'use client';
export default function InteractiveButton() {
  return <button onClick={() => alert('Clicked!')}>Click me</button>;
}

Marking component as client component enables event handlers to run in browser, improving responsiveness.

📈 Performance GainImproves INP by enabling instant client-side event handling; avoids full reloads

Adding interactive features to a Next.js app

NextJS

export default function Page() {
  return <button onClick={() => alert('Clicked!')}>Click me</button>;
}
// Entire component is server component by default

Server components cannot handle client-side events, so interactivity is broken or requires full page reloads.

📉 Performance CostBlocks interactivity until full page reload; poor INP score

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Server component with interactivity	Minimal DOM nodes	0 reflows for events	No paint cost for events	[X] Bad - no client event handling
Client component with interactivity	Minimal DOM nodes	0 reflows for events	Paint cost only on interaction	[OK] Good - responsive interactivity

Rendering Pipeline

Client components are sent as JavaScript to the browser, which parses, executes, and attaches event listeners for interactivity.

→JavaScript Parsing

→Hydration

→Event Handling

⚠️ BottleneckJavaScript Parsing and Hydration can delay interactivity if bundle size is large.

Core Web Vital Affected

INP

This affects how fast the page becomes interactive and how smoothly user inputs are handled.

Optimization Tips

1Use client components only for parts that need interactivity.

2Keep client components small to reduce JavaScript parsing and hydration time.

3Lazy-load client components to improve initial load and interactivity.

Performance Quiz - 3 Questions

Why must interactive parts of a Next.js app be client components?

A Because only client components can run JavaScript in the browser to handle events

B Because server components load faster

C Because client components reduce bundle size

D Because server components handle CSS better

DevTools: Performance

How to check: Record a session while interacting with the page. Look for event handler execution and hydration times.

What to look for: Short hydration time and fast event handler response indicate good client component interactivity.

Practice

1. Why do client components in Next.js handle interactivity like clicks and typing?

easy

A. Because they only render static content

B. Because they run on the server to improve performance

C. Because they do not use React hooks

D. Because they run in the browser where user actions happen

Solution

1. Step 1: Understand where interactivity happens

   User actions like clicks and typing happen in the browser, not on the server.

2. Step 2: Identify where client components run

   Client components run in the browser, so they can respond to user actions directly.

3. Final Answer:

   Because they run in the browser where user actions happen -> Option D

4. Quick Check:

   Interactivity needs browser execution = A [OK]

Hint: Interactivity needs browser code, so client components handle it [OK]

Common Mistakes:

• Thinking server components handle clicks
• Believing client components run on the server
• Confusing static rendering with interactivity

2. Which syntax correctly marks a Next.js component as a client component to enable interactivity?

easy

A. Use export default clientComponent() instead of export default

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

C. Add 'use client' at the top of the component file

D. Add interactive=true inside the component function

Solution

1. Step 1: Recall how to enable client components

   Next.js requires the special directive 'use client' at the top of the file to mark it as a client component.

2. Step 2: Check the options for correct syntax

   Only Add 'use client' at the top of the component file uses the exact correct syntax: 'use client' at the top.

3. Final Answer:

   Add 'use client' at the top of the component file -> Option C

4. Quick Check:

   Directive 'use client' = A [OK]

Hint: Look for 'use client' directive at file top to enable client component [OK]

Common Mistakes:

• Trying to wrap component in special tags
• Using incorrect export syntax
• Adding props instead of directive

3. What will be the output when clicking the button in this client component?

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

medium

A. Button shows 'Clicked 0 times' initially and increments count on each click

B. Button shows 'Clicked 0 times' but does not update on click

C. Syntax error because useState is not allowed in client components

D. Button shows 'Clicked NaN times' due to wrong state initialization

Solution

1. Step 1: Identify component type and hooks usage

   The component uses 'use client' and React's useState hook correctly to track count.

2. Step 2: Understand button behavior on click

   Clicking the button calls setCount(count + 1), increasing count and updating the displayed text.

3. Final Answer:

   Button shows 'Clicked 0 times' initially and increments count on each click -> Option A

4. Quick Check:

   useState updates count on click = D [OK]

Hint: useState in client components updates UI on events like clicks [OK]

Common Mistakes:

• Thinking useState is disallowed in client components
• Expecting no update on click
• Confusing initial state with NaN

4. Identify the error in this client component code that prevents interactivity:

"use client";
import { useState } from 'react';
export default function Toggle() {
  const [on, setOn] = useState(false);
  return (
    <button onClick={setOn(!on)}>{on ? 'ON' : 'OFF'}</button>
  );
}

medium

A. The onClick handler calls setOn immediately instead of on click

B. Missing 'use client' directive at the top

C. useState is not imported correctly

D. Button text should be uppercase only

Solution

1. Step 1: Analyze the onClick handler syntax

   The onClick is set to setOn(!on), which calls the function immediately during render instead of on click.

2. Step 2: Correct usage of onClick

   It should be a function: onClick={() => setOn(!on)} to delay execution until click.

3. Final Answer:

   The onClick handler calls setOn immediately instead of on click -> Option A

4. Quick Check:

   onClick needs a function, not direct call = B [OK]

Hint: Wrap setState calls in arrow function for onClick [OK]

Common Mistakes:

• Calling setState directly in onClick
• Forgetting 'use client' directive
• Ignoring function syntax for event handlers

5. You want to create a client component that toggles a dark mode theme on button click. Which approach correctly combines client component rules and React hooks?

"use client";
import { useState } from 'react';
export default function DarkModeToggle() {
  const [dark, setDark] = useState(false);
  return (
    <button onClick={() => {
      setDark(!dark);
      document.body.classList.toggle('dark-theme', !dark);
    }}>
      {dark ? 'Light Mode' : 'Dark Mode'}
    </button>
  );
}

hard

A. Incorrect: uses useState but tries to update DOM outside React lifecycle

B. Correct: uses 'use client', useState, and toggles class on click

C. Incorrect: missing 'use client' directive

D. Incorrect: uses server component syntax with useState

Solution

1. Step 1: Verify client component directive and hooks

   The code starts with 'use client' and uses useState correctly to track dark mode state.

2. Step 2: Check interactivity and DOM update

   The onClick handler toggles the state and updates the document body class to reflect the theme, which is valid in client components.

3. Final Answer:

   Correct: uses 'use client', useState, and toggles class on click -> Option B

4. Quick Check:

   Client component with useState and DOM update = C [OK]

Hint: Use 'use client' and hooks for interactivity and DOM changes [OK]

Common Mistakes:

• Forgetting 'use client' directive
• Trying to update DOM in server components
• Misusing useState in server components