All Frameworks

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

Framework	Deps	Dev	Prod	Graph
Astro	80	27	53	View
Next.js	229	223	6	View
Nuxt	68	11	57	View
React Router	51	23	28	View
SolidStart	29	4	25	View
SvelteKit	24	12	12	View
TanStack Start	8	0	8	View

Metaframework Dependencies

Metaframework Dependencies chart

Metaframework Dependencies data

Framework	Dependency count
TanStack Start	8
SvelteKit	24
SolidStart	29
React Router	51
Nuxt	68
Astro	80
Next.js	229

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

Framework	Dependency count
TanStack Start	0
SolidStart	4
Nuxt	11
SvelteKit	12
React Router	23
Astro	27
Next.js	223

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

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

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	9 / 6	269	9	115.95MB	110.94MB	View
SolidStart	1 / 6	227	8	124.34MB	99.61MB	View
SvelteKit	8 / 0	158	1	98.44MB	101.18MB	View
TanStack Start	11 / 13	424	14	234.77MB	198.52MB	View

Starter Project Dev Dependencies

Starter Project Dev Dependencies chart

Starter Project Dev Dependencies data

Framework	Dependency count
SolidStart	1
Astro	2
Nuxt	2
Next.js	6
SvelteKit	8
React Router	9
TanStack Start	11

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

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

Starter Project Duplicate Dependencies chart

Starter Project Duplicate Dependencies data

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

Methodology: Node Modules Size.

Node modules size

Node modules size chart

Node modules size data

Framework	Megabytes
SvelteKit	98.44 MB
React Router	115.95 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

Methodology: Build and Install Times.

Framework	Avg Install	Min Install	Max Install	Avg Cold Build	Avg Warm Build
Astro	3.22s	1.59s	3.89s	0.83s	0.92s
Next.js	5.68s	3.09s	6.43s	5.15s	5.06s
Nuxt	4.74s	2.90s	5.54s	3.74s	3.72s
React Router	1.29s	1.14s	1.46s	1.73s	1.68s
SolidStart	1.72s	1.45s	2.04s	2.74s	2.66s
SvelteKit	1.54s	1.29s	1.71s	1.87s	1.65s
TanStack Start	14.10s	6.39s	21.10s	5.79s	5.43s

Avg install time

Avg install time chart

Avg install time data

Framework	Seconds
React Router	1.29s
SvelteKit	1.54s
SolidStart	1.72s
Astro	3.22s
Nuxt	4.74s
Next.js	5.68s
TanStack Start	14.10s

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

Framework	Seconds
Astro	0.83s
React Router	1.73s
SvelteKit	1.87s
SolidStart	2.74s
Nuxt	3.74s
Next.js	5.15s
TanStack Start	5.79s

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

Framework	Seconds
Astro	0.92s
SvelteKit	1.65s
React Router	1.68s
SolidStart	2.66s
Nuxt	3.72s
Next.js	5.06s
TanStack Start	5.43s

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

Dev Server Startup

Methodology: Dev Server Startup.

Framework	Avg Start	Min Start	Max Start
Astro	1.29s	1.24s	1.40s
Next.js	2.41s	2.34s	2.61s
Nuxt	2.56s	2.50s	2.65s
React Router	0.83s	0.81s	0.85s
SolidStart	2.98s	2.92s	3.01s
SvelteKit	4.16s	2.96s	6.17s
TanStack Start	3.00s	2.92s	3.05s

Avg dev server startup time

Avg dev server startup time chart

Avg dev server startup time data

Framework	Seconds
React Router	0.83s
Astro	1.29s
Next.js	2.41s
Nuxt	2.56s
SolidStart	2.98s
TanStack Start	3.00s
SvelteKit	4.16s

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

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

Methodology: Browser Baseline.

Framework	Baseline	Feature	Year	Features
Astro	—	—	—	0
Next.js	High	—	2022	46
Nuxt	High	—	2023	39
React Router	High	—	2022	40
SolidStart	High	—	2020	30
SvelteKit	High	—	2020	42
TanStack Start	High	—	2022	45

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

Methodology: Client Side Rendered Tests.

Framework	First Paint	FCP	Interaction Latency	Input Delay	Processing Duration	Presentation Delay
Astro	128.4ms	128.25ms	6.23ms	2.35ms	1.26ms	2.62ms
Next.js	337.8ms	337.77ms	19.58ms	1.41ms	7.18ms	10.99ms
Nuxt	167ms	167.15ms	11.3ms	0.47ms	1.72ms	9.12ms
React Router	163.4ms	163.37ms	23.91ms	2.14ms	2.76ms	19.01ms
SolidStart	107.4ms	107.1ms	15.32ms	0.87ms	2.12ms	12.33ms
SvelteKit	118.4ms	118.3ms	16.71ms	0.78ms	3.97ms	11.96ms
TanStack Start	158ms	157.83ms	26.08ms	1.54ms	14.05ms	10.49ms

First Paint (ms)

First Paint (ms) chart

First Paint (ms) data

Framework	Milliseconds
SolidStart	107.40 ms
SvelteKit	118.40 ms
Astro	128.40 ms
TanStack Start	158.00 ms
React Router	163.40 ms
Nuxt	167.00 ms
Next.js	337.80 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

Framework	Milliseconds
SolidStart	107.10 ms
SvelteKit	118.30 ms
Astro	128.25 ms
TanStack Start	157.83 ms
React Router	163.37 ms
Nuxt	167.15 ms
Next.js	337.77 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.

• Input delay
• Processing duration
• Presentation delay

Median: 16.71 ms

Median: 16.71 ms

6.23 ms

11.30 ms

15.32 ms

16.71 ms

19.58 ms

23.91 ms

26.08 ms

Interaction Breakdown data

Framework or version	Interaction latency	Input delay	Processing duration	Presentation delay
Astro	6.23 ms	2.35 ms	1.26 ms	2.62 ms
Nuxt	11.30 ms	0.47 ms	1.72 ms	9.12 ms
SolidStart	15.32 ms	0.87 ms	2.12 ms	12.33 ms
SvelteKit	16.71 ms	0.78 ms	3.97 ms	11.96 ms
Next.js	19.58 ms	1.41 ms	7.18 ms	10.99 ms
React Router	23.91 ms	2.14 ms	2.76 ms	19.01 ms
TanStack Start	26.08 ms	1.54 ms	14.05 ms	10.49 ms

Server Side Rendered Tests

Methodology: Server Side Rendered Tests.

Framework	First Paint	FCP	Interaction Latency	Input Delay	Processing Duration	Presentation Delay
Astro	69.2ms	69.09ms	0.96ms	0.58ms	0.38ms	0ms
Next.js	143.2ms	143.17ms	19.14ms	1.26ms	9.35ms	8.54ms
Nuxt	110ms	110.08ms	13.78ms	0.47ms	1.36ms	11.95ms
React Router	126.2ms	126.16ms	18.88ms	1.65ms	3.49ms	13.75ms
SolidStart	105.8ms	105.9ms	14.86ms	1.39ms	2.21ms	11.25ms
SvelteKit	97ms	96.98ms	16.46ms	0.74ms	2.45ms	13.27ms
TanStack Start	120.2ms	120.14ms	31.77ms	1.87ms	12.41ms	17.49ms

First Paint (ms)

First Paint (ms) chart

First Paint (ms) data

Framework	Milliseconds
Astro	69.20 ms
SvelteKit	97.00 ms
SolidStart	105.80 ms
Nuxt	110.00 ms
TanStack Start	120.20 ms
React Router	126.20 ms
Next.js	143.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

Framework	Milliseconds
Astro	69.09 ms
SvelteKit	96.98 ms
SolidStart	105.90 ms
Nuxt	110.08 ms
TanStack Start	120.14 ms
React Router	126.16 ms
Next.js	143.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.

• Input delay
• Processing duration
• Presentation delay

Median: 16.46 ms

Median: 16.46 ms

0.96 ms

13.78 ms

14.86 ms

16.46 ms

18.88 ms

19.14 ms

31.77 ms

Interaction Breakdown data

Framework or version	Interaction latency	Input delay	Processing duration	Presentation delay
Astro	0.96 ms	0.58 ms	0.38 ms	0.00 ms
Nuxt	13.78 ms	0.47 ms	1.36 ms	11.95 ms
SolidStart	14.86 ms	1.39 ms	2.21 ms	11.25 ms
SvelteKit	16.46 ms	0.74 ms	2.45 ms	13.27 ms
React Router	18.88 ms	1.65 ms	3.49 ms	13.75 ms
Next.js	19.14 ms	1.26 ms	9.35 ms	8.54 ms
TanStack Start	31.77 ms	1.87 ms	12.41 ms	17.49 ms

Server Side Throughput Tests

Methodology: Server Side Throughput Tests.

Framework	Ops/sec	Median Latency	Body Size	Duplication
Baseline HTML	643	1.338ms	96.83kb	1x
Astro	662	1.446ms	96.89kb	1x
Next.js	197	5.042ms	199.57kb	2x
Nuxt	376	2.568ms	201.27kb	2x
React Router	345	2.865ms	211.85kb	2x
SolidStart	428	2.25ms	224.17kb	2x
SvelteKit	445	2.156ms	183.53kb	2x
TanStack Start	329	3.009ms	193.62kb	2x

Ops/sec

Ops/sec chart

Ops/sec data

Framework	Operations per second
Astro	662
Baseline HTML	643
SvelteKit	445
SolidStart	428
Nuxt	376
React Router	345
TanStack Start	329
Next.js	197

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

Body Size

Body Size chart

Body Size data

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

Median Latency chart

Median Latency data

Framework	Milliseconds
Baseline HTML	1.34 ms
Astro	1.45 ms
SvelteKit	2.16 ms
SolidStart	2.25 ms
Nuxt	2.57 ms
React Router	2.87 ms
TanStack Start	3.01 ms
Next.js	5.04 ms

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

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,473.6	100	22ms	51ms	126ms	44,058
Astro	1,159.41	50	33ms	65ms	338ms	35,465
Next.js	39.6	5	2015ms	4708ms	4650ms	1,141
Nuxt	73	10	1846ms	4172ms	4231ms	2,361
React Router	178.4	25	255ms	304ms	3877ms	5,922
SolidStart	471	10	118ms	709ms	2224ms	14,582
SvelteKit	477.8	5	85ms	454ms	2521ms	15,227
TanStack Start	45.4	10	3177ms	4031ms	4511ms	1,401

P99 Latency

P99 Latency at 25 Connections

P99 Latency at 25 Connections chart

P99 Latency at 25 Connections data

Framework	Milliseconds
Baseline HTML	22.00 ms
Astro	33.00 ms
SvelteKit	85.00 ms
SolidStart	118.00 ms
React Router	255.00 ms
Nuxt	1846.00 ms
Next.js	2015.00 ms
TanStack Start	3177.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

Framework	Milliseconds
Baseline HTML	51.00 ms
Astro	65.00 ms
React Router	304.00 ms
SvelteKit	454.00 ms
SolidStart	709.00 ms
TanStack Start	4031.00 ms
Nuxt	4172.00 ms
Next.js	4708.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

Framework	Milliseconds
Baseline HTML	126.00 ms
Astro	338.00 ms
SolidStart	2224.00 ms
SvelteKit	2521.00 ms
React Router	3877.00 ms
Nuxt	4231.00 ms
TanStack Start	4511.00 ms
Next.js	4650.00 ms

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

P90 Latency

P90 Latency at 25 Connections

P90 Latency at 25 Connections chart

P90 Latency at 25 Connections data

Framework	Milliseconds
Baseline HTML	20.00 ms
Astro	23.00 ms
SvelteKit	63.00 ms
SolidStart	81.00 ms
React Router	146.00 ms
Nuxt	347.00 ms
Next.js	712.00 ms
TanStack Start	835.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

Framework	Milliseconds
Baseline HTML	39.00 ms
Astro	45.00 ms
SvelteKit	148.00 ms
SolidStart	179.00 ms
React Router	294.00 ms
Nuxt	479.00 ms
TanStack Start	859.00 ms
Next.js	2392.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

Framework	Milliseconds
Baseline HTML	80.00 ms
Astro	92.00 ms
SolidStart	199.00 ms
SvelteKit	241.00 ms
React Router	385.00 ms
Nuxt	567.00 ms
TanStack Start	1311.00 ms
Next.js	2622.00 ms

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

Core Web Vitals

CWV Desktop

Framework	LCP%	CLS%	FCP%	TTFB%	INP%
Astro	93	89	92	81	98
SolidStart	100	77	100	85	100
SvelteKit	79	78	77	68	95
Next.js	74	72	76	66	94
TanStack Start	55	81	46	29	91
Nuxt	68	58	69	59	96
React Router	59	61	65	68	90

Good Largest Contentful Paint

Measures how fast a page's main content loads. To provide a good user experience, the LCP should be 2.5 seconds or less.

Good Largest Contentful Paint chart

Good Largest Contentful Paint data

Framework	%
SolidStart	100
Astro	93
SvelteKit	79
Next.js	74
Nuxt	68
React Router	59
TanStack Start	55

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

Good Cumulative Layout Shift

Measures how much and how far content unexpectedly moves on a page. To provide a good user experience, sites should maintain a CLS score of 0.1 or less for at least 75% of page visits.

Good Cumulative Layout Shift chart

Good Cumulative Layout Shift data

Framework	%
Astro	89
TanStack Start	81
SvelteKit	78
SolidStart	77
Next.js	72
React Router	61
Nuxt	58

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

Good First Contentful Paint

Measures initial loading speed. To provide a good user experience, the FCP should be 1.8 seconds or less.

Good First Contentful Paint chart

Good First Contentful Paint data

Framework	%
SolidStart	100
Astro	92
SvelteKit	77
Next.js	76
Nuxt	69
React Router	65
TanStack Start	46

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

Good Time To First Byte

Measures the time between the request for a resource and when the first byte of a response begins to arrive. A good TTFB is less than or equal to 800ms.

Good Time To First Byte chart

Good Time To First Byte data

Framework	%
SolidStart	85
Astro	81
SvelteKit	68
React Router	68
Next.js	66
Nuxt	59
TanStack Start	29

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

Good Interaction to Next Paint

Measures overall page responsiveness to user actions. To provide a good user experience, the INP should be 200ms or less.

Good Interaction to Next Paint chart

Good Interaction to Next Paint data

Framework	%
SolidStart	100
Astro	98
Nuxt	96
SvelteKit	95
Next.js	94
TanStack Start	91
React Router	90

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

CWV Mobile

Framework	LCP%	CLS%	FCP%	TTFB%	INP%
Astro	80	93	73	64	85
SolidStart	88	66	88	85	75
SvelteKit	67	81	58	54	74
Next.js	53	72	48	45	59
Nuxt	46	59	44	46	65
React Router	37	63	37	50	53
TanStack Start	31	84	19	13	51

Good Largest Contentful Paint

Measures how fast a page's main content loads. To provide a good user experience, the LCP should be 2.5 seconds or less.

Good Largest Contentful Paint chart

Good Largest Contentful Paint data

Framework	%
SolidStart	88
Astro	80
SvelteKit	67
Next.js	53
Nuxt	46
React Router	37
TanStack Start	31

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

Good Cumulative Layout Shift

Measures how much and how far content unexpectedly moves on a page. To provide a good user experience, sites should maintain a CLS score of 0.1 or less for at least 75% of page visits.

Good Cumulative Layout Shift chart

Good Cumulative Layout Shift data

Framework	%
Astro	93
TanStack Start	84
SvelteKit	81
Next.js	72
SolidStart	66
React Router	63
Nuxt	59

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

Good First Contentful Paint

Measures initial loading speed. To provide a good user experience, the FCP should be 1.8 seconds or less.

Good First Contentful Paint chart

Good First Contentful Paint data

Framework	%
SolidStart	88
Astro	73
SvelteKit	58
Next.js	48
Nuxt	44
React Router	37
TanStack Start	19

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

Good Time To First Byte

Measures the time between the request for a resource and when the first byte of a response begins to arrive. A good TTFB is less than or equal to 800ms.

Good Time To First Byte chart

Good Time To First Byte data

Framework	%
SolidStart	85
Astro	64
SvelteKit	54
React Router	50
Nuxt	46
Next.js	45
TanStack Start	13

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

Good Interaction to Next Paint

Measures overall page responsiveness to user actions. To provide a good user experience, the INP should be 200ms or less.

Good Interaction to Next Paint chart

Good Interaction to Next Paint data

Framework	%
Astro	85
SolidStart	75
SvelteKit	74
Nuxt	65
Next.js	59
React Router	53
TanStack Start	51

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

Methodology: Core Web Vitals.