Dev Time Run Time e18e.dev Blog

Run Time Stats

SSR Request Throughput

Framework Ops/sec Median Latency Body Size Duplication
Baseline HTML 831 1.201ms 96.81kb 1x
Astro 563 1.771ms 99.86kb 1x
Mastro 516 1.911ms 181.95kb 1x
Next.js 230 4.581ms 199.07kb 2x
Nuxt 385 2.525ms 201.26kb 2x
React Router 64 0ms 211.14kb 2x
SolidStart 399 2.494ms 228.11kb 2x
SvelteKit 429 2.257ms 183.55kb 2x
TanStack Start 315 3.137ms 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 server-rendered React. To keep the comparison fair, Next.js uses "use client" to opt out of RSC and use traditional server rendering + hydration like most of the other frameworks
  • Inspired by eknkc/ssr-benchmark

Client Side Rendered Performance

First Paint (ms)

First Paint (ms) chart
Framework First Paint FCP INP
Astro 91.4ms 91.42ms 7.19ms
Next.js 348.6ms 348.73ms 21.13ms
Nuxt 90.8ms 90.96ms 11ms
React Router 121.6ms 121.6ms 19.24ms
SolidStart 97.6ms 97.4ms 13.37ms
SvelteKit 118ms 117.87ms 11.88ms
TanStack Start 146ms 145.73ms 23.59ms

Methodology

  • Each framework renders a table of 1000 rows with two UUID columns
  • Measured using Lighthouse flow with Chromium via Puppeteer for accurate browser metrics
  • First Paint and First Contentful Paint are measured on initial navigation
  • Interaction to Next Paint is measured by clicking the first row's detail link
  • Benchmarks run 5 times and results are averaged
  • Next.js, TanStack Start, and React Router default to SSR with no per-route opt-out. Next.js wraps the client-side rendered table in a dynamic import with ssr: false to prevent build-time prerendering. TanStack Start uses its built-in spa mode. React Router disables SSR entirely via ssr: false in its config. All other frameworks (Nuxt, SvelteKit, SolidStart, Astro) disable SSR per-route without a separate build.

Server Side Rendered Performance

First Paint (ms)

First Paint (ms) chart
Framework First Paint FCP INP
Astro 74.2ms 74.12ms 0.5ms
Next.js 132ms 131.83ms 18.42ms
Nuxt 96.2ms 96.16ms 10.05ms
React Router 155.6ms 155.61ms 15.48ms
SolidStart 98.2ms 98ms 17.68ms
SvelteKit 77.8ms 77.93ms 0.47ms
TanStack Start 112.6ms 112.71ms 28.69ms

Methodology

  • Each framework renders a table of 1000 rows with two UUID columns
  • Measured using Lighthouse flow with Chromium via Puppeteer for accurate browser metrics
  • First Paint and First Contentful Paint are measured on initial navigation
  • Interaction to Next Paint is measured by clicking the first row's detail link
  • Benchmarks run 5 times and results are averaged
  • The measured route is /server-side-rendered, and detail navigation uses /server-side-rendered/:id.