Finding and querying documents in Express - Performance & Optimization

Performance: Finding and querying documents

MEDIUM IMPACT

This affects server response time and how quickly the client receives data after a query.

Querying documents from a database in an Express app

Express

app.get('/users', async (req, res) => {
  const users = await User.find({ active: true }).limit(50);
  res.json(users);
});

Filters data and limits results to reduce server load and response size.

📈 Performance GainFaster query execution and smaller payload; improves LCP.

Querying documents from a database in an Express app

Express

app.get('/users', async (req, res) => {
  const users = await User.find();
  res.json(users);
});

Fetching all documents without filters can return large data sets, increasing response time and payload size.

📉 Performance CostBlocks response until all documents load; large payload increases network time.

Performance Comparison

Pattern	Server Processing	Network Payload	Response Time	Verdict
Query all documents without filters	High (full collection scan)	Large (all data sent)	Slow (blocks response)	[X] Bad
Query with filters and limit	Low (uses indexes)	Small (limited data)	Fast (quick response)	[OK] Good

Rendering Pipeline

Express queries run on the server before sending data to the browser. Slow queries delay the server response, which delays the browser's rendering start.

→Server Processing

→Network Transfer

→Browser Rendering

⚠️ BottleneckServer Processing (database query execution)

Core Web Vital Affected

LCP

This affects server response time and how quickly the client receives data after a query.

Optimization Tips

1Always filter queries to return only needed documents.

2Use database indexes to speed up queries.

3Limit the number of documents returned to reduce payload size.

Performance Quiz - 3 Questions

What is a common performance issue when querying documents without filters in Express?

A Returning too many documents increases response time and payload size.

B Using filters slows down the query.

C Limiting results causes server errors.

D Queries without filters always use indexes.

DevTools: Network

How to check: Open DevTools, go to Network tab, filter by XHR/fetch, and inspect the API request timing and payload size.

What to look for: Look for long waiting times or large response sizes indicating slow or heavy queries.