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	116.15MB	111.11MB	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	116.15 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	4.08s	3.52s	4.43s	0.89s	0.96s
Next.js	7.15s	3.96s	9.74s	5.36s	5.29s
Nuxt	6.30s	4.70s	7.04s	4.07s	4.01s
React Router	1.33s	1.22s	1.51s	1.71s	1.68s
SolidStart	2.24s	1.46s	3.78s	2.84s	2.72s
SvelteKit	1.63s	1.40s	1.79s	1.93s	1.74s
TanStack Start	5.07s	2.08s	6.27s	5.65s	5.44s

Avg install time

Avg install time chart

Avg install time data

Framework	Seconds
React Router	1.33s
SvelteKit	1.63s
SolidStart	2.24s
Astro	4.08s
TanStack Start	5.07s
Nuxt	6.30s
Next.js	7.15s

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.89s
React Router	1.71s
SvelteKit	1.93s
SolidStart	2.84s
Nuxt	4.07s
Next.js	5.36s
TanStack Start	5.65s

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.96s
React Router	1.68s
SvelteKit	1.74s
SolidStart	2.72s
Nuxt	4.01s
Next.js	5.29s
TanStack Start	5.44s

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.56s	1.50s	1.61s
Next.js	2.56s	2.36s	2.69s
Nuxt	2.74s	2.60s	3.00s
React Router	0.84s	0.81s	0.88s
SolidStart	2.96s	2.90s	3.02s
SvelteKit	1.23s	1.15s	1.32s
TanStack Start	2.98s	2.87s	3.06s

Avg dev server startup time

Avg dev server startup time chart

Avg dev server startup time data

Framework	Seconds
React Router	0.84s
SvelteKit	1.23s
Astro	1.56s
Next.js	2.56s
Nuxt	2.74s
SolidStart	2.96s
TanStack Start	2.98s

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	133.6ms	133.56ms	2.27ms	1.89ms	0.38ms	0ms
Next.js	345.2ms	345.01ms	23.66ms	2.3ms	8.33ms	13.03ms
Nuxt	183.8ms	183.77ms	12.07ms	0.76ms	2.94ms	8.36ms
React Router	168.8ms	168.93ms	24.93ms	1.68ms	3.09ms	20.17ms
SolidStart	124ms	124.05ms	18.14ms	0.98ms	2.81ms	14.34ms
SvelteKit	131.2ms	131ms	14.06ms	0.64ms	2.57ms	10.85ms
TanStack Start	156.4ms	156.62ms	28.5ms	1.69ms	15.09ms	11.72ms

First Paint (ms)

First Paint (ms) chart

First Paint (ms) data

Framework	Milliseconds
SolidStart	124.00 ms
SvelteKit	131.20 ms
Astro	133.60 ms
TanStack Start	156.40 ms
React Router	168.80 ms
Nuxt	183.80 ms
Next.js	345.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
SolidStart	124.05 ms
SvelteKit	131.00 ms
Astro	133.56 ms
TanStack Start	156.62 ms
React Router	168.93 ms
Nuxt	183.77 ms
Next.js	345.01 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: 18.14 ms

Median: 18.14 ms

2.27 ms

12.07 ms

14.06 ms

18.14 ms

23.66 ms

24.93 ms

28.50 ms

Interaction Breakdown data

Framework or version	Interaction latency	Input delay	Processing duration	Presentation delay
Astro	2.27 ms	1.89 ms	0.38 ms	0.00 ms
Nuxt	12.07 ms	0.76 ms	2.94 ms	8.36 ms
SvelteKit	14.06 ms	0.64 ms	2.57 ms	10.85 ms
SolidStart	18.14 ms	0.98 ms	2.81 ms	14.34 ms
Next.js	23.66 ms	2.30 ms	8.33 ms	13.03 ms
React Router	24.93 ms	1.68 ms	3.09 ms	20.17 ms
TanStack Start	28.50 ms	1.69 ms	15.09 ms	11.72 ms

Server Side Rendered Tests

Methodology: Server Side Rendered Tests.

Framework	First Paint	FCP	Interaction Latency	Input Delay	Processing Duration	Presentation Delay
Astro	87ms	87.19ms	1.47ms	1.2ms	0.27ms	0ms
Next.js	175ms	175.15ms	21.9ms	1.49ms	8.02ms	12.4ms
Nuxt	110.8ms	110.78ms	14.6ms	1.43ms	2.06ms	11.1ms
React Router	126ms	126.05ms	20.6ms	2.2ms	3.01ms	15.39ms
SolidStart	96ms	96.07ms	15.08ms	0.86ms	2.6ms	11.62ms
SvelteKit	111.8ms	111.76ms	18.2ms	0.81ms	4.71ms	12.68ms
TanStack Start	146.8ms	146.89ms	32.07ms	1.78ms	18.23ms	12.05ms

First Paint (ms)

First Paint (ms) chart

First Paint (ms) data

Framework	Milliseconds
Astro	87.00 ms
SolidStart	96.00 ms
Nuxt	110.80 ms
SvelteKit	111.80 ms
React Router	126.00 ms
TanStack Start	146.80 ms
Next.js	175.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

Framework	Milliseconds
Astro	87.19 ms
SolidStart	96.07 ms
Nuxt	110.78 ms
SvelteKit	111.76 ms
React Router	126.05 ms
TanStack Start	146.89 ms
Next.js	175.15 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: 18.20 ms

Median: 18.20 ms

1.47 ms

14.60 ms

15.08 ms

18.20 ms

20.60 ms

21.90 ms

32.07 ms

Interaction Breakdown data

Framework or version	Interaction latency	Input delay	Processing duration	Presentation delay
Astro	1.47 ms	1.20 ms	0.27 ms	0.00 ms
Nuxt	14.60 ms	1.43 ms	2.06 ms	11.10 ms
SolidStart	15.08 ms	0.86 ms	2.60 ms	11.62 ms
SvelteKit	18.20 ms	0.81 ms	4.71 ms	12.68 ms
React Router	20.60 ms	2.20 ms	3.01 ms	15.39 ms
Next.js	21.90 ms	1.49 ms	8.02 ms	12.40 ms
TanStack Start	32.07 ms	1.78 ms	18.23 ms	12.05 ms

Server Side Throughput Tests

Methodology: Server Side Throughput Tests.

Framework	Ops/sec	Median Latency	Body Size	Duplication
Baseline HTML	844	1.204ms	96.83kb	1x
Astro	661	1.453ms	96.89kb	1x
Next.js	235	4.543ms	199.57kb	2x
Nuxt	333	2.875ms	201.27kb	2x
React Router	289	3.341ms	212.07kb	2x
SolidStart	400	2.437ms	224.17kb	2x
SvelteKit	442	2.182ms	183.53kb	2x
TanStack Start	305	3.238ms	193.62kb	2x

Ops/sec

Ops/sec chart

Ops/sec data

Framework	Operations per second
Baseline HTML	844
Astro	661
SvelteKit	442
SolidStart	400
Nuxt	333
TanStack Start	305
React Router	289
Next.js	235

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	212.07 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.20 ms
Astro	1.45 ms
SvelteKit	2.18 ms
SolidStart	2.44 ms
Nuxt	2.88 ms
TanStack Start	3.24 ms
React Router	3.34 ms
Next.js	4.54 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,655.8	200	20ms	50ms	104ms	48,097
Astro	1,150.8	50	37ms	65ms	317ms	34,086
Next.js	34	1	2288ms	4690ms	4668ms	978
Nuxt	71.8	5	2064ms	4177ms	4198ms	2,262
React Router	175	10	270ms	1786ms	3934ms	5,708
SolidStart	541.21	10	89ms	481ms	2326ms	16,962
SvelteKit	470.6	5	87ms	519ms	2381ms	15,194
TanStack Start	45.8	5	3217ms	4285ms	4723ms	1,411

P99 Latency

P99 Latency at 25 Connections

P99 Latency at 25 Connections chart

P99 Latency at 25 Connections data

Framework	Milliseconds
Baseline HTML	20.00 ms
Astro	37.00 ms
SvelteKit	87.00 ms
SolidStart	89.00 ms
React Router	270.00 ms
Nuxt	2064.00 ms
Next.js	2288.00 ms
TanStack Start	3217.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	50.00 ms
Astro	65.00 ms
SolidStart	481.00 ms
SvelteKit	519.00 ms
React Router	1786.00 ms
Nuxt	4177.00 ms
TanStack Start	4285.00 ms
Next.js	4690.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	104.00 ms
Astro	317.00 ms
SolidStart	2326.00 ms
SvelteKit	2381.00 ms
React Router	3934.00 ms
Nuxt	4198.00 ms
Next.js	4668.00 ms
TanStack Start	4723.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	18.00 ms
Astro	25.00 ms
SvelteKit	62.00 ms
SolidStart	68.00 ms
React Router	147.00 ms
Nuxt	350.00 ms
TanStack Start	786.00 ms
Next.js	800.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	36.00 ms
Astro	45.00 ms
SvelteKit	133.00 ms
SolidStart	164.00 ms
React Router	295.00 ms
Nuxt	497.00 ms
TanStack Start	862.00 ms
Next.js	2600.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	74.00 ms
Astro	90.00 ms
SolidStart	172.00 ms
SvelteKit	235.00 ms
React Router	403.00 ms
Nuxt	653.00 ms
TanStack Start	1286.00 ms
Next.js	2835.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.