Client-side session access in NextJS - Performance & Optimization

Performance: Client-side session access

MEDIUM IMPACT

This affects page load speed and interaction responsiveness by how session data is accessed and rendered on the client side.

Access user session data on the client to personalize UI

NextJS

import { useSession } from 'next-auth/react';

export default function Profile() {
  const { data: session } = useSession({ required: false });

  return <p>Welcome, {session?.user?.name ?? 'Guest'}</p>;
}

Allows immediate render with fallback content, reducing blocking and layout shifts.

📈 Performance GainNon-blocking render, reduces CLS and improves INP.

Access user session data on the client to personalize UI

NextJS

import { useSession } from 'next-auth/react';

export default function Profile() {
  const { data: session, status } = useSession();

  if (status === 'loading') return <p>Loading...</p>;

  return <p>Welcome, {session.user.name}</p>;
}

Calling useSession directly in the component causes the component to wait for session data, blocking initial render and causing layout shifts.

📉 Performance CostBlocks rendering until session loads, increasing INP and causing CLS due to content shift.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Blocking session fetch with loading UI	Moderate (conditional DOM nodes)	Multiple reflows due to content shift	High paint cost on update	[X] Bad
Non-blocking session fetch with fallback UI	Low (static DOM initially)	Single reflow on update	Low paint cost	[OK] Good

Rendering Pipeline

Client-side session access triggers JavaScript execution to fetch session data, which affects style calculation and layout if content changes after initial paint.

→JavaScript Execution

→Style Calculation

→Layout

→Paint

⚠️ BottleneckLayout due to content changes after session data loads

Core Web Vital Affected

INP

This affects page load speed and interaction responsiveness by how session data is accessed and rendered on the client side.

Optimization Tips

1Avoid blocking UI rendering while waiting for session data.

2Use fallback content to prevent layout shifts.

3Load session data asynchronously to improve interaction responsiveness.

Performance Quiz - 3 Questions

What is a main performance risk when accessing session data client-side in Next.js?

A Slowing down server response time

B Blocking initial render and causing layout shifts

C Increasing bundle size by importing session libraries

D Causing network latency for API calls

DevTools: Performance

How to check: Record a performance profile while loading the page and interacting. Look for long scripting tasks and layout shifts after initial paint.

What to look for: Check for delayed interactivity (INP) and layout shifts (CLS) caused by session data loading.

Practice

1. What does the useSession hook from next-auth provide in a Next.js app?

easy

A. Access to the current user's session data and status on the client side

B. Server-side rendering of session data only

C. A way to store session data in local storage manually

D. Automatic user authentication without any configuration

Solution

1. Step 1: Understand the purpose of useSession

   The useSession hook is designed to provide session data and status on the client side in Next.js apps using next-auth.

2. Step 2: Compare options with the hook's functionality

   Access to the current user's session data and status on the client side correctly states it provides access to current user's session data and status. Other options describe unrelated or incorrect behaviors.

3. Final Answer:

   Access to the current user's session data and status on the client side -> Option A

4. Quick Check:

   useSession gives client session data = A [OK]

Hint: Remember: useSession is for client-side session info [OK]

Common Mistakes:

• Thinking useSession works only server-side
• Confusing useSession with local storage
• Assuming useSession auto-authenticates without setup

2. Which of the following is the correct way to import and use useSession in a Next.js component?

easy

A. import { useSession } from 'next-auth/client'; const session = useSession();

B. import useSession from 'next-auth/client'; const session = useSession();

C. import { useSession } from 'next-auth/react'; const session = useSession.data;

D. import { useSession } from 'next-auth/react'; const { data: session } = useSession();

Solution

1. Step 1: Check the correct import path and usage

   The official import for useSession in next-auth v4+ is from 'next-auth/react'. The hook returns an object with data and status.

2. Step 2: Validate the destructuring syntax

   import { useSession } from 'next-auth/react'; const { data: session } = useSession(); correctly imports and destructures data as session. Other options use wrong import paths or incorrect usage.

3. Final Answer:

   import { useSession } from 'next-auth/react'; const { data: session } = useSession(); -> Option D

4. Quick Check:

   Correct import and destructuring = C [OK]

Hint: Use 'next-auth/react' and destructure data as session [OK]

Common Mistakes:

• Importing from 'next-auth/client' which is outdated
• Not destructuring the returned object
• Accessing session data incorrectly

3. Given this Next.js component using useSession:

import { useSession } from 'next-auth/react';
export default function Profile() {
  const { data: session, status } = useSession();
  if (status === 'loading') return <p>Loading...</p>;
  if (!session) return <p>Not signed in</p>;
  return <p>Welcome, {session.user.name}!</p>;
}

What will be rendered if the user is signed in with name "Alex"?

medium

A. Not signed in

B. Loading...

C. Welcome, Alex!

D. Nothing is rendered

Solution

1. Step 1: Understand the session states

   The component shows "Loading..." if status is 'loading', "Not signed in" if no session, and welcome message if session exists.

2. Step 2: Apply the signed-in user condition

   Since the user is signed in with name "Alex", session exists and status is not 'loading'. So it renders the welcome message with the user's name.

3. Final Answer:

   <p>Welcome, Alex!</p> -> Option C

4. Quick Check:

   Signed-in user shows welcome message = A [OK]

Hint: Check session presence to show welcome, else loading or sign-in [OK]

Common Mistakes:

• Confusing loading and signed-in states
• Assuming session.user.name is undefined
• Ignoring the status check order

4. Identify the error in this Next.js component using useSession:

import { useSession } from 'next-auth/react';
export default function Dashboard() {
  const session = useSession();
  if (session.status === 'loading') return <p>Loading...</p>;
  if (!session.data) return <p>Please sign in</p>;
  return <p>Hello, {session.user.name}</p>;
}

medium

A. Accessing session.user.name directly instead of session.data.user.name

B. Incorrect import path for useSession

C. Missing useEffect to fetch session

D. Using session.status instead of session.state

Solution

1. Step 1: Check how useSession returns data

   useSession returns an object with data and status. The user info is inside data.user.

2. Step 2: Identify incorrect property access

   The code tries to access session.user.name directly, but it should be session.data.user.name. This causes an error.

3. Final Answer:

   Accessing session.user.name directly instead of session.data.user.name -> Option A

4. Quick Check:

   Use session.data.user for user info, not session.user [OK]

Hint: Remember session data is in session.data, not top-level [OK]

Common Mistakes:

• Accessing user info directly on session object
• Confusing status property names
• Adding unnecessary hooks like useEffect

5. You want to show a personalized greeting only if the user is signed in and their email is verified in the session. Given useSession returns { data: session, status }, which code snippet correctly implements this in a Next.js component?

hard

A. if (!session) return Please verify your email;
if (status === 'loading') return Loading...;
return Welcome back, {session.user.name}!;

B. if (status === 'loading') return Loading...;
if (!session || !session.user.emailVerified) return Please verify your email;
return Welcome back, {session.user.name}!;

C. if (status === 'loading') return Loading...;
if (!session.user.emailVerified) return Please verify your email;
return Welcome back, {session.user.name}!;

D. if (status === 'loading') return Loading...;
if (!session || session.user.emailVerified) return Please verify your email;
return Welcome back, {session.user.name}!;

Solution

1. Step 1: Check loading state first

   Always handle status === 'loading' first to avoid rendering before session is ready.

2. Step 2: Verify session existence and email verification

   We must check if session exists and if session.user.emailVerified is true. If not, show the verification message.

3. Step 3: Render personalized greeting if checks pass

   If session exists and email is verified, show welcome message with user name.

4. Final Answer:

   if (status === 'loading') return <p>Loading...</p>; if (!session || !session.user.emailVerified) return <p>Please verify your email</p>; return <p>Welcome back, {session.user.name}!</p>; -> Option B

5. Quick Check:

   Check loading, then session and emailVerified before greeting [OK]

Hint: Check loading first, then session and emailVerified [OK]

Common Mistakes:

• Checking session after loading state
• Not verifying session existence before accessing properties
• Incorrect logic for email verification condition