Server routes and API in Vue - Performance & Optimization

Performance: Server routes and API

MEDIUM IMPACT

This concept affects page load speed and interaction responsiveness by controlling how data is fetched and served from the backend.

Fetching data for a Vue app from the backend

Vue

app.get('/api/data', (req, res) => {
  const { page = 1, limit = 20 } = req.query;
  // Fetch only needed data with pagination
  const data = database.getPage(page, limit);
  res.json(data);
});

Pagination limits data size, reducing response time and improving UI responsiveness.

📈 Performance GainReduces blocking time to under 100ms; lowers payload size by 80% or more

Fetching data for a Vue app from the backend

Vue

app.get('/api/data', (req, res) => {
  // Fetch all data without pagination or filtering
  const data = database.getAll();
  res.json(data);
});

Fetching all data at once causes large payloads and slow responses, blocking the UI.

📉 Performance CostBlocks rendering for 200-500ms on large datasets; increases payload size due to large JSON payloads

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Fetch all data at once	N/A	N/A	High due to large data rendering	[X] Bad
Paginated API requests	N/A	N/A	Low due to smaller data chunks	[OK] Good

Rendering Pipeline

Server routes handle requests and send data to the client. Efficient APIs reduce waiting time before the browser can render or update content.

→Network

→JavaScript Execution

→Rendering

⚠️ BottleneckNetwork latency and server processing time delay data availability for rendering.

Core Web Vital Affected

INP

This concept affects page load speed and interaction responsiveness by controlling how data is fetched and served from the backend.

Optimization Tips

1Limit API response size with pagination or filtering.

2Cache frequent data on the server to reduce processing time.

3Avoid sending unnecessary data to improve response speed.

Performance Quiz - 3 Questions

What is a key performance benefit of paginating API responses?

A Increases server CPU usage

B Reduces data size sent to client, speeding up response

C Makes the API more complex without speed benefits

D Blocks rendering longer due to multiple requests

DevTools: Network

How to check: Open DevTools, go to Network tab, filter by XHR/fetch, and observe API request size and response time.

What to look for: Look for large payload sizes and long response times indicating slow or inefficient API routes.

Practice

1. What is the main purpose of server routes in a Vue app using Nitro?

easy

A. To style the frontend components

B. To handle backend requests and send responses

C. To manage client-side state only

D. To create animations on the page

Solution

1. Step 1: Understand server routes role

   Server routes act as backend endpoints that receive requests from the frontend.

2. Step 2: Identify their function in Vue Nitro

   They process these requests and return data or responses, enabling communication between frontend and backend.

3. Final Answer:

   To handle backend requests and send responses -> Option B

4. Quick Check:

   Server routes = backend communication [OK]

Hint: Server routes handle backend requests, not frontend styling [OK]

Common Mistakes:

• Confusing server routes with frontend styling
• Thinking server routes manage only client state
• Assuming server routes create animations

2. Which of the following is the correct way to define a server route in a Vue Nitro project?

easy

A. app.get('/api', () => 'Hello')

B. const route = () => { console.log('Hello') }

C. export default defineEventHandler(() => { return { message: 'Hello' } })

D. function serverRoute() { return 'Hello' }

Solution

1. Step 1: Recognize Nitro server route syntax

   In Vue Nitro, server routes export a default function using defineEventHandler that returns data.

2. Step 2: Check each option

   export default defineEventHandler(() => { return { message: 'Hello' } }) uses defineEventHandler and returns an object, which is correct. Others either lack export, use wrong syntax, or are not Nitro style.

3. Final Answer:

   export default defineEventHandler(() => { return { message: 'Hello' } }) -> Option C

4. Quick Check:

   Use defineEventHandler for Nitro routes [OK]

Hint: Look for export default with defineEventHandler [OK]

Common Mistakes:

• Missing export default
• Not using defineEventHandler
• Using Express.js style instead of Nitro

3. Given this server route code in Vue Nitro:

export default defineEventHandler(() => { return { status: 'ok', count: 5 } })

What will the frontend receive when calling this API?

medium

A. Undefined

B. A string 'ok5'

C. An error because of missing await

D. { status: 'ok', count: 5 }

Solution

1. Step 1: Analyze the returned object

   The route returns an object with keys status and count, so the response is JSON with those values.

2. Step 2: Understand Nitro response behavior

   Nitro automatically serializes the returned object to JSON for the frontend.

3. Final Answer:

   { status: 'ok', count: 5 } -> Option D

4. Quick Check:

   Returned object = JSON response [OK]

Hint: Returned object becomes JSON response automatically [OK]

Common Mistakes:

• Expecting string concatenation
• Thinking await is needed for sync return
• Assuming undefined if no explicit JSON

4. What is wrong with this Vue Nitro server route code?

export default () => { return { message: 'Hi' } }

medium

A. Missing defineEventHandler wrapper

B. Return value must be a string

C. Export default is not allowed

D. Arrow function syntax is invalid

Solution

1. Step 1: Check Nitro route requirements

   Vue Nitro requires server routes to export a default function wrapped with defineEventHandler.

2. Step 2: Identify missing part

   The code exports a function but does not use defineEventHandler, so it won't work as a proper Nitro route.

3. Final Answer:

   Missing defineEventHandler wrapper -> Option A

4. Quick Check:

   Always wrap route with defineEventHandler [OK]

Hint: Always use defineEventHandler for server routes [OK]

Common Mistakes:

• Forgetting defineEventHandler
• Thinking return must be string
• Confusing export default rules

5. You want to create a server route in Vue Nitro that returns a list of users filtered by a query parameter `role`. Which code correctly accesses the query and returns filtered users?

hard

A. export default defineEventHandler(event => { const role = getQuery(event).role; return users.filter(u => u.role === role) })

B. export default defineEventHandler(() => { return users })

C. export default defineEventHandler(event => { const role = event.node.req.url.split('role=')[1]; return users.filter(u => u.role === role) })

D. export default defineEventHandler(event => { const role = event.query.role; return users.filter(u => u.role === role) })

Solution

1. Step 1: Understand query access in Nitro

   Vue Nitro provides a helper getQuery(event) to safely get query parameters from the request.

2. Step 2: Check each option for correct query usage

   export default defineEventHandler(event => { const role = getQuery(event).role; return users.filter(u => u.role === role) }) uses getQuery(event).role correctly. export default defineEventHandler(event => { const role = event.node.req.url.split('role=')[1]; return users.filter(u => u.role === role) }) manually parses URL which is error-prone. export default defineEventHandler(() => { return users }) ignores query. export default defineEventHandler(event => { const role = event.query.role; return users.filter(u => u.role === role) }) uses event.query which is not standard.

3. Final Answer:

   export default defineEventHandler(event => { const role = getQuery(event).role; return users.filter(u => u.role === role) }) -> Option A

4. Quick Check:

   Use getQuery(event) to read query params [OK]

Hint: Use getQuery(event) to access query parameters [OK]

Common Mistakes:

• Parsing URL manually instead of getQuery
• Using event.query which is undefined
• Ignoring query parameters