Open Graph and Twitter cards in NextJS - Performance & Optimization

Performance: Open Graph and Twitter cards

MEDIUM IMPACT

This affects the page load speed and initial rendering by adding metadata that social platforms use to generate rich previews.

Adding social media preview metadata to a Next.js page

NextJS

import Head from 'next/head';

export default function Page() {
  return (
    <>
      <Head>
        <meta property="og:title" content="My Page" />
        <meta property="og:description" content="Description here" />
        <meta property="og:image" content="/optimized-image.webp" />
        <meta name="twitter:card" content="summary_large_image" />
        <meta name="twitter:image" content="/optimized-image.webp" />
      </Head>
      <main>Content</main>
    </>
  );
}

Using optimized, compressed images in modern formats reduces load time and speeds up LCP.

📈 Performance GainReduces image load time by 50-70%, improving LCP by 150-300ms.

Adding social media preview metadata to a Next.js page

NextJS

import Head from 'next/head';

export default function Page() {
  return (
    <>
      <Head>
        <meta property="og:title" content="My Page" />
        <meta property="og:description" content="Description here" />
        <meta property="og:image" content="/large-image.jpg" />
        <meta name="twitter:card" content="summary_large_image" />
        <meta name="twitter:image" content="/large-image.jpg" />
      </Head>
      <main>Content</main>
    </>
  );
}

Using large images without optimization causes slower page load and delays Largest Contentful Paint (LCP).

📉 Performance CostBlocks rendering for 200-400ms on slow connections due to large image fetch.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Large unoptimized OG image	Minimal (metadata only)	0	High due to image load delay	[X] Bad
Optimized OG image with compressed format	Minimal (metadata only)	0	Low paint cost	[OK] Good
Metadata with blocking scripts in head	Minimal	0	High due to render-blocking	[X] Bad
Metadata only, no blocking scripts	Minimal	0	Low paint cost	[OK] Good

Rendering Pipeline

Open Graph and Twitter card metadata are parsed during the HTML parsing stage and do not trigger layout or paint. However, referenced images can delay the loading of the main content if not optimized.

→HTML Parsing

→Network Loading

→Largest Contentful Paint

⚠️ BottleneckNetwork Loading of large images referenced in metadata

Core Web Vital Affected

LCP

This affects the page load speed and initial rendering by adding metadata that social platforms use to generate rich previews.

Optimization Tips

1Use optimized, compressed images in Open Graph and Twitter card metadata to improve LCP.

2Avoid adding render-blocking scripts or large assets in the head with metadata.

3Keep metadata minimal and only include necessary tags to prevent blocking the critical rendering path.

Performance Quiz - 3 Questions

How does using large unoptimized images in Open Graph tags affect page performance?

A It delays Largest Contentful Paint by increasing image load time

B It improves page load speed by caching images

C It has no effect on page performance

D It reduces Cumulative Layout Shift

DevTools: Performance

How to check: Open DevTools, go to Performance tab, record page load, and look for Largest Contentful Paint timing and any long tasks blocking rendering.

What to look for: Check if image loading delays LCP or if scripts block main thread causing delayed paint.

Practice

1. What is the main purpose of adding Open Graph and Twitter card meta tags in a Next.js page?

easy

A. To speed up the page loading time

B. To improve how links appear when shared on social media platforms

C. To add custom fonts to the page

D. To enable server-side rendering

Solution

1. Step 1: Understand Open Graph and Twitter cards

   These meta tags control how links look when shared on social media, like showing images and descriptions.

2. Step 2: Identify their purpose in Next.js

   Adding these tags inside the Head component improves link previews, not performance or fonts.

3. Final Answer:

   To improve how links appear when shared on social media platforms -> Option B

4. Quick Check:

   Open Graph = Better social media previews [OK]

Hint: Open Graph tags control social media link previews [OK]

Common Mistakes:

• Thinking they speed up page loading
• Confusing with styling or fonts
• Assuming they enable server-side rendering

2. Which of the following is the correct way to add an Open Graph title tag inside a Next.js page using the Head component?

easy

A. My Page Title

B.

C.

D.

Solution

1. Step 1: Recall Open Graph meta tag syntax

   Open Graph tags use property="og:..." attribute, not name.

2. Step 2: Check Next.js Head usage

   Meta tags go inside Head with correct attributes; property="og:title" is correct for Open Graph title.

3. Final Answer:

   <Head><meta property="og:title" content="My Page Title" /></Head> -> Option D

4. Quick Check:

   Open Graph uses property="og:title" [OK]

Hint: Use property="og:title" for Open Graph title meta tag [OK]

Common Mistakes:

• Using name="og:title" instead of property
• Confusing Twitter card tags with Open Graph
• Placing meta tags outside <Head>

3. Given this Next.js component, what will be the rendered meta tag for Twitter card title?

import Head from 'next/head';

export default function Page() {
  return (
    <Head>
      <meta name="twitter:title" content="Welcome to Next.js" />
    </Head>
  );
}

medium

A. <meta name="og:title" content="Welcome to Next.js" />

B. <meta property="twitter:title" content="Welcome to Next.js" />

C. <meta name="twitter:title" content="Welcome to Next.js" />

D. No meta tag will be rendered

Solution

1. Step 1: Check the meta tag syntax in the component

   The component uses name="twitter:title" which is correct for Twitter cards.

2. Step 2: Confirm rendering behavior

   Next.js Head renders meta tags as written, so the tag will appear exactly as coded.

3. Final Answer:

   <meta name="twitter:title" content="Welcome to Next.js" /> -> Option C

4. Quick Check:

   Twitter card title uses name="twitter:title" [OK]

Hint: Twitter card title uses name="twitter:title" attribute [OK]

Common Mistakes:

• Using property instead of name for Twitter tags
• Confusing Open Graph and Twitter meta attributes
• Assuming Next.js modifies meta tags automatically

4. You added this code to your Next.js page but the Twitter card image is not showing:

<Head>
  <meta name="twitter:card" content="summary_large_image" />
  <meta name="twitter:image" content="/images/card.png" />
</Head>

What is the most likely reason the image does not appear on Twitter?

medium

A. The image URL is relative and should be absolute with full domain

B. The meta tag name should be property instead of name

C. Twitter cards do not support images

D. The content attribute is missing

Solution

1. Step 1: Check the image URL format

   Twitter requires absolute URLs (including https://domain) for images, not relative paths.

2. Step 2: Verify meta tag attributes

   Using name="twitter:image" is correct; Twitter supports images in cards.

3. Final Answer:

   The image URL is relative and should be absolute with full domain -> Option A

4. Quick Check:

   Twitter image URLs must be absolute [OK]

Hint: Use full URL for Twitter card images, not relative paths [OK]

Common Mistakes:

• Using relative image URLs
• Changing name to property for Twitter tags
• Thinking Twitter cards don't support images

5. You want to create a Next.js page that sets both Open Graph and Twitter card meta tags for title, description, and image. Which code snippet correctly combines these tags inside the Head component?

hard

A.

B.

C.

D.

Solution

1. Step 1: Verify Open Graph meta tags

   Open Graph tags use property="og:..." with absolute image URL, which is correct in options A, C, D.

2. Step 2: Verify Twitter card meta tags

   Twitter tags use name="twitter:..." and include twitter:card with value summary_large_image for large image preview, correctly done only in A.

3. Step 3: Check image URLs and completeness

   uses absolute URLs for images and includes all required tags for both Open Graph and Twitter cards.

4. Final Answer:

   Option A correctly combines Open Graph and Twitter card meta tags with proper attributes and URLs -> Option A

5. Quick Check:

   Open Graph uses property, Twitter uses name, absolute URLs needed [OK]

Hint: Use property for Open Graph, name for Twitter, absolute URLs for images [OK]

Common Mistakes:

• Using name instead of property for Open Graph
• Using relative URLs for images
• Omitting twitter:card meta tag