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
SolidStart4
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
SolidStart25
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 / 42104View
SvelteKit5 / 01081View
TanStack Start1 / 71943View
First-Party Dependencies
First-Party Dependencies data
FrameworkDependency count
SvelteKit108
TanStack Start194
SolidStart210
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
SolidStart4
React Router5
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 / 62425128.50MB104.51MBView
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
SolidStart5
Next.js12
Astro14
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
SolidStart128.50 MB
Pracht132.56 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
Astro4.37s1.88s4.72s0.90s0.86s
Next.js7.08s3.53s7.81s5.76s2.42s
Nuxt6.08s3.50s6.50s4.37s4.13s
Pracht2.12s1.65s2.29s0.77s0.76s
React Router1.48s1.28s1.69s2.06s1.97s
SolidStart2.00s1.54s2.35s3.40s3.18s
SvelteKit1.59s1.41s2.69s1.93s1.75s
TanStack Start5.39s2.16s5.72s2.25s2.01s
Median Install Time
Median Install Time data
FrameworkSeconds
React Router1.48s
SvelteKit1.59s
SolidStart2.00s
Pracht2.12s
Astro4.37s
TanStack Start5.39s
Nuxt6.08s
Next.js7.08s

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.77s
Astro0.90s
SvelteKit1.93s
React Router2.06s
TanStack Start2.25s
SolidStart3.40s
Nuxt4.37s
Next.js5.76s

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.76s
Astro0.86s
SvelteKit1.75s
React Router1.97s
TanStack Start2.01s
Next.js2.42s
SolidStart3.18s
Nuxt4.13s

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

Methodology: Dev Server Startup.

FrameworkMedian StartMin StartMax Start
Astro1.46s1.43s2.06s
Next.js2.13s2.04s2.27s
Nuxt2.56s2.49s3.11s
Pracht1.22s1.06s1.41s
React Router0.91s0.89s0.92s
SolidStart2.73s2.56s2.89s
SvelteKit1.23s1.18s1.33s
TanStack Start1.71s1.70s2.16s
Median Dev Server Startup Time
Median Dev Server Startup Time data
FrameworkSeconds
React Router0.91s
Pracht1.22s
SvelteKit1.23s
Astro1.46s
TanStack Start1.71s
Next.js2.13s
Nuxt2.56s
SolidStart2.73s

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—202033
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
Astro91ms90.752ms2.195ms1.912ms0.283ms0ms
Next.js347ms347.385ms16.595ms1.541ms5.809ms9.245ms
Nuxt151ms151.182ms14.648ms1.589ms1.428ms11.631ms
Pracht110ms110.243ms20.946ms0.74ms2.555ms17.651ms
React Router181ms180.939ms19.979ms1.732ms2.974ms15.273ms
SolidStart89ms89.046ms17.236ms0.94ms2.038ms14.258ms
SvelteKit107ms107.11ms14.374ms0.833ms4.422ms9.119ms
TanStack Start146ms145.627ms21.586ms1.546ms3.665ms16.375ms
Client First Paint (Lighthouse)
Client First Paint (Lighthouse) data
FrameworkMilliseconds
SolidStart89.00 ms
Astro91.00 ms
SvelteKit107.00 ms
Pracht110.00 ms
TanStack Start146.00 ms
Nuxt151.00 ms
React Router181.00 ms
Next.js347.00 ms

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

Client FCP (Lighthouse)
Client FCP (Lighthouse) data
FrameworkMilliseconds
SolidStart89.05 ms
Astro90.75 ms
SvelteKit107.11 ms
Pracht110.24 ms
TanStack Start145.63 ms
Nuxt151.18 ms
React Router180.94 ms
Next.js347.38 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.19 ms
14.37 ms
14.65 ms
16.59 ms
17.24 ms
19.98 ms
20.95 ms
21.59 ms
Interaction Breakdown (Lighthouse) data
Framework or versionInteraction latencyInput delayProcessing durationPresentation delay
Astro2.19 ms1.91 ms0.28 ms0.00 ms
SvelteKit14.37 ms0.83 ms4.42 ms9.12 ms
Nuxt14.65 ms1.59 ms1.43 ms11.63 ms
Next.js16.59 ms1.54 ms5.81 ms9.24 ms
SolidStart17.24 ms0.94 ms2.04 ms14.26 ms
React Router19.98 ms1.73 ms2.97 ms15.27 ms
Pracht20.95 ms0.74 ms2.56 ms17.65 ms
TanStack Start21.59 ms1.55 ms3.67 ms16.38 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
Astro56ms55.515ms0.817ms0.541ms0.276ms0ms
Next.js382ms381.755ms23.21ms4.344ms7.313ms11.553ms
Nuxt93ms93.39ms9.909ms0.681ms4.728ms4.5ms
Pracht81ms81.155ms19.135ms1.059ms2.279ms15.797ms
React Router117ms116.935ms21.136ms1.532ms2.779ms16.825ms
SolidStart90ms90.069ms13.709ms1.019ms3.809ms8.881ms
SvelteKit81ms81.043ms17.826ms0.764ms1.822ms15.24ms
TanStack Start88ms88.256ms20.63ms1.32ms3.501ms15.809ms
Server First Paint (Lighthouse)
Server First Paint (Lighthouse) data
FrameworkMilliseconds
Astro56.00 ms
Pracht81.00 ms
SvelteKit81.00 ms
TanStack Start88.00 ms
SolidStart90.00 ms
Nuxt93.00 ms
React Router117.00 ms
Next.js382.00 ms

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

Server FCP (Lighthouse)
Server FCP (Lighthouse) data
FrameworkMilliseconds
Astro55.52 ms
SvelteKit81.04 ms
Pracht81.16 ms
TanStack Start88.26 ms
SolidStart90.07 ms
Nuxt93.39 ms
React Router116.94 ms
Next.js381.75 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.82 ms
9.91 ms
13.71 ms
17.83 ms
19.14 ms
20.63 ms
21.14 ms
23.21 ms
Interaction Breakdown (Lighthouse) data
Framework or versionInteraction latencyInput delayProcessing durationPresentation delay
Astro0.82 ms0.54 ms0.28 ms0.00 ms
Nuxt9.91 ms0.68 ms4.73 ms4.50 ms
SolidStart13.71 ms1.02 ms3.81 ms8.88 ms
SvelteKit17.83 ms0.76 ms1.82 ms15.24 ms
Pracht19.14 ms1.06 ms2.28 ms15.80 ms
TanStack Start20.63 ms1.32 ms3.50 ms15.81 ms
React Router21.14 ms1.53 ms2.78 ms16.82 ms
Next.js23.21 ms4.34 ms7.31 ms11.55 ms

Methodology: Server Side Throughput Tests.

FrameworkOps/secMedian LatencyBody SizeDuplication
Baseline HTML8311.217ms96.83kb1x
Astro7621.409ms96.89kb1x
Next.js1327.871ms204.56kb2x
Nuxt4122.503ms201.73kb2x
Pracht6001.745ms187.02kb2x
React Router3363.002ms216.84kb2x
SolidStart3862.64ms224.26kb2x
SvelteKit4482.261ms184.3kb2x
TanStack Start3532.86ms192.53kb2x
Ops/sec
Ops/sec data
FrameworkOperations per second
Baseline HTML831
Astro762
Pracht600
SvelteKit448
Nuxt412
SolidStart386
TanStack Start353
React Router336
Next.js132

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.30 KB
Pracht187.02 KB
TanStack Start192.53 KB
Nuxt201.73 KB
Next.js204.56 KB
React Router216.84 KB
SolidStart224.26 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.22 ms
Astro1.41 ms
Pracht1.75 ms
SvelteKit2.26 ms
Nuxt2.50 ms
SolidStart2.64 ms
TanStack Start2.86 ms
React Router3.00 ms
Next.js7.87 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,796.410017ms38ms96ms154,824
Astro1,6042522ms46ms95ms142,597
Next.js50.6101,264ms4,265ms4,667ms4,598
Nuxt544.810071ms297ms2,540ms52,286
Pracht623.215044ms116ms1,350ms58,675
React Router319.225109ms615ms3,589ms30,126
SolidStart5585093ms314ms2,042ms54,065
SvelteKit5752576ms265ms2,102ms55,745
TanStack Start409100114ms656ms2,686ms40,588
Median Sweep P99 Latency at 25 Connections
Median Sweep P99 Latency at 25 Connections data
FrameworkMilliseconds
Baseline HTML17.00 ms
Astro22.00 ms
Pracht44.00 ms
Nuxt71.00 ms
SvelteKit76.00 ms
SolidStart93.00 ms
React Router109.00 ms
TanStack Start114.00 ms
Next.js1264.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 HTML38.00 ms
Astro46.00 ms
Pracht116.00 ms
SvelteKit265.00 ms
Nuxt297.00 ms
SolidStart314.00 ms
React Router615.00 ms
TanStack Start656.00 ms
Next.js4265.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
Astro95.00 ms
Baseline HTML96.00 ms
Pracht1350.00 ms
SolidStart2042.00 ms
SvelteKit2102.00 ms
Nuxt2540.00 ms
TanStack Start2686.00 ms
React Router3589.00 ms
Next.js4667.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
Astro17.00 ms
Baseline HTML17.00 ms
Pracht41.00 ms
Nuxt47.00 ms
SvelteKit55.00 ms
SolidStart65.00 ms
React Router81.00 ms
TanStack Start81.00 ms
Next.js527.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
Pracht86.00 ms
Nuxt97.00 ms
SvelteKit121.00 ms
SolidStart137.00 ms
TanStack Start155.00 ms
React Router176.00 ms
Next.js1830.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
Astro64.00 ms
Baseline HTML69.00 ms
SolidStart163.00 ms
Pracht169.00 ms
Nuxt182.00 ms
SvelteKit186.00 ms
TanStack Start239.00 ms
React Router292.00 ms
Next.js2396.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
Astro16.00 ms
Pracht41.00 ms
SvelteKit44.00 ms
Nuxt46.00 ms
SolidStart57.00 ms
TanStack Start63.00 ms
React Router78.00 ms
Next.js495.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 HTML29.00 ms
Astro31.00 ms
Pracht82.00 ms
SolidStart89.00 ms
Nuxt91.00 ms
SvelteKit99.00 ms
TanStack Start136.00 ms
React Router153.00 ms
Next.js994.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
Astro62.00 ms
SolidStart121.00 ms
SvelteKit136.00 ms
Pracht161.00 ms
Nuxt167.00 ms
TanStack Start173.00 ms
React Router270.00 ms
Next.js1037.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.451,361ms4,531ms4,798ms4,465
Nuxt1775507ms2,629ms3,733ms17,240
Pracht330.45095ms395ms3,454ms32,334
React Router16925353ms1,707ms3,905ms16,887
TanStack Start245.825185ms1,758ms3,135ms24,570
Median Sweep P99 Latency at 25 Connections
Median Sweep P99 Latency at 25 Connections data
FrameworkMilliseconds
Pracht95.00 ms
TanStack Start185.00 ms
React Router353.00 ms
Nuxt507.00 ms
Next.js1361.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
Pracht395.00 ms
React Router1707.00 ms
TanStack Start1758.00 ms
Nuxt2629.00 ms
Next.js4531.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 Start3135.00 ms
Pracht3454.00 ms
Nuxt3733.00 ms
React Router3905.00 ms
Next.js4798.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
Pracht84.00 ms
TanStack Start132.00 ms
Nuxt143.00 ms
React Router158.00 ms
Next.js552.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
Pracht162.00 ms
TanStack Start257.00 ms
Nuxt298.00 ms
React Router302.00 ms
Next.js2090.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
Pracht291.00 ms
TanStack Start312.00 ms
Nuxt328.00 ms
React Router420.00 ms
Next.js2419.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
Pracht78.00 ms
TanStack Start104.00 ms
Nuxt138.00 ms
React Router145.00 ms
Next.js522.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
Pracht156.00 ms
TanStack Start214.00 ms
Nuxt287.00 ms
React Router296.00 ms
Next.js1019.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 Start232.00 ms
Pracht265.00 ms
Nuxt303.00 ms
React Router387.00 ms
Next.js1002.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.