Skip to content

All Frameworks

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.
FrameworkDepsDevProdGraph
Astro802753View
Next.js2292236View
Nuxt681157View
React Router512328View
SolidStart29425View
SvelteKit241212View
TanStack Start808View

Metaframework Dependencies

Metaframework Dependencies chart
Metaframework Dependencies data
FrameworkDependency count
TanStack Start8
SvelteKit24
SolidStart29
React Router51
Nuxt68
Astro80
Next.js229

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

Metaframework Development Dependencies

Metaframework Development Dependencies chart
Metaframework Development Dependencies data
FrameworkDependency count
TanStack Start0
SolidStart4
Nuxt11
SvelteKit12
React Router23
Astro27
Next.js223

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

Metaframework Production Dependencies

Metaframework Production Dependencies chart
Metaframework Production Dependencies data
FrameworkDependency count
Next.js6
TanStack Start8
SvelteKit12
SolidStart25
React Router28
Astro53
Nuxt57

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

FrameworkDeps Dev / ProdAll DepsDup. Depsnode_modulesDep Install SizeGraph
Astro2 / 138711207.94MB186.65MBView
Next.js6 / 342112560.04MB506.22MBView
Nuxt2 / 369463208.80MB172.24MBView
React Router9 / 62699116.15MB111.11MBView
SolidStart1 / 62278124.34MB99.61MBView
SvelteKit8 / 0158197.02MB99.76MBView
TanStack Start11 / 1342414234.76MB198.52MBView

Starter Project Dev Dependencies

Starter Project Dev Dependencies chart
Starter Project Dev Dependencies data
FrameworkDependency count
SolidStart1
Astro2
Nuxt2
Next.js6
SvelteKit8
React Router9
TanStack Start11

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

Starter Project Production Dependencies

Starter Project Production Dependencies chart
Starter Project Production Dependencies data
FrameworkDependency count
SvelteKit0
Astro1
Next.js3
Nuxt3
React Router6
SolidStart6
TanStack Start13

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

Starter Project Duplicate Dependencies

Starter Project Duplicate Dependencies chart
Starter Project Duplicate Dependencies data
FrameworkDependency count
SvelteKit1
SolidStart8
React Router9
Astro11
Next.js12
TanStack Start14
Nuxt63

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

Methodology: Node Modules Size.

Node modules size

Node modules size chart
Node modules size data
FrameworkMegabytes
SvelteKit97.02 MB
React Router116.15 MB
SolidStart124.34 MB
Astro207.94 MB
Nuxt208.80 MB
TanStack Start234.76 MB
Next.js560.04 MB

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

Methodology: Build and Install Times.

FrameworkAvg InstallMin InstallMax InstallAvg Cold BuildAvg Warm Build
Astro3.25s1.73s3.78s0.98s1.09s
Next.js5.73s3.08s6.55s4.87s5.02s
Nuxt4.87s3.43s5.72s3.64s3.48s
React Router1.41s1.24s1.54s1.62s1.67s
SolidStart1.71s1.37s2.03s2.81s2.68s
SvelteKit1.51s1.43s1.58s1.87s1.67s
TanStack Start4.82s2.14s5.58s5.26s5.07s

Avg install time

Avg install time chart
Avg install time data
FrameworkSeconds
React Router1.41s
SvelteKit1.51s
SolidStart1.71s
Astro3.25s
TanStack Start4.82s
Nuxt4.87s
Next.js5.73s

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

Cold build time

Cold build time chart
Cold build time data
FrameworkSeconds
Astro0.98s
React Router1.62s
SvelteKit1.87s
SolidStart2.81s
Nuxt3.64s
Next.js4.87s
TanStack Start5.26s

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

Warm build time

Warm build time chart
Warm build time data
FrameworkSeconds
Astro1.09s
React Router1.67s
SvelteKit1.67s
SolidStart2.68s
Nuxt3.48s
Next.js5.02s
TanStack Start5.07s

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

Methodology: Dev Server Startup.

FrameworkAvg StartMin StartMax Start
Astro1.38s1.27s1.70s
Next.js2.46s2.33s2.65s
Nuxt2.39s2.31s2.44s
React Router0.86s0.82s0.91s
SolidStart2.95s2.94s2.96s
SvelteKit1.25s1.15s1.38s
TanStack Start2.99s2.83s3.24s

Avg dev server startup time

Avg dev server startup time chart
Avg dev server startup time data
FrameworkSeconds
React Router0.86s
SvelteKit1.25s
Astro1.38s
Nuxt2.39s
Next.js2.46s
SolidStart2.95s
TanStack Start2.99s

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

Methodology: Core-JS Polyfills.

Framework~SizeUnnecessary Modules
Astro
Next.js110.0 KB302
Nuxt
React Router
SolidStart
SvelteKit
TanStack Start

Methodology: Browser Baseline.

FrameworkBaselineFeatureYearFeatures
Astro0
Next.jsHigh202246
NuxtHigh202339
React RouterHigh202240
SolidStartHigh202030
SvelteKitHigh202042
TanStack StartHigh202245

Methodology: Minimum Node Version.

FrameworkMin NodeSet by
Astrov22.12.0
Next.jsv20.9.0next
Nuxtv20.19.0
React Routerv20.19.0vite
SolidStartv24.0.0@solidjs/start, starter-solid-start
SvelteKitv22.20.0@napi-rs/lzma-linux-x64-gnu
TanStack Startv22.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

Methodology: Client Side Rendered Tests.

FrameworkFirst PaintFCPInteraction LatencyInput DelayProcessing DurationPresentation Delay
Astro112.6ms112.62ms1.94ms1.63ms0.31ms0ms
Next.js338.2ms338.17ms18.03ms1.25ms6.95ms9.83ms
Nuxt153.8ms153.93ms9.83ms1.44ms1.5ms6.89ms
React Router165.2ms165.35ms19.37ms2.76ms2.91ms13.7ms
SolidStart103.6ms103.45ms18.43ms0.9ms3.08ms14.46ms
SvelteKit121.4ms121.44ms15.18ms0.65ms2.97ms11.56ms
TanStack Start149.6ms149.73ms22.2ms2.09ms12.22ms7.89ms

First Paint (ms)

First Paint (ms) chart
First Paint (ms) data
FrameworkMilliseconds
SolidStart103.60 ms
Astro112.60 ms
SvelteKit121.40 ms
TanStack Start149.60 ms
Nuxt153.80 ms
React Router165.20 ms
Next.js338.20 ms

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

First Contentful Paint (ms)

First Contentful Paint (ms) chart
First Contentful Paint (ms) data
FrameworkMilliseconds
SolidStart103.45 ms
Astro112.62 ms
SvelteKit121.44 ms
TanStack Start149.73 ms
Nuxt153.93 ms
React Router165.35 ms
Next.js338.17 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.
1.94 ms
9.83 ms
15.18 ms
18.03 ms
18.43 ms
19.37 ms
22.20 ms
Interaction Breakdown data
Framework or versionInteraction latencyInput delayProcessing durationPresentation delay
Astro1.94 ms1.63 ms0.31 ms0.00 ms
Nuxt9.83 ms1.44 ms1.50 ms6.89 ms
SvelteKit15.18 ms0.65 ms2.97 ms11.56 ms
Next.js18.03 ms1.25 ms6.95 ms9.83 ms
SolidStart18.43 ms0.90 ms3.08 ms14.46 ms
React Router19.37 ms2.76 ms2.91 ms13.70 ms
TanStack Start22.20 ms2.09 ms12.22 ms7.89 ms

Methodology: Server Side Rendered Tests.

FrameworkFirst PaintFCPInteraction LatencyInput DelayProcessing DurationPresentation Delay
Astro68.6ms68.58ms0.88ms0.61ms0.27ms0ms
Next.js152ms151.84ms19.5ms1.34ms6.94ms11.22ms
Nuxt101.2ms101.32ms9.2ms0.46ms1.43ms7.31ms
React Router137.2ms137.3ms21.47ms1.6ms3.26ms16.6ms
SolidStart88.4ms88.27ms15.14ms0.82ms1.99ms12.33ms
SvelteKit94.4ms94.49ms15.54ms1.07ms3.57ms10.9ms
TanStack Start131.4ms131.34ms25.87ms1.6ms13.21ms11.06ms

First Paint (ms)

First Paint (ms) chart
First Paint (ms) data
FrameworkMilliseconds
Astro68.60 ms
SolidStart88.40 ms
SvelteKit94.40 ms
Nuxt101.20 ms
TanStack Start131.40 ms
React Router137.20 ms
Next.js152.00 ms

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

First Contentful Paint (ms)

First Contentful Paint (ms) chart
First Contentful Paint (ms) data
FrameworkMilliseconds
Astro68.58 ms
SolidStart88.27 ms
SvelteKit94.49 ms
Nuxt101.32 ms
TanStack Start131.34 ms
React Router137.30 ms
Next.js151.84 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.
0.88 ms
9.20 ms
15.14 ms
15.54 ms
19.50 ms
21.47 ms
25.87 ms
Interaction Breakdown data
Framework or versionInteraction latencyInput delayProcessing durationPresentation delay
Astro0.88 ms0.61 ms0.27 ms0.00 ms
Nuxt9.20 ms0.46 ms1.43 ms7.31 ms
SolidStart15.14 ms0.82 ms1.99 ms12.33 ms
SvelteKit15.54 ms1.07 ms3.57 ms10.90 ms
Next.js19.50 ms1.34 ms6.94 ms11.22 ms
React Router21.47 ms1.60 ms3.26 ms16.60 ms
TanStack Start25.87 ms1.60 ms13.21 ms11.06 ms

Methodology: Server Side Throughput Tests.

FrameworkOps/secMedian LatencyBody SizeDuplication
Baseline HTML8461.202ms96.83kb1x
Astro6641.439ms96.89kb1x
Next.js2154.732ms199.57kb2x
Nuxt3502.738ms201.27kb2x
React Router3412.885ms212.07kb2x
SolidStart4162.304ms224.17kb2x
SvelteKit4392.209ms183.53kb2x
TanStack Start3223.071ms193.62kb2x

Ops/sec

Ops/sec chart
Ops/sec data
FrameworkOperations per second
Baseline HTML846
Astro664
SvelteKit439
SolidStart416
Nuxt350
React Router341
TanStack Start322
Next.js215

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

Body Size

Body Size chart
Body Size data
FrameworkKilobytes
Baseline HTML96.83 KB
Astro96.89 KB
SvelteKit183.53 KB
TanStack Start193.62 KB
Next.js199.57 KB
Nuxt201.27 KB
React Router212.07 KB
SolidStart224.17 KB

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

Median Latency

Median Latency chart
Median Latency data
FrameworkMilliseconds
Baseline HTML1.20 ms
Astro1.44 ms
SvelteKit2.21 ms
SolidStart2.30 ms
Nuxt2.74 ms
React Router2.88 ms
TanStack Start3.07 ms
Next.js4.73 ms

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

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.

FrameworkPeak req/sPeak ConnectionsP99 @ 25P99 @ 50P99 @ 100Total Req.
Baseline HTML1,680.820020ms46ms104ms48,986
Astro1,162.210032ms66ms289ms35,518
Next.js45.251713ms4654ms4777ms1,298
Nuxt479.25083ms135ms2871ms15,535
React Router337.610107ms184ms3539ms11,058
SolidStart516.61098ms403ms2221ms16,823
SvelteKit453.2100100ms622ms2557ms14,475
TanStack Start293.6110172ms1463ms2803ms9,658

P99 Latency at 25 Connections

P99 Latency at 25 Connections chart
P99 Latency at 25 Connections data
FrameworkMilliseconds
Baseline HTML20.00 ms
Astro32.00 ms
Nuxt83.00 ms
SolidStart98.00 ms
SvelteKit100.00 ms
React Router107.00 ms
TanStack Start172.00 ms
Next.js1713.00 ms

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

P99 Latency at 50 Connections

P99 Latency at 50 Connections chart
P99 Latency at 50 Connections data
FrameworkMilliseconds
Baseline HTML46.00 ms
Astro66.00 ms
Nuxt135.00 ms
React Router184.00 ms
SolidStart403.00 ms
SvelteKit622.00 ms
TanStack Start1463.00 ms
Next.js4654.00 ms

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

P99 Latency at 100 Connections

P99 Latency at 100 Connections chart
P99 Latency at 100 Connections data
FrameworkMilliseconds
Baseline HTML104.00 ms
Astro289.00 ms
SolidStart2221.00 ms
SvelteKit2557.00 ms
TanStack Start2803.00 ms
Nuxt2871.00 ms
React Router3539.00 ms
Next.js4777.00 ms

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

P90 Latency at 25 Connections

P90 Latency at 25 Connections chart
P90 Latency at 25 Connections data
FrameworkMilliseconds
Baseline HTML18.00 ms
Astro24.00 ms
Nuxt56.00 ms
SolidStart71.00 ms
SvelteKit73.00 ms
React Router75.00 ms
TanStack Start123.00 ms
Next.js619.00 ms

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

P90 Latency at 50 Connections

P90 Latency at 50 Connections chart
P90 Latency at 50 Connections data
FrameworkMilliseconds
Baseline HTML35.00 ms
Astro46.00 ms
Nuxt105.00 ms
SvelteKit135.00 ms
React Router150.00 ms
SolidStart152.00 ms
TanStack Start256.00 ms
Next.js2275.00 ms

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

P90 Latency at 100 Connections

P90 Latency at 100 Connections chart
P90 Latency at 100 Connections data
FrameworkMilliseconds
Baseline HTML81.00 ms
Astro88.00 ms
SolidStart162.00 ms
Nuxt192.00 ms
SvelteKit224.00 ms
TanStack Start274.00 ms
React Router280.00 ms
Next.js2467.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.

FrameworkPeak req/sPeak ConnectionsP99 @ 25P99 @ 50P99 @ 100Total Req.
Next.js4211966ms4726ms4682ms1,171
Nuxt71.851947ms4114ms4224ms2,286
React Router176.650309ms298ms3843ms5,584
TanStack Start45.653878ms4100ms4678ms1,426

P99 Latency at 25 Connections

P99 Latency at 25 Connections chart
P99 Latency at 25 Connections data
FrameworkMilliseconds
React Router309.00 ms
Nuxt1947.00 ms
Next.js1966.00 ms
TanStack Start3878.00 ms

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

P99 Latency at 50 Connections

P99 Latency at 50 Connections chart
P99 Latency at 50 Connections data
FrameworkMilliseconds
React Router298.00 ms
TanStack Start4100.00 ms
Nuxt4114.00 ms
Next.js4726.00 ms

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

P99 Latency at 100 Connections

P99 Latency at 100 Connections chart
P99 Latency at 100 Connections data
FrameworkMilliseconds
React Router3843.00 ms
Nuxt4224.00 ms
TanStack Start4678.00 ms
Next.js4682.00 ms

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

P90 Latency at 25 Connections

P90 Latency at 25 Connections chart
P90 Latency at 25 Connections data
FrameworkMilliseconds
React Router150.00 ms
Nuxt365.00 ms
Next.js700.00 ms
TanStack Start711.00 ms

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

P90 Latency at 50 Connections

P90 Latency at 50 Connections chart
P90 Latency at 50 Connections data
FrameworkMilliseconds
React Router289.00 ms
Nuxt508.00 ms
TanStack Start660.00 ms
Next.js2384.00 ms

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

P90 Latency at 100 Connections

P90 Latency at 100 Connections chart
P90 Latency at 100 Connections data
FrameworkMilliseconds
React Router393.00 ms
Nuxt614.00 ms
TanStack Start1302.00 ms
Next.js2759.00 ms

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

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 chart
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 chart
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 chart
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 chart
Good Time To First Byte data
Framework%
SolidStart85
Astro81
SvelteKit68
React Router68
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 chart
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 chart
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 chart
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 chart
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 chart
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 chart
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.

Methodology: Core Web Vitals.