Dev Time Run Time e18e.dev Blog

Run Time Stats

SSR Performance

Framework Ops/sec Median Latency Body Size Duplication
Baseline HTML 849 1.198ms 96.81kb 1x
Astro 561 1.764ms 99.86kb 1x
Mastro 503 1.991ms 181.95kb 1x
Next.js 214 4.807ms 199.07kb 2x
Nuxt 388 2.509ms 201.26kb 2x
React Router 64 0ms 211.14kb 2x
SolidStart 399 2.558ms 227.77kb 2x
SvelteKit 432 2.247ms 183.55kb 2x
TanStack Start 310 3.169ms 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 93.2ms 93.15ms 5.86ms
Next.js 348ms 348.19ms 19.61ms
Nuxt 93.2ms 93.13ms 12.99ms
React Router 119.4ms 119.24ms 19.84ms
SolidStart 90.2ms 90.27ms 12.47ms
SvelteKit 102.6ms 102.49ms 12.22ms
TanStack Start 148.6ms 148.5ms 25.8ms

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 68ms 67.95ms 0.44ms
Next.js 128.6ms 128.87ms 14.48ms
Nuxt 77.8ms 77.75ms 2.89ms
React Router 143.8ms 143.91ms 3.98ms
SolidStart 80ms 80.06ms 16.25ms
SvelteKit 71.8ms 71.87ms 0.5ms
TanStack Start 86.4ms 86.26ms 6.76ms

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.