Dev Time Run Time e18e.dev Blog

Run Time Stats

SSR Performance

Framework Ops/sec Median Latency Body Size Duplication
Baseline HTML 845 1.199ms 96.81kb 1x
Astro 559 1.761ms 99.86kb 1x
Mastro 514 1.917ms 181.95kb 1x
Next.js 233 4.521ms 199.11kb 2x
Nuxt 359 2.692ms 201.26kb 2x
React Router 64 0ms 211.14kb 2x
SolidStart 396 2.469ms 227.79kb 2x
SvelteKit 439 2.219ms 183.55kb 2x
TanStack Start 314 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 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 89.4ms 89.45ms 3.28ms
Next.js 347.8ms 347.72ms 16.49ms
Nuxt 90.2ms 90.11ms 13.03ms
React Router 118.4ms 118.51ms 16.28ms
SolidStart 91ms 91.15ms 16.37ms
SvelteKit 113.2ms 113.27ms 13.02ms
TanStack Start 669ms 669.07ms 122.22ms

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.02ms 0.42ms
Next.js 152.4ms 152.24ms 14.05ms
Nuxt 76.2ms 76.11ms 1.14ms
React Router 138.2ms 138.2ms 4.39ms
SolidStart 87.2ms 87ms 14.14ms
SvelteKit 80.4ms 80.33ms 2.67ms
TanStack Start 92.6ms 92.74ms 5.03ms

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.