All Frameworks
Dependency Counts
Section titled “Dependency Counts”Methodology: Dependency Counts.
For dependency counts, we start by looking at the dependencies for the meta-framework package directly. For example, how many production, development and overall dependencies does `Nuxt` have? We then look at dependencies for the starter projects specifically. Looking at a project's dependencies is more realistic (like the `starter-*` projects) as meta-frameworks rarely just include the meta-framework package alone. It is also important to look at direct dependencies.Meta-framework Direct Package Counts
Section titled “Meta-framework Direct Package Counts”| Framework | Deps | Dev | Prod | Graph |
|---|---|---|---|---|
| Astro | 80 | 27 | 53 | View |
| Next.js | 229 | 223 | 6 | View |
| Nuxt | 68 | 11 | 57 | View |
| React Router | 50 | 22 | 28 | View |
| SolidStart | 29 | 4 | 25 | View |
| SvelteKit | 24 | 12 | 12 | View |
| TanStack Start | 8 | 0 | 8 | View |
Metaframework Dependencies
| Framework | Dependency count |
|---|---|
| TanStack Start | 8 |
| SvelteKit | 24 |
| SolidStart | 29 |
| React Router | 50 |
| Nuxt | 68 |
| Astro | 80 |
| Next.js | 229 |
The chart includes a dotted median reference line calculated from the visible framework values.
Metaframework Development Dependencies
| Framework | Dependency count |
|---|---|
| TanStack Start | 0 |
| SolidStart | 4 |
| Nuxt | 11 |
| SvelteKit | 12 |
| React Router | 22 |
| Astro | 27 |
| Next.js | 223 |
The chart includes a dotted median reference line calculated from the visible framework values.
Metaframework Production Dependencies
| Framework | Dependency count |
|---|---|
| Next.js | 6 |
| TanStack Start | 8 |
| SvelteKit | 12 |
| SolidStart | 25 |
| React Router | 28 |
| Astro | 53 |
| Nuxt | 57 |
The chart includes a dotted median reference line calculated from the visible framework values.
Starter Projects
Section titled “Starter Projects”| Framework | Deps Dev / Prod | All Deps | Dup. Deps | node_modules | Dep Install Size | Graph |
|---|---|---|---|---|---|---|
| Astro | 2 / 1 | 387 | 11 | 207.93MB | 186.65MB | View |
| Next.js | 6 / 3 | 421 | 12 | 560.04MB | 506.22MB | View |
| Nuxt | 2 / 3 | 694 | 63 | 208.80MB | 172.24MB | View |
| React Router | 8 / 6 | 268 | 9 | 106.86MB | 102.22MB | View |
| SolidStart | 1 / 6 | 227 | 8 | 124.34MB | 99.61MB | View |
| SvelteKit | 7 / 0 | 156 | 1 | 95.65MB | 98.77MB | View |
| TanStack Start | 11 / 13 | 424 | 14 | 234.77MB | 198.52MB | View |
Starter Project Dev Dependencies
| Framework | Dependency count |
|---|---|
| SolidStart | 1 |
| Astro | 2 |
| Nuxt | 2 |
| Next.js | 6 |
| SvelteKit | 7 |
| React Router | 8 |
| TanStack Start | 11 |
The chart includes a dotted median reference line calculated from the visible framework values.
Starter Project Production Dependencies
| Framework | Dependency count |
|---|---|
| SvelteKit | 0 |
| Astro | 1 |
| Next.js | 3 |
| Nuxt | 3 |
| React Router | 6 |
| SolidStart | 6 |
| TanStack Start | 13 |
The chart includes a dotted median reference line calculated from the visible framework values.
Starter Project Duplicate Dependencies
| Framework | Dependency count |
|---|---|
| SvelteKit | 1 |
| SolidStart | 8 |
| React Router | 9 |
| Astro | 11 |
| Next.js | 12 |
| TanStack Start | 14 |
| Nuxt | 63 |
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.
Node modules size
| Framework | Megabytes |
|---|---|
| SvelteKit | 95.65 MB |
| React Router | 106.86 MB |
| SolidStart | 124.34 MB |
| Astro | 207.93 MB |
| Nuxt | 208.80 MB |
| TanStack Start | 234.77 MB |
| Next.js | 560.04 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 | Avg Install | Min Install | Max Install | Avg Cold Build | Avg Warm Build |
|---|---|---|---|---|---|
| Astro | 3.11s | 1.73s | 3.72s | 0.90s | 0.90s |
| Next.js | 5.95s | 3.18s | 7.40s | 5.04s | 5.03s |
| Nuxt | 4.51s | 3.11s | 5.37s | 3.73s | 3.69s |
| React Router | 9.00s | 7.51s | 10.00s | 1.63s | 1.67s |
| SolidStart | 10.28s | 7.09s | 12.88s | 3.01s | 2.89s |
| SvelteKit | 18.29s | 16.03s | 20.82s | 1.91s | 1.70s |
| TanStack Start | 16.31s | 6.84s | 26.90s | 5.68s | 5.35s |
Avg install time
| Framework | Seconds |
|---|---|
| Astro | 3.11s |
| Nuxt | 4.51s |
| Next.js | 5.95s |
| React Router | 9.00s |
| SolidStart | 10.28s |
| TanStack Start | 16.31s |
| SvelteKit | 18.29s |
The chart includes a dotted median reference line calculated from the visible framework values.
Cold build time
| Framework | Seconds |
|---|---|
| Astro | 0.90s |
| React Router | 1.63s |
| SvelteKit | 1.91s |
| SolidStart | 3.01s |
| Nuxt | 3.73s |
| Next.js | 5.04s |
| TanStack Start | 5.68s |
The chart includes a dotted median reference line calculated from the visible framework values.
Warm build time
| Framework | Seconds |
|---|---|
| Astro | 0.90s |
| React Router | 1.67s |
| SvelteKit | 1.70s |
| SolidStart | 2.89s |
| Nuxt | 3.69s |
| Next.js | 5.03s |
| TanStack Start | 5.35s |
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 | Avg Start | Min Start | Max Start |
|---|---|---|---|
| Astro | 1.31s | 1.29s | 1.33s |
| Next.js | 2.43s | 2.35s | 2.59s |
| Nuxt | 4.25s | 2.48s | 7.34s |
| React Router | 0.84s | 0.81s | 0.92s |
| SolidStart | 2.96s | 2.91s | 3.04s |
| SvelteKit | 1.24s | 1.14s | 1.47s |
| TanStack Start | 3.00s | 2.81s | 3.15s |
Avg dev server startup time
| Framework | Seconds |
|---|---|
| React Router | 0.84s |
| SvelteKit | 1.24s |
| Astro | 1.31s |
| Next.js | 2.43s |
| SolidStart | 2.96s |
| TanStack Start | 3.00s |
| Nuxt | 4.25s |
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 | ~Size | Unnecessary Modules |
|---|---|---|
| Astro | — | — |
| Next.js | 110.0 KB | 302 |
| Nuxt | — | — |
| React Router | — | — |
| SolidStart | — | — |
| SvelteKit | — | — |
| TanStack Start | — | — |
Browser Baseline
Section titled “Browser Baseline”Methodology: Browser Baseline.
| Framework | Baseline | Feature | Year | Features |
|---|---|---|---|---|
| Astro | — | — | — | 0 |
| Next.js | High | — | 2022 | 46 |
| Nuxt | Limited | temporal | — | 40 |
| React Router | High | — | 2022 | 40 |
| SolidStart | High | — | 2020 | 30 |
| SvelteKit | High | — | 2020 | 42 |
| TanStack Start | High | — | 2022 | 45 |
Minimum Node Version
Section titled “Minimum Node Version”Methodology: Minimum Node Version.
| Framework | Min Node | Set by |
|---|---|---|
| Astro | v22.12.0 | — |
| Next.js | v20.9.0 | next |
| Nuxt | v20.19.0 | — |
| React Router | v20.19.0 | vite |
| SolidStart | v24.0.0 | @solidjs/start, starter-solid-start |
| SvelteKit | v22.20.0 | @napi-rs/lzma-linux-x64-gnu |
| TanStack Start | v22.12.0 | @tanstack/react-start, @tanstack/react-start-client, @tanstack/react-start-server, @tanstack/start-client-core, @tanstack/start-fn-stubs, @tanstack/start-plugin-core, @tanstack/start-server-core, @tanstack/start-storage-context |
Client Side Rendered Tests
Section titled “Client Side Rendered Tests”Methodology: Client Side Rendered Tests.
| Framework | First Paint | FCP | Interaction Latency | Input Delay | Processing Duration | Presentation Delay |
|---|---|---|---|---|---|---|
| Astro | 103.2ms | 103.21ms | 7.47ms | 1.53ms | 0.97ms | 4.96ms |
| Next.js | 395.8ms | 395.7ms | 20.5ms | 1.32ms | 6.49ms | 12.7ms |
| Nuxt | 149.8ms | 149.95ms | 8.89ms | 0.58ms | 1.31ms | 7ms |
| React Router | 166.4ms | 166.5ms | 19.29ms | 1.5ms | 2.78ms | 15.01ms |
| SolidStart | 115.6ms | 115.64ms | 14.31ms | 1.04ms | 2.38ms | 10.89ms |
| SvelteKit | 128.6ms | 128.78ms | 18.6ms | 0.67ms | 3.36ms | 14.57ms |
| TanStack Start | 153.6ms | 153.82ms | 22.76ms | 1.51ms | 12.7ms | 8.55ms |
First Paint (ms)
| Framework | Milliseconds |
|---|---|
| Astro | 103.20 ms |
| SolidStart | 115.60 ms |
| SvelteKit | 128.60 ms |
| Nuxt | 149.80 ms |
| TanStack Start | 153.60 ms |
| React Router | 166.40 ms |
| Next.js | 395.80 ms |
The chart includes a dotted median reference line calculated from the visible framework values.
First Contentful Paint (ms)
| Framework | Milliseconds |
|---|---|
| Astro | 103.21 ms |
| SolidStart | 115.64 ms |
| SvelteKit | 128.78 ms |
| Nuxt | 149.95 ms |
| TanStack Start | 153.82 ms |
| React Router | 166.50 ms |
| Next.js | 395.70 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 | 7.47 ms | 1.53 ms | 0.97 ms | 4.96 ms |
| Nuxt | 8.89 ms | 0.58 ms | 1.31 ms | 7.00 ms |
| SolidStart | 14.31 ms | 1.04 ms | 2.38 ms | 10.89 ms |
| SvelteKit | 18.60 ms | 0.67 ms | 3.36 ms | 14.57 ms |
| React Router | 19.29 ms | 1.50 ms | 2.78 ms | 15.01 ms |
| Next.js | 20.50 ms | 1.32 ms | 6.49 ms | 12.70 ms |
| TanStack Start | 22.76 ms | 1.51 ms | 12.70 ms | 8.55 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 | 79ms | 79.24ms | 1.14ms | 0.61ms | 0.53ms | 0ms |
| Next.js | 152.2ms | 152.17ms | 18.55ms | 1.31ms | 8.21ms | 9.03ms |
| Nuxt | 122.8ms | 122.98ms | 11.02ms | 0.46ms | 1.95ms | 8.61ms |
| React Router | 108.8ms | 108.9ms | 17.15ms | 1.47ms | 2.54ms | 13.14ms |
| SolidStart | 381.4ms | 381.53ms | 30.02ms | 2.28ms | 3.67ms | 24.07ms |
| SvelteKit | 96ms | 96.12ms | 14.92ms | 1.11ms | 3.35ms | 10.46ms |
| TanStack Start | 126.6ms | 126.76ms | 26.36ms | 2.31ms | 13.87ms | 10.18ms |
First Paint (ms)
| Framework | Milliseconds |
|---|---|
| Astro | 79.00 ms |
| SvelteKit | 96.00 ms |
| React Router | 108.80 ms |
| Nuxt | 122.80 ms |
| TanStack Start | 126.60 ms |
| Next.js | 152.20 ms |
| SolidStart | 381.40 ms |
The chart includes a dotted median reference line calculated from the visible framework values.
First Contentful Paint (ms)
| Framework | Milliseconds |
|---|---|
| Astro | 79.24 ms |
| SvelteKit | 96.12 ms |
| React Router | 108.90 ms |
| Nuxt | 122.98 ms |
| TanStack Start | 126.76 ms |
| Next.js | 152.17 ms |
| SolidStart | 381.53 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.14 ms | 0.61 ms | 0.53 ms | 0.00 ms |
| Nuxt | 11.02 ms | 0.46 ms | 1.95 ms | 8.61 ms |
| SvelteKit | 14.92 ms | 1.11 ms | 3.35 ms | 10.46 ms |
| React Router | 17.15 ms | 1.47 ms | 2.54 ms | 13.14 ms |
| Next.js | 18.55 ms | 1.31 ms | 8.21 ms | 9.03 ms |
| TanStack Start | 26.36 ms | 2.31 ms | 13.87 ms | 10.18 ms |
| SolidStart | 30.02 ms | 2.28 ms | 3.67 ms | 24.07 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 | 842 | 1.203ms | 96.83kb | 1x |
| Astro | 668 | 1.48ms | 96.89kb | 1x |
| Next.js | 216 | 4.725ms | 199.57kb | 2x |
| Nuxt | 335 | 2.897ms | 201.27kb | 2x |
| React Router | 347 | 2.841ms | 211.85kb | 2x |
| SolidStart | 412 | 2.34ms | 224.17kb | 2x |
| SvelteKit | 441 | 2.184ms | 183.53kb | 2x |
| TanStack Start | 319 | 3.07ms | 193.62kb | 2x |
Ops/sec
| Framework | Operations per second |
|---|---|
| Baseline HTML | 842 |
| Astro | 668 |
| SvelteKit | 441 |
| SolidStart | 412 |
| React Router | 347 |
| Nuxt | 335 |
| TanStack Start | 319 |
| Next.js | 216 |
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 | 183.53 KB |
| TanStack Start | 193.62 KB |
| Next.js | 199.57 KB |
| Nuxt | 201.27 KB |
| React Router | 211.85 KB |
| SolidStart | 224.17 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.48 ms |
| SvelteKit | 2.18 ms |
| SolidStart | 2.34 ms |
| React Router | 2.84 ms |
| Nuxt | 2.90 ms |
| TanStack Start | 3.07 ms |
| Next.js | 4.72 ms |
The chart includes a dotted median reference line calculated from the visible framework values.
Server Side Load Test
Section titled “Server Side Load Test”Methodology: Server Side Load Test.
| Framework | Peak req/s | Peak Connections | P99 @ 25 | P99 @ 50 | P99 @ 100 | Total Req. |
|---|---|---|---|---|---|---|
| Baseline HTML | 1,635.6 | 100 | 18ms | 44ms | 107ms | 48,518 |
| Astro | 1,190.6 | 100 | 31ms | 83ms | 326ms | 35,583 |
| Next.js | 41 | 5 | 1914ms | 4793ms | 4713ms | 1,150 |
| Nuxt | 74.6 | 10 | 1949ms | 4084ms | 4268ms | 2,369 |
| React Router | 174.4 | 25 | 329ms | 1745ms | 3971ms | 5,752 |
| SolidStart | 524.21 | 10 | 103ms | 179ms | 2127ms | 16,924 |
| SvelteKit | 498 | 25 | 79ms | 388ms | 2567ms | 15,793 |
| TanStack Start | 43.8 | 5 | 3467ms | 4572ms | 4488ms | 1,337 |
P99 Latency
Section titled “P99 Latency”P99 Latency at 25 Connections
| Framework | Milliseconds |
|---|---|
| Baseline HTML | 18.00 ms |
| Astro | 31.00 ms |
| SvelteKit | 79.00 ms |
| SolidStart | 103.00 ms |
| React Router | 329.00 ms |
| Next.js | 1914.00 ms |
| Nuxt | 1949.00 ms |
| TanStack Start | 3467.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 | 44.00 ms |
| Astro | 83.00 ms |
| SolidStart | 179.00 ms |
| SvelteKit | 388.00 ms |
| React Router | 1745.00 ms |
| Nuxt | 4084.00 ms |
| TanStack Start | 4572.00 ms |
| Next.js | 4793.00 ms |
The chart includes a dotted median reference line calculated from the visible framework values.
P99 Latency at 100 Connections
| Framework | Milliseconds |
|---|---|
| Baseline HTML | 107.00 ms |
| Astro | 326.00 ms |
| SolidStart | 2127.00 ms |
| SvelteKit | 2567.00 ms |
| React Router | 3971.00 ms |
| Nuxt | 4268.00 ms |
| TanStack Start | 4488.00 ms |
| Next.js | 4713.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 |
|---|---|
| Baseline HTML | 17.00 ms |
| Astro | 23.00 ms |
| SvelteKit | 61.00 ms |
| SolidStart | 70.00 ms |
| React Router | 160.00 ms |
| Nuxt | 384.00 ms |
| Next.js | 697.00 ms |
| TanStack Start | 776.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 | 32.00 ms |
| Astro | 43.00 ms |
| SvelteKit | 133.00 ms |
| SolidStart | 153.00 ms |
| React Router | 316.00 ms |
| Nuxt | 470.00 ms |
| TanStack Start | 822.00 ms |
| Next.js | 2407.00 ms |
The chart includes a dotted median reference line calculated from the visible framework values.
P90 Latency at 100 Connections
| Framework | Milliseconds |
|---|---|
| Baseline HTML | 77.00 ms |
| Astro | 85.00 ms |
| SolidStart | 165.00 ms |
| SvelteKit | 214.00 ms |
| React Router | 381.00 ms |
| Nuxt | 497.00 ms |
| TanStack Start | 1341.00 ms |
| Next.js | 2797.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 | 92 | 88 | 92 | 81 | 98 |
| SolidStart | 81 | 75 | 100 | 88 | 100 |
| SvelteKit | 79 | 78 | 78 | 69 | 95 |
| Next.js | 73 | 71 | 76 | 66 | 94 |
| Nuxt | 67 | 58 | 70 | 59 | 96 |
| React Router | 59 | 60 | 64 | 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 | % |
|---|---|
| Astro | 92 |
| SolidStart | 81 |
| SvelteKit | 79 |
| Next.js | 73 |
| Nuxt | 67 |
| React Router | 59 |
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 | 88 |
| SvelteKit | 78 |
| SolidStart | 75 |
| Next.js | 71 |
| React Router | 60 |
| 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 | 78 |
| Next.js | 76 |
| Nuxt | 70 |
| React Router | 64 |
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 | 88 |
| Astro | 81 |
| SvelteKit | 69 |
| React Router | 68 |
| Next.js | 66 |
| Nuxt | 59 |
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 |
| 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% |
|---|---|---|---|---|---|
| SolidStart | 80 | 80 | 100 | 87 | 90 |
| Astro | 79 | 93 | 72 | 63 | 85 |
| SvelteKit | 67 | 80 | 58 | 55 | 74 |
| Next.js | 52 | 71 | 48 | 46 | 58 |
| Nuxt | 45 | 58 | 43 | 45 | 65 |
| React Router | 37 | 63 | 36 | 51 | 53 |
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 | 80 |
| Astro | 79 |
| SvelteKit | 67 |
| Next.js | 52 |
| Nuxt | 45 |
| React Router | 37 |
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 |
| SolidStart | 80 |
| SvelteKit | 80 |
| Next.js | 71 |
| React Router | 63 |
| 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 | 72 |
| SvelteKit | 58 |
| Next.js | 48 |
| Nuxt | 43 |
| React Router | 36 |
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 | 87 |
| Astro | 63 |
| SvelteKit | 55 |
| React Router | 51 |
| Next.js | 46 |
| Nuxt | 45 |
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 | 90 |
| Astro | 85 |
| SvelteKit | 74 |
| Nuxt | 65 |
| Next.js | 58 |
| React Router | 53 |
The chart includes a dotted median reference line calculated from the visible framework values.
Methodology: Core Web Vitals.