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 741 1.368ms 96.81kb 1x
Astro 390 2.596ms 99.86kb 1x
Mastro 343 2.932ms 181.95kb 1x
Next.js 136 7.478ms 199.11kb 2x
Nuxt 247 4.138ms 201.26kb 2x
React Router 64 15.528ms 211.14kb 2x
SolidStart 259 4.108ms 227.79kb 2x
SvelteKit 287 3.58ms 183.55kb 2x
TanStack Start 199 5.083ms 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 145.2ms 145.23ms 14.42ms
    Next.js 383.8ms 384.05ms 19.38ms
    Nuxt 146.8ms 146.79ms 15.33ms
    React Router 182.4ms 182.56ms 19.68ms
    SolidStart 124.6ms 124.67ms 18.36ms
    SvelteKit 171ms 170.88ms 17.34ms
    TanStack Start 825.6ms 825.45ms 226.56ms

    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)

    Default

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

    Framework First Paint FCP INP
    Astro 112.4ms 112.55ms 1.29ms
    Next.js 185.6ms 185.58ms 0ms
    Nuxt 107.8ms 107.76ms 3.15ms
    React Router 207.6ms 207.46ms 2.99ms
    SolidStart 135.8ms 135.83ms 20.44ms
    SvelteKit 100ms 100.01ms 0.85ms
    TanStack Start 120.2ms 120.16ms 8.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.