Dev Time Run Time e18e.dev Blog

Run Time Stats

SSR Performance

Measured on GitHub Actions (ubuntu-latest, Node 24) using custom SSR benchmark apps.

Framework Ops/sec Avg Latency Body Size Duplication
Baseline HTML 706 1.417ms 96.81kb 1x
Astro 366 2.735ms 99.86kb 1x
Mastro 223 4.485ms 181.95kb 1x
Next.js 129 7.74ms 198.59kb 2x
Nuxt 248 4.037ms 201.18kb 2x
React Router 64 15.528ms 211.14kb 2x
SolidStart 234 4.275ms 225.49kb 2x
SvelteKit 259 3.858ms 183.55kb 2x
TanStack Start 185 5.395ms 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)

Default

    • Measured on GitHub Actions (ubuntu-latest, Node 24) using Lighthouse flow with Chromium.

    Framework First Paint FCP INP
    Astro 36.8ms 36.8ms 98.72ms
    Next.js 48ms 48ms 75.48ms
    Nuxt 32.8ms 32.8ms 69.98ms
    React Router 35.2ms 35.2ms 59.78ms
    SolidStart 22.4ms 22.4ms 63.09ms
    SvelteKit 26.4ms 26.4ms 64.89ms
    TanStack Start 40.8ms 40.8ms 59.27ms

    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.