Self-hosting with Node.js in NextJS - Performance & Optimization

Performance: Self-hosting with Node.js

MEDIUM IMPACT

This affects the server response time and initial page load speed by controlling how the Next.js app is served and assets are delivered.

Serving a Next.js app with Node.js for production

NextJS

import { createServer } from 'http';
import { parse } from 'url';
import next from 'next';

const app = next({ dev: false });
const handle = app.getRequestHandler();

app.prepare().then(() => {
  createServer((req, res) => {
    const parsedUrl = parse(req.url, true);
    handle(req, res, parsedUrl);
  }).listen(3000, () => {
    console.log('> Ready on http://localhost:3000');
  });
});

Running Next.js in production mode enables server-side optimizations and smaller bundles, improving response time and LCP.

📈 Performance GainReduces server response time by 30-50%; smaller JS bundles speed up initial paint.

Serving a Next.js app with Node.js for production

NextJS

const express = require('express');
const next = require('next');

const app = next({ dev: true });
const handle = app.getRequestHandler();

app.prepare().then(() => {
  const server = express();
  server.all('*', (req, res) => {
    return handle(req, res);
  });
  server.listen(3000, () => {
    console.log('> Ready on http://localhost:3000');
  });
});

Running Next.js in development mode disables optimizations and causes slower server response and larger bundles.

📉 Performance CostBlocks rendering for 200-500ms longer on initial load; larger JS bundles increase LCP.

Performance Comparison

Pattern	Server Response	Bundle Size	LCP Impact	Verdict
Dev mode self-hosting	Slow (200-500ms delay)	Large (unminified bundles)	High delay	[X] Bad
Prod mode self-hosting	Fast (50-100ms delay)	Small (minified bundles)	Low delay	[OK] Good

Rendering Pipeline

Self-hosting with Node.js affects the server response phase of the rendering pipeline, which impacts when the browser can start parsing and rendering content.

→Server Response

→Critical Rendering Path

→Resource Loading

⚠️ BottleneckServer Response time delays the start of browser rendering.

Core Web Vital Affected

LCP

This affects the server response time and initial page load speed by controlling how the Next.js app is served and assets are delivered.

Optimization Tips

1Always run Next.js in production mode for self-hosting to enable optimizations.

2Monitor server response time (TTFB) to ensure fast initial content delivery.

3Serve minified and cached assets to reduce bundle size and improve LCP.

Performance Quiz - 3 Questions

What is the main performance benefit of running Next.js in production mode when self-hosting with Node.js?

A Faster server response and smaller JS bundles

B More detailed error messages

C Automatic code splitting disabled

D Longer server startup time

DevTools: Network

How to check: Open DevTools, go to Network tab, reload the page, and check the Time to First Byte (TTFB) and size of JS bundles.

What to look for: Lower TTFB and smaller JS files indicate better self-hosting performance.