404 and error pages in Astro - Performance & Optimization

Performance: 404 and error pages

MEDIUM IMPACT

This affects the page load speed and user experience when users hit a missing or error page.

Serving a 404 page when a user visits a missing URL

Astro

export function GET() {
  return new Response('<h1>404 - Page Not Found</h1><p>Sorry, this page does not exist.</p>', {
    status: 404,
    headers: {'content-type': 'text/html'}
  });
}

Returns a simple static 404 page immediately without extra data fetching.

📈 Performance GainNon-blocking, renders instantly improving LCP

Serving a 404 page when a user visits a missing URL

Astro

export async function GET({ params }) {
  // Heavy data fetching or complex logic
  const data = await fetch('https://api.example.com/data');
  if (!data.ok) {
    return new Response('Page not found', { status: 404 });
  }
  return data;
}

Fetching heavy data or running complex logic delays the 404 page rendering, increasing load time.

📉 Performance CostBlocks rendering for 300-500ms depending on data fetch latency

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Heavy data fetching in 404 page	Multiple nodes due to dynamic content	Triggers 1 reflow after data loads	Higher paint cost due to complex layout	[X] Bad
Static simple 404 page	Few nodes with simple markup	Single reflow on initial paint	Low paint cost with minimal styles	[OK] Good

Rendering Pipeline

When a 404 or error page is requested, the server responds with a status and content. If the page is static and simple, the browser can start rendering immediately. Complex logic or data fetching delays the response, blocking the critical rendering path.

→Server Response

→HTML Parsing

→Style Calculation

→Layout

→Paint

⚠️ BottleneckServer Response time due to heavy data fetching or logic

Core Web Vital Affected

LCP

This affects the page load speed and user experience when users hit a missing or error page.

Optimization Tips

1Serve static 404 and error pages without heavy data fetching.

2Cache error pages to reduce server response time on repeated requests.

3Keep error page markup simple to minimize DOM and paint cost.

Performance Quiz - 3 Questions

What is the main performance benefit of serving a static 404 page in Astro?

A It reduces server response time and speeds up page load

B It increases the bundle size for better caching

C It triggers more reflows for better layout accuracy

D It delays rendering to fetch more data

DevTools: Network

How to check: Open DevTools > Network tab, reload the 404 page URL, and check the response time and size.

What to look for: Look for fast response time under 100ms and small payload size indicating a lightweight 404 page.

Practice

1. What is the main purpose of a 404.astro page in an Astro project?

easy

A. To speed up the loading of the homepage

B. To display the site map automatically

C. To handle user login and authentication

D. To show a friendly message when a user visits a page that does not exist

Solution

1. Step 1: Understand the role of 404 pages

   A 404 page appears when a user tries to visit a page that the website cannot find.

2. Step 2: Identify the purpose in Astro

   In Astro, 404.astro is used to show a friendly message for missing pages.

3. Final Answer:

   To show a friendly message when a user visits a page that does not exist -> Option D

4. Quick Check:

   404 page = friendly missing page message [OK]

Hint: 404 pages show missing page messages [OK]

Common Mistakes:

• Thinking 404 pages speed up the homepage
• Confusing 404 pages with login pages
• Assuming 404 pages show site maps

2. Which file name should you create in an Astro project to automatically handle 404 errors?

easy

A. error.astro

B. notfound.astro

C. 404.astro

D. page404.astro

Solution

1. Step 1: Recall Astro's naming convention for 404 pages

   Astro uses the exact file name 404.astro to detect and serve 404 error pages automatically.

2. Step 2: Compare options with the required file name

   Only 404.astro matches the required name; others won't be recognized automatically.

3. Final Answer:

   404.astro -> Option C

4. Quick Check:

   404 page file = 404.astro [OK]

Hint: Use exact file name 404.astro for error pages [OK]

Common Mistakes:

• Using names like error.astro or notfound.astro
• Adding prefixes or suffixes to 404 file name
• Assuming any file with '404' works

3. Given this 404.astro code snippet, what will the user see when visiting a missing page?

<!-- 404.astro -->
<h1>Oops! Page not found.</h1>
<p>Try going back to the <a href='/'>homepage</a>.</p>

medium

A. A blank page with no message

B. A message saying 'Oops! Page not found.' with a link to homepage

C. An error message with code 500

D. The homepage content without any error message

Solution

1. Step 1: Read the 404.astro content

   The code shows a heading with 'Oops! Page not found.' and a paragraph with a homepage link.

2. Step 2: Understand what Astro renders on missing pages

   Astro will display this content when a user visits a missing page.

3. Final Answer:

   A message saying 'Oops! Page not found.' with a link to homepage -> Option B

4. Quick Check:

   404 page shows friendly message + homepage link [OK]

Hint: 404 page content shows on missing pages [OK]

Common Mistakes:

• Expecting a blank page instead of message
• Confusing 404 with server error 500
• Thinking homepage content shows on 404

4. You created a 404.astro page but it does not show when visiting a missing page. What is the most likely mistake?

medium

A. The 404.astro file is inside the src/components folder

B. The file is named 404.html instead of 404.astro

C. The homepage link is missing inside the 404 page

D. The project does not have a package.json file

Solution

1. Step 1: Check file location requirements in Astro

   Astro expects 404.astro to be in the root of the src/pages folder, not inside components.

2. Step 2: Understand why wrong location breaks 404 page

   If placed in src/components, Astro won't serve it automatically as a 404 page.

3. Final Answer:

   The 404.astro file is inside the src/components folder -> Option A

4. Quick Check:

   404 page must be in pages folder [OK]

Hint: Place 404.astro in src/pages folder [OK]

Common Mistakes:

• Naming file 404.html instead of 404.astro
• Putting 404.astro in components folder
• Thinking missing homepage link breaks 404 page
• Assuming package.json affects 404 page

5. You want to create a custom error page in Astro that shows different messages for 404 and 500 errors. Which approach is best?

hard

A. Create separate 404.astro and 500.astro files in src/pages

B. Use only 404.astro and add JavaScript to detect 500 errors

C. Create a single error.astro file and rename it to 404.astro when needed

D. Handle errors only in client-side JavaScript, no Astro pages needed

Solution

1. Step 1: Understand Astro's error page handling

   Astro supports special files like 404.astro and 500.astro to handle different error codes automatically.

2. Step 2: Choose the best way to show different messages

   Creating separate files for 404 and 500 errors is clean and follows Astro conventions.

3. Final Answer:

   Create separate 404.astro and 500.astro files in src/pages -> Option A

4. Quick Check:

   Separate files for each error code [OK]

Hint: Use separate 404.astro and 500.astro files [OK]

Common Mistakes:

• Trying to detect errors with JavaScript in 404.astro
• Renaming files manually instead of separate files
• Ignoring server-side error handling