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.94MB	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	129.44MB	View
SvelteKit	7 / 0	156	1	95.68MB	98.82MB	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	7
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	95.68 MB
React Router	115.95 MB
SolidStart	124.34 MB
Astro	207.94 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.29s	1.74s	3.96s	0.92s	0.90s
Next.js	5.50s	2.96s	6.25s	5.42s	5.46s
Nuxt	4.71s	2.92s	5.81s	3.81s	3.73s
React Router	1.28s	1.15s	1.45s	1.66s	1.63s
SolidStart	1.84s	1.40s	2.23s	2.76s	2.70s
SvelteKit	1.39s	1.23s	1.53s	1.86s	1.67s
TanStack Start	5.01s	2.06s	6.20s	5.07s	4.88s

Avg install time

Avg install time chart

Avg install time data

Framework	Seconds
React Router	1.28s
SvelteKit	1.39s
SolidStart	1.84s
Astro	3.29s
Nuxt	4.71s
TanStack Start	5.01s
Next.js	5.50s

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.92s
React Router	1.66s
SvelteKit	1.86s
SolidStart	2.76s
Nuxt	3.81s
TanStack Start	5.07s
Next.js	5.42s

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.90s
React Router	1.63s
SvelteKit	1.67s
SolidStart	2.70s
Nuxt	3.73s
TanStack Start	4.88s
Next.js	5.46s

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.32s	1.31s	1.34s
Next.js	2.37s	2.27s	2.44s
Nuxt	2.57s	2.45s	2.69s
React Router	0.92s	0.90s	0.96s
SolidStart	3.28s	3.04s	3.95s
SvelteKit	1.17s	1.09s	1.34s
TanStack Start	3.02s	2.87s	3.21s

Avg dev server startup time

Avg dev server startup time chart

Avg dev server startup time data

Framework	Seconds
React Router	0.92s
SvelteKit	1.17s
Astro	1.32s
Next.js	2.37s
Nuxt	2.57s
TanStack Start	3.02s
SolidStart	3.28s

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	101.2ms	101.37ms	1.95ms	1.68ms	0.26ms	0ms
Next.js	341ms	340.89ms	19.43ms	1.06ms	6.72ms	11.65ms
Nuxt	167.2ms	167.08ms	11.64ms	0.65ms	2.05ms	8.94ms
React Router	154.6ms	154.63ms	22.25ms	1.43ms	1.91ms	18.9ms
SolidStart	105.6ms	105.51ms	18.83ms	0.82ms	2.86ms	15.14ms
SvelteKit	130.2ms	130.06ms	15.41ms	0.63ms	3.31ms	11.47ms
TanStack Start	134.8ms	134.7ms	26.82ms	1.77ms	13.15ms	11.9ms

First Paint (ms)

First Paint (ms) chart

First Paint (ms) data

Framework	Milliseconds
Astro	101.20 ms
SolidStart	105.60 ms
SvelteKit	130.20 ms
TanStack Start	134.80 ms
React Router	154.60 ms
Nuxt	167.20 ms
Next.js	341.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	101.37 ms
SolidStart	105.51 ms
SvelteKit	130.06 ms
TanStack Start	134.70 ms
React Router	154.63 ms
Nuxt	167.08 ms
Next.js	340.89 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.83 ms

Median: 18.83 ms

1.95 ms

11.64 ms

15.41 ms

18.83 ms

19.43 ms

22.25 ms

26.82 ms

Interaction Breakdown data

Framework or version	Interaction latency	Input delay	Processing duration	Presentation delay
Astro	1.95 ms	1.68 ms	0.26 ms	0.00 ms
Nuxt	11.64 ms	0.65 ms	2.05 ms	8.94 ms
SvelteKit	15.41 ms	0.63 ms	3.31 ms	11.47 ms
SolidStart	18.83 ms	0.82 ms	2.86 ms	15.14 ms
Next.js	19.43 ms	1.06 ms	6.72 ms	11.65 ms
React Router	22.25 ms	1.43 ms	1.91 ms	18.90 ms
TanStack Start	26.82 ms	1.77 ms	13.15 ms	11.90 ms

Server Side Rendered Tests

Methodology: Server Side Rendered Tests.

Framework	First Paint	FCP	Interaction Latency	Input Delay	Processing Duration	Presentation Delay
Astro	67.8ms	67.72ms	1.39ms	0.72ms	0.67ms	0ms
Next.js	151.4ms	151.45ms	21.07ms	1.42ms	9.46ms	10.19ms
Nuxt	111.8ms	111.73ms	11.55ms	0.89ms	1.96ms	8.69ms
React Router	128.6ms	128.55ms	18.39ms	1.89ms	2.69ms	13.81ms
SolidStart	106.8ms	106.88ms	15.02ms	0.81ms	2.23ms	11.98ms
SvelteKit	87.6ms	87.73ms	14.64ms	0.64ms	2.99ms	11ms
TanStack Start	133.2ms	133.27ms	29.29ms	1.84ms	17.24ms	10.21ms

First Paint (ms)

First Paint (ms) chart

First Paint (ms) data

Framework	Milliseconds
Astro	67.80 ms
SvelteKit	87.60 ms
SolidStart	106.80 ms
Nuxt	111.80 ms
React Router	128.60 ms
TanStack Start	133.20 ms
Next.js	151.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	67.72 ms
SvelteKit	87.73 ms
SolidStart	106.88 ms
Nuxt	111.73 ms
React Router	128.55 ms
TanStack Start	133.27 ms
Next.js	151.45 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.02 ms

Median: 15.02 ms

1.39 ms

11.55 ms

14.64 ms

15.02 ms

18.39 ms

21.07 ms

29.29 ms

Interaction Breakdown data

Framework or version	Interaction latency	Input delay	Processing duration	Presentation delay
Astro	1.39 ms	0.72 ms	0.67 ms	0.00 ms
Nuxt	11.55 ms	0.89 ms	1.96 ms	8.69 ms
SvelteKit	14.64 ms	0.64 ms	2.99 ms	11.00 ms
SolidStart	15.02 ms	0.81 ms	2.23 ms	11.98 ms
React Router	18.39 ms	1.89 ms	2.69 ms	13.81 ms
Next.js	21.07 ms	1.42 ms	9.46 ms	10.19 ms
TanStack Start	29.29 ms	1.84 ms	17.24 ms	10.21 ms

Server Side Throughput Tests

Methodology: Server Side Throughput Tests.

Framework	Ops/sec	Median Latency	Body Size	Duplication
Baseline HTML	845	1.203ms	96.83kb	1x
Astro	641	1.508ms	96.89kb	1x
Next.js	213	4.758ms	199.57kb	2x
Nuxt	366	2.638ms	201.27kb	2x
React Router	340	2.891ms	211.85kb	2x
SolidStart	423	2.268ms	224.17kb	2x
SvelteKit	449	2.142ms	183.53kb	2x
TanStack Start	328	3.035ms	193.62kb	2x

Ops/sec

Ops/sec chart

Ops/sec data

Framework	Operations per second
Baseline HTML	845
Astro	641
SvelteKit	449
SolidStart	423
Nuxt	366
React Router	340
TanStack Start	328
Next.js	213

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.20 ms
Astro	1.51 ms
SvelteKit	2.14 ms
SolidStart	2.27 ms
Nuxt	2.64 ms
React Router	2.89 ms
TanStack Start	3.04 ms
Next.js	4.76 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,617.4	100	20ms	46ms	116ms	46,505
Astro	1,169.6	100	34ms	67ms	276ms	34,875
Next.js	42.8	5	1854ms	4726ms	4755ms	1,217
Nuxt	71.41	5	1881ms	4182ms	4260ms	2,337
React Router	176.6	10	384ms	1666ms	3945ms	5,893
SolidStart	520.21	50	95ms	179ms	2116ms	16,858
SvelteKit	457.2	25	91ms	514ms	2786ms	14,706
TanStack Start	44.2	5	3517ms	4181ms	4446ms	1,335

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	34.00 ms
SvelteKit	91.00 ms
SolidStart	95.00 ms
React Router	384.00 ms
Next.js	1854.00 ms
Nuxt	1881.00 ms
TanStack Start	3517.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	46.00 ms
Astro	67.00 ms
SolidStart	179.00 ms
SvelteKit	514.00 ms
React Router	1666.00 ms
TanStack Start	4181.00 ms
Nuxt	4182.00 ms
Next.js	4726.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	116.00 ms
Astro	276.00 ms
SolidStart	2116.00 ms
SvelteKit	2786.00 ms
React Router	3945.00 ms
Nuxt	4260.00 ms
TanStack Start	4446.00 ms
Next.js	4755.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	19.00 ms
Astro	24.00 ms
SvelteKit	64.00 ms
SolidStart	70.00 ms
React Router	156.00 ms
Nuxt	342.00 ms
Next.js	661.00 ms
TanStack Start	711.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	37.00 ms
Astro	47.00 ms
SvelteKit	144.00 ms
SolidStart	150.00 ms
React Router	279.00 ms
Nuxt	471.00 ms
TanStack Start	877.00 ms
Next.js	2283.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	75.00 ms
Astro	88.00 ms
SolidStart	192.00 ms
SvelteKit	227.00 ms
React Router	383.00 ms
Nuxt	589.00 ms
TanStack Start	1297.00 ms
Next.js	2705.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.