Dynamic OG images in NextJS - Performance & Optimization

Performance: Dynamic OG images

MEDIUM IMPACT

Dynamic OG images affect the initial page load speed and server response time because the image is generated on demand when the page is shared.

Generating Open Graph images dynamically for social sharing

NextJS

import { cache } from 'react';

const generateCachedImage = cache(async (params) => {
  return await generateImage(params);
});

export async function GET() {
  const image = await generateCachedImage({
    title: 'Dynamic OG Image',
    style: 'complex',
  });
  return new Response(image, { headers: { 'Content-Type': 'image/png' } });
}

Caches generated images in memory or on disk to serve repeated requests instantly, reducing server load and response time.

📈 Performance GainReduces server response time to under 50ms for cached images, improving LCP and user experience.

Generating Open Graph images dynamically for social sharing

NextJS

export async function GET() {
  const image = await generateImage({
    title: 'Dynamic OG Image',
    style: 'complex',
  });
  return new Response(image, { headers: { 'Content-Type': 'image/png' } });
}

Generates the image on every request without caching, causing high server load and slow response times.

📉 Performance CostBlocks server response for 300-500ms per request, increasing LCP and slowing page sharing previews.

Performance Comparison

Pattern	Server Processing	Network Transfer	Cache Usage	Verdict
Generate on every request	High (300-500ms)	Medium (image size)	None	[X] Bad
Generate once and cache	Low (<50ms after cache)	Medium (image size)	Effective caching	[OK] Good

Rendering Pipeline

When a social platform requests the OG image, the server generates or retrieves the image, then sends it back. This affects the server response phase before the browser can render the preview.

→Server Processing

→Network Transfer

→Browser Rendering

⚠️ BottleneckServer Processing (image generation time)

Core Web Vital Affected

LCP

Dynamic OG images affect the initial page load speed and server response time because the image is generated on demand when the page is shared.

Optimization Tips

1Cache dynamic OG images to avoid regenerating on every request.

2Keep image generation lightweight to reduce server processing time.

3Monitor server response times for OG image requests in DevTools Network panel.

Performance Quiz - 3 Questions

What is the main performance drawback of generating OG images dynamically on every request?

A Increased server response time delaying page preview rendering

B Increased client-side JavaScript bundle size

C Higher CSS complexity causing layout shifts

D More DOM nodes created on the page

DevTools: Network

How to check: Open DevTools, go to Network tab, filter by image requests, and observe the response time for the OG image request.

What to look for: Look for long server response times (TTFB) on the OG image request indicating slow generation; fast responses indicate good caching.

Practice

1. What is the main purpose of dynamic OG images in Next.js?

easy

A. To create custom preview images automatically based on URL data

B. To improve server response time by caching images

C. To replace all static images with animated GIFs

D. To generate CSS styles dynamically for components

Solution

1. Step 1: Understand OG images

   OG images are preview pictures shown when sharing links on social media.

2. Step 2: Role of dynamic OG images in Next.js

   Dynamic OG images let you create these previews automatically using URL parameters, making each preview unique.

3. Final Answer:

   To create custom preview images automatically based on URL data -> Option A

4. Quick Check:

   Dynamic OG images = Custom previews [OK]

Hint: Dynamic OG images create previews from URL info [OK]

Common Mistakes:

• Thinking dynamic OG images improve server speed
• Confusing OG images with CSS or animations
• Assuming all images become GIFs automatically

2. Which Next.js import is required to create a dynamic OG image?

easy

A. import { generateImage } from 'next/api';

B. import { createImage } from 'next/image';

C. import { DynamicImage } from 'next/og';

D. import { ImageResponse } from 'next/server';

Solution

1. Step 1: Identify the correct import for OG images

   Next.js provides ImageResponse from 'next/server' to build dynamic OG images.

2. Step 2: Check other options

   Other imports like createImage, DynamicImage, or generateImage do not exist or are incorrect for this purpose.

3. Final Answer:

   import { ImageResponse } from 'next/server'; -> Option D

4. Quick Check:

   ImageResponse import = import { ImageResponse } from 'next/server'; [OK]

Hint: Use ImageResponse from next/server for OG images [OK]

Common Mistakes:

• Using imports from 'next/image' instead of 'next/server'
• Assuming 'next/og' or 'next/api' provide OG image tools
• Misspelling ImageResponse or import path

3. Given this Next.js API route code snippet for dynamic OG images, what will be the output image text if the URL query is ?title=Hello?

import { ImageResponse } from 'next/server';

export const runtime = 'edge';

export async function GET(request) {
  const { searchParams } = new URL(request.url);
  const title = searchParams.get('title') || 'Default';

  return new ImageResponse(
    (
      <div style={{
        backgroundColor: 'white',
        width: '100%',
        height: '100%',
        display: 'flex',
        justifyContent: 'center',
        alignItems: 'center',
        fontSize: 48,
        color: 'black'
      }}>
        {title}
      </div>
    ),
    { width: 1200, height: 630 }
  );
}

medium

A. An image with the text 'Default' centered

B. An image with the text 'Hello' centered

C. An image with no text displayed

D. A runtime error due to missing title parameter

Solution

1. Step 1: Extract the title from URL query

   The code gets the 'title' parameter from the URL. If missing, it defaults to 'Default'. Here, the query is '?title=Hello', so title = 'Hello'.

2. Step 2: Render the image with the title text

   The ImageResponse renders a div with the title text centered. Since title is 'Hello', the image will show 'Hello' centered.

3. Final Answer:

   An image with the text 'Hello' centered -> Option B

4. Quick Check:

   title param 'Hello' = text shown [OK]

Hint: Check URL param, fallback used only if missing [OK]

Common Mistakes:

• Assuming 'Default' shows even when title is provided
• Thinking missing text causes error
• Ignoring the URL query parameters

4. Identify the error in this Next.js dynamic OG image code snippet:

import { ImageResponse } from 'next/server';

export async function GET(request) {
  const { searchParams } = new URL(request.url);
  const name = searchParams.get('name');

  return new ImageResponse(
    (
      <div style={{ fontSize: 40 }}>
        Welcome, {name.toUpperCase()}!
      </div>
    ),
    { width: 800, height: 400 }
  );
}

medium

A. Calling toUpperCase() on null if 'name' is missing causes an error

B. ImageResponse must be imported from 'next/image' instead of 'next/server'

C. The style object cannot be used inside JSX for ImageResponse

D. The GET function must be synchronous, not async

Solution

1. Step 1: Check usage of name variable

   The code calls name.toUpperCase() without checking if name is null. If the URL has no 'name' parameter, name is null, causing a runtime error.

2. Step 2: Verify other parts

   Import from 'next/server' is correct. Style objects are allowed in JSX for ImageResponse. The GET function can be async.

3. Final Answer:

   Calling toUpperCase() on null if 'name' is missing causes an error -> Option A

4. Quick Check:

   Null check missing before toUpperCase() [OK]

Hint: Always check for null before string methods [OK]

Common Mistakes:

• Assuming name is always present
• Confusing import source for ImageResponse
• Thinking style objects are disallowed in JSX

5. You want to create a dynamic OG image in Next.js that shows a user's name and their score from URL parameters. The score should show 'N/A' if missing or zero. Which code snippet correctly implements this logic? A:

const score = searchParams.get('score') || 'N/A';
const displayScore = score === 0 ? 'N/A' : score;

B:

const score = Number(searchParams.get('score'));
const displayScore = score ?? 'N/A';

C:

const score = Number(searchParams.get('score'));
const displayScore = score > 0 ? score : 'N/A';

D:

const score = searchParams.get('score');
const displayScore = score === null || score === 0 ? 'N/A' : score;

hard

A. Option A

B. Option B

C. Option C

D. Option D

Solution

1. Step 1: Understand the requirement for score

   The score should be shown as a number if positive, otherwise 'N/A' if missing or zero.

2. Step 2: Analyze each option

   Snippet A uses string fallback and compares score === 0 but score is string, so '0' === 0 false and displays '0'.
   Snippet B converts score to number but uses ?? which only replaces null/undefined, not 0 or NaN, so displays 0 for score=0.
   Snippet C converts score to number and uses a clear check: if score > 0 show score else 'N/A'. This matches requirement perfectly.
   Snippet D compares score as string with === 0, but '0' === 0 false, so displays '0'.

3. Final Answer:

   Option C -> Option C

4. Quick Check:

   Number conversion + >0 check = Option C [OK]

Hint: Convert to number and check > 0 for score display [OK]

Common Mistakes:

• Not converting score to number before comparison
• Using nullish coalescing (??) that ignores zero
• Comparing string '0' instead of numeric zero