Dev Time Run Time e18e.dev Blog

Run Time Stats

SSR Performance

Framework Ops/sec Median Latency Body Size Duplication
Baseline HTML 849 1.201ms 96.81kb 1x
Astro 575 1.725ms 99.86kb 1x
Mastro 525 1.884ms 181.95kb 1x
Next.js 221 4.725ms 199.11kb 2x
Nuxt 388 2.505ms 201.26kb 2x
React Router 64 0ms 211.14kb 2x
SolidStart 403 2.468ms 227.77kb 2x
SvelteKit 441 2.199ms 183.55kb 2x
TanStack Start 317 3.123ms 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

SPA Performance

First Paint (ms)

First Paint (ms) chart
Framework First Paint FCP INP
Astro 95.6ms 95.46ms 11.03ms
Next.js 347ms 347.14ms 16.89ms
Nuxt 95.6ms 95.59ms 9.05ms
React Router 125ms 125.21ms 18.41ms
SolidStart 105.6ms 105.6ms 16.21ms
SvelteKit 107.4ms 107.7ms 14.19ms
TanStack Start 142.6ms 142.54ms 28.14ms

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 SPA 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.

MPA Performance

First Paint (ms)

First Paint (ms) chart
Framework First Paint FCP INP
Astro 79.4ms 79.21ms 3.59ms
Next.js 139.8ms 139.94ms 13.99ms
Nuxt 72.4ms 72.34ms 2.94ms
React Router 144ms 143.91ms 2.14ms
SolidStart 77.8ms 77.93ms 11.95ms
SvelteKit 81.6ms 81.81ms 0.82ms
TanStack Start 85.2ms 85.11ms 2.25ms

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 SPA 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.