Admin vs user route protection in Express - Performance Comparison

Performance: Admin vs user route protection

MEDIUM IMPACT

This affects server response time and user experience by controlling access efficiently and avoiding unnecessary processing.

Protecting admin routes from unauthorized users

Express

function adminOnly(req, res, next) {
  if (!req.user || req.user.role !== 'admin') {
    return res.status(403).send('Forbidden');
  }
  next();
}

app.use('/admin', adminOnly);

app.get('/admin/dashboard', (req, res) => {
  // heavy data processing
  res.send('Admin Dashboard');
});

Middleware stops unauthorized requests early, avoiding unnecessary processing and reducing server load.

📈 Performance GainSaves CPU cycles and reduces response time for unauthorized users by early exit.

Protecting admin routes from unauthorized users

Express

app.get('/admin/dashboard', (req, res) => {
  // heavy data processing
  if (!req.user || req.user.role !== 'admin') {
    return res.status(403).send('Forbidden');
  } else {
    res.send('Admin Dashboard');
  }
});

Checking authorization inside route handlers or after heavy processing causes unnecessary server work and slower responses for unauthorized users.

📉 Performance CostBlocks response until processing finishes, increasing server CPU and delaying rejection.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Authorization in route handler after processing	N/A (server-side)	N/A	N/A	[X] Bad
Authorization middleware before route handler	N/A (server-side)	N/A	N/A	[OK] Good

Rendering Pipeline

Route protection middleware runs early in the request lifecycle, preventing unauthorized requests from reaching heavy processing or database calls.

→Request Handling

→Middleware Execution

→Response Generation

⚠️ BottleneckHeavy processing after authorization check if protection is delayed

Core Web Vital Affected

INP

This affects server response time and user experience by controlling access efficiently and avoiding unnecessary processing.

Optimization Tips

1Use middleware to check user roles before route handlers run.

2Reject unauthorized requests early to save server CPU and reduce response time.

3Centralize authorization logic for maintainability and consistent performance.

Performance Quiz - 3 Questions

Why is it better to use middleware for admin route protection instead of checking inside each route handler?

A Middleware stops unauthorized requests early, saving server resources.

B Middleware makes the code longer and harder to read.

C Middleware delays response time by adding extra steps.

D Middleware only works for user routes, not admin routes.

DevTools: Network

How to check: Open DevTools, go to Network tab, filter requests to protected routes, and observe response times and status codes.

What to look for: Fast 403 or redirect responses for unauthorized requests indicate efficient route protection middleware.

Practice

1. What is the main purpose of using middleware for admin vs user route protection in Express?

easy

A. To check user roles and allow or deny access accordingly

B. To speed up the server response time

C. To log every request made to the server

D. To change the URL of the route dynamically

Solution

1. Step 1: Understand middleware role

   Middleware runs before route handlers and can check conditions like user roles.

2. Step 2: Role-based access control

   Middleware can allow access only if the user has the right role, such as admin or user.

3. Final Answer:

   To check user roles and allow or deny access accordingly -> Option A

4. Quick Check:

   Middleware controls access = D [OK]

Hint: Middleware checks roles to protect routes [OK]

Common Mistakes:

• Thinking middleware speeds up server
• Confusing middleware with logging only
• Believing middleware changes URLs

2. Which of the following is the correct way to apply middleware for admin route protection in Express?

easy

A. app.get('/admin', (req, res) => adminMiddleware, res.send('Admin page'));

B. app.get('/admin', adminMiddleware, (req, res) => { res.send('Admin page'); });

C. app.use('/admin', (req, res) => { adminMiddleware(); res.send('Admin page'); });

D. app.get('/admin', (req, res) => { res.send('Admin page'); adminMiddleware(); });

Solution

1. Step 1: Understand middleware placement

   Middleware should be passed as a second argument before the route handler function.

2. Step 2: Check syntax correctness

   app.get('/admin', adminMiddleware, (req, res) => { res.send('Admin page'); }); correctly places adminMiddleware between route path and handler.

3. Final Answer:

   app.get('/admin', adminMiddleware, (req, res) => { res.send('Admin page'); }); -> Option B

4. Quick Check:

   Middleware before handler = A [OK]

Hint: Middleware goes between path and handler in route [OK]

Common Mistakes:

• Calling middleware inside handler instead of passing it
• Using middleware after sending response
• Passing middleware as a function call instead of reference

3. Given this middleware and route code, what will be the response if a user with role 'user' tries to access '/admin'?

function adminMiddleware(req, res, next) {
  if (req.user.role === 'admin') next();
  else res.status(403).send('Access denied');
}
app.get('/admin', adminMiddleware, (req, res) => {
  res.send('Welcome Admin');
});

medium

A. 'Access denied' with status 403

B. 'Welcome Admin'

C. Server error due to missing next()

D. Empty response with status 200

Solution

1. Step 1: Analyze middleware condition

   The middleware checks if req.user.role is 'admin'. If not, it sends 403 with 'Access denied'.

2. Step 2: User role is 'user'

   Since role is 'user', the else branch runs, sending 403 and 'Access denied'.

3. Final Answer:

   'Access denied' with status 403 -> Option A

4. Quick Check:

   Non-admin blocked with 403 = A [OK]

Hint: Check role condition in middleware to predict response [OK]

Common Mistakes:

• Assuming next() always runs
• Ignoring status code sent by middleware
• Thinking response is 'Welcome Admin' for all roles

4. Identify the error in this Express route protection code:

function adminMiddleware(req, res, next) {
  if (req.user.role === 'admin') next();
  else res.send('Access denied');
}
app.get('/admin', adminMiddleware, (req, res) => {
  res.send('Admin area');
});

medium

A. Route handler should be before middleware

B. Middleware should not call next()

C. Missing status code when sending 'Access denied'

D. req.user.role check is incorrect syntax

Solution

1. Step 1: Check middleware response

   When denying access, middleware sends a message but does not set HTTP status code.

2. Step 2: Importance of status code

   Without status 403, client gets status 200 which is misleading for access denial.

3. Final Answer:

   Missing status code when sending 'Access denied' -> Option C

4. Quick Check:

   Send 403 on denial = C [OK]

Hint: Always send status code with error messages [OK]

Common Mistakes:

• Not setting status code on error
• Calling next() after sending response
• Placing middleware after route handler

5. You want to protect two routes: '/admin' for admins only and '/profile' for logged-in users. Which Express setup correctly applies middleware for this scenario?

function authMiddleware(req, res, next) {
  if (req.user) next();
  else res.status(401).send('Login required');
}
function adminMiddleware(req, res, next) {
  if (req.user?.role === 'admin') next();
  else res.status(403).send('Admin only');
}
// Which setup is correct?

hard

A. app.get('/admin', adminMiddleware, authMiddleware, (req, res) => res.send('Admin')); app.get('/profile', adminMiddleware, (req, res) => res.send('Profile'));

B. app.get('/admin', (req, res) => res.send('Admin')); app.get('/profile', authMiddleware, (req, res) => res.send('Profile'));

C. app.get('/admin', authMiddleware, (req, res) => res.send('Admin')); app.get('/profile', adminMiddleware, (req, res) => res.send('Profile'));

D. app.get('/admin', authMiddleware, adminMiddleware, (req, res) => res.send('Admin')); app.get('/profile', authMiddleware, (req, res) => res.send('Profile'));

Solution

1. Step 1: Understand middleware order

   For '/admin', user must be logged in (authMiddleware) and have admin role (adminMiddleware).

2. Step 2: Apply correct middleware per route

   '/profile' only needs authMiddleware to check login. app.get('/admin', authMiddleware, adminMiddleware, (req, res) => res.send('Admin')); app.get('/profile', authMiddleware, (req, res) => res.send('Profile')); applies both correctly in order.

3. Final Answer:

   app.get('/admin', authMiddleware, adminMiddleware, (req, res) => res.send('Admin')); app.get('/profile', authMiddleware, (req, res) => res.send('Profile')); -> Option D

4. Quick Check:

   Auth then admin for admin route = B [OK]

Hint: Check middleware order: auth before admin [OK]

Common Mistakes:

• Reversing middleware order
• Using adminMiddleware alone for profile
• Not protecting admin route with authMiddleware