Dev Time Run Time e18e.dev Blog

Run Time Stats

SSR Performance

Framework Ops/sec Median Latency Body Size Duplication
Baseline HTML 827 1.196ms 96.81kb 1x
Astro 559 1.793ms 99.86kb 1x
Mastro 496 2.002ms 181.95kb 1x
Next.js 231 4.564ms 199.11kb 2x
Nuxt 390 2.497ms 201.26kb 2x
React Router 64 0ms 211.14kb 2x
SolidStart 397 2.488ms 227.79kb 2x
SvelteKit 434 2.241ms 183.55kb 2x
TanStack Start 316 3.129ms 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 88.8ms 88.9ms 5.64ms
Next.js 346.6ms 346.88ms 18.54ms
Nuxt 94.2ms 94.1ms 15.52ms
React Router 118ms 118.1ms 16.78ms
SolidStart 98ms 98ms 17.4ms
SvelteKit 108.6ms 108.77ms 13.14ms
TanStack Start 180ms 179.82ms 116.16ms

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 69.2ms 69.1ms 0.94ms
Next.js 137ms 136.98ms 12.06ms
Nuxt 74.8ms 74.8ms 0.7ms
React Router 155.8ms 155.93ms 3.96ms
SolidStart 77.8ms 77.92ms 19.82ms
SvelteKit 69.8ms 69.6ms 0.51ms
TanStack Start 83.4ms 83.29ms 2.95ms

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.