Dev Time Run Time e18e.dev Blog

Run Time Stats

SSR Performance

Framework Ops/sec Median Latency Body Size Duplication
Baseline HTML 740 1.347ms 96.81kb 1x
Astro 582 1.719ms 99.86kb 1x
Mastro 504 1.942ms 181.95kb 1x
Next.js 227 4.612ms 199.11kb 2x
Nuxt 390 2.5ms 201.26kb 2x
React Router 64 0ms 211.14kb 2x
SolidStart 405 2.468ms 227.77kb 2x
SvelteKit 437 2.226ms 183.55kb 2x
TanStack Start 312 3.165ms 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 90.8ms 90.73ms 7.93ms
Next.js 353.6ms 353.44ms 19.85ms
Nuxt 95.2ms 95.02ms 14.78ms
React Router 119ms 118.93ms 14.27ms
SolidStart 94.8ms 94.61ms 16.97ms
SvelteKit 110ms 110.02ms 15.79ms
TanStack Start 145.8ms 145.78ms 26.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
  • 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 78.2ms 78.12ms 0.7ms
Next.js 125ms 124.96ms 13.24ms
Nuxt 98.4ms 98.35ms 11.32ms
React Router 136.6ms 136.58ms 2.07ms
SolidStart 85ms 84.84ms 19.77ms
SvelteKit 71.2ms 70.99ms 3.26ms
TanStack Start 89.4ms 89.61ms 4.86ms

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.