Run Time Stats
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 | 99.4ms | 99.34ms | 1.69ms | 1.33ms | 0.36ms | 0ms |
| Next.js | 338.8ms | 338.87ms | 18.84ms | 1.47ms | 4.42ms | 12.95ms |
| Nuxt | 154.2ms | 154.21ms | 10.81ms | 0.9ms | 1.55ms | 8.36ms |
| Pracht | 94.2ms | 94.32ms | 17.81ms | 0.92ms | 3.23ms | 13.66ms |
| React Router | 162.4ms | 162.42ms | 22.13ms | 1.66ms | 2.98ms | 17.5ms |
| SolidStart | 108ms | 107.88ms | 16.86ms | 1.09ms | 3.44ms | 12.33ms |
| SvelteKit | 115.8ms | 115.87ms | 15.74ms | 0.81ms | 1.75ms | 13.19ms |
| TanStack Start | 121.4ms | 121.14ms | 18.96ms | 1.46ms | 2.88ms | 14.63ms |
Client First Paint
| Framework | Milliseconds |
|---|---|
| Pracht | 94.20 ms |
| Astro | 99.40 ms |
| SolidStart | 108.00 ms |
| SvelteKit | 115.80 ms |
| TanStack Start | 121.40 ms |
| Nuxt | 154.20 ms |
| React Router | 162.40 ms |
| Next.js | 338.80 ms |
The chart includes a dotted median reference line calculated from the visible framework values.
Client FCP
| Framework | Milliseconds |
|---|---|
| Pracht | 94.32 ms |
| Astro | 99.34 ms |
| SolidStart | 107.88 ms |
| SvelteKit | 115.87 ms |
| TanStack Start | 121.14 ms |
| Nuxt | 154.21 ms |
| React Router | 162.42 ms |
| Next.js | 338.87 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.69 ms | 1.33 ms | 0.36 ms | 0.00 ms |
| Nuxt | 10.81 ms | 0.90 ms | 1.55 ms | 8.36 ms |
| SvelteKit | 15.74 ms | 0.81 ms | 1.75 ms | 13.19 ms |
| SolidStart | 16.86 ms | 1.09 ms | 3.44 ms | 12.33 ms |
| Pracht | 17.81 ms | 0.92 ms | 3.23 ms | 13.66 ms |
| Next.js | 18.84 ms | 1.47 ms | 4.42 ms | 12.95 ms |
| TanStack Start | 18.96 ms | 1.46 ms | 2.88 ms | 14.63 ms |
| React Router | 22.13 ms | 1.66 ms | 2.98 ms | 17.50 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 | 61.6ms | 61.54ms | 4.13ms | 0.6ms | 0.76ms | 2.76ms |
| Next.js | 369.2ms | 369.11ms | 16.99ms | 1.47ms | 6.38ms | 9.14ms |
| Nuxt | 89ms | 89.04ms | 15.86ms | 0.91ms | 1.32ms | 13.64ms |
| Pracht | 86.2ms | 86.13ms | 16.78ms | 0.81ms | 2.74ms | 13.23ms |
| React Router | 125.6ms | 125.54ms | 18.32ms | 1.59ms | 2.93ms | 13.8ms |
| SolidStart | 91ms | 90.78ms | 14.93ms | 0.96ms | 2.74ms | 11.23ms |
| SvelteKit | 81.6ms | 81.42ms | 17.92ms | 0.82ms | 3.24ms | 13.85ms |
| TanStack Start | 90.4ms | 90.17ms | 21.27ms | 1.54ms | 4.33ms | 15.4ms |
Server First Paint
| Framework | Milliseconds |
|---|---|
| Astro | 61.60 ms |
| SvelteKit | 81.60 ms |
| Pracht | 86.20 ms |
| Nuxt | 89.00 ms |
| TanStack Start | 90.40 ms |
| SolidStart | 91.00 ms |
| React Router | 125.60 ms |
| Next.js | 369.20 ms |
The chart includes a dotted median reference line calculated from the visible framework values.
Server FCP
| Framework | Milliseconds |
|---|---|
| Astro | 61.54 ms |
| SvelteKit | 81.42 ms |
| Pracht | 86.13 ms |
| Nuxt | 89.04 ms |
| TanStack Start | 90.17 ms |
| SolidStart | 90.78 ms |
| React Router | 125.54 ms |
| Next.js | 369.11 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 | 4.13 ms | 0.60 ms | 0.76 ms | 2.76 ms |
| SolidStart | 14.93 ms | 0.96 ms | 2.74 ms | 11.23 ms |
| Nuxt | 15.86 ms | 0.91 ms | 1.32 ms | 13.64 ms |
| Pracht | 16.78 ms | 0.81 ms | 2.74 ms | 13.23 ms |
| Next.js | 16.99 ms | 1.47 ms | 6.38 ms | 9.14 ms |
| SvelteKit | 17.92 ms | 0.82 ms | 3.24 ms | 13.85 ms |
| React Router | 18.32 ms | 1.59 ms | 2.93 ms | 13.80 ms |
| TanStack Start | 21.27 ms | 1.54 ms | 4.33 ms | 15.40 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 | 838 | 1.202ms | 96.83kb | 1x |
| Astro | 722 | 1.333ms | 96.89kb | 1x |
| Next.js | 136 | 7.322ms | 204.56kb | 2x |
| Nuxt | 368 | 2.637ms | 201.73kb | 2x |
| Pracht | 590 | 1.614ms | 187.02kb | 2x |
| React Router | 327 | 2.974ms | 216.98kb | 2x |
| SolidStart | 391 | 2.453ms | 224.26kb | 2x |
| SvelteKit | 452 | 2.17ms | 184.29kb | 2x |
| TanStack Start | 369 | 2.674ms | 192.53kb | 2x |
Ops/sec
| Framework | Operations per second |
|---|---|
| Baseline HTML | 838 |
| Astro | 722 |
| Pracht | 590 |
| SvelteKit | 452 |
| SolidStart | 391 |
| TanStack Start | 369 |
| Nuxt | 368 |
| React Router | 327 |
| Next.js | 136 |
The chart includes a dotted median reference line calculated from the visible framework values.
Body Size
| 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 Latency
| Framework | Milliseconds |
|---|---|
| Baseline HTML | 1.20 ms |
| Astro | 1.33 ms |
| Pracht | 1.61 ms |
| SvelteKit | 2.17 ms |
| SolidStart | 2.45 ms |
| Nuxt | 2.64 ms |
| TanStack Start | 2.67 ms |
| React Router | 2.97 ms |
| Next.js | 7.32 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.
All eight frameworks render 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 | Peak req/s | Peak Connections | P99 @ 25 | P99 @ 50 | P99 @ 100 | Total Req. |
|---|---|---|---|---|---|---|
| Baseline HTML | 1,722 | 200 | 23ms | 39ms | 99ms | 50,764 |
| Astro | 1,588.6 | 50 | 24ms | 47ms | 86ms | 46,800 |
| Next.js | 52.8 | 10 | 1230ms | 4244ms | 4638ms | 1,610 |
| Nuxt | 525.6 | 50 | 77ms | 180ms | 2680ms | 17,151 |
| Pracht | 707 | 25 | 38ms | 109ms | 956ms | 21,984 |
| React Router | 336.6 | 25 | 93ms | 619ms | 3447ms | 11,044 |
| SolidStart | 555 | 10 | 92ms | 344ms | 2123ms | 18,027 |
| SvelteKit | 559.8 | 25 | 84ms | 276ms | 2168ms | 18,310 |
| TanStack Start | 394.4 | 50 | 109ms | 422ms | 2484ms | 13,082 |
P99 Latency
Section titled “P99 Latency”P99 Latency at 25 Connections
| Framework | Milliseconds |
|---|---|
| Baseline HTML | 23.00 ms |
| Astro | 24.00 ms |
| Pracht | 38.00 ms |
| Nuxt | 77.00 ms |
| SvelteKit | 84.00 ms |
| SolidStart | 92.00 ms |
| React Router | 93.00 ms |
| TanStack Start | 109.00 ms |
| Next.js | 1230.00 ms |
The chart includes a dotted median reference line calculated from the visible framework values.
P99 Latency at 50 Connections
| Framework | Milliseconds |
|---|---|
| Baseline HTML | 39.00 ms |
| Astro | 47.00 ms |
| Pracht | 109.00 ms |
| Nuxt | 180.00 ms |
| SvelteKit | 276.00 ms |
| SolidStart | 344.00 ms |
| TanStack Start | 422.00 ms |
| React Router | 619.00 ms |
| Next.js | 4244.00 ms |
The chart includes a dotted median reference line calculated from the visible framework values.
P99 Latency at 100 Connections
| Framework | Milliseconds |
|---|---|
| Astro | 86.00 ms |
| Baseline HTML | 99.00 ms |
| Pracht | 956.00 ms |
| SolidStart | 2123.00 ms |
| SvelteKit | 2168.00 ms |
| TanStack Start | 2484.00 ms |
| Nuxt | 2680.00 ms |
| React Router | 3447.00 ms |
| Next.js | 4638.00 ms |
The chart includes a dotted median reference line calculated from the visible framework values.
P90 Latency
Section titled “P90 Latency”P90 Latency at 25 Connections
| Framework | Milliseconds |
|---|---|
| Astro | 17.00 ms |
| Baseline HTML | 17.00 ms |
| Pracht | 36.00 ms |
| Nuxt | 49.00 ms |
| SvelteKit | 58.00 ms |
| SolidStart | 65.00 ms |
| React Router | 80.00 ms |
| TanStack Start | 86.00 ms |
| Next.js | 511.00 ms |
The chart includes a dotted median reference line calculated from the visible framework values.
P90 Latency at 50 Connections
| Framework | Milliseconds |
|---|---|
| Baseline HTML | 31.00 ms |
| Astro | 32.00 ms |
| Pracht | 71.00 ms |
| Nuxt | 96.00 ms |
| SvelteKit | 128.00 ms |
| SolidStart | 140.00 ms |
| React Router | 165.00 ms |
| TanStack Start | 171.00 ms |
| Next.js | 1781.00 ms |
The chart includes a dotted median reference line calculated from the visible framework values.
P90 Latency at 100 Connections
| Framework | Milliseconds |
|---|---|
| Astro | 64.00 ms |
| Baseline HTML | 73.00 ms |
| Pracht | 144.00 ms |
| SolidStart | 158.00 ms |
| Nuxt | 182.00 ms |
| SvelteKit | 208.00 ms |
| TanStack Start | 230.00 ms |
| React Router | 292.00 ms |
| Next.js | 2343.00 ms |
The chart includes a dotted median reference line calculated from the visible framework values.
P75 Latency
Section titled “P75 Latency”P75 Latency at 25 Connections
| Framework | Milliseconds |
|---|---|
| Baseline HTML | 15.00 ms |
| Astro | 16.00 ms |
| Pracht | 35.00 ms |
| SvelteKit | 47.00 ms |
| Nuxt | 48.00 ms |
| SolidStart | 56.00 ms |
| TanStack Start | 67.00 ms |
| React Router | 73.00 ms |
| Next.js | 501.00 ms |
The chart includes a dotted median reference line calculated from the visible framework values.
P75 Latency at 50 Connections
| Framework | Milliseconds |
|---|---|
| Baseline HTML | 30.00 ms |
| Astro | 31.00 ms |
| Pracht | 70.00 ms |
| SolidStart | 87.00 ms |
| Nuxt | 92.00 ms |
| SvelteKit | 102.00 ms |
| TanStack Start | 132.00 ms |
| React Router | 148.00 ms |
| Next.js | 969.00 ms |
The chart includes a dotted median reference line calculated from the visible framework values.
P75 Latency at 100 Connections
| Framework | Milliseconds |
|---|---|
| Baseline HTML | 61.00 ms |
| Astro | 63.00 ms |
| SolidStart | 116.00 ms |
| Pracht | 140.00 ms |
| SvelteKit | 154.00 ms |
| Nuxt | 175.00 ms |
| TanStack Start | 178.00 ms |
| React Router | 264.00 ms |
| Next.js | 975.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 | Peak req/s | Peak Connections | P99 @ 25 | P99 @ 50 | P99 @ 100 | Total Req. |
|---|---|---|---|---|---|---|
| Next.js | 47 | 5 | 1490ms | 4769ms | 4839ms | 1,423 |
| Nuxt | 177.4 | 5 | 490ms | 2659ms | 3561ms | 5,821 |
| Pracht | 334.8 | 25 | 95ms | 575ms | 3309ms | 10,847 |
| React Router | 166.4 | 100 | 415ms | 1478ms | 3843ms | 5,302 |
| TanStack Start | 242.8 | 50 | 165ms | 1703ms | 3145ms | 8,188 |
P99 Latency
Section titled “P99 Latency”P99 Latency at 25 Connections
| Framework | Milliseconds |
|---|---|
| Pracht | 95.00 ms |
| TanStack Start | 165.00 ms |
| React Router | 415.00 ms |
| Nuxt | 490.00 ms |
| Next.js | 1490.00 ms |
The chart includes a dotted median reference line calculated from the visible framework values.
P99 Latency at 50 Connections
| Framework | Milliseconds |
|---|---|
| Pracht | 575.00 ms |
| React Router | 1478.00 ms |
| TanStack Start | 1703.00 ms |
| Nuxt | 2659.00 ms |
| Next.js | 4769.00 ms |
The chart includes a dotted median reference line calculated from the visible framework values.
P99 Latency at 100 Connections
| Framework | Milliseconds |
|---|---|
| TanStack Start | 3145.00 ms |
| Pracht | 3309.00 ms |
| Nuxt | 3561.00 ms |
| React Router | 3843.00 ms |
| Next.js | 4839.00 ms |
The chart includes a dotted median reference line calculated from the visible framework values.
P90 Latency
Section titled “P90 Latency”P90 Latency at 25 Connections
| Framework | Milliseconds |
|---|---|
| Pracht | 83.00 ms |
| TanStack Start | 131.00 ms |
| Nuxt | 153.00 ms |
| React Router | 162.00 ms |
| Next.js | 590.00 ms |
The chart includes a dotted median reference line calculated from the visible framework values.
P90 Latency at 50 Connections
| Framework | Milliseconds |
|---|---|
| Pracht | 158.00 ms |
| TanStack Start | 262.00 ms |
| Nuxt | 291.00 ms |
| React Router | 301.00 ms |
| Next.js | 2290.00 ms |
The chart includes a dotted median reference line calculated from the visible framework values.
P90 Latency at 100 Connections
| Framework | Milliseconds |
|---|---|
| TanStack Start | 296.00 ms |
| Pracht | 303.00 ms |
| Nuxt | 326.00 ms |
| React Router | 429.00 ms |
| Next.js | 2416.00 ms |
The chart includes a dotted median reference line calculated from the visible framework values.
P75 Latency
Section titled “P75 Latency”P75 Latency at 25 Connections
| Framework | Milliseconds |
|---|---|
| Pracht | 77.00 ms |
| TanStack Start | 109.00 ms |
| Nuxt | 140.00 ms |
| React Router | 156.00 ms |
| Next.js | 585.00 ms |
The chart includes a dotted median reference line calculated from the visible framework values.
P75 Latency at 50 Connections
| Framework | Milliseconds |
|---|---|
| Pracht | 152.00 ms |
| TanStack Start | 199.00 ms |
| Nuxt | 286.00 ms |
| React Router | 295.00 ms |
| Next.js | 1098.00 ms |
The chart includes a dotted median reference line calculated from the visible framework values.
P75 Latency at 100 Connections
| Framework | Milliseconds |
|---|---|
| TanStack Start | 230.00 ms |
| Pracht | 273.00 ms |
| Nuxt | 301.00 ms |
| React Router | 380.00 ms |
| Next.js | 1020.00 ms |
The chart includes a dotted median reference line calculated from the visible framework values.
Core Web Vitals
Section titled “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 |
Good Largest Contentful Paint
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.
Good Cumulative Layout Shift
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.
Good First Contentful Paint
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.
Good Time To First Byte
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 |
| SvelteKit | 68 |
| React Router | 68 |
| Next.js | 66 |
| Nuxt | 59 |
| TanStack Start | 29 |
The chart includes a dotted median reference line calculated from the visible framework values.
Good Interaction to Next Paint
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 |
Good Largest Contentful Paint
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.
Good Cumulative Layout Shift
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.
Good First Contentful Paint
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.
Good Time To First Byte
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.
Good Interaction to Next Paint
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.
Methodology: Core Web Vitals.