Metadata API (static metadata) in NextJS - Performance & Optimization

Performance: Metadata API (static metadata)

MEDIUM IMPACT

This affects the initial page load speed by providing metadata without runtime overhead.

Defining page metadata in Next.js

NextJS

export const metadata = {
  title: 'Static Page Title',
  description: 'Static description for SEO',
};

Metadata is defined statically at build time, so no runtime fetch or delay occurs.

📈 Performance GainImproves LCP by 100-300ms by eliminating runtime metadata fetch

Defining page metadata in Next.js

NextJS

export async function generateMetadata() {
  const res = await fetch('https://api.example.com/meta');
  const data = await res.json();
  return { title: data.title };
}

Fetching metadata at runtime delays page rendering and blocks initial paint.

📉 Performance CostBlocks rendering for 100-300ms depending on network latency

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Runtime metadata fetch	No extra DOM nodes	0 reflows	Blocks paint until data arrives	[X] Bad
Static metadata export	No extra DOM nodes	0 reflows	No paint blocking, immediate metadata	[OK] Good

Rendering Pipeline

Static metadata is injected during build time, so the browser receives fully formed HTML with metadata, avoiding runtime delays.

→Server Rendering

→HTML Delivery

→First Paint

⚠️ BottleneckRuntime metadata fetching delays server response and blocks first paint

Core Web Vital Affected

LCP

This affects the initial page load speed by providing metadata without runtime overhead.

Optimization Tips

1Define metadata statically to avoid runtime delays.

2Avoid fetching metadata during server rendering to improve LCP.

3Static metadata reduces server response time and speeds up first paint.

Performance Quiz - 3 Questions

What is the main performance benefit of using static metadata in Next.js?

A It decreases JavaScript bundle size significantly.

B It avoids runtime data fetching, speeding up initial page load.

C It reduces the number of DOM nodes created.

D It improves client-side navigation speed.

DevTools: Network and Performance

How to check: Open DevTools, go to Network tab, reload page and check if metadata fetch requests occur; then use Performance tab to see if first paint is delayed.

What to look for: Look for absence of metadata fetch requests and earlier First Contentful Paint (FCP) and Largest Contentful Paint (LCP) timings.

Practice

1. What is the primary purpose of exporting a metadata object in a Next.js page or layout?

easy

A. To provide static information like title and description for SEO and social sharing

B. To define dynamic routes for the page

C. To handle user authentication on the page

D. To style the page with CSS variables

Solution

1. Step 1: Understand the role of metadata in Next.js

   The metadata object is used to add static information such as page title and description.

2. Step 2: Connect metadata to SEO and social sharing

   This information helps search engines and social media platforms display the page correctly.

3. Final Answer:

   To provide static information like title and description for SEO and social sharing -> Option A

4. Quick Check:

   Metadata = SEO info [OK]

Hint: Metadata sets page info for SEO and sharing [OK]

Common Mistakes:

• Confusing metadata with routing or styling
• Thinking metadata handles user login
• Assuming metadata is dynamic by default

2. Which of the following is the correct way to export static metadata in a Next.js page?

easy

A. export default { metadata: { title: 'Home' } }

B. export function metadata() { return { title: 'Home' } }

C. export const metadata = { title: 'Home' }

D. const metadata = { title: 'Home' }; export metadata

Solution

1. Step 1: Recall the syntax for static metadata export

   Next.js expects a named export called metadata as an object.

2. Step 2: Check each option's syntax

   export const metadata = { title: 'Home' } correctly exports a constant object named metadata. The other options use incorrect export forms or syntax.

3. Final Answer:

   export const metadata = { title: 'Home' } -> Option C

4. Quick Check:

   Named export of object = export const metadata = { title: 'Home' } [OK]

Hint: Use named export const metadata = {...} [OK]

Common Mistakes:

• Using default export instead of named export
• Exporting a function instead of an object
• Incorrect export syntax causing errors

3. Given this metadata export in a Next.js page:

export const metadata = { title: 'About Us', description: 'Learn about our team' }

What will be the page's title shown in the browser tab?

medium

A. About Us

B. Learn about our team

C. metadata

D. No title will be shown

Solution

1. Step 1: Identify the title property in metadata

   The metadata object has a title set to 'About Us'.

2. Step 2: Understand how Next.js uses metadata

   Next.js uses the title property to set the browser tab's page title.

3. Final Answer:

   About Us -> Option A

4. Quick Check:

   Page title = metadata.title [OK]

Hint: Page title comes from metadata.title [OK]

Common Mistakes:

• Confusing description with title
• Expecting metadata object name as title
• Assuming no title is set without explicit <title> tag

4. You wrote this metadata export:

export const metadata = { title: 'Contact', description: Contact us page }

Why does this cause an error?

medium

A. export keyword is not allowed here

B. Missing quotes around the description string

C. title property cannot be 'Contact'

D. metadata must be a function, not an object

Solution

1. Step 1: Check the syntax of the description value

   The description value is written without quotes, which is invalid for strings in JavaScript.

2. Step 2: Understand JavaScript string syntax

   Strings must be enclosed in quotes (' or ") to be valid. Missing quotes cause a syntax error.

3. Final Answer:

   Missing quotes around the description string -> Option B

4. Quick Check:

   Strings need quotes [OK]

Hint: Always quote string values in metadata [OK]

Common Mistakes:

• Forgetting quotes around strings
• Thinking metadata must be a function
• Misplacing export keyword

5. You want to add static metadata with a title, description, and open graph image to a Next.js layout. Which is the correct way to include all these in the metadata export?

hard

A. export const metadata = { title: 'Blog', description: 'Latest posts', openGraph: { images: { src: '/blog.png' } } }

B. export const metadata = { title: 'Blog', description: 'Latest posts', openGraph: '/blog.png' }

C. export const metadata = { title: 'Blog', description: 'Latest posts', openGraph: { image: '/blog.png' } }

D. export const metadata = { title: 'Blog', description: 'Latest posts', openGraph: { images: [{ url: '/blog.png' }] } }

Solution

1. Step 1: Understand openGraph image format in Next.js metadata

   The openGraph images property expects an array of objects with a url key.

2. Step 2: Check each option's openGraph structure

   export const metadata = { title: 'Blog', description: 'Latest posts', openGraph: { images: [{ url: '/blog.png' }] } } correctly uses an array with an object containing url. The other options use incorrect formats.

3. Final Answer:

   export const metadata = { title: 'Blog', description: 'Latest posts', openGraph: { images: [{ url: '/blog.png' }] } } -> Option D

4. Quick Check:

   openGraph images = array of {url} objects [OK]

Hint: Use array of objects with url for openGraph images [OK]

Common Mistakes:

• Using string instead of array for images
• Using wrong property name like image instead of images
• Not wrapping image url in an object