Next.js
Dev Time Performance
Measured using pnpm on GitHub Actions (ubuntu-latest, Node 24) based on the starter project set up by each framework's CLI.
| Prod Deps | Dev Deps | Size | Size (Prod Only) | Graph |
|---|---|---|---|---|
| 3 | 6 | 560.03MB | 435.99MB | View |
| Metric | Avg | Min | Max |
|---|---|---|---|
| Install | 2.04s | 1.89s | 2.35s |
| Cold Build | 7.22s | 7.09s | 7.51s |
| Warm Build | 7.24s | 7.21s | 7.30s |
Build output size: 6.18MB
Runtime Performance
SSR Performance
Measured on GitHub Actions (ubuntu-latest, Node 24) using custom SSR benchmark apps.
| Framework | Ops/sec | Avg Latency | Body Size | Duplication |
|---|---|---|---|---|
| Baseline HTML | 706 | 1.417ms | 96.81kb | 1x |
| Next.js | 129 | 7.74ms | 198.59kb | 2x |
Methodology
- Each framework renders a table of 1000 rows with two UUID columns
- Mock HTTP requests bypass TCP overhead for accurate rendering measurement
- Data is loaded asynchronously to simulate real-world data fetching
- Duplication factor indicates how many times each UUID appears in the response (1x = optimal, 2x = includes hydration payload)
- Benchmarks run for 10 seconds using tinybench
-
Astro, Nuxt, and SvelteKit handle Node.js HTTP requests natively. React
Router, SolidStart, and TanStack Start use Web APIs internally, so
benchmarks include the cost of their Node.js adapter layers (
@react-router/node, h3, and srvx respectively) -
Next.js defaults to React Server Components (RSC), a different rendering
model than traditional SSR. To keep the comparison fair, Next.js uses
"use client"to opt out of RSC and use traditional SSR + hydration like most of the other frameworks - Inspired by eknkc/ssr-benchmark