All Frameworks
Dev Time
Section titled “Dev Time”Dev Time benchmarks use each meta-framework’s starter-* package.
Each starter follows its framework’s CLI or documented setup, with the selected options and adjustments recorded in the methodology.
See Default Benchmark Setup for the shared benchmark environment.
Dependency Counts
Section titled “Dependency Counts”Methodology: Dependency Counts.
Measuring a meta-framework’s dependencies isn’t as straightforward as you might think. You could:
- Measure just the meta-framework package itself
- Maybe a full project setup
Both approaches have flaws. Some meta-frameworks need many other packages to work. A full project setup can include more packages than necessary.
To provide a clearer picture, we run the dependency-count tests three times, starting small and expanding in scope. In this order, we:
- Start with the meta-framework package itself, for example,
@sveltejs/kit - We then expand this to the meta-framework and its first-party packages. Looking at
@sveltejs/kitagain, this means any package maintained by the meta-framework authors that’s needed to run a project, for example, thesveltepackage. - Finally, we count the dependencies for the entire
starter-*project. Their CLI or documentation recommends this setup by default, so this is the default most people will start with.
Core Package Dependencies
Section titled “Core Package Dependencies”The meta-framework package itself, for example, @sveltejs/kit.
| Framework | Deps | Dev | Prod | Graph |
|---|---|---|---|---|
| Astro | 77 | 25 | 52 | View |
| Next.js | 6 | 0 | 6 | View |
| Nuxt | 79 | 13 | 66 | View |
| Pracht | 5 | 2 | 3 | View |
| React Router | 47 | 24 | 23 | View |
| SolidStart | 29 | 4 | 25 | View |
| SvelteKit | 23 | 15 | 8 | View |
| TanStack Start | 23 | 14 | 9 | View |
| Framework | Dependency count |
|---|---|
| Pracht | 5 |
| Next.js | 6 |
| SvelteKit | 23 |
| TanStack Start | 23 |
| SolidStart | 29 |
| React Router | 47 |
| Astro | 77 |
| Nuxt | 79 |
The chart includes a dotted median reference line calculated from the visible framework values.
| Framework | Dependency count |
|---|---|
| Next.js | 0 |
| Pracht | 2 |
| SolidStart | 4 |
| Nuxt | 13 |
| TanStack Start | 14 |
| SvelteKit | 15 |
| React Router | 24 |
| Astro | 25 |
The chart includes a dotted median reference line calculated from the visible framework values.
| Framework | Dependency count |
|---|---|
| Pracht | 3 |
| Next.js | 6 |
| SvelteKit | 8 |
| TanStack Start | 9 |
| React Router | 23 |
| SolidStart | 25 |
| Astro | 52 |
| Nuxt | 66 |
The chart includes a dotted median reference line calculated from the visible framework values.
First-Party Package Dependencies
Section titled “First-Party Package Dependencies”Looking at a meta-framework’s first-party packages. For @sveltejs/kit, this means packages maintained by the meta-framework authors that are needed to run a project, for example, svelte.
| Framework | Deps Dev / Prod | All Deps | Dup. Deps | Graph |
|---|---|---|---|---|
| Astro | 1 / 1 | 335 | 16 | View |
| Next.js | 1 / 1 | 388 | 12 | View |
| Nuxt | 0 / 1 | 611 | 55 | View |
| Pracht | 2 / 2 | 218 | 4 | View |
| React Router | 1 / 3 | 223 | 5 | View |
| SolidStart | 0 / 4 | 210 | 4 | View |
| SvelteKit | 5 / 0 | 108 | 1 | View |
| TanStack Start | 1 / 7 | 195 | 3 | View |
| Framework | Dependency count |
|---|---|
| SvelteKit | 108 |
| TanStack Start | 195 |
| SolidStart | 210 |
| Pracht | 218 |
| React Router | 223 |
| Astro | 335 |
| Next.js | 388 |
| Nuxt | 611 |
The chart includes a dotted median reference line calculated from the visible framework values.
| Framework | Dependency count |
|---|---|
| Nuxt | 0 |
| SolidStart | 0 |
| Astro | 1 |
| Next.js | 1 |
| React Router | 1 |
| TanStack Start | 1 |
| Pracht | 2 |
| SvelteKit | 5 |
The chart includes a dotted median reference line calculated from the visible framework values.
| Framework | Dependency count |
|---|---|
| SvelteKit | 0 |
| Astro | 1 |
| Next.js | 1 |
| Nuxt | 1 |
| Pracht | 2 |
| React Router | 3 |
| SolidStart | 4 |
| TanStack Start | 7 |
The chart includes a dotted median reference line calculated from the visible framework values.
| Framework | Dependency count |
|---|---|
| SvelteKit | 1 |
| TanStack Start | 3 |
| Pracht | 4 |
| SolidStart | 4 |
| React Router | 5 |
| Next.js | 12 |
| Astro | 16 |
| Nuxt | 55 |
The chart includes a dotted median reference line calculated from the visible framework values.
Starter Project Dependencies
Section titled “Starter Project Dependencies”Finally, we look at the complete dependency footprint of the default starter project, including third-party packages selected by its CLI or documented setup.
| Framework | Deps Dev / Prod | All Deps | Dup. Deps | node_modules | Dep Install Size | Graph |
|---|---|---|---|---|---|---|
| Astro | 2 / 1 | 335 | 16 | 204.43MB | 172.24MB | View |
| Next.js | 6 / 3 | 424 | 12 | 463.61MB | 405.32MB | View |
| Nuxt | 3 / 3 | 611 | 55 | 222.79MB | 190.59MB | View |
| Pracht | 6 / 2 | 239 | 4 | 132.56MB | 109.29MB | View |
| React Router | 9 / 6 | 250 | 6 | 108.68MB | 102.51MB | View |
| SolidStart | 1 / 6 | 242 | 5 | 128.50MB | 104.51MB | View |
| SvelteKit | 8 / 0 | 108 | 1 | 88.32MB | 92.09MB | View |
| TanStack Start | 12 / 14 | 331 | 37 | 272.60MB | 228.67MB | View |
| Framework | Dependencies |
|---|---|
| SolidStart | 1 |
| Astro | 2 |
| Nuxt | 3 |
| Next.js | 6 |
| Pracht | 6 |
| SvelteKit | 8 |
| React Router | 9 |
| TanStack Start | 12 |
The chart includes a dotted median reference line calculated from the visible framework values.
| Framework | Dependencies |
|---|---|
| SvelteKit | 0 |
| Astro | 1 |
| Pracht | 2 |
| Next.js | 3 |
| Nuxt | 3 |
| React Router | 6 |
| SolidStart | 6 |
| TanStack Start | 14 |
The chart includes a dotted median reference line calculated from the visible framework values.
| Framework | Duplicates |
|---|---|
| SvelteKit | 1 |
| Pracht | 4 |
| SolidStart | 5 |
| React Router | 6 |
| Next.js | 12 |
| Astro | 16 |
| TanStack Start | 37 |
| Nuxt | 55 |
The chart includes a dotted median reference line calculated from the visible framework values.
Node Modules Size
Section titled “Node Modules Size”Methodology: Node Modules Size.
| Framework | MB |
|---|---|
| SvelteKit | 88.32 MB |
| React Router | 108.68 MB |
| SolidStart | 128.50 MB |
| Pracht | 132.56 MB |
| Astro | 204.43 MB |
| Nuxt | 222.79 MB |
| TanStack Start | 272.60 MB |
| Next.js | 463.61 MB |
The chart includes a dotted median reference line calculated from the visible framework values.
Build and Install Times
Section titled “Build and Install Times”Methodology: Build and Install Times.
| Framework | Median Install | Min Install | Max Install | Median Cold Build | Median Warm Build |
|---|---|---|---|---|---|
| Astro | 4.71s | 1.88s | 5.27s | 0.98s | 0.93s |
| Next.js | 6.66s | 3.00s | 6.70s | 6.77s | 2.56s |
| Nuxt | 4.83s | 2.79s | 5.48s | 3.97s | 3.75s |
| Pracht | 2.29s | 1.53s | 2.87s | 0.71s | 0.72s |
| React Router | 1.46s | 1.22s | 1.70s | 1.69s | 1.72s |
| SolidStart | 1.74s | 1.48s | 2.22s | 2.93s | 2.91s |
| SvelteKit | 1.48s | 1.35s | 1.56s | 1.90s | 1.77s |
| TanStack Start | 5.80s | 2.22s | 5.85s | 2.34s | 2.10s |
| Framework | Seconds |
|---|---|
| React Router | 1.46s |
| SvelteKit | 1.48s |
| SolidStart | 1.74s |
| Pracht | 2.29s |
| Astro | 4.71s |
| Nuxt | 4.83s |
| TanStack Start | 5.80s |
| Next.js | 6.66s |
The chart includes a dotted median reference line calculated from the visible framework values.
| Framework | Seconds |
|---|---|
| Pracht | 0.71s |
| Astro | 0.98s |
| React Router | 1.69s |
| SvelteKit | 1.90s |
| TanStack Start | 2.34s |
| SolidStart | 2.93s |
| Nuxt | 3.97s |
| Next.js | 6.77s |
The chart includes a dotted median reference line calculated from the visible framework values.
| Framework | Seconds |
|---|---|
| Pracht | 0.72s |
| Astro | 0.93s |
| React Router | 1.72s |
| SvelteKit | 1.77s |
| TanStack Start | 2.10s |
| Next.js | 2.56s |
| SolidStart | 2.91s |
| Nuxt | 3.75s |
The chart includes a dotted median reference line calculated from the visible framework values.
Dev Server Startup
Section titled “Dev Server Startup”Methodology: Dev Server Startup.
| Framework | Median Start | Min Start | Max Start |
|---|---|---|---|
| Astro | 1.41s | 1.38s | 1.43s |
| Next.js | 2.23s | 2.21s | 2.83s |
| Nuxt | 2.53s | 2.43s | 2.85s |
| Pracht | 0.86s | 0.83s | 1.11s |
| React Router | 0.96s | 0.94s | 1.01s |
| SolidStart | 2.55s | 2.52s | 2.72s |
| SvelteKit | 1.28s | 1.24s | 1.36s |
| TanStack Start | 2.14s | 2.07s | 2.19s |
| Framework | Seconds |
|---|---|
| Pracht | 0.86s |
| React Router | 0.96s |
| SvelteKit | 1.28s |
| Astro | 1.41s |
| TanStack Start | 2.14s |
| Next.js | 2.23s |
| Nuxt | 2.53s |
| SolidStart | 2.55s |
The chart includes a dotted median reference line calculated from the visible framework values.
Core-JS Polyfills
Section titled “Core-JS Polyfills”Methodology: Core-JS Polyfills.
| Framework | Core-JS detected | Matching JS files | Modules not needed by target browsers |
|---|---|---|---|
| Astro | No | — | — |
| Next.js | Yes | 110.0 KB | 302 |
| Nuxt | No | — | — |
| Pracht | No | — | — |
| React Router | No | — | — |
| SolidStart | No | — | — |
| SvelteKit | No | — | — |
| TanStack Start | No | — | — |
Browser Baseline
Section titled “Browser Baseline”Methodology: Browser Baseline.
| Framework | Baseline | Feature | Year | Features |
|---|---|---|---|---|
| Astro | — | — | — | 0 |
| Next.js | High | — | 2022 | 47 |
| Nuxt | High | — | 2023 | 42 |
| Pracht | High | — | 2020 | 37 |
| React Router | High | — | 2022 | 44 |
| SolidStart | High | — | 2020 | 33 |
| SvelteKit | Limited | temporal | — | 48 |
| TanStack Start | Limited | temporal | — | 49 |
Minimum Node Version
Section titled “Minimum Node Version”Methodology: Minimum Node Version.
| Framework | Min Node | Set by |
|---|---|---|
| Astro | v22.22.0 | @astrojs/prism, @astrojs/telemetry, astro |
| Next.js | v20.19.0 | eslint-visitor-keys |
| Nuxt | v22.22.3 | @nuxt/nitro-server, @nuxt/vite-builder, @nuxt/vite-server, cssnano, nuxt, postcss-calc |
| Pracht | v22.18.0 | @pracht/adapter-node, @pracht/capabilities, @pracht/cli, @pracht/core, @pracht/preact-ssr-precompile, @pracht/vite-plugin |
| React Router | v22.22.0 | @react-router/dev, @react-router/express, @react-router/node, @react-router/serve, react-router |
| SolidStart | v24.0.0 | @solidjs/start, starter-solid-start |
| SvelteKit | v22.17.0 | @sveltejs/kit |
| TanStack Start | v22.22.2 | @asamuzakjp/css-color, @asamuzakjp/dom-selector, jsdom, w3c-xmlserializer |
Run Time
Section titled “Run Time”Runtime apps implement comparable benchmark routes across frameworks. See Default Benchmark Setup for the shared environment and each framework’s build tool and adapter. Test-specific differences are documented in the linked methodology sections below.
Client Side Rendered Tests
Section titled “Client Side Rendered Tests”Methodology: Client Side Rendered Tests.
Some frameworks have been moved off their golden path to make client side tests fair when comparing. See the methodology link above for the full details.
| Framework | First Paint | FCP | Interaction Latency | Input Delay | Processing Duration | Presentation Delay |
|---|---|---|---|---|---|---|
| Astro | 98ms | 98.495ms | 2.537ms | 2.206ms | 0.327ms | 0ms |
| Next.js | 339ms | 338.596ms | 16ms | 1.445ms | 3.607ms | 10.479ms |
| Nuxt | 168ms | 168.478ms | 8.579ms | 0.875ms | 1.246ms | 6.586ms |
| Pracht | 110ms | 110.133ms | 22.221ms | 0.978ms | 3.031ms | 17.108ms |
| React Router | 173ms | 173.334ms | 15.74ms | 1.674ms | 2.832ms | 11.06ms |
| SolidStart | 95ms | 94.815ms | 20.802ms | 0.915ms | 2.309ms | 15.992ms |
| SvelteKit | 113ms | 112.645ms | 19.886ms | 0.778ms | 2.167ms | 14.31ms |
| TanStack Start | 110ms | 110.45ms | 19.301ms | 1.205ms | 2.95ms | 14.845ms |
| Framework | Milliseconds |
|---|---|
| SolidStart | 95.00 ms |
| Astro | 98.00 ms |
| Pracht | 110.00 ms |
| TanStack Start | 110.00 ms |
| SvelteKit | 113.00 ms |
| Nuxt | 168.00 ms |
| React Router | 173.00 ms |
| Next.js | 339.00 ms |
The chart includes a dotted median reference line calculated from the visible framework values.
| Framework | Milliseconds |
|---|---|
| SolidStart | 94.81 ms |
| Astro | 98.50 ms |
| Pracht | 110.13 ms |
| TanStack Start | 110.45 ms |
| SvelteKit | 112.64 ms |
| Nuxt | 168.48 ms |
| React Router | 173.33 ms |
| Next.js | 338.60 ms |
The chart includes a dotted median reference line calculated from the visible framework values.
Interaction Breakdown
Total latency is split into the three consecutive phases reported by Lighthouse.
- The input delay, which starts when the user initiates an interaction with the page, and ends when the event callbacks for the interaction begin to run.
- The processing duration, which consists of the time it takes for event callbacks to run to completion.
- The presentation delay, which is the time it takes for the browser to present the next frame which contains the visual result of the interaction.
| Framework or version | Interaction latency | Input delay | Processing duration | Presentation delay |
|---|---|---|---|---|
| Astro | 2.54 ms | 2.21 ms | 0.33 ms | 0.00 ms |
| Nuxt | 8.58 ms | 0.88 ms | 1.25 ms | 6.59 ms |
| React Router | 15.74 ms | 1.67 ms | 2.83 ms | 11.06 ms |
| Next.js | 16.00 ms | 1.45 ms | 3.61 ms | 10.48 ms |
| TanStack Start | 19.30 ms | 1.21 ms | 2.95 ms | 14.85 ms |
| SvelteKit | 19.89 ms | 0.78 ms | 2.17 ms | 14.31 ms |
| SolidStart | 20.80 ms | 0.92 ms | 2.31 ms | 15.99 ms |
| Pracht | 22.22 ms | 0.98 ms | 3.03 ms | 17.11 ms |
Server Side Rendered Tests
Section titled “Server Side Rendered Tests”Methodology: Server Side Rendered Tests.
| Framework | First Paint | FCP | Interaction Latency | Input Delay | Processing Duration | Presentation Delay |
|---|---|---|---|---|---|---|
| Astro | 61ms | 61.141ms | 1.719ms | 0.69ms | 0.932ms | 0ms |
| Next.js | 385ms | 384.775ms | 19.694ms | 1.659ms | 9.697ms | 8.507ms |
| Nuxt | 92ms | 91.923ms | 13.931ms | 0.91ms | 1.286ms | 11.807ms |
| Pracht | 90ms | 89.555ms | 16.674ms | 0.913ms | 2.148ms | 12.885ms |
| React Router | 89ms | 88.589ms | 21.311ms | 1.634ms | 2.826ms | 15.336ms |
| SolidStart | 91ms | 91.085ms | 13.247ms | 0.833ms | 2.859ms | 9.645ms |
| SvelteKit | 79ms | 79.355ms | 17.914ms | 0.872ms | 2.187ms | 14.705ms |
| TanStack Start | 87ms | 86.615ms | 20.495ms | 1.425ms | 3.672ms | 15.64ms |
| Framework | Milliseconds |
|---|---|
| Astro | 61.00 ms |
| SvelteKit | 79.00 ms |
| TanStack Start | 87.00 ms |
| React Router | 89.00 ms |
| Pracht | 90.00 ms |
| SolidStart | 91.00 ms |
| Nuxt | 92.00 ms |
| Next.js | 385.00 ms |
The chart includes a dotted median reference line calculated from the visible framework values.
| Framework | Milliseconds |
|---|---|
| Astro | 61.14 ms |
| SvelteKit | 79.36 ms |
| TanStack Start | 86.61 ms |
| React Router | 88.59 ms |
| Pracht | 89.56 ms |
| SolidStart | 91.08 ms |
| Nuxt | 91.92 ms |
| Next.js | 384.77 ms |
The chart includes a dotted median reference line calculated from the visible framework values.
Interaction Breakdown
Total latency is split into the three consecutive phases reported by Lighthouse.
- The input delay, which starts when the user initiates an interaction with the page, and ends when the event callbacks for the interaction begin to run.
- The processing duration, which consists of the time it takes for event callbacks to run to completion.
- The presentation delay, which is the time it takes for the browser to present the next frame which contains the visual result of the interaction.
| Framework or version | Interaction latency | Input delay | Processing duration | Presentation delay |
|---|---|---|---|---|
| Astro | 1.72 ms | 0.69 ms | 0.93 ms | 0.00 ms |
| SolidStart | 13.25 ms | 0.83 ms | 2.86 ms | 9.64 ms |
| Nuxt | 13.93 ms | 0.91 ms | 1.29 ms | 11.81 ms |
| Pracht | 16.67 ms | 0.91 ms | 2.15 ms | 12.88 ms |
| SvelteKit | 17.91 ms | 0.87 ms | 2.19 ms | 14.71 ms |
| Next.js | 19.69 ms | 1.66 ms | 9.70 ms | 8.51 ms |
| TanStack Start | 20.50 ms | 1.43 ms | 3.67 ms | 15.64 ms |
| React Router | 21.31 ms | 1.63 ms | 2.83 ms | 15.34 ms |
Server Side Throughput Tests
Section titled “Server Side Throughput Tests”Methodology: Server Side Throughput Tests.
| Framework | Ops/sec | Median Latency | Body Size | Duplication |
|---|---|---|---|---|
| Baseline HTML | 821 | 1.237ms | 96.83kb | 1x |
| Astro | 752 | 1.395ms | 96.89kb | 1x |
| Next.js | 128 | 8.068ms | 204.56kb | 2x |
| Nuxt | 396 | 2.63ms | 201.73kb | 2x |
| Pracht | 588 | 1.788ms | 187.02kb | 2x |
| React Router | 334 | 3.054ms | 216.98kb | 2x |
| SolidStart | 384 | 2.668ms | 224.26kb | 2x |
| SvelteKit | 426 | 2.401ms | 184.29kb | 2x |
| TanStack Start | 378 | 2.668ms | 192.53kb | 2x |
| Framework | Operations per second |
|---|---|
| Baseline HTML | 821 |
| Astro | 752 |
| Pracht | 588 |
| SvelteKit | 426 |
| Nuxt | 396 |
| SolidStart | 384 |
| TanStack Start | 378 |
| React Router | 334 |
| Next.js | 128 |
The chart includes a dotted median reference line calculated from the visible framework values.
| Framework | Kilobytes |
|---|---|
| Baseline HTML | 96.83 KB |
| Astro | 96.89 KB |
| SvelteKit | 184.29 KB |
| Pracht | 187.02 KB |
| TanStack Start | 192.53 KB |
| Nuxt | 201.73 KB |
| Next.js | 204.56 KB |
| React Router | 216.98 KB |
| SolidStart | 224.26 KB |
The chart includes a dotted median reference line calculated from the visible framework values.
Median of measured run average latencies; not a pooled request-level median.
| Framework | Milliseconds |
|---|---|
| Baseline HTML | 1.24 ms |
| Astro | 1.39 ms |
| Pracht | 1.79 ms |
| SvelteKit | 2.40 ms |
| Nuxt | 2.63 ms |
| TanStack Start | 2.67 ms |
| SolidStart | 2.67 ms |
| React Router | 3.05 ms |
| Next.js | 8.07 ms |
The chart includes a dotted median reference line calculated from the visible framework values.
SSR Load Test
Section titled “SSR Load Test”Methodology: SSR Load Test.
Each runtime app renders the same 1,000-row, three-column table using ordinary
<a> links. This compares server rendering under HTTP load without the extra work
of rendering framework router link components. Requests still pass through each
framework’s server routing. No browser runs and no links are clicked.
| Framework | Representative peak req/s | Representative peak connections | Median sweep P99 @ 25 | Median sweep P99 @ 50 | Median sweep P99 @ 100 | Total measured requests |
|---|---|---|---|---|---|---|
| Baseline HTML | 1,792.8 | 200 | 17ms | 36ms | 96ms | 157,048 |
| Astro | 1,597.4 | 50 | 23ms | 49ms | 92ms | 140,154 |
| Next.js | 54 | 5 | 1,190ms | 4,154ms | 4,551ms | 4,871 |
| Nuxt | 544.8 | 10 | 71ms | 306ms | 2,619ms | 52,710 |
| Pracht | 704.2 | 25 | 40ms | 109ms | 919ms | 66,871 |
| React Router | 356.2 | 25 | 97ms | 509ms | 3,382ms | 34,469 |
| SolidStart | 575.4 | 50 | 89ms | 273ms | 2,057ms | 55,293 |
| SvelteKit | 561.21 | 100 | 84ms | 289ms | 2,012ms | 54,311 |
| TanStack Start | 404 | 200 | 110ms | 828ms | 2,439ms | 39,448 |
P99 Latency
Section titled “P99 Latency”| Framework | Milliseconds |
|---|---|
| Baseline HTML | 17.00 ms |
| Astro | 23.00 ms |
| Pracht | 40.00 ms |
| Nuxt | 71.00 ms |
| SvelteKit | 84.00 ms |
| SolidStart | 89.00 ms |
| React Router | 97.00 ms |
| TanStack Start | 110.00 ms |
| Next.js | 1190.00 ms |
The chart includes a dotted median reference line calculated from the visible framework values.
| Framework | Milliseconds |
|---|---|
| Baseline HTML | 36.00 ms |
| Astro | 49.00 ms |
| Pracht | 109.00 ms |
| SolidStart | 273.00 ms |
| SvelteKit | 289.00 ms |
| Nuxt | 306.00 ms |
| React Router | 509.00 ms |
| TanStack Start | 828.00 ms |
| Next.js | 4154.00 ms |
The chart includes a dotted median reference line calculated from the visible framework values.
| Framework | Milliseconds |
|---|---|
| Astro | 92.00 ms |
| Baseline HTML | 96.00 ms |
| Pracht | 919.00 ms |
| SvelteKit | 2012.00 ms |
| SolidStart | 2057.00 ms |
| TanStack Start | 2439.00 ms |
| Nuxt | 2619.00 ms |
| React Router | 3382.00 ms |
| Next.js | 4551.00 ms |
The chart includes a dotted median reference line calculated from the visible framework values.
P90 Latency
Section titled “P90 Latency”| Framework | Milliseconds |
|---|---|
| Baseline HTML | 16.00 ms |
| Astro | 17.00 ms |
| Pracht | 36.00 ms |
| Nuxt | 46.00 ms |
| SvelteKit | 56.00 ms |
| SolidStart | 63.00 ms |
| React Router | 71.00 ms |
| TanStack Start | 83.00 ms |
| Next.js | 514.00 ms |
The chart includes a dotted median reference line calculated from the visible framework values.
| Framework | Milliseconds |
|---|---|
| Baseline HTML | 30.00 ms |
| Astro | 32.00 ms |
| Pracht | 71.00 ms |
| Nuxt | 100.00 ms |
| SvelteKit | 122.00 ms |
| SolidStart | 138.00 ms |
| React Router | 144.00 ms |
| TanStack Start | 174.00 ms |
| Next.js | 1766.00 ms |
The chart includes a dotted median reference line calculated from the visible framework values.
| Framework | Milliseconds |
|---|---|
| Astro | 63.00 ms |
| Baseline HTML | 69.00 ms |
| Pracht | 142.00 ms |
| SolidStart | 143.00 ms |
| Nuxt | 186.00 ms |
| SvelteKit | 191.00 ms |
| TanStack Start | 236.00 ms |
| React Router | 283.00 ms |
| Next.js | 2163.00 ms |
The chart includes a dotted median reference line calculated from the visible framework values.
P75 Latency
Section titled “P75 Latency”| Framework | Milliseconds |
|---|---|
| Baseline HTML | 15.00 ms |
| Astro | 16.00 ms |
| Pracht | 35.00 ms |
| Nuxt | 46.00 ms |
| SvelteKit | 46.00 ms |
| SolidStart | 53.00 ms |
| React Router | 70.00 ms |
| TanStack Start | 70.00 ms |
| Next.js | 490.00 ms |
The chart includes a dotted median reference line calculated from the visible framework values.
| Framework | Milliseconds |
|---|---|
| Baseline HTML | 29.00 ms |
| Astro | 31.00 ms |
| Pracht | 70.00 ms |
| Nuxt | 89.00 ms |
| SolidStart | 93.00 ms |
| SvelteKit | 97.00 ms |
| TanStack Start | 138.00 ms |
| React Router | 142.00 ms |
| Next.js | 964.00 ms |
The chart includes a dotted median reference line calculated from the visible framework values.
| Framework | Milliseconds |
|---|---|
| Baseline HTML | 57.00 ms |
| Astro | 61.00 ms |
| SolidStart | 121.00 ms |
| Pracht | 140.00 ms |
| SvelteKit | 147.00 ms |
| Nuxt | 165.00 ms |
| TanStack Start | 167.00 ms |
| React Router | 258.00 ms |
| Next.js | 980.00 ms |
The chart includes a dotted median reference line calculated from the visible framework values.
SSR Router Link Load Test
Section titled “SSR Router Link Load Test”Methodology: SSR Router Link Load Test.
The same load test using framework router link components, showing how rendering those components affects server performance compared with ordinary HTML links.
| Framework | Representative peak req/s | Representative peak connections | Median sweep P99 @ 25 | Median sweep P99 @ 50 | Median sweep P99 @ 100 | Total measured requests |
|---|---|---|---|---|---|---|
| Next.js | 49.6 | 5 | 1,320ms | 4,541ms | 4,735ms | 4,468 |
| Nuxt | 178.6 | 10 | 476ms | 2,719ms | 3,640ms | 17,466 |
| Pracht | 334.6 | 25 | 91ms | 545ms | 3,230ms | 33,878 |
| React Router | 167.8 | 25 | 325ms | 1,762ms | 3,893ms | 16,830 |
| TanStack Start | 261.4 | 5 | 199ms | 1,460ms | 3,025ms | 25,679 |
P99 Latency
Section titled “P99 Latency”| Framework | Milliseconds |
|---|---|
| Pracht | 91.00 ms |
| TanStack Start | 199.00 ms |
| React Router | 325.00 ms |
| Nuxt | 476.00 ms |
| Next.js | 1320.00 ms |
The chart includes a dotted median reference line calculated from the visible framework values.
| Framework | Milliseconds |
|---|---|
| Pracht | 545.00 ms |
| TanStack Start | 1460.00 ms |
| React Router | 1762.00 ms |
| Nuxt | 2719.00 ms |
| Next.js | 4541.00 ms |
The chart includes a dotted median reference line calculated from the visible framework values.
| Framework | Milliseconds |
|---|---|
| TanStack Start | 3025.00 ms |
| Pracht | 3230.00 ms |
| Nuxt | 3640.00 ms |
| React Router | 3893.00 ms |
| Next.js | 4735.00 ms |
The chart includes a dotted median reference line calculated from the visible framework values.
P90 Latency
Section titled “P90 Latency”| Framework | Milliseconds |
|---|---|
| Pracht | 82.00 ms |
| TanStack Start | 123.00 ms |
| Nuxt | 141.00 ms |
| React Router | 154.00 ms |
| Next.js | 544.00 ms |
The chart includes a dotted median reference line calculated from the visible framework values.
| Framework | Milliseconds |
|---|---|
| Pracht | 159.00 ms |
| TanStack Start | 259.00 ms |
| React Router | 299.00 ms |
| Nuxt | 301.00 ms |
| Next.js | 2038.00 ms |
The chart includes a dotted median reference line calculated from the visible framework values.
| Framework | Milliseconds |
|---|---|
| Pracht | 285.00 ms |
| TanStack Start | 310.00 ms |
| Nuxt | 325.00 ms |
| React Router | 406.00 ms |
| Next.js | 2486.00 ms |
The chart includes a dotted median reference line calculated from the visible framework values.
P75 Latency
Section titled “P75 Latency”| Framework | Milliseconds |
|---|---|
| Pracht | 77.00 ms |
| TanStack Start | 101.00 ms |
| Nuxt | 139.00 ms |
| React Router | 147.00 ms |
| Next.js | 530.00 ms |
The chart includes a dotted median reference line calculated from the visible framework values.
| Framework | Milliseconds |
|---|---|
| Pracht | 153.00 ms |
| TanStack Start | 210.00 ms |
| Nuxt | 292.00 ms |
| React Router | 292.00 ms |
| Next.js | 1052.00 ms |
The chart includes a dotted median reference line calculated from the visible framework values.
| Framework | Milliseconds |
|---|---|
| TanStack Start | 211.00 ms |
| Pracht | 261.00 ms |
| Nuxt | 300.00 ms |
| React Router | 379.00 ms |
| Next.js | 1053.00 ms |
The chart includes a dotted median reference line calculated from the visible framework values.
Core Web Vitals
Section titled “Core Web Vitals”Methodology: Core Web Vitals.
CWV Desktop
Section titled “CWV Desktop”| Framework | LCP% | CLS% | FCP% | TTFB% | INP% |
|---|---|---|---|---|---|
| Astro | 93 | 89 | 92 | 81 | 98 |
| SolidStart | 100 | 77 | 100 | 85 | 100 |
| SvelteKit | 79 | 78 | 77 | 68 | 95 |
| Next.js | 74 | 72 | 76 | 66 | 94 |
| TanStack Start | 55 | 81 | 46 | 29 | 91 |
| Nuxt | 68 | 58 | 69 | 59 | 96 |
| React Router | 59 | 61 | 65 | 68 | 90 |
Measures how fast a page's main content loads. To provide a good user experience, the LCP should be 2.5 seconds or less.
| Framework | % |
|---|---|
| SolidStart | 100 |
| Astro | 93 |
| SvelteKit | 79 |
| Next.js | 74 |
| Nuxt | 68 |
| React Router | 59 |
| TanStack Start | 55 |
The chart includes a dotted median reference line calculated from the visible framework values.
Measures how much and how far content unexpectedly moves on a page. To provide a good user experience, sites should maintain a CLS score of 0.1 or less for at least 75% of page visits.
| Framework | % |
|---|---|
| Astro | 89 |
| TanStack Start | 81 |
| SvelteKit | 78 |
| SolidStart | 77 |
| Next.js | 72 |
| React Router | 61 |
| Nuxt | 58 |
The chart includes a dotted median reference line calculated from the visible framework values.
Measures initial loading speed. To provide a good user experience, the FCP should be 1.8 seconds or less.
| Framework | % |
|---|---|
| SolidStart | 100 |
| Astro | 92 |
| SvelteKit | 77 |
| Next.js | 76 |
| Nuxt | 69 |
| React Router | 65 |
| TanStack Start | 46 |
The chart includes a dotted median reference line calculated from the visible framework values.
Measures the time between the request for a resource and when the first byte of a response begins to arrive. A good TTFB is less than or equal to 800ms.
| Framework | % |
|---|---|
| SolidStart | 85 |
| Astro | 81 |
| React Router | 68 |
| SvelteKit | 68 |
| Next.js | 66 |
| Nuxt | 59 |
| TanStack Start | 29 |
The chart includes a dotted median reference line calculated from the visible framework values.
Measures overall page responsiveness to user actions. To provide a good user experience, the INP should be 200ms or less.
| Framework | % |
|---|---|
| SolidStart | 100 |
| Astro | 98 |
| Nuxt | 96 |
| SvelteKit | 95 |
| Next.js | 94 |
| TanStack Start | 91 |
| React Router | 90 |
The chart includes a dotted median reference line calculated from the visible framework values.
CWV Mobile
Section titled “CWV Mobile”| Framework | LCP% | CLS% | FCP% | TTFB% | INP% |
|---|---|---|---|---|---|
| Astro | 80 | 93 | 73 | 64 | 85 |
| SolidStart | 88 | 66 | 88 | 85 | 75 |
| SvelteKit | 67 | 81 | 58 | 54 | 74 |
| Next.js | 53 | 72 | 48 | 45 | 59 |
| Nuxt | 46 | 59 | 44 | 46 | 65 |
| React Router | 37 | 63 | 37 | 50 | 53 |
| TanStack Start | 31 | 84 | 19 | 13 | 51 |
Measures how fast a page's main content loads. To provide a good user experience, the LCP should be 2.5 seconds or less.
| Framework | % |
|---|---|
| SolidStart | 88 |
| Astro | 80 |
| SvelteKit | 67 |
| Next.js | 53 |
| Nuxt | 46 |
| React Router | 37 |
| TanStack Start | 31 |
The chart includes a dotted median reference line calculated from the visible framework values.
Measures how much and how far content unexpectedly moves on a page. To provide a good user experience, sites should maintain a CLS score of 0.1 or less for at least 75% of page visits.
| Framework | % |
|---|---|
| Astro | 93 |
| TanStack Start | 84 |
| SvelteKit | 81 |
| Next.js | 72 |
| SolidStart | 66 |
| React Router | 63 |
| Nuxt | 59 |
The chart includes a dotted median reference line calculated from the visible framework values.
Measures initial loading speed. To provide a good user experience, the FCP should be 1.8 seconds or less.
| Framework | % |
|---|---|
| SolidStart | 88 |
| Astro | 73 |
| SvelteKit | 58 |
| Next.js | 48 |
| Nuxt | 44 |
| React Router | 37 |
| TanStack Start | 19 |
The chart includes a dotted median reference line calculated from the visible framework values.
Measures the time between the request for a resource and when the first byte of a response begins to arrive. A good TTFB is less than or equal to 800ms.
| Framework | % |
|---|---|
| SolidStart | 85 |
| Astro | 64 |
| SvelteKit | 54 |
| React Router | 50 |
| Nuxt | 46 |
| Next.js | 45 |
| TanStack Start | 13 |
The chart includes a dotted median reference line calculated from the visible framework values.
Measures overall page responsiveness to user actions. To provide a good user experience, the INP should be 200ms or less.
| Framework | % |
|---|---|
| Astro | 85 |
| SolidStart | 75 |
| SvelteKit | 74 |
| Nuxt | 65 |
| Next.js | 59 |
| React Router | 53 |
| TanStack Start | 51 |
The chart includes a dotted median reference line calculated from the visible framework values.