Geolocation and edge logic in NextJS - Performance & Optimization

Performance: Geolocation and edge logic

MEDIUM IMPACT

This affects page load speed and responsiveness by deciding where and how geolocation logic runs, impacting server response time and client rendering.

Determining user location to customize content

NextJS

import { cookies } from 'next/headers';
export const runtime = 'edge';
export async function GET() {
  const cookieStore = cookies();
  const userLocation = cookieStore.get('user-location');
  // Use edge logic to read location from cookie or fallback
  return new Response(JSON.stringify({ location: userLocation?.value || 'default' }));
}

// Client fetches precomputed location from edge API

Runs geolocation logic or location retrieval at the edge before page render, reducing server response time and enabling faster personalized content.

📈 Performance GainReduces server latency by 50-200ms and improves LCP by delivering location-based content faster.

Determining user location to customize content

NextJS

'use client';
import { useState, useEffect } from 'react';
export default function Page() {
  const [location, setLocation] = useState(null);
  useEffect(() => {
    navigator.geolocation.getCurrentPosition(pos => {
      setLocation(pos.coords);
    });
  }, []);
  return <div>{location ? `Lat: ${location.latitude}` : 'Loading...'}</div>;
}

Geolocation runs only on client after full page load, delaying personalized content and increasing Largest Contentful Paint (LCP).

📉 Performance CostBlocks meaningful content rendering until client geolocation completes, increasing LCP by 500-1000ms.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Client-side geolocation after load	Minimal DOM changes	1 reflow after location set	Delays initial paint	[X] Bad
Edge runtime geolocation or precomputed location	No extra DOM operations	No reflows caused by location fetch	Faster initial paint	[OK] Good

Rendering Pipeline

Geolocation logic at the edge runs during server response generation, reducing client wait time. Client-side geolocation delays content rendering until after load.

→Server Response

→Layout

→Paint

⚠️ BottleneckServer Response time when geolocation runs on origin server or client-side delays content rendering.

Core Web Vital Affected

LCP

This affects page load speed and responsiveness by deciding where and how geolocation logic runs, impacting server response time and client rendering.

Optimization Tips

1Run geolocation logic at the edge to reduce server latency and speed up content delivery.

2Avoid client-only geolocation that delays meaningful content rendering and increases LCP.

3Use cookies or headers to pass location data to edge functions for faster personalized responses.

Performance Quiz - 3 Questions

Where should geolocation logic run to improve page load speed in Next.js?

A In a serverless function with high latency

B Only on the client after page load

C At the edge runtime before page render

D Inside a React useEffect hook without prefetch

DevTools: Performance

How to check: Record a page load and look for delays between navigation start and Largest Contentful Paint. Check if geolocation or location fetch delays server response or client rendering.

What to look for: Long gaps before LCP or delayed content updates indicate slow geolocation logic placement.

Practice

1. What is the main purpose of using geolocation in a Next.js app with edge logic?

easy

A. To manage user authentication

B. To improve server-side rendering speed

C. To store user data securely

D. To customize content based on the user's location

Solution

1. Step 1: Understand geolocation usage

   Geolocation helps identify where a user is accessing the app from.

2. Step 2: Connect geolocation with edge logic

   Edge logic runs code near the user to customize responses quickly, often based on location.

3. Final Answer:

   To customize content based on the user's location -> Option D

4. Quick Check:

   Geolocation = Customize content [OK]

Hint: Geolocation customizes content by user location [OK]

Common Mistakes:

• Confusing geolocation with authentication
• Thinking geolocation improves rendering speed directly
• Assuming geolocation stores user data

2. Which of the following is the correct way to access the user's country code in Next.js middleware using edge logic?

easy

A. const country = request.geo.country

B. const country = request.location.countryCode

C. const country = request.headers['x-country']

D. const country = request.geoCode.country

Solution

1. Step 1: Recall Next.js middleware geo API

   Next.js provides a geo object on the request with location info.

2. Step 2: Identify correct property for country code

   The correct property is request.geo.country to get the country code.

3. Final Answer:

   const country = request.geo.country -> Option A

4. Quick Check:

   request.geo.country = country code [OK]

Hint: Use request.geo.country to get country code [OK]

Common Mistakes:

• Using incorrect property names like geoCode or location
• Trying to get country from headers without custom setup
• Confusing geo with location objects

3. Given this Next.js middleware code snippet, what will be the redirect URL if the user is from 'US'?

export function middleware(request) {
  const country = request.geo?.country || 'unknown';
  if (country === 'US') {
    return Response.redirect(new URL('/us-home', request.url));
  }
  return Response.next();
}

medium

A. /unknown

B. /home

C. /us-home

D. /

Solution

1. Step 1: Check country value from request

   The code sets country to request.geo?.country or 'unknown'. For a US user, it is 'US'.

2. Step 2: Analyze redirect condition

   If country is 'US', the middleware redirects to '/us-home'. Otherwise, it continues normally.

3. Final Answer:

   /us-home -> Option C

4. Quick Check:

   Country 'US' triggers redirect to /us-home [OK]

Hint: Country 'US' redirects to /us-home [OK]

Common Mistakes:

• Ignoring the redirect condition
• Assuming default path is used for US
• Confusing Response.next() with redirect

4. Identify the error in this Next.js middleware code that tries to redirect users from Canada to '/ca-home':

export function middleware(request) {
  const country = request.geo.country;
  if (country = 'CA') {
    return Response.redirect(new URL('/ca-home', request.url));
  }
  return Response.next();
}

medium

A. Missing optional chaining on request.geo

B. Using assignment '=' instead of comparison '===' in the if condition

C. Response.redirect should be Response.redirectTo

D. URL constructor is used incorrectly

Solution

1. Step 1: Check the if condition syntax

   The condition uses country = 'CA', which assigns 'CA' instead of comparing.

2. Step 2: Identify correct comparison operator

   It should use === to compare values, not =.

3. Final Answer:

   Using assignment '=' instead of comparison '===' in the if condition -> Option B

4. Quick Check:

   Use '===' for comparison, not '=' [OK]

Hint: Use '===' for comparison, not '=' [OK]

Common Mistakes:

• Confusing assignment and comparison operators
• Thinking Response.redirectTo exists
• Overlooking optional chaining necessity

5. You want to serve different homepage content for users from Europe and Asia using Next.js edge middleware. Which approach correctly implements this logic?

export function middleware(request) {
  const country = request.geo?.country || '';
  const europeCountries = ['FR', 'DE', 'IT'];
  const asiaCountries = ['JP', 'CN', 'IN'];

  if (europeCountries.includes(country)) {
    return Response.redirect(new URL('/eu-home', request.url));
  } else if (asiaCountries.includes(country)) {
    return Response.redirect(new URL('/asia-home', request.url));
  }
  return Response.next();
}

hard

A. This code correctly redirects European and Asian users to their homepages

B. The includes method cannot be used on arrays in middleware

C. The country variable should be fetched from request.headers instead

D. Response.redirect requires a status code as second argument

Solution

1. Step 1: Verify country detection and arrays

   The code safely gets country with optional chaining and defines arrays for Europe and Asia countries.

2. Step 2: Check redirect logic

   It uses includes to check membership and redirects accordingly, else continues normally.

3. Final Answer:

   This code correctly redirects European and Asian users to their homepages -> Option A

4. Quick Check:

   Array.includes works and redirects correctly [OK]

Hint: Use array.includes to check country and redirect [OK]

Common Mistakes:

• Thinking includes is not allowed in middleware
• Trying to get country from headers without setup
• Assuming Response.redirect needs status code