GET route handling in Express - Performance & Optimization

Performance: GET route handling

MEDIUM IMPACT

This affects server response time and how quickly the browser receives content to start rendering.

Serving a simple static response on a GET request

Express

app.get('/data', async (req, res) => {
  // asynchronous processing or cached result
  const result = await getCachedResult();
  res.send(`Result is ${result}`);
});

Non-blocking async code allows server to handle other requests and respond faster.

📈 Performance GainReduces server response delay, improving LCP by hundreds of milliseconds

Serving a simple static response on a GET request

Express

app.get('/data', (req, res) => {
  // heavy synchronous processing
  let result = 0;
  for(let i = 0; i < 1e8; i++) {
    result += i;
  }
  res.send(`Result is ${result}`);
});

Blocking synchronous processing delays response, increasing server response time and slowing page load.

📉 Performance CostBlocks event loop, delaying response by hundreds of milliseconds

Performance Comparison

Pattern	Server Blocking	Response Delay	Security Risk	Verdict
Synchronous heavy processing in GET route	Blocks event loop	High delay (100+ ms)	Low	[X] Bad
Asynchronous or cached response in GET route	Non-blocking	Low delay (<10 ms)	Low	[OK] Good
Unparameterized DB query in GET route	Blocks event loop	Medium delay (50+ ms)	High	[X] Bad
Parameterized async DB query in GET route	Non-blocking	Low delay (<20 ms)	Low	[OK] Good

Rendering Pipeline

GET route handling affects the server's ability to quickly send HTML or data to the browser, which impacts when the browser can start rendering the page.

→Server Processing

→Network Transfer

→Browser Rendering Start

⚠️ BottleneckServer Processing when route handlers block or do heavy synchronous work

Core Web Vital Affected

LCP

This affects server response time and how quickly the browser receives content to start rendering.

Optimization Tips

1Avoid synchronous blocking code in GET route handlers to keep server responsive.

2Use asynchronous calls and caching to speed up GET route responses.

3Parameterize database queries to improve security and performance.

Performance Quiz - 3 Questions

What is the main performance problem with synchronous heavy processing inside a GET route handler?

A It blocks the server event loop, delaying all responses

B It increases client-side rendering time

C It reduces network bandwidth

D It causes layout shifts in the browser

DevTools: Network

How to check: Open DevTools, go to Network tab, reload the page, and look at the time for the GET request to complete.

What to look for: Look for long waiting (TTFB) times indicating slow server response; shorter times mean better performance.

Practice

1. What does the app.get() method do in an Express app?

easy

A. Starts the Express server and listens on a port

B. Defines a route to handle GET requests at a specific URL

C. Sends a POST request to a server

D. Deletes a route from the Express app

Solution

1. Step 1: Understand the purpose of app.get()

   The app.get() method is used to define a route that listens for GET requests on a given URL path.

2. Step 2: Compare with other methods

   Other methods like app.post() handle POST requests, and app.listen() starts the server, so they do not define GET routes.

3. Final Answer:

   Defines a route to handle GET requests at a specific URL -> Option B

4. Quick Check:

   app.get() defines GET routes [OK]

Hint: app.get() always sets up a GET route handler [OK]

Common Mistakes:

• Confusing app.get() with app.listen()
• Thinking app.get() sends requests instead of handling them
• Mixing GET with POST methods

2. Which of the following is the correct syntax to create a GET route for the path /hello that sends "Hello World" as a response?

easy

A. app.get('/hello', (req, res) => { res.send('Hello World'); });

B. app.get('/hello', (res, req) => { res.send('Hello World'); });

C. app.get('/hello', (req, res) => { res.write('Hello World'); });

D. app.get('/hello', (req, res) => { res.sendHello('Hello World'); });

Solution

1. Step 1: Check parameter order in callback

   The callback function parameters must be req first, then res. app.get('/hello', (res, req) => { res.send('Hello World'); }); reverses them, which is incorrect.

2. Step 2: Verify response method usage

   The correct method to send a response string is res.send(). app.get('/hello', (req, res) => { res.write('Hello World'); }); uses res.write() which is not standard in Express, and app.get('/hello', (req, res) => { res.sendHello('Hello World'); }); uses a non-existent method res.sendHello().

3. Final Answer:

   app.get('/hello', (req, res) => { res.send('Hello World'); }); -> Option A

4. Quick Check:

   Correct syntax uses req, res and res.send() [OK]

Hint: Use (req, res) and res.send() to respond in GET routes [OK]

Common Mistakes:

• Swapping req and res parameters
• Using res.write() instead of res.send()
• Calling non-existent response methods

3. What will be the output when a GET request is made to /user/42 with this route handler?

app.get('/user/:id', (req, res) => {
  res.send(`User ID is ${req.params.id}`);
});

medium

A. User ID is undefined

B. User ID is :id

C. Error: req.params is not defined

D. User ID is 42

Solution

1. Step 1: Understand route parameters

   The route /user/:id captures the part after /user/ as req.params.id.

2. Step 2: Substitute parameter in response

   When visiting /user/42, req.params.id is "42", so the response is "User ID is 42".

3. Final Answer:

   User ID is 42 -> Option D

4. Quick Check:

   Route params fill req.params.id correctly [OK]

Hint: Use req.params to get URL parts in routes [OK]

Common Mistakes:

• Using req.params without defining route parameter
• Expecting literal ':id' in output
• Forgetting to use backticks for template strings

4. Identify the error in this GET route handler:

app.get('/data', (req, res) => {
  res.send('Data received')
  res.send('Another response');
});

medium

A. Missing semicolon after first res.send()

B. Route path should be '/data/' with trailing slash

C. Cannot call res.send() twice in the same request handler

D. req parameter is unused and causes error

Solution

1. Step 1: Check response sending rules

   Express allows sending only one response per request. Calling res.send() twice causes an error.

2. Step 2: Analyze other options

   Missing semicolons do not cause runtime errors here, trailing slash is optional, and unused parameters do not cause errors.

3. Final Answer:

   Cannot call res.send() twice in the same request handler -> Option C

4. Quick Check:

   Only one res.send() per request allowed [OK]

Hint: Send response only once per route handler [OK]

Common Mistakes:

• Calling res.send() multiple times
• Thinking missing semicolons cause errors
• Confusing trailing slash necessity

5. You want to create a GET route /product/:category/:id that responds with a message like "Category: electronics, ID: 123". Which code correctly implements this?

hard

A. app.get('/product/:category/:id', (req, res) => { res.send(`Category: ${req.params.category}, ID: ${req.params.id}`); });

B. app.get('/product/:category/:id', (req, res) => { res.send('Category: req.params.category, ID: req.params.id'); });

C. app.get('/product/:category/:id', (res, req) => { res.send(`Category: ${req.params.category}, ID: ${req.params.id}`); });

D. app.get('/product/:category/:id', (req, res) => { res.send(`Category: ${req.query.category}, ID: ${req.query.id}`); });

Solution

1. Step 1: Use correct parameter order and template literals

   The callback must have (req, res) and use backticks with ${} to insert variables. app.get('/product/:category/:id', (req, res) => { res.send(`Category: ${req.params.category}, ID: ${req.params.id}`); }); does this correctly.

2. Step 2: Use req.params for URL parameters

   Route parameters are accessed via req.params, not req.query. app.get('/product/:category/:id', (req, res) => { res.send(`Category: ${req.query.category}, ID: ${req.query.id}`); }); incorrectly uses req.query. app.get('/product/:category/:id', (req, res) => { res.send('Category: req.params.category, ID: req.params.id'); }); uses quotes, so variables won't be evaluated. app.get('/product/:category/:id', (res, req) => { res.send(`Category: ${req.params.category}, ID: ${req.params.id}`); }); swaps parameters.

3. Final Answer:

   app.get('/product/:category/:id', (req, res) => { res.send(`Category: ${req.params.category}, ID: ${req.params.id}`); }); -> Option A

4. Quick Check:

   Use req.params and template literals correctly [OK]

Hint: Use req.params and backticks for dynamic route responses [OK]

Common Mistakes:

• Swapping req and res parameters
• Using string quotes instead of template literals
• Using req.query instead of req.params for route params