Server-side session access in NextJS - Performance & Optimization

Performance: Server-side session access

MEDIUM IMPACT

This affects the time to first byte (TTFB) and overall server response time, impacting how quickly the page starts rendering.

Reading user session data during server-side rendering

NextJS

import { unstable_getServerSession } from 'next-auth/next';
export async function getServerSideProps(context) {
  const session = await unstable_getServerSession(context.req, context.res, authOptions);
  return { props: { user: session?.user ?? null } };
}

Uses optimized async session retrieval with caching and minimal parsing, reducing server blocking time.

📈 Performance Gainreduces blocking time by 50-70ms on average

Reading user session data during server-side rendering

NextJS

export async function getServerSideProps(context) {
  const session = await getSession({ req: context.req });
  // heavy synchronous session parsing or multiple session reads
  return { props: { user: session.user } };
}

Multiple or heavy synchronous session reads block server response, increasing TTFB and delaying page render.

📉 Performance Costblocks rendering for 100-300ms depending on session complexity

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Heavy synchronous session parsing	N/A (server-side)	N/A	N/A	[X] Bad
Optimized async session retrieval with caching	N/A (server-side)	N/A	N/A	[OK] Good

Rendering Pipeline

Server-side session access happens before HTML is sent to the browser, affecting server response time and delaying the start of the browser's rendering pipeline.

→Server Processing

→Network Transfer

→First Paint

⚠️ BottleneckServer Processing (session retrieval and parsing)

Core Web Vital Affected

LCP

This affects the time to first byte (TTFB) and overall server response time, impacting how quickly the page starts rendering.

Optimization Tips

1Avoid heavy synchronous session parsing during server-side rendering.

2Use async session retrieval methods with caching to reduce server blocking.

3Keep session data minimal to speed up server response and improve LCP.

Performance Quiz - 3 Questions

How does inefficient server-side session access affect page load?

A It increases CSS selector complexity.

B It increases server response time, delaying the first content paint.

C It causes more DOM nodes to be created on the client.

D It causes layout shifts after page load.

DevTools: Network

How to check: Open DevTools, go to Network tab, reload page, and check the TTFB value for the main document request.

What to look for: A high TTFB indicates slow server processing, possibly due to inefficient session access.

Practice

1. What is the main purpose of using getServerSession in Next.js?

easy

A. To fetch data from an external API on the client side

B. To handle client-side routing between pages

C. To style components dynamically based on user input

D. To access user session data securely on the server side

Solution

1. Step 1: Understand the role of getServerSession

   This function is designed to retrieve session information securely on the server side in Next.js.

2. Step 2: Compare with other options

   Options A, C, and D describe client-side or unrelated tasks, not server-side session access.

3. Final Answer:

   To access user session data securely on the server side -> Option D

4. Quick Check:

   Server-side session access = To access user session data securely on the server side [OK]

Hint: Remember: sessions store user info safely on the server [OK]

Common Mistakes:

• Confusing client-side data fetching with server session access
• Thinking getServerSession runs on the client
• Mixing session access with styling or routing

2. Which is the correct way to import getServerSession in a Next.js page?

easy

A. import { getServerSession } from 'next-auth/next';

B. import getServerSession from 'next/server';

C. import { getServerSession } from 'next/router';

D. import { getServerSession } from 'next/head';

Solution

1. Step 1: Identify the correct import source

   The official Next.js authentication library exports getServerSession from 'next-auth/next'.

2. Step 2: Check other imports

   Options A, B, and D import from unrelated Next.js modules, causing errors or undefined functions.

3. Final Answer:

   import { getServerSession } from 'next-auth/next'; -> Option A

4. Quick Check:

   Correct import path = import { getServerSession } from 'next-auth/next'; [OK]

Hint: Use 'next-auth/next' to import server session helpers [OK]

Common Mistakes:

• Importing from 'next/server' which lacks session helpers
• Confusing routing or head modules with auth imports
• Using default import instead of named import

3. Given this code inside getServerSideProps in Next.js, what will be logged if the user is not logged in?

export async function getServerSideProps(context) {
  const session = await getServerSession(context.req, context.res, authOptions);
  console.log(session);
  return { props: { user: session?.user || null } };
}

medium

A. undefined

B. An object with user details

C. null

D. A runtime error

Solution

1. Step 1: Understand session when user is not logged in

   If no user is logged in, getServerSession returns null, not undefined or error.

2. Step 2: Check the code's handling of session

   The code logs session directly, so it logs null. The props user is set to null safely.

3. Final Answer:

   null -> Option C

4. Quick Check:

   Session for no user = null [OK]

Hint: No login means session is null, not undefined or error [OK]

Common Mistakes:

• Assuming session is undefined instead of null
• Expecting an error when session is missing
• Confusing logged user object with session presence

4. What is wrong with this Next.js server-side session code?

export async function getServerSideProps(context) {
  const session = getServerSession(context.req, context.res, authOptions);
  if (!session) {
    return { redirect: { destination: '/login', permanent: false } };
  }
  return { props: { user: session.user } };
}

medium

A. Missing await before getServerSession call

B. Redirect destination should be '/home' instead of '/login'

C. session.user is undefined even if session exists

D. getServerSideProps cannot return redirect objects

Solution

1. Step 1: Check async function usage

   getServerSession returns a Promise, so it must be awaited to get the session object.

2. Step 2: Analyze the impact of missing await

   Without await, session is a Promise, so the if check fails and code behaves incorrectly.

3. Final Answer:

   Missing await before getServerSession call -> Option A

4. Quick Check:

   Async calls need await = Missing await before getServerSession call [OK]

Hint: Always await async session calls in server functions [OK]

Common Mistakes:

• Forgetting to await async functions
• Confusing redirect destinations with errors
• Thinking getServerSideProps can't redirect

5. You want to protect a Next.js page so only logged-in users can access it. Which approach correctly uses getServerSession inside getServerSideProps to redirect unauthenticated users to '/login' and pass user data to the page?

hard

A. export async function getServerSideProps(context) {
const session = getServerSession(context.req, context.res, authOptions);
if (session) {
return { redirect: { destination: '/login', permanent: false } };
}
return { props: { user: null } };
}

B. export async function getServerSideProps(context) {
const session = await getServerSession(context.req, context.res, authOptions);
if (!session) {
return { redirect: { destination: '/login', permanent: false } };
}
return { props: { user: session.user } };
}

C. export async function getServerSideProps(context) {
const session = await getServerSession(context.req, context.res, authOptions);
return { props: { user: session.user } };
}

D. export async function getServerSideProps(context) {
const session = await getServerSession(context.req, context.res, authOptions);
if (!session.user) {
return { redirect: { destination: '/login', permanent: false } };
}
return { props: { user: session.user } };
}

Solution

1. Step 1: Check session retrieval and await usage

   export async function getServerSideProps(context) { const session = await getServerSession(context.req, context.res, authOptions); if (!session) { return { redirect: { destination: '/login', permanent: false } }; } return { props: { user: session.user } }; } correctly awaits getServerSession to get the session object.

2. Step 2: Verify redirect logic for unauthenticated users

   export async function getServerSideProps(context) { const session = await getServerSession(context.req, context.res, authOptions); if (!session) { return { redirect: { destination: '/login', permanent: false } }; } return { props: { user: session.user } }; } redirects if !session, which means no logged-in user, correctly protecting the page.

3. Step 3: Confirm user data is passed when session exists

   export async function getServerSideProps(context) { const session = await getServerSession(context.req, context.res, authOptions); if (!session) { return { redirect: { destination: '/login', permanent: false } }; } return { props: { user: session.user } }; } returns user data in props only if session exists, enabling page to render user info.

4. Final Answer:

   export async function getServerSideProps(context) { const session = await getServerSession(context.req, context.res, authOptions); if (!session) { return { redirect: { destination: '/login', permanent: false } }; } return { props: { user: session.user } }; } -> Option B

5. Quick Check:

   Await session + redirect if no session = export async function getServerSideProps(context) { const session = await getServerSession(context.req, context.res, authOptions); if (!session) { return { redirect: { destination: '/login', permanent: false } }; } return { props: { user: session.user } }; } [OK]

Hint: Await session, redirect if missing, pass user in props [OK]

Common Mistakes:

• Not awaiting the session Promise
• Redirecting when session exists instead of missing
• Checking session.user without confirming session exists