Why optimization matters for performance in NextJS - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to import the Next.js Image component correctly.

NextJS

import [1] from 'next/image';

Drag options to blanks, or click blank then click option'

APicture

Bimg

CImage

DNextImage

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'img' instead of 'Image' which is a standard HTML tag, not the Next.js optimized component.

Using 'Picture' or 'NextImage' which are not valid imports.

The Next.js Image component is imported as Image from 'next/image'. This component helps optimize images automatically.

2fill in blank

medium

Complete the code to use the Next.js Image component with a fixed width and height.

NextJS

<Image src="/logo.png" alt="Logo" width=[1] height={50} />

Drag options to blanks, or click blank then click option'

A100

B"100"

C"100px"

Dpx100

Attempts:

3 left

💡 Hint

Common Mistakes

Passing width as a string with quotes or units causes errors.

Using invalid values like 'px100' which is not a number.

The width and height props expect numbers, not strings with units. So use 100 without quotes or units.

3fill in blank

hard

Fix the error in the Next.js API route handler to send a JSON response.

NextJS

export default function handler(req, res) {
  res.[1]({ message: 'Hello' });
}

Drag options to blanks, or click blank then click option'

Awrite

Bsend

Crender

Djson

Attempts:

3 left

💡 Hint

Common Mistakes

Using res.send() which is not recommended in Next.js API routes.

Using res.render() which is for server-side rendering, not API responses.

In Next.js API routes, res.json() sends a JSON response properly.

4fill in blank

hard

Fill both blanks to create a dynamic route in Next.js that fetches data based on the URL parameter.

NextJS

export async function getServerSideProps(context) {
  const id = context.params.[1];
  const res = await fetch(`https://api.example.com/data/$[2]`);
  const data = await res.json();
  return { props: { data } };
}

Drag options to blanks, or click blank then click option'

Aid

Bslug

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing 'id' and 'slug' inconsistently causes errors.

Using undefined parameter names.

The URL parameter is accessed via context.params.id, and the same id is used in the fetch URL.

5fill in blank

hard

Fill all three blanks to optimize a Next.js page by using React's useMemo hook to memoize a computed value.

NextJS

import { useMemo } from 'react';

export default function Page({ items }) {
  const total = useMemo(() => items.[1]((sum, item) => sum [2] item.value, [3]), [items]);
  return <div>Total: {total}</div>;
}

Drag options to blanks, or click blank then click option'

Areduce

B+

C0

Dmap

Attempts:

3 left

💡 Hint

Common Mistakes

Using map instead of reduce for summing values.

Using wrong initial value or operator causing incorrect totals.

Use reduce to sum values, + as the operator, and 0 as the initial sum value. useMemo memoizes this calculation for performance.

Practice

1. Why is optimization important for a Next.js app's performance?

easy

A. It disables important features to save resources.

B. It increases the app's file size significantly.

C. It makes the app load faster and run smoother for users.

D. It makes the app harder to maintain.

Solution

1. Step 1: Understand what optimization does

   Optimization improves how fast and smoothly an app works by reducing delays and resource use.

2. Step 2: Connect optimization to user experience

   Faster and smoother apps keep users happy and reduce wasted resources like bandwidth and CPU.

3. Final Answer:

   It makes the app load faster and run smoother for users. -> Option C

4. Quick Check:

   Optimization = faster, smoother app [OK]

Hint: Optimization means faster and smoother apps [OK]

Common Mistakes:

• Thinking optimization increases file size
• Believing optimization disables features
• Assuming optimization makes maintenance harder

2. Which Next.js feature helps optimize images automatically?

easy

A. <img> tag with manual resizing

B. <Image> component with built-in optimization

C. Using external image URLs without optimization

D. Loading images with JavaScript after page load

Solution

1. Step 1: Identify Next.js image optimization feature

   Next.js provides the <Image> component that automatically optimizes images for size and format.

2. Step 2: Compare with other options

   Using plain <img> or external URLs does not optimize images automatically, and loading images with JS delays display.

3. Final Answer:

   <Image> component with built-in optimization -> Option B

4. Quick Check:

   Next.js image optimization = <Image> component [OK]

Hint: Next.js image optimization uses <Image> component [OK]

Common Mistakes:

• Confusing <img> tag with Next.js optimization
• Thinking external URLs optimize images automatically
• Believing JavaScript image loading is optimization

3. What will happen if you use Next.js static generation for a page instead of server-side rendering?

medium

A. The page loads faster because HTML is pre-built at build time.

B. The page will always show outdated data because it never updates.

C. The server will generate the page on every user request.

D. The page will not be accessible without internet connection.

Solution

1. Step 1: Understand static generation in Next.js

   Static generation builds the page HTML once during build time, so it can be served quickly without server delay.

2. Step 2: Compare with server-side rendering

   Server-side rendering builds the page on each request, which is slower. Static pages load faster but may not have real-time data.

3. Final Answer:

   The page loads faster because HTML is pre-built at build time. -> Option A

4. Quick Check:

   Static generation = faster load via pre-built HTML [OK]

Hint: Static generation pre-builds pages for faster load [OK]

Common Mistakes:

• Confusing static generation with server-side rendering
• Assuming static pages never update (can use revalidation)
• Thinking static pages require server on each request

4. You notice your Next.js app is slow because it loads large JavaScript bundles. What is a good way to fix this?

medium

A. Use dynamic imports to load components only when needed.

B. Combine all JavaScript into one big file to reduce requests.

C. Disable code splitting to simplify the app structure.

D. Remove all images to reduce bundle size.

Solution

1. Step 1: Identify cause of slow app

   Large JavaScript bundles slow down loading because users download too much code at once.

2. Step 2: Apply dynamic imports for optimization

   Dynamic imports split code so parts load only when needed, reducing initial bundle size and speeding up load.

3. Final Answer:

   Use dynamic imports to load components only when needed. -> Option A

4. Quick Check:

   Dynamic imports = smaller initial bundles [OK]

Hint: Dynamic imports load code only when needed [OK]

Common Mistakes:

• Combining all JS into one file increases bundle size
• Disabling code splitting removes optimization benefits
• Removing images is unrelated to JS bundle size

5. You want to optimize a Next.js app that fetches user data on every page load. Which approach best improves performance without losing fresh data?

hard

A. Use only client-side fetching to load data after page renders.

B. Pre-build pages once and never update them.

C. Use server-side rendering for every request without caching.

D. Use static generation with incremental static regeneration (ISR) to update pages periodically.

Solution

1. Step 1: Understand the need for fresh data and performance

   Fetching data on every load can slow pages; static generation is fast but can be stale.

2. Step 2: Use ISR to balance speed and freshness

   ISR lets Next.js pre-build pages and update them in the background at set intervals, keeping data fresh and fast.

3. Final Answer:

   Use static generation with incremental static regeneration (ISR) to update pages periodically. -> Option D

4. Quick Check:

   ISR = fast pages + fresh data [OK]

Hint: ISR updates static pages for fresh data [OK]

Common Mistakes:

• Relying only on client-side fetching delays content display
• Server-side rendering every request can be slow
• Never updating pre-built pages causes stale data