All Results
All results for every tracked framework, including the featured frameworks shown on the Dev Time, Run Time, and Core Web Vitals pages.
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 | 5 | 24 | 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 | 5 |
| 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 | 24 |
| 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 | 333 | 14 | View |
| Next.js | 1 / 1 | 388 | 12 | View |
| Nuxt | 0 / 1 | 634 | 76 | View |
| Pracht | 2 / 2 | 218 | 4 | View |
| React Router | 1 / 3 | 226 | 5 | View |
| SolidStart | 0 / 4 | 212 | 6 | View |
| SvelteKit | 5 / 0 | 108 | 1 | View |
| TanStack Start | 1 / 7 | 194 | 3 | View |
| Framework | Dependency count |
|---|---|
| SvelteKit | 108 |
| TanStack Start | 194 |
| SolidStart | 212 |
| Pracht | 218 |
| React Router | 226 |
| Astro | 333 |
| Next.js | 388 |
| Nuxt | 634 |
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 |
| React Router | 5 |
| SolidStart | 6 |
| Next.js | 12 |
| Astro | 14 |
| Nuxt | 76 |
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 | 333 | 14 | 204.20MB | 172.07MB | View |
| Next.js | 6 / 3 | 424 | 12 | 463.42MB | 405.08MB | View |
| Nuxt | 3 / 3 | 634 | 76 | 246.13MB | 213.96MB | View |
| Pracht | 6 / 2 | 239 | 4 | 132.55MB | 109.29MB | View |
| React Router | 9 / 6 | 249 | 5 | 109.34MB | 103.24MB | View |
| SolidStart | 1 / 6 | 261 | 23 | 149.16MB | 125.07MB | View |
| SvelteKit | 8 / 0 | 108 | 1 | 88.32MB | 92.09MB | View |
| TanStack Start | 12 / 14 | 330 | 37 | 274.10MB | 230.99MB | 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 |
| React Router | 5 |
| Next.js | 12 |
| Astro | 14 |
| SolidStart | 23 |
| TanStack Start | 37 |
| Nuxt | 76 |
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 | 109.34 MB |
| Pracht | 132.55 MB |
| SolidStart | 149.16 MB |
| Astro | 204.20 MB |
| Nuxt | 246.13 MB |
| TanStack Start | 274.10 MB |
| Next.js | 463.42 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.02s | 2.04s | 4.44s | 1.00s | 0.96s |
| Next.js | 6.80s | 2.97s | 7.05s | 5.36s | 2.26s |
| Nuxt | 5.68s | 3.61s | 6.24s | 3.97s | 3.76s |
| Pracht | 2.13s | 1.56s | 2.44s | 0.69s | 0.69s |
| React Router | 1.58s | 1.24s | 1.65s | 1.70s | 1.65s |
| SolidStart | 1.97s | 1.47s | 2.31s | 3.06s | 2.96s |
| SvelteKit | 1.70s | 1.50s | 1.82s | 1.85s | 1.65s |
| TanStack Start | 5.24s | 1.99s | 5.41s | 1.96s | 1.77s |
| Framework | Seconds |
|---|---|
| React Router | 1.58s |
| SvelteKit | 1.70s |
| SolidStart | 1.97s |
| Pracht | 2.13s |
| Astro | 4.02s |
| TanStack Start | 5.24s |
| Nuxt | 5.68s |
| Next.js | 6.80s |
The chart includes a dotted median reference line calculated from the visible framework values.
| Framework | Seconds |
|---|---|
| Pracht | 0.69s |
| Astro | 1.00s |
| React Router | 1.70s |
| SvelteKit | 1.85s |
| TanStack Start | 1.96s |
| SolidStart | 3.06s |
| Nuxt | 3.97s |
| Next.js | 5.36s |
The chart includes a dotted median reference line calculated from the visible framework values.
| Framework | Seconds |
|---|---|
| Pracht | 0.69s |
| Astro | 0.96s |
| React Router | 1.65s |
| SvelteKit | 1.65s |
| TanStack Start | 1.77s |
| Next.js | 2.26s |
| SolidStart | 2.96s |
| Nuxt | 3.76s |
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.37s | 1.34s | 1.41s |
| Next.js | 2.11s | 2.03s | 2.53s |
| Nuxt | 2.52s | 2.44s | 2.75s |
| Pracht | 0.85s | 0.81s | 0.90s |
| React Router | 0.88s | 0.85s | 0.92s |
| SolidStart | 2.57s | 2.55s | 2.66s |
| SvelteKit | 1.24s | 1.21s | 1.43s |
| TanStack Start | 1.86s | 1.83s | 1.95s |
| Framework | Seconds |
|---|---|
| Pracht | 0.85s |
| React Router | 0.88s |
| SvelteKit | 1.24s |
| Astro | 1.37s |
| TanStack Start | 1.86s |
| Next.js | 2.11s |
| Nuxt | 2.52s |
| SolidStart | 2.57s |
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 | 31 |
| SvelteKit | High | — | 2021 | 47 |
| TanStack Start | High | — | 2022 | 48 |
Minimum Node Version
Section titled “Minimum Node Version”Methodology: Minimum Node Version.
| Framework | Min Node | Set by |
|---|---|---|
| Astro | v22.23.4 | @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”Run Time benchmarks use each meta-framework’s app-* package.
Currently, each test uses a different route in its app, configured to meet each test’s requirements.
See Default Benchmark Setup for the base set-up. Each test’s specific setup is linked in the methodology with links in each section.
Client Side Rendered Tests (Lighthouse)
Section titled “Client Side Rendered Tests (Lighthouse)”These CSR browser performance tests use Lighthouse to measure paint timings and a controlled navigation interaction.
Methodology: Client Side Rendered Tests (Lighthouse).
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 | 93ms | 92.7ms | 2.539ms | 2.232ms | 0.307ms | 0ms |
| Next.js | 341ms | 340.981ms | 16.161ms | 1.586ms | 4.464ms | 10.111ms |
| Nuxt | 164ms | 163.983ms | 10.499ms | 0.854ms | 1.242ms | 8.403ms |
| Pracht | 105ms | 104.909ms | 17.961ms | 1.007ms | 4.769ms | 12.185ms |
| React Router | 162ms | 162.185ms | 17.499ms | 1.517ms | 2.168ms | 13.814ms |
| SolidStart | 108ms | 108.479ms | 19.453ms | 1.05ms | 2.946ms | 15.457ms |
| SvelteKit | 109ms | 109.227ms | 15.763ms | 0.727ms | 1.447ms | 13.589ms |
| TanStack Start | 137ms | 136.717ms | 26.29ms | 1.386ms | 2.726ms | 22.178ms |
| Framework | Milliseconds |
|---|---|
| Astro | 93.00 ms |
| Pracht | 105.00 ms |
| SolidStart | 108.00 ms |
| SvelteKit | 109.00 ms |
| TanStack Start | 137.00 ms |
| React Router | 162.00 ms |
| Nuxt | 164.00 ms |
| Next.js | 341.00 ms |
The chart includes a dotted median reference line calculated from the visible framework values.
| Framework | Milliseconds |
|---|---|
| Astro | 92.70 ms |
| Pracht | 104.91 ms |
| SolidStart | 108.48 ms |
| SvelteKit | 109.23 ms |
| TanStack Start | 136.72 ms |
| React Router | 162.19 ms |
| Nuxt | 163.98 ms |
| Next.js | 340.98 ms |
The chart includes a dotted median reference line calculated from the visible framework values.
Interaction Breakdown (Lighthouse)
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.23 ms | 0.31 ms | 0.00 ms |
| Nuxt | 10.50 ms | 0.85 ms | 1.24 ms | 8.40 ms |
| SvelteKit | 15.76 ms | 0.73 ms | 1.45 ms | 13.59 ms |
| Next.js | 16.16 ms | 1.59 ms | 4.46 ms | 10.11 ms |
| React Router | 17.50 ms | 1.52 ms | 2.17 ms | 13.81 ms |
| Pracht | 17.96 ms | 1.01 ms | 4.77 ms | 12.19 ms |
| SolidStart | 19.45 ms | 1.05 ms | 2.95 ms | 15.46 ms |
| TanStack Start | 26.29 ms | 1.39 ms | 2.73 ms | 22.18 ms |
Server Side Rendered Tests (Lighthouse)
Section titled “Server Side Rendered Tests (Lighthouse)”These SSR browser performance tests use Lighthouse to measure paint timings and a controlled navigation interaction.
Methodology: Server Side Rendered Tests (Lighthouse).
| Framework | First Paint | FCP | Interaction Latency | Input Delay | Processing Duration | Presentation Delay |
|---|---|---|---|---|---|---|
| Astro | 52ms | 51.982ms | 0.867ms | 0.629ms | 0.238ms | 0ms |
| Next.js | 376ms | 376.211ms | 19.652ms | 1.571ms | 4.898ms | 13.183ms |
| Nuxt | 94ms | 94.22ms | 11.76ms | 1.285ms | 1.365ms | 9.11ms |
| Pracht | 84ms | 84.455ms | 16.253ms | 0.874ms | 2.128ms | 13.251ms |
| React Router | 108ms | 107.637ms | 16.258ms | 1.65ms | 3.505ms | 11.103ms |
| SolidStart | 83ms | 83.451ms | 16.157ms | 0.84ms | 3.009ms | 12.308ms |
| SvelteKit | 76ms | 75.722ms | 14.079ms | 0.765ms | 1.82ms | 11.494ms |
| TanStack Start | 94ms | 93.684ms | 22.78ms | 1.304ms | 3.816ms | 17.66ms |
| Framework | Milliseconds |
|---|---|
| Astro | 52.00 ms |
| SvelteKit | 76.00 ms |
| SolidStart | 83.00 ms |
| Pracht | 84.00 ms |
| Nuxt | 94.00 ms |
| TanStack Start | 94.00 ms |
| React Router | 108.00 ms |
| Next.js | 376.00 ms |
The chart includes a dotted median reference line calculated from the visible framework values.
| Framework | Milliseconds |
|---|---|
| Astro | 51.98 ms |
| SvelteKit | 75.72 ms |
| SolidStart | 83.45 ms |
| Pracht | 84.45 ms |
| TanStack Start | 93.68 ms |
| Nuxt | 94.22 ms |
| React Router | 107.64 ms |
| Next.js | 376.21 ms |
The chart includes a dotted median reference line calculated from the visible framework values.
Interaction Breakdown (Lighthouse)
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 | 0.87 ms | 0.63 ms | 0.24 ms | 0.00 ms |
| Nuxt | 11.76 ms | 1.28 ms | 1.36 ms | 9.11 ms |
| SvelteKit | 14.08 ms | 0.77 ms | 1.82 ms | 11.49 ms |
| SolidStart | 16.16 ms | 0.84 ms | 3.01 ms | 12.31 ms |
| Pracht | 16.25 ms | 0.87 ms | 2.13 ms | 13.25 ms |
| React Router | 16.26 ms | 1.65 ms | 3.50 ms | 11.10 ms |
| Next.js | 19.65 ms | 1.57 ms | 4.90 ms | 13.18 ms |
| TanStack Start | 22.78 ms | 1.30 ms | 3.82 ms | 17.66 ms |
Initial Load
Section titled “Initial Load”Compare the resources transferred on a first visit to the same small, styled landing page. Sizes include response headers; lower is better. Inline CSS and JavaScript count toward HTML. Other includes images, media, fonts, and remaining resources. See Methodology for collection details.
| Framework | Requests | HTML | CSS | JavaScript | Other | Total |
|---|---|---|---|---|---|---|
| Astro | 1 | 3.28 KB | 0.00 KB | 0.00 KB | 0.00 KB | 3.28 KB |
| Next.js | 8 | 5.34 KB | 1.05 KB | 134.98 KB | 0.00 KB | 141.38 KB |
| Nuxt | 13 | 4.67 KB | 0.88 KB | 66.20 KB | 5.48 KB | 77.24 KB |
| Pracht | 6 | 1.19 KB | 1.18 KB | 19.06 KB | 0.00 KB | 21.44 KB |
| React Router | 8 | 2.45 KB | 1.00 KB | 118.19 KB | 0.00 KB | 121.64 KB |
| SolidStart | 8 | 2.65 KB | 0.88 KB | 30.26 KB | 0.00 KB | 33.79 KB |
| SvelteKit | 12 | 3.11 KB | 0.86 KB | 34.35 KB | 0.00 KB | 38.32 KB |
| TanStack Start | 6 | 3.72 KB | 0.88 KB | 97.28 KB | 0.00 KB | 101.88 KB |
- HTML
- CSS
- JavaScript
- Other
| Framework | HTML | CSS | JavaScript | Other |
|---|---|---|---|---|
| Astro | 3.28 KB | 0.00 KB | 0.00 KB | 0.00 KB |
| Next.js | 5.34 KB | 1.05 KB | 134.98 KB | 0.00 KB |
| Nuxt | 4.67 KB | 0.88 KB | 66.20 KB | 5.48 KB |
| Pracht | 1.19 KB | 1.18 KB | 19.06 KB | 0.00 KB |
| React Router | 2.45 KB | 1.00 KB | 118.19 KB | 0.00 KB |
| SolidStart | 2.65 KB | 0.88 KB | 30.26 KB | 0.00 KB |
| SvelteKit | 3.11 KB | 0.86 KB | 34.35 KB | 0.00 KB |
| TanStack Start | 3.72 KB | 0.88 KB | 97.28 KB | 0.00 KB |
- HTML
- CSS
- Other
| Framework | HTML | CSS | Other |
|---|---|---|---|
| Astro | 3.28 KB | 0.00 KB | 0.00 KB |
| Next.js | 5.34 KB | 1.05 KB | 0.00 KB |
| Nuxt | 4.67 KB | 0.88 KB | 5.48 KB |
| Pracht | 1.19 KB | 1.18 KB | 0.00 KB |
| React Router | 2.45 KB | 1.00 KB | 0.00 KB |
| SolidStart | 2.65 KB | 0.88 KB | 0.00 KB |
| SvelteKit | 3.11 KB | 0.86 KB | 0.00 KB |
| TanStack Start | 3.72 KB | 0.88 KB | 0.00 KB |
Server Side Throughput Tests
Section titled “Server Side Throughput Tests”Methodology: Server Side Throughput Tests.
Measures how many requests each framework’s server handler can process per second when rendering a 1,000-row table, and how long each response takes. Requests bypass network overhead to focus on server rendering performance.
| Framework | Ops/sec | Median Latency | Body Size | Duplication |
|---|---|---|---|---|
| Baseline HTML | 829 | 1.22ms | 96.83kb | 1x |
| Astro | 767 | 1.426ms | 96.89kb | 1x |
| Next.js | 130 | 7.97ms | 204.56kb | 2x |
| Nuxt | 390 | 2.707ms | 201.8kb | 2x |
| Pracht | 607 | 1.713ms | 187.02kb | 2x |
| React Router | 360 | 2.803ms | 216.84kb | 2x |
| SolidStart | 405 | 2.525ms | 224.22kb | 2x |
| SvelteKit | 447 | 2.272ms | 184.29kb | 2x |
| TanStack Start | 296 | 3.484ms | 192.78kb | 2x |
| Framework | Operations per second |
|---|---|
| Baseline HTML | 829 |
| Astro | 767 |
| Pracht | 607 |
| SvelteKit | 447 |
| SolidStart | 405 |
| Nuxt | 390 |
| React Router | 360 |
| TanStack Start | 296 |
| Next.js | 130 |
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.78 KB |
| Nuxt | 201.80 KB |
| Next.js | 204.56 KB |
| React Router | 216.84 KB |
| SolidStart | 224.22 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.22 ms |
| Astro | 1.43 ms |
| Pracht | 1.71 ms |
| SvelteKit | 2.27 ms |
| SolidStart | 2.52 ms |
| Nuxt | 2.71 ms |
| React Router | 2.80 ms |
| TanStack Start | 3.48 ms |
| Next.js | 7.97 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.
Measures server throughput and response latency as concurrent connections increase, with each request rendering a 1,000-row table.
This version uses ordinary <a> links to measure server rendering without the extra work of rendering framework router link components.
Compare it with the router link load test to see how framework router link components affect server rendering performance.
| 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,804.8 | 100 | 17ms | 35ms | 91ms | 158,577 |
| Astro | 1,623.2 | 50 | 23ms | 46ms | 94ms | 144,676 |
| Next.js | 49.8 | 5 | 1,328ms | 4,435ms | 4,666ms | 4,499 |
| Nuxt | 524.8 | 50 | 71ms | 315ms | 2,704ms | 51,170 |
| Pracht | 695.2 | 25 | 41ms | 112ms | 994ms | 63,942 |
| React Router | 338.6 | 25 | 103ms | 599ms | 3,372ms | 32,971 |
| SolidStart | 528.6 | 50 | 97ms | 433ms | 2,101ms | 51,319 |
| SvelteKit | 596.8 | 25 | 74ms | 218ms | 2,027ms | 57,310 |
| TanStack Start | 413 | 100 | 116ms | 603ms | 2,500ms | 40,305 |
P99 Latency
Section titled “P99 Latency”| Framework | Milliseconds |
|---|---|
| Baseline HTML | 17.00 ms |
| Astro | 23.00 ms |
| Pracht | 41.00 ms |
| Nuxt | 71.00 ms |
| SvelteKit | 74.00 ms |
| SolidStart | 97.00 ms |
| React Router | 103.00 ms |
| TanStack Start | 116.00 ms |
| Next.js | 1328.00 ms |
The chart includes a dotted median reference line calculated from the visible framework values.
| Framework | Milliseconds |
|---|---|
| Baseline HTML | 35.00 ms |
| Astro | 46.00 ms |
| Pracht | 112.00 ms |
| SvelteKit | 218.00 ms |
| Nuxt | 315.00 ms |
| SolidStart | 433.00 ms |
| React Router | 599.00 ms |
| TanStack Start | 603.00 ms |
| Next.js | 4435.00 ms |
The chart includes a dotted median reference line calculated from the visible framework values.
| Framework | Milliseconds |
|---|---|
| Baseline HTML | 91.00 ms |
| Astro | 94.00 ms |
| Pracht | 994.00 ms |
| SvelteKit | 2027.00 ms |
| SolidStart | 2101.00 ms |
| TanStack Start | 2500.00 ms |
| Nuxt | 2704.00 ms |
| React Router | 3372.00 ms |
| Next.js | 4666.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 | 37.00 ms |
| Nuxt | 50.00 ms |
| SvelteKit | 53.00 ms |
| SolidStart | 68.00 ms |
| React Router | 76.00 ms |
| TanStack Start | 79.00 ms |
| Next.js | 529.00 ms |
The chart includes a dotted median reference line calculated from the visible framework values.
| Framework | Milliseconds |
|---|---|
| Baseline HTML | 30.00 ms |
| Astro | 31.00 ms |
| Pracht | 73.00 ms |
| Nuxt | 105.00 ms |
| SvelteKit | 120.00 ms |
| SolidStart | 150.00 ms |
| React Router | 155.00 ms |
| TanStack Start | 171.00 ms |
| Next.js | 2025.00 ms |
The chart includes a dotted median reference line calculated from the visible framework values.
| Framework | Milliseconds |
|---|---|
| Astro | 62.00 ms |
| Baseline HTML | 73.00 ms |
| Pracht | 154.00 ms |
| SolidStart | 160.00 ms |
| Nuxt | 185.00 ms |
| SvelteKit | 192.00 ms |
| TanStack Start | 218.00 ms |
| React Router | 296.00 ms |
| Next.js | 2396.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 | 14.00 ms |
| Astro | 15.00 ms |
| Pracht | 36.00 ms |
| SvelteKit | 43.00 ms |
| Nuxt | 49.00 ms |
| SolidStart | 57.00 ms |
| TanStack Start | 64.00 ms |
| React Router | 74.00 ms |
| Next.js | 511.00 ms |
The chart includes a dotted median reference line calculated from the visible framework values.
| Framework | Milliseconds |
|---|---|
| Baseline HTML | 29.00 ms |
| Astro | 30.00 ms |
| Pracht | 71.00 ms |
| Nuxt | 93.00 ms |
| SolidStart | 93.00 ms |
| SvelteKit | 93.00 ms |
| TanStack Start | 135.00 ms |
| React Router | 149.00 ms |
| Next.js | 1022.00 ms |
The chart includes a dotted median reference line calculated from the visible framework values.
| Framework | Milliseconds |
|---|---|
| Baseline HTML | 56.00 ms |
| Astro | 61.00 ms |
| SolidStart | 123.00 ms |
| SvelteKit | 137.00 ms |
| Pracht | 148.00 ms |
| Nuxt | 169.00 ms |
| TanStack Start | 169.00 ms |
| React Router | 264.00 ms |
| Next.js | 993.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.
Measures server throughput and response latency as concurrent connections increase, with each request rendering a 1,000-row table using framework router link components.
Compare it with the plain link load test to see how these components affect server rendering performance. These tests make HTTP requests only; they do not measure browser navigation or prefetching.
Frameworks without a router link component are excluded.
| 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 | 46.2 | 5 | 1,385ms | 4,628ms | 4,706ms | 4,178 |
| Nuxt | 178.6 | 5 | 476ms | 2,712ms | 3,671ms | 17,481 |
| Pracht | 362.2 | 25 | 100ms | 479ms | 3,281ms | 33,897 |
| React Router | 177.8 | 25 | 269ms | 1,664ms | 3,821ms | 17,665 |
| TanStack Start | 262.61 | 50 | 172ms | 495ms | 2,955ms | 26,231 |
P99 Latency
Section titled “P99 Latency”| Framework | Milliseconds |
|---|---|
| Pracht | 100.00 ms |
| TanStack Start | 172.00 ms |
| React Router | 269.00 ms |
| Nuxt | 476.00 ms |
| Next.js | 1385.00 ms |
The chart includes a dotted median reference line calculated from the visible framework values.
| Framework | Milliseconds |
|---|---|
| Pracht | 479.00 ms |
| TanStack Start | 495.00 ms |
| React Router | 1664.00 ms |
| Nuxt | 2712.00 ms |
| Next.js | 4628.00 ms |
The chart includes a dotted median reference line calculated from the visible framework values.
| Framework | Milliseconds |
|---|---|
| TanStack Start | 2955.00 ms |
| Pracht | 3281.00 ms |
| Nuxt | 3671.00 ms |
| React Router | 3821.00 ms |
| Next.js | 4706.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 | 71.00 ms |
| TanStack Start | 119.00 ms |
| React Router | 150.00 ms |
| Nuxt | 153.00 ms |
| Next.js | 582.00 ms |
The chart includes a dotted median reference line calculated from the visible framework values.
| Framework | Milliseconds |
|---|---|
| Pracht | 147.00 ms |
| TanStack Start | 238.00 ms |
| React Router | 288.00 ms |
| Nuxt | 297.00 ms |
| Next.js | 2225.00 ms |
The chart includes a dotted median reference line calculated from the visible framework values.
| Framework | Milliseconds |
|---|---|
| Pracht | 273.00 ms |
| TanStack Start | 300.00 ms |
| Nuxt | 321.00 ms |
| React Router | 403.00 ms |
| Next.js | 2485.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 | 69.00 ms |
| TanStack Start | 98.00 ms |
| Nuxt | 139.00 ms |
| React Router | 140.00 ms |
| Next.js | 562.00 ms |
The chart includes a dotted median reference line calculated from the visible framework values.
| Framework | Milliseconds |
|---|---|
| Pracht | 140.00 ms |
| TanStack Start | 190.00 ms |
| React Router | 282.00 ms |
| Nuxt | 288.00 ms |
| Next.js | 1073.00 ms |
The chart includes a dotted median reference line calculated from the visible framework values.
| Framework | Milliseconds |
|---|---|
| TanStack Start | 216.00 ms |
| Pracht | 254.00 ms |
| Nuxt | 302.00 ms |
| React Router | 375.00 ms |
| Next.js | 1046.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.
Desktop
Section titled “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.
Mobile
Section titled “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.