Interleaving server and client in NextJS - Performance & Optimization

Performance: Interleaving server and client

HIGH IMPACT

This affects how quickly the user sees meaningful content and how responsive the page feels during loading.

Rendering a page with both server and client components

NextJS

export default async function Page() {
  const data = await fetchDataAsync();
  return (
    <>
      <ServerComponent data={data} />
      <ClientComponent />
    </>
  );
}

function ServerComponent({ data }) {
  return <div>{data}</div>;
}

'use client';
function ClientComponent() {
  const [state, setState] = React.useState(null);
  React.useEffect(() => {
    setState('Client loaded');
  }, []);
  return <div>{state}</div>;
}

Server sends HTML progressively with data, while client components hydrate separately, enabling faster first contentful paint.

📈 Performance GainReduces blocking time, improves LCP by 300+ ms, and allows interaction sooner.

Rendering a page with both server and client components

NextJS

export default function Page() {
  const data = fetchDataSync();
  return <ClientComponent data={data} />;
}

function ClientComponent({ data }) {
  const [state, setState] = React.useState(null);
  React.useEffect(() => {
    setState(data);
  }, [data]);
  return <div>{state}</div>;
}

Fetching data synchronously blocks server rendering and delays sending HTML to the client, causing slower initial paint.

📉 Performance CostBlocks rendering until data fetch completes, increasing LCP by 500+ ms depending on data size.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Synchronous data fetch blocking server render	Low initial DOM nodes	Single large reflow after data fetch	High paint cost due to delayed content	[X] Bad
Interleaved server streaming with client hydration	More DOM nodes progressively added	Multiple small reflows during hydration	Lower paint cost with faster content display	[OK] Good

Rendering Pipeline

Interleaving server and client components lets the browser start rendering server HTML immediately while client JavaScript loads and hydrates separately.

→HTML Streaming

→Hydration

→Paint

→Composite

⚠️ BottleneckHydration stage can delay interactivity if client components are large or complex.

Core Web Vital Affected

LCP

This affects how quickly the user sees meaningful content and how responsive the page feels during loading.

Optimization Tips

1Stream server HTML early to improve Largest Contentful Paint (LCP).

2Defer client component hydration to avoid blocking initial render.

3Split components to balance server rendering and client interactivity.

Performance Quiz - 3 Questions

What is the main performance benefit of interleaving server and client rendering in Next.js?

A Eliminating all reflows during page load

B Faster initial content display by streaming HTML progressively

C Reducing JavaScript bundle size by removing client code

D Avoiding hydration completely

DevTools: Performance

How to check: Record page load, look for HTML streaming in the network waterfall and check when first contentful paint occurs relative to hydration start.

What to look for: Early HTML arrival and paint marks with hydration happening after initial paint indicate good interleaving.

Practice

1. In Next.js, what is the main benefit of interleaving server and client components?

easy

A. It disables server-side rendering completely.

B. It improves performance by loading data on the server and handling interactions on the client.

C. It forces all components to run only on the client side.

D. It allows you to write all code in one file without separation.

Solution

1. Step 1: Understand server and client roles

   Server components fetch data and render HTML, while client components handle user interactions.

2. Step 2: Identify the benefit of mixing them

   Combining them improves performance by reducing client work and speeding up data loading.

3. Final Answer:

   It improves performance by loading data on the server and handling interactions on the client. -> Option B

4. Quick Check:

   Interleaving = Better performance [OK]

Hint: Remember: server for data, client for interaction [OK]

Common Mistakes:

• Thinking all code runs only on client
• Believing interleaving disables server rendering
• Assuming no performance benefit

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

easy

A. Add client: true in the component's props.

B. Wrap the component with <ClientComponent> tags.

C. Use export default clientComponent() instead of a normal export.

D. Add the directive 'use client' at the top of the file.

Solution

1. Step 1: Recall client component syntax

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

2. Step 2: Check other options

   Wrapping tags, special exports, or props flags are not valid Next.js patterns.

3. Final Answer:

   Add the directive 'use client' at the top of the file. -> Option D

4. Quick Check:

   Client component directive = 'use client' [OK]

Hint: Look for 'use client' at file top to mark client components [OK]

Common Mistakes:

• Trying to wrap components with special tags
• Using props to mark client components
• Confusing export syntax for client marking

3. Given this Next.js code snippet, what will be rendered on the page?

export default function ServerComponent() {
  const data = fetch('https://api.example.com/data').then(res => res.json());
  return (
    <div>
      <ClientComponent />
      <p>Data loaded</p>
    </div>
  );
}

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

medium

A. Only the paragraph 'Data loaded' because ClientComponent is not marked as client.

B. A button showing 'Clicked 0 times' and a paragraph 'Data loaded'.

C. An error because fetch is used incorrectly in ServerComponent.

D. Nothing renders because ClientComponent is inside ServerComponent.

Solution

1. Step 1: Check ClientComponent usage

   ClientComponent uses useState, so it must be marked with 'use client' directive to work as client component.

2. Step 2: Analyze missing 'use client' directive

   Without 'use client', ClientComponent is treated as server component, but hooks are invalid there, causing it not to render properly.

3. Final Answer:

   Only the paragraph 'Data loaded' because ClientComponent is not marked as client. -> Option A

4. Quick Check:

   Missing 'use client' = ClientComponent won't render [OK]

Hint: Client components need 'use client' directive to render hooks [OK]

Common Mistakes:

• Assuming ClientComponent renders without 'use client'
• Thinking fetch usage causes error here
• Believing nested client components always render

4. Identify the error in this Next.js component interleaving code:

'use client';

export default function ClientComponent() {
  const data = fetch('https://api.example.com/data').then(res => res.json());
  return <div>Data count: {data.length}</div>;
}

medium

A. Missing 'use server' directive at the top of the file.

B. The component should not return JSX inside a client component.

C. Using fetch directly in a client component without async/await causes a Promise error.

D. The fetch URL is invalid syntax.

Solution

1. Step 1: Understand fetch in client components

   fetch returns a Promise; using it directly without awaiting causes data to be a Promise, not the actual data.

2. Step 2: Identify the error in rendering

   Trying to access data.length on a Promise causes runtime error because Promise has no length property.

3. Final Answer:

   Using fetch directly in a client component without async/await causes a Promise error. -> Option C

4. Quick Check:

   Fetch returns Promise; must await in client [OK]

Hint: Always await fetch in client components to get data [OK]

Common Mistakes:

• Thinking 'use server' is needed in client components
• Believing JSX can't be returned in client components
• Assuming fetch URL syntax is wrong

5. You want to display a list of products fetched on the server and allow users to add products to a cart on the client. Which is the best way to interleave server and client components in Next.js?

hard

A. Fetch products in a server component and render a client component for the add-to-cart buttons inside it.

B. Fetch products inside a client component and handle add-to-cart in the same component.

C. Fetch products in a client component and render server components for buttons.

D. Fetch products and handle add-to-cart both in server components only.

Solution

1. Step 1: Separate data fetching and interactivity

   Fetching products is best done on the server for performance and SEO benefits.

2. Step 2: Use client components for user actions

   Add-to-cart buttons require client interactivity, so they should be client components nested inside the server component.

3. Final Answer:

   Fetch products in a server component and render a client component for the add-to-cart buttons inside it. -> Option A

4. Quick Check:

   Server fetch + client interactivity = Fetch products in a server component and render a client component for the add-to-cart buttons inside it. [OK]

Hint: Server fetch data, client handle clicks inside [OK]

Common Mistakes:

• Fetching data on client causing slower load
• Trying to handle interactivity in server components
• Rendering server components inside client components incorrectly