Run Time Stats
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 |
| Astro | 366 | 2.735ms | 99.86kb | 1x |
| Mastro | 223 | 4.485ms | 181.95kb | 1x |
| Next.js | 129 | 7.74ms | 198.59kb | 2x |
| Nuxt | 248 | 4.037ms | 201.18kb | 2x |
| React Router | 64 | 15.528ms | 211.14kb | 2x |
| SolidStart | 234 | 4.275ms | 225.49kb | 2x |
| SvelteKit | 259 | 3.858ms | 183.55kb | 2x |
| TanStack Start | 185 | 5.395ms | 193.53kb | 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