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.99MB	110.99MB	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.99 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.38s	1.71s	4.42s	0.90s	0.87s
Next.js	5.77s	3.00s	6.54s	4.76s	4.71s
Nuxt	5.01s	3.27s	6.30s	3.62s	3.77s
React Router	1.40s	1.27s	1.55s	1.61s	1.57s
SolidStart	1.80s	1.45s	2.08s	2.80s	2.69s
SvelteKit	1.59s	1.37s	1.77s	1.80s	1.62s
TanStack Start	4.86s	1.97s	6.99s	5.25s	5.03s

Avg install time

Avg install time chart

Avg install time data

Framework	Seconds
React Router	1.40s
SvelteKit	1.59s
SolidStart	1.80s
Astro	3.38s
TanStack Start	4.86s
Nuxt	5.01s
Next.js	5.77s

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.90s
React Router	1.61s
SvelteKit	1.80s
SolidStart	2.80s
Nuxt	3.62s
Next.js	4.76s
TanStack Start	5.25s

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.87s
React Router	1.57s
SvelteKit	1.62s
SolidStart	2.69s
Nuxt	3.77s
Next.js	4.71s
TanStack Start	5.03s

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.21s	1.18s	1.26s
Next.js	2.38s	2.26s	2.52s
Nuxt	2.37s	2.35s	2.40s
React Router	0.85s	0.79s	0.88s
SolidStart	3.00s	2.95s	3.03s
SvelteKit	1.12s	1.07s	1.16s
TanStack Start	3.07s	2.94s	3.29s

Avg dev server startup time

Avg dev server startup time chart

Avg dev server startup time data

Framework	Seconds
React Router	0.85s
SvelteKit	1.12s
Astro	1.21s
Nuxt	2.37s
Next.js	2.38s
SolidStart	3.00s
TanStack Start	3.07s

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	100.4ms	100.3ms	1.81ms	1.55ms	0.26ms	0ms
Next.js	339.4ms	339.44ms	20.08ms	1.28ms	8.08ms	10.72ms
Nuxt	145.2ms	145.14ms	10.04ms	0.48ms	1.92ms	7.63ms
React Router	156.8ms	156.82ms	19.27ms	1.41ms	2.87ms	14.99ms
SolidStart	102ms	101.78ms	14.3ms	0.92ms	3.01ms	10.37ms
SvelteKit	123.4ms	123.39ms	15.53ms	0.65ms	3.61ms	11.27ms
TanStack Start	151.4ms	151.42ms	23.97ms	1.5ms	12.34ms	10.14ms

First Paint (ms)

First Paint (ms) chart

First Paint (ms) data

Framework	Milliseconds
Astro	100.40 ms
SolidStart	102.00 ms
SvelteKit	123.40 ms
Nuxt	145.20 ms
TanStack Start	151.40 ms
React Router	156.80 ms
Next.js	339.40 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	100.30 ms
SolidStart	101.78 ms
SvelteKit	123.39 ms
Nuxt	145.14 ms
TanStack Start	151.42 ms
React Router	156.82 ms
Next.js	339.44 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: 15.53 ms

Median: 15.53 ms

1.81 ms

10.04 ms

14.30 ms

15.53 ms

19.27 ms

20.08 ms

23.97 ms

Interaction Breakdown data

Framework or version	Interaction latency	Input delay	Processing duration	Presentation delay
Astro	1.81 ms	1.55 ms	0.26 ms	0.00 ms
Nuxt	10.04 ms	0.48 ms	1.92 ms	7.63 ms
SolidStart	14.30 ms	0.92 ms	3.01 ms	10.37 ms
SvelteKit	15.53 ms	0.65 ms	3.61 ms	11.27 ms
React Router	19.27 ms	1.41 ms	2.87 ms	14.99 ms
Next.js	20.08 ms	1.28 ms	8.08 ms	10.72 ms
TanStack Start	23.97 ms	1.50 ms	12.34 ms	10.14 ms

Server Side Rendered Tests

Methodology: Server Side Rendered Tests.

Framework	First Paint	FCP	Interaction Latency	Input Delay	Processing Duration	Presentation Delay
Astro	73.4ms	73.53ms	1.65ms	0.96ms	0.69ms	0ms
Next.js	148.2ms	148.16ms	18.83ms	1.14ms	8.1ms	9.59ms
Nuxt	106.6ms	106.51ms	10.12ms	0.5ms	1.4ms	8.22ms
React Router	93ms	92.95ms	21.98ms	1.48ms	3.32ms	17.18ms
SolidStart	91ms	90.9ms	14.15ms	0.81ms	1.89ms	11.44ms
SvelteKit	94.6ms	94.51ms	13.94ms	0.64ms	3.54ms	9.77ms
TanStack Start	133.8ms	133.68ms	24.78ms	1.64ms	15.25ms	7.89ms

First Paint (ms)

First Paint (ms) chart

First Paint (ms) data

Framework	Milliseconds
Astro	73.40 ms
SolidStart	91.00 ms
React Router	93.00 ms
SvelteKit	94.60 ms
Nuxt	106.60 ms
TanStack Start	133.80 ms
Next.js	148.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	73.53 ms
SolidStart	90.90 ms
React Router	92.95 ms
SvelteKit	94.51 ms
Nuxt	106.51 ms
TanStack Start	133.68 ms
Next.js	148.16 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: 14.15 ms

Median: 14.15 ms

1.65 ms

10.12 ms

13.94 ms

14.15 ms

18.83 ms

21.98 ms

24.78 ms

Interaction Breakdown data

Framework or version	Interaction latency	Input delay	Processing duration	Presentation delay
Astro	1.65 ms	0.96 ms	0.69 ms	0.00 ms
Nuxt	10.12 ms	0.50 ms	1.40 ms	8.22 ms
SvelteKit	13.94 ms	0.64 ms	3.54 ms	9.77 ms
SolidStart	14.15 ms	0.81 ms	1.89 ms	11.44 ms
Next.js	18.83 ms	1.14 ms	8.10 ms	9.59 ms
React Router	21.98 ms	1.48 ms	3.32 ms	17.18 ms
TanStack Start	24.78 ms	1.64 ms	15.25 ms	7.89 ms

Server Side Throughput Tests

Methodology: Server Side Throughput Tests.

Framework	Ops/sec	Median Latency	Body Size	Duplication
Baseline HTML	847	1.199ms	96.83kb	1x
Astro	659	1.453ms	96.89kb	1x
Next.js	221	4.681ms	199.57kb	2x
Nuxt	365	2.635ms	201.27kb	2x
React Router	337	2.924ms	211.9kb	2x
SolidStart	413	2.336ms	224.17kb	2x
SvelteKit	447	2.17ms	183.53kb	2x
TanStack Start	326	3.031ms	193.62kb	2x

Ops/sec

Ops/sec chart

Ops/sec data

Framework	Operations per second
Baseline HTML	847
Astro	659
SvelteKit	447
SolidStart	413
Nuxt	365
React Router	337
TanStack Start	326
Next.js	221

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.90 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.17 ms
SolidStart	2.34 ms
Nuxt	2.63 ms
React Router	2.92 ms
TanStack Start	3.03 ms
Next.js	4.68 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,683	200	19ms	38ms	119ms	49,063
Astro	1,214.6	25	31ms	62ms	309ms	36,308
Next.js	42.4	5	1848ms	4703ms	4696ms	1,207
Nuxt	68.8	5	2009ms	4150ms	4262ms	2,227
React Router	176	10	351ms	1627ms	3863ms	5,786
SolidStart	523.6	10	102ms	179ms	2195ms	17,035
SvelteKit	500.4	5	84ms	390ms	2429ms	15,693
TanStack Start	45.6	10	3435ms	4156ms	4487ms	1,396

P99 Latency

P99 Latency at 25 Connections

P99 Latency at 25 Connections chart

P99 Latency at 25 Connections data

Framework	Milliseconds
Baseline HTML	19.00 ms
Astro	31.00 ms
SvelteKit	84.00 ms
SolidStart	102.00 ms
React Router	351.00 ms
Next.js	1848.00 ms
Nuxt	2009.00 ms
TanStack Start	3435.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	38.00 ms
Astro	62.00 ms
SolidStart	179.00 ms
SvelteKit	390.00 ms
React Router	1627.00 ms
Nuxt	4150.00 ms
TanStack Start	4156.00 ms
Next.js	4703.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	119.00 ms
Astro	309.00 ms
SolidStart	2195.00 ms
SvelteKit	2429.00 ms
React Router	3863.00 ms
Nuxt	4262.00 ms
TanStack Start	4487.00 ms
Next.js	4696.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	22.00 ms
SvelteKit	60.00 ms
SolidStart	70.00 ms
React Router	156.00 ms
Nuxt	392.00 ms
TanStack Start	625.00 ms
Next.js	653.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	35.00 ms
Astro	44.00 ms
SvelteKit	133.00 ms
SolidStart	154.00 ms
React Router	284.00 ms
Nuxt	512.00 ms
TanStack Start	687.00 ms
Next.js	2229.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	76.00 ms
Astro	87.00 ms
SolidStart	172.00 ms
SvelteKit	228.00 ms
React Router	404.00 ms
Nuxt	667.00 ms
TanStack Start	1226.00 ms
Next.js	2637.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.