Skip to content

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 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.

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:

  1. Start with the meta-framework package itself, for example, @sveltejs/kit
  2. We then expand this to the meta-framework and its first-party packages. Looking at @sveltejs/kit again, this means any package maintained by the meta-framework authors that’s needed to run a project, for example, the svelte package.
  3. 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.

The meta-framework package itself, for example, @sveltejs/kit.

Core Package Dependencies
Core Package Dependencies data
FrameworkDependency count
Pracht5
Next.js6
SvelteKit23
TanStack Start23
SolidStart29
React Router47
Astro77
Nuxt79

The chart includes a dotted median reference line calculated from the visible framework values.

Core Package Development Dependencies
Core Package Development Dependencies data
FrameworkDependency count
Next.js0
Pracht2
SolidStart5
Nuxt13
TanStack Start14
SvelteKit15
React Router24
Astro25

The chart includes a dotted median reference line calculated from the visible framework values.

Core Package Production Dependencies
Core Package Production Dependencies data
FrameworkDependency count
Pracht3
Next.js6
SvelteKit8
TanStack Start9
React Router23
SolidStart24
Astro52
Nuxt66

The chart includes a dotted median reference line calculated from the visible framework values.

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.

FrameworkDeps Dev / ProdAll DepsDup. DepsGraph
Astro1 / 133314View
Next.js1 / 138812View
Nuxt0 / 163476View
Pracht2 / 22184View
React Router1 / 32265View
SolidStart0 / 42126View
SvelteKit5 / 01081View
TanStack Start1 / 71943View
First-Party Dependencies
First-Party Dependencies data
FrameworkDependency count
SvelteKit108
TanStack Start194
SolidStart212
Pracht218
React Router226
Astro333
Next.js388
Nuxt634

The chart includes a dotted median reference line calculated from the visible framework values.

First-Party Development Dependencies
First-Party Development Dependencies data
FrameworkDependency count
Nuxt0
SolidStart0
Astro1
Next.js1
React Router1
TanStack Start1
Pracht2
SvelteKit5

The chart includes a dotted median reference line calculated from the visible framework values.

First-Party Production Dependencies
First-Party Production Dependencies data
FrameworkDependency count
SvelteKit0
Astro1
Next.js1
Nuxt1
Pracht2
React Router3
SolidStart4
TanStack Start7

The chart includes a dotted median reference line calculated from the visible framework values.

First-Party Duplicate Dependencies
First-Party Duplicate Dependencies data
FrameworkDependency count
SvelteKit1
TanStack Start3
Pracht4
React Router5
SolidStart6
Next.js12
Astro14
Nuxt76

The chart includes a dotted median reference line calculated from the visible framework values.

Finally, we look at the complete dependency footprint of the default starter project, including third-party packages selected by its CLI or documented setup.

FrameworkDeps Dev / ProdAll DepsDup. Depsnode_modulesDep Install SizeGraph
Astro2 / 133314204.22MB172.07MBView
Next.js6 / 342412463.42MB405.08MBView
Nuxt3 / 363476246.14MB213.96MBView
Pracht6 / 22394132.56MB109.29MBView
React Router9 / 62495109.35MB103.24MBView
SolidStart1 / 626123149.17MB125.07MBView
SvelteKit8 / 0108188.32MB92.09MBView
TanStack Start12 / 1433037274.09MB230.99MBView
Starter Project · Development Dependencies
Starter Project · Development Dependencies data
FrameworkDependencies
SolidStart1
Astro2
Nuxt3
Next.js6
Pracht6
SvelteKit8
React Router9
TanStack Start12

The chart includes a dotted median reference line calculated from the visible framework values.

Starter Project · Production Dependencies
Starter Project · Production Dependencies data
FrameworkDependencies
SvelteKit0
Astro1
Pracht2
Next.js3
Nuxt3
React Router6
SolidStart6
TanStack Start14

The chart includes a dotted median reference line calculated from the visible framework values.

Starter Project · Duplicate Dependencies
Starter Project · Duplicate Dependencies data
FrameworkDuplicates
SvelteKit1
Pracht4
React Router5
Next.js12
Astro14
SolidStart23
TanStack Start37
Nuxt76

The chart includes a dotted median reference line calculated from the visible framework values.

Methodology: Node Modules Size.

Node Modules Size
Node Modules Size data
FrameworkMB
SvelteKit88.32 MB
React Router109.35 MB
Pracht132.56 MB
SolidStart149.17 MB
Astro204.22 MB
Nuxt246.14 MB
TanStack Start274.09 MB
Next.js463.42 MB

The chart includes a dotted median reference line calculated from the visible framework values.

Methodology: Build and Install Times.

FrameworkMedian InstallMin InstallMax InstallMedian Cold BuildMedian Warm Build
Astro3.94s1.66s4.32s1.00s0.95s
Next.js6.15s3.31s6.76s5.17s2.33s
Nuxt5.60s3.91s6.84s4.00s3.81s
Pracht2.04s1.67s2.74s0.71s0.68s
React Router1.48s1.25s1.58s1.59s1.62s
SolidStart2.40s1.70s2.54s3.09s2.95s
SvelteKit1.89s1.67s2.08s1.82s1.62s
TanStack Start5.30s2.12s5.49s2.03s1.82s
Median Install Time
Median Install Time data
FrameworkSeconds
React Router1.48s
SvelteKit1.89s
Pracht2.04s
SolidStart2.40s
Astro3.94s
TanStack Start5.30s
Nuxt5.60s
Next.js6.15s

The chart includes a dotted median reference line calculated from the visible framework values.

Median Cold Build Time
Median Cold Build Time data
FrameworkSeconds
Pracht0.71s
Astro1.00s
React Router1.59s
SvelteKit1.82s
TanStack Start2.03s
SolidStart3.09s
Nuxt4.00s
Next.js5.17s

The chart includes a dotted median reference line calculated from the visible framework values.

Median Warm Build Time
Median Warm Build Time data
FrameworkSeconds
Pracht0.68s
Astro0.95s
React Router1.62s
SvelteKit1.62s
TanStack Start1.82s
Next.js2.33s
SolidStart2.95s
Nuxt3.81s

The chart includes a dotted median reference line calculated from the visible framework values.

Methodology: Dev Server Startup.

FrameworkMedian StartMin StartMax Start
Astro1.36s1.32s1.52s
Next.js2.29s2.15s2.36s
Nuxt2.79s2.75s2.82s
Pracht0.98s0.94s1.47s
React Router0.98s0.96s1.03s
SolidStart2.83s2.79s3.38s
SvelteKit1.37s1.27s1.66s
TanStack Start2.05s1.95s2.46s
Median Dev Server Startup Time
Median Dev Server Startup Time data
FrameworkSeconds
Pracht0.98s
React Router0.98s
Astro1.36s
SvelteKit1.37s
TanStack Start2.05s
Next.js2.29s
Nuxt2.79s
SolidStart2.83s

The chart includes a dotted median reference line calculated from the visible framework values.

Methodology: Core-JS Polyfills.

FrameworkCore-JS detectedMatching JS filesModules not needed by target browsers
AstroNo——
Next.jsYes110.0 KB302
NuxtNo——
PrachtNo——
React RouterNo——
SolidStartNo——
SvelteKitNo——
TanStack StartNo——

Methodology: Browser Baseline.

FrameworkBaselineFeatureYearFeatures
Astro———0
Next.jsHigh—202247
NuxtHigh—202342
PrachtHigh—202037
React RouterHigh—202244
SolidStartHigh—202031
SvelteKitLimitedtemporal—48
TanStack StartLimitedtemporal—49

Methodology: Minimum Node Version.

FrameworkMin NodeSet by
Astrov22.23.4@astrojs/prism, @astrojs/telemetry, astro
Next.jsv20.19.0eslint-visitor-keys
Nuxtv22.22.3@nuxt/nitro-server, @nuxt/vite-builder, @nuxt/vite-server, cssnano, nuxt, postcss-calc
Prachtv22.18.0@pracht/adapter-node, @pracht/capabilities, @pracht/cli, @pracht/core, @pracht/preact-ssr-precompile, @pracht/vite-plugin
React Routerv22.22.0@react-router/dev, @react-router/express, @react-router/node, @react-router/serve, react-router
SolidStartv24.0.0@solidjs/start, starter-solid-start
SvelteKitv22.17.0@sveltejs/kit
TanStack Startv22.22.2@asamuzakjp/css-color, @asamuzakjp/dom-selector, jsdom, w3c-xmlserializer

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.

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.

FrameworkFirst PaintFCPInteraction LatencyInput DelayProcessing DurationPresentation Delay
Astro97ms97.083ms2.264ms1.902ms0.362ms0ms
Next.js337ms337.141ms21.88ms1.161ms4.53ms16.189ms
Nuxt161ms160.954ms15.207ms0.832ms1.458ms12.917ms
Pracht109ms108.779ms19.313ms0.808ms3.195ms15.31ms
React Router173ms172.621ms17.674ms1.621ms5.027ms11.026ms
SolidStart97ms97.103ms18.946ms0.976ms2.018ms15.952ms
SvelteKit108ms108.186ms17.399ms0.67ms1.751ms14.978ms
TanStack Start122ms121.746ms23.325ms1.347ms3.044ms18.934ms
Client First Paint (Lighthouse)
Client First Paint (Lighthouse) data
FrameworkMilliseconds
Astro97.00 ms
SolidStart97.00 ms
SvelteKit108.00 ms
Pracht109.00 ms
TanStack Start122.00 ms
Nuxt161.00 ms
React Router173.00 ms
Next.js337.00 ms

The chart includes a dotted median reference line calculated from the visible framework values.

Client FCP (Lighthouse)
Client FCP (Lighthouse) data
FrameworkMilliseconds
Astro97.08 ms
SolidStart97.10 ms
SvelteKit108.19 ms
Pracht108.78 ms
TanStack Start121.75 ms
Nuxt160.95 ms
React Router172.62 ms
Next.js337.14 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.
2.26 ms
15.21 ms
17.40 ms
17.67 ms
18.95 ms
19.31 ms
21.88 ms
23.33 ms
Interaction Breakdown (Lighthouse) data
Framework or versionInteraction latencyInput delayProcessing durationPresentation delay
Astro2.26 ms1.90 ms0.36 ms0.00 ms
Nuxt15.21 ms0.83 ms1.46 ms12.92 ms
SvelteKit17.40 ms0.67 ms1.75 ms14.98 ms
React Router17.67 ms1.62 ms5.03 ms11.03 ms
SolidStart18.95 ms0.98 ms2.02 ms15.95 ms
Pracht19.31 ms0.81 ms3.19 ms15.31 ms
Next.js21.88 ms1.16 ms4.53 ms16.19 ms
TanStack Start23.33 ms1.35 ms3.04 ms18.93 ms

These SSR browser performance tests use Lighthouse to measure paint timings and a controlled navigation interaction.

Methodology: Server Side Rendered Tests (Lighthouse).

FrameworkFirst PaintFCPInteraction LatencyInput DelayProcessing DurationPresentation Delay
Astro57ms57.414ms0.9ms0.642ms0.258ms0ms
Next.js383ms383.007ms23.416ms1.851ms8.77ms12.795ms
Nuxt86ms86.462ms13.817ms0.89ms2.073ms10.854ms
Pracht88ms87.59ms18.17ms0.846ms1.712ms15.612ms
React Router121ms121.017ms15.734ms1.672ms6.621ms7.441ms
SolidStart82ms81.711ms17.779ms0.911ms2.887ms13.981ms
SvelteKit82ms82.24ms15.139ms0.915ms2.352ms11.872ms
TanStack Start89ms89.366ms22.231ms1.343ms3.862ms17.026ms
Server First Paint (Lighthouse)
Server First Paint (Lighthouse) data
FrameworkMilliseconds
Astro57.00 ms
SolidStart82.00 ms
SvelteKit82.00 ms
Nuxt86.00 ms
Pracht88.00 ms
TanStack Start89.00 ms
React Router121.00 ms
Next.js383.00 ms

The chart includes a dotted median reference line calculated from the visible framework values.

Server FCP (Lighthouse)
Server FCP (Lighthouse) data
FrameworkMilliseconds
Astro57.41 ms
SolidStart81.71 ms
SvelteKit82.24 ms
Nuxt86.46 ms
Pracht87.59 ms
TanStack Start89.37 ms
React Router121.02 ms
Next.js383.01 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.
0.90 ms
13.82 ms
15.14 ms
15.73 ms
17.78 ms
18.17 ms
22.23 ms
23.42 ms
Interaction Breakdown (Lighthouse) data
Framework or versionInteraction latencyInput delayProcessing durationPresentation delay
Astro0.90 ms0.64 ms0.26 ms0.00 ms
Nuxt13.82 ms0.89 ms2.07 ms10.85 ms
SvelteKit15.14 ms0.92 ms2.35 ms11.87 ms
React Router15.73 ms1.67 ms6.62 ms7.44 ms
SolidStart17.78 ms0.91 ms2.89 ms13.98 ms
Pracht18.17 ms0.85 ms1.71 ms15.61 ms
TanStack Start22.23 ms1.34 ms3.86 ms17.03 ms
Next.js23.42 ms1.85 ms8.77 ms12.79 ms

Methodology: Server Side Throughput Tests.

FrameworkOps/secMedian LatencyBody SizeDuplication
Baseline HTML8331.211ms96.83kb1x
Astro7781.364ms96.89kb1x
Next.js1427.24ms204.56kb2x
Nuxt3652.87ms201.73kb2x
Pracht6101.708ms187.02kb2x
React Router3472.91ms216.84kb2x
SolidStart3752.742ms224.22kb2x
SvelteKit4552.233ms184.29kb2x
TanStack Start3622.787ms192.53kb2x
Ops/sec
Ops/sec data
FrameworkOperations per second
Baseline HTML833
Astro778
Pracht610
SvelteKit455
SolidStart375
Nuxt365
TanStack Start362
React Router347
Next.js142

The chart includes a dotted median reference line calculated from the visible framework values.

Body Size
Body Size data
FrameworkKilobytes
Baseline HTML96.83 KB
Astro96.89 KB
SvelteKit184.29 KB
Pracht187.02 KB
TanStack Start192.53 KB
Nuxt201.73 KB
Next.js204.56 KB
React Router216.84 KB
SolidStart224.22 KB

The chart includes a dotted median reference line calculated from the visible framework values.

Median Latency

Median of measured run average latencies; not a pooled request-level median.

Median Latency data
FrameworkMilliseconds
Baseline HTML1.21 ms
Astro1.36 ms
Pracht1.71 ms
SvelteKit2.23 ms
SolidStart2.74 ms
TanStack Start2.79 ms
Nuxt2.87 ms
React Router2.91 ms
Next.js7.24 ms

The chart includes a dotted median reference line calculated from the visible framework values.

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.

FrameworkRepresentative peak req/sRepresentative peak connectionsMedian sweep P99 @ 25Median sweep P99 @ 50Median sweep P99 @ 100Total measured requests
Baseline HTML1,782.210017ms32ms96ms153,613
Astro1,626.82522ms49ms93ms144,438
Next.js55.451,193ms4,193ms4,593ms4,894
Nuxt51010080ms391ms2,829ms49,759
Pracht677.62542ms103ms1,034ms64,071
React Router303.225108ms757ms3,590ms29,583
SolidStart5711088ms325ms2,033ms54,914
SvelteKit590.62575ms226ms1,976ms56,792
TanStack Start415.850106ms571ms2,572ms40,817
Median Sweep P99 Latency at 25 Connections
Median Sweep P99 Latency at 25 Connections data
FrameworkMilliseconds
Baseline HTML17.00 ms
Astro22.00 ms
Pracht42.00 ms
SvelteKit75.00 ms
Nuxt80.00 ms
SolidStart88.00 ms
TanStack Start106.00 ms
React Router108.00 ms
Next.js1193.00 ms

The chart includes a dotted median reference line calculated from the visible framework values.

Median Sweep P99 Latency at 50 Connections
Median Sweep P99 Latency at 50 Connections data
FrameworkMilliseconds
Baseline HTML32.00 ms
Astro49.00 ms
Pracht103.00 ms
SvelteKit226.00 ms
SolidStart325.00 ms
Nuxt391.00 ms
TanStack Start571.00 ms
React Router757.00 ms
Next.js4193.00 ms

The chart includes a dotted median reference line calculated from the visible framework values.

Median Sweep P99 Latency at 100 Connections
Median Sweep P99 Latency at 100 Connections data
FrameworkMilliseconds
Astro93.00 ms
Baseline HTML96.00 ms
Pracht1034.00 ms
SvelteKit1976.00 ms
SolidStart2033.00 ms
TanStack Start2572.00 ms
Nuxt2829.00 ms
React Router3590.00 ms
Next.js4593.00 ms

The chart includes a dotted median reference line calculated from the visible framework values.

Median Sweep P90 Latency at 25 Connections
Median Sweep P90 Latency at 25 Connections data
FrameworkMilliseconds
Astro16.00 ms
Baseline HTML16.00 ms
Pracht38.00 ms
Nuxt53.00 ms
SvelteKit54.00 ms
SolidStart64.00 ms
TanStack Start82.00 ms
React Router85.00 ms
Next.js499.00 ms

The chart includes a dotted median reference line calculated from the visible framework values.

Median Sweep P90 Latency at 50 Connections
Median Sweep P90 Latency at 50 Connections data
FrameworkMilliseconds
Baseline HTML30.00 ms
Astro32.00 ms
Pracht77.00 ms
Nuxt102.00 ms
SvelteKit114.00 ms
SolidStart137.00 ms
TanStack Start164.00 ms
React Router180.00 ms
Next.js1807.00 ms

The chart includes a dotted median reference line calculated from the visible framework values.

Median Sweep P90 Latency at 100 Connections
Median Sweep P90 Latency at 100 Connections data
FrameworkMilliseconds
Astro63.00 ms
Baseline HTML70.00 ms
SolidStart146.00 ms
Pracht153.00 ms
SvelteKit182.00 ms
Nuxt187.00 ms
TanStack Start232.00 ms
React Router300.00 ms
Next.js2234.00 ms

The chart includes a dotted median reference line calculated from the visible framework values.

Median Sweep P75 Latency at 25 Connections
Median Sweep P75 Latency at 25 Connections data
FrameworkMilliseconds
Baseline HTML14.00 ms
Astro15.00 ms
Pracht37.00 ms
SvelteKit43.00 ms
Nuxt50.00 ms
SolidStart54.00 ms
TanStack Start65.00 ms
React Router83.00 ms
Next.js478.00 ms

The chart includes a dotted median reference line calculated from the visible framework values.

Median Sweep P75 Latency at 50 Connections
Median Sweep P75 Latency at 50 Connections data
FrameworkMilliseconds
Baseline HTML30.00 ms
Astro31.00 ms
Pracht75.00 ms
SolidStart86.00 ms
SvelteKit93.00 ms
Nuxt97.00 ms
TanStack Start132.00 ms
React Router171.00 ms
Next.js951.00 ms

The chart includes a dotted median reference line calculated from the visible framework values.

Median Sweep P75 Latency at 100 Connections
Median Sweep P75 Latency at 100 Connections data
FrameworkMilliseconds
Baseline HTML57.00 ms
Astro61.00 ms
SolidStart120.00 ms
SvelteKit139.00 ms
Pracht149.00 ms
TanStack Start163.00 ms
Nuxt171.00 ms
React Router286.00 ms
Next.js992.00 ms

The chart includes a dotted median reference line calculated from the visible framework values.

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.

FrameworkRepresentative peak req/sRepresentative peak connectionsMedian sweep P99 @ 25Median sweep P99 @ 50Median sweep P99 @ 100Total measured requests
Next.js49.651,330ms4,597ms4,788ms4,483
Nuxt165.45539ms3,055ms3,802ms16,313
Pracht371.62593ms453ms3,144ms34,660
React Router17650287ms1,627ms3,963ms17,221
TanStack Start255.25179ms1,678ms3,019ms25,379
Median Sweep P99 Latency at 25 Connections
Median Sweep P99 Latency at 25 Connections data
FrameworkMilliseconds
Pracht93.00 ms
TanStack Start179.00 ms
React Router287.00 ms
Nuxt539.00 ms
Next.js1330.00 ms

The chart includes a dotted median reference line calculated from the visible framework values.

Median Sweep P99 Latency at 50 Connections
Median Sweep P99 Latency at 50 Connections data
FrameworkMilliseconds
Pracht453.00 ms
React Router1627.00 ms
TanStack Start1678.00 ms
Nuxt3055.00 ms
Next.js4597.00 ms

The chart includes a dotted median reference line calculated from the visible framework values.

Median Sweep P99 Latency at 100 Connections
Median Sweep P99 Latency at 100 Connections data
FrameworkMilliseconds
TanStack Start3019.00 ms
Pracht3144.00 ms
Nuxt3802.00 ms
React Router3963.00 ms
Next.js4788.00 ms

The chart includes a dotted median reference line calculated from the visible framework values.

Median Sweep P90 Latency at 25 Connections
Median Sweep P90 Latency at 25 Connections data
FrameworkMilliseconds
Pracht71.00 ms
TanStack Start122.00 ms
React Router160.00 ms
Nuxt161.00 ms
Next.js543.00 ms

The chart includes a dotted median reference line calculated from the visible framework values.

Median Sweep P90 Latency at 50 Connections
Median Sweep P90 Latency at 50 Connections data
FrameworkMilliseconds
Pracht143.00 ms
TanStack Start268.00 ms
React Router296.00 ms
Nuxt305.00 ms
Next.js2141.00 ms

The chart includes a dotted median reference line calculated from the visible framework values.

Median Sweep P90 Latency at 100 Connections
Median Sweep P90 Latency at 100 Connections data
FrameworkMilliseconds
Pracht287.00 ms
TanStack Start297.00 ms
Nuxt331.00 ms
React Router409.00 ms
Next.js2475.00 ms

The chart includes a dotted median reference line calculated from the visible framework values.

Median Sweep P75 Latency at 25 Connections
Median Sweep P75 Latency at 25 Connections data
FrameworkMilliseconds
Pracht68.00 ms
TanStack Start98.00 ms
React Router142.00 ms
Nuxt154.00 ms
Next.js526.00 ms

The chart includes a dotted median reference line calculated from the visible framework values.

Median Sweep P75 Latency at 50 Connections
Median Sweep P75 Latency at 50 Connections data
FrameworkMilliseconds
Pracht136.00 ms
TanStack Start200.00 ms
React Router279.00 ms
Nuxt292.00 ms
Next.js1053.00 ms

The chart includes a dotted median reference line calculated from the visible framework values.

Median Sweep P75 Latency at 100 Connections
Median Sweep P75 Latency at 100 Connections data
FrameworkMilliseconds
TanStack Start213.00 ms
Pracht263.00 ms
Nuxt308.00 ms
React Router369.00 ms
Next.js1033.00 ms

The chart includes a dotted median reference line calculated from the visible framework values.

Methodology: Core Web Vitals.

FrameworkLCP%CLS%FCP%TTFB%INP%
Astro9389928198
SolidStart1007710085100
SvelteKit7978776895
Next.js7472766694
TanStack Start5581462991
Nuxt6858695996
React Router5961656890
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.

Good Largest Contentful Paint data
Framework%
SolidStart100
Astro93
SvelteKit79
Next.js74
Nuxt68
React Router59
TanStack Start55

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.

Good Cumulative Layout Shift data
Framework%
Astro89
TanStack Start81
SvelteKit78
SolidStart77
Next.js72
React Router61
Nuxt58

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.

Good First Contentful Paint data
Framework%
SolidStart100
Astro92
SvelteKit77
Next.js76
Nuxt69
React Router65
TanStack Start46

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.

Good Time To First Byte data
Framework%
SolidStart85
Astro81
React Router68
SvelteKit68
Next.js66
Nuxt59
TanStack Start29

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.

Good Interaction to Next Paint data
Framework%
SolidStart100
Astro98
Nuxt96
SvelteKit95
Next.js94
TanStack Start91
React Router90

The chart includes a dotted median reference line calculated from the visible framework values.

FrameworkLCP%CLS%FCP%TTFB%INP%
Astro8093736485
SolidStart8866888575
SvelteKit6781585474
Next.js5372484559
Nuxt4659444665
React Router3763375053
TanStack Start3184191351
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.

Good Largest Contentful Paint data
Framework%
SolidStart88
Astro80
SvelteKit67
Next.js53
Nuxt46
React Router37
TanStack Start31

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.

Good Cumulative Layout Shift data
Framework%
Astro93
TanStack Start84
SvelteKit81
Next.js72
SolidStart66
React Router63
Nuxt59

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.

Good First Contentful Paint data
Framework%
SolidStart88
Astro73
SvelteKit58
Next.js48
Nuxt44
React Router37
TanStack Start19

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.

Good Time To First Byte data
Framework%
SolidStart85
Astro64
SvelteKit54
React Router50
Nuxt46
Next.js45
TanStack Start13

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.

Good Interaction to Next Paint data
Framework%
Astro85
SolidStart75
SvelteKit74
Nuxt65
Next.js59
React Router53
TanStack Start51

The chart includes a dotted median reference line calculated from the visible framework values.