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
Mastro	1	0	1	View
Next.js	229	223	6	View
Nuxt	68	11	57	View
React Router	50	22	28	View
SolidStart	29	4	25	View
SvelteKit	25	13	12	View
TanStack Start	8	0	8	View

Metaframework Dependencies

Metaframework Dependencies chart

Metaframework Dependencies data

Framework	Dependency count
Mastro	1
TanStack Start	8
SvelteKit	25
SolidStart	29
React Router	50
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
Mastro	0
TanStack Start	0
SolidStart	4
Nuxt	11
SvelteKit	13
React Router	22
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
Mastro	1
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
Mastro	2 / 2	6	0	29.16MB	27.39MB	View
Next.js	6 / 3	421	12	560.04MB	506.22MB	View
Nuxt	2 / 3	694	63	208.80MB	172.24MB	View
React Router	8 / 6	268	9	106.86MB	102.22MB	View
SolidStart	1 / 6	227	8	124.34MB	99.61MB	View
SvelteKit	7 / 0	157	2	94.96MB	98.06MB	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
Mastro	2
Nuxt	2
Next.js	6
SvelteKit	7
React Router	8
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
Mastro	2
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
Mastro	0
SvelteKit	2
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
Mastro	29.16 MB
SvelteKit	94.96 MB
React Router	106.86 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.18s	1.70s	3.85s	0.87s	1.27s
Mastro	0.49s	0.47s	0.51s	0.30s	0.30s
Next.js	5.50s	3.04s	6.33s	4.67s	4.66s
Nuxt	4.67s	3.01s	5.71s	3.65s	3.54s
React Router	1.35s	1.17s	1.58s	1.67s	1.63s
SolidStart	1.75s	1.42s	2.12s	2.70s	2.63s
SvelteKit	1.42s	1.26s	1.52s	1.91s	1.67s
TanStack Start	4.18s	1.91s	4.82s	5.17s	4.86s

Avg install time

Avg install time chart

Avg install time data

Framework	Seconds
Mastro	0.49s
React Router	1.35s
SvelteKit	1.42s
SolidStart	1.75s
Astro	3.18s
TanStack Start	4.18s
Nuxt	4.67s
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
Mastro	0.30s
Astro	0.87s
React Router	1.67s
SvelteKit	1.91s
SolidStart	2.70s
Nuxt	3.65s
Next.js	4.67s
TanStack Start	5.17s

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
Mastro	0.30s
Astro	1.27s
React Router	1.63s
SvelteKit	1.67s
SolidStart	2.63s
Nuxt	3.54s
Next.js	4.66s
TanStack Start	4.86s

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	—	—	—
Mastro	—	—	—
Next.js	—	—	—
Nuxt	—	—	—
React Router	—	—	—
SolidStart	—	—	—
SvelteKit	—	—	—
TanStack Start	—	—	—

Avg dev server startup time

Avg dev server startup time chart

Avg dev server startup time data

Framework	Seconds

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	—	—
Mastro	—	—
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
Mastro	—	—	—	0
Next.js	High	—	2022	46
Nuxt	Limited	temporal	—	40
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	—
Mastro	v24.12.0	starter-mastro
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	95.4ms	95.42ms	5.67ms	2.53ms	0.45ms	2.69ms
Next.js	338.2ms	338.2ms	16.44ms	1.14ms	6.47ms	8.84ms
Nuxt	155ms	154.9ms	9.43ms	0.52ms	2.18ms	6.73ms
React Router	158.2ms	158.17ms	16.8ms	1.55ms	2.9ms	12.35ms
SolidStart	102.2ms	102.33ms	15.05ms	0.8ms	2.5ms	11.75ms
SvelteKit	122.8ms	122.75ms	15.05ms	0.71ms	3.75ms	10.59ms
TanStack Start	140ms	140.04ms	22.68ms	1.29ms	12.5ms	8.89ms

First Paint (ms)

First Paint (ms) chart

First Paint (ms) data

Framework	Milliseconds
Astro	95.40 ms
SolidStart	102.20 ms
SvelteKit	122.80 ms
TanStack Start	140.00 ms
Nuxt	155.00 ms
React Router	158.20 ms
Next.js	338.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	95.42 ms
SolidStart	102.33 ms
SvelteKit	122.75 ms
TanStack Start	140.04 ms
Nuxt	154.90 ms
React Router	158.17 ms
Next.js	338.20 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.05 ms

Median: 15.05 ms

5.67 ms

9.43 ms

15.05 ms

15.05 ms

16.44 ms

16.80 ms

22.68 ms

Interaction Breakdown data

Framework or version	Interaction latency	Input delay	Processing duration	Presentation delay
Astro	5.67 ms	2.53 ms	0.45 ms	2.69 ms
Nuxt	9.43 ms	0.52 ms	2.18 ms	6.73 ms
SolidStart	15.05 ms	0.80 ms	2.50 ms	11.75 ms
SvelteKit	15.05 ms	0.71 ms	3.75 ms	10.59 ms
Next.js	16.44 ms	1.14 ms	6.47 ms	8.84 ms
React Router	16.80 ms	1.55 ms	2.90 ms	12.35 ms
TanStack Start	22.68 ms	1.29 ms	12.50 ms	8.89 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.84ms	1.37ms	0.67ms	0.7ms	0ms
Mastro	77.8ms	77.71ms	1.85ms	1.53ms	0.31ms	0ms
Next.js	143.2ms	143.07ms	16.76ms	1.21ms	7.52ms	8.04ms
Nuxt	98.2ms	98.09ms	9.82ms	0.49ms	1.25ms	8.07ms
React Router	102.4ms	102.36ms	17ms	1.37ms	2.41ms	13.23ms
SolidStart	92.2ms	92.38ms	16.14ms	0.82ms	2.53ms	12.79ms
SvelteKit	89.2ms	89.1ms	14.72ms	1.62ms	3.51ms	9.59ms
TanStack Start	118.2ms	118.4ms	26.17ms	1.61ms	14.54ms	10.02ms

First Paint (ms)

First Paint (ms) chart

First Paint (ms) data

Framework	Milliseconds
Astro	67.80 ms
Mastro	77.80 ms
SvelteKit	89.20 ms
SolidStart	92.20 ms
Nuxt	98.20 ms
React Router	102.40 ms
TanStack Start	118.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	67.84 ms
Mastro	77.71 ms
SvelteKit	89.10 ms
SolidStart	92.38 ms
Nuxt	98.09 ms
React Router	102.36 ms
TanStack Start	118.40 ms
Next.js	143.07 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.43 ms

Median: 16.14 ms

1.37 ms

M

1.85 ms

9.82 ms

14.72 ms

16.14 ms

16.76 ms

17.00 ms

26.17 ms

Interaction Breakdown data

Framework or version	Interaction latency	Input delay	Processing duration	Presentation delay
Astro	1.37 ms	0.67 ms	0.70 ms	0.00 ms
Mastro	1.85 ms	1.53 ms	0.31 ms	0.00 ms
Nuxt	9.82 ms	0.49 ms	1.25 ms	8.07 ms
SvelteKit	14.72 ms	1.62 ms	3.51 ms	9.59 ms
SolidStart	16.14 ms	0.82 ms	2.53 ms	12.79 ms
Next.js	16.76 ms	1.21 ms	7.52 ms	8.04 ms
React Router	17.00 ms	1.37 ms	2.41 ms	13.23 ms
TanStack Start	26.17 ms	1.61 ms	14.54 ms	10.02 ms

Server Side Throughput Tests

Methodology: Server Side Throughput Tests.

Framework	Ops/sec	Median Latency	Body Size	Duplication
Baseline HTML	851	1.198ms	96.83kb	1x
Astro	661	1.451ms	96.89kb	1x
Mastro	345	2.866ms	327.46kb	1.5x
Next.js	236	4.46ms	199.52kb	2x
Nuxt	361	2.658ms	201.27kb	2x
React Router	338	2.886ms	211.63kb	2x
SolidStart	422	2.283ms	224.17kb	2x
SvelteKit	454	2.13ms	183.53kb	2x
TanStack Start	323	3.036ms	193.62kb	2x

Ops/sec

Ops/sec chart

Ops/sec data

Framework	Operations per second
Baseline HTML	851
Astro	661
SvelteKit	454
SolidStart	422
Nuxt	361
Mastro	345
React Router	338
TanStack Start	323
Next.js	236

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.52 KB
Nuxt	201.27 KB
React Router	211.63 KB
SolidStart	224.17 KB
Mastro	327.46 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.13 ms
SolidStart	2.28 ms
Nuxt	2.66 ms
Mastro	2.87 ms
React Router	2.89 ms
TanStack Start	3.04 ms
Next.js	4.46 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,642	200	17ms	46ms	100ms	49,088
Astro	1,222	100	30ms	66ms	279ms	36,185
Mastro	582.6	25	44ms	112ms	1431ms	18,499
Next.js	42	5	1946ms	4807ms	4672ms	1,162
Nuxt	73	10	1886ms	4109ms	4111ms	2,385
React Router	175.8	25	213ms	1637ms	3959ms	5,829
SolidStart	537.4	25	101ms	170ms	2083ms	17,413
SvelteKit	504	25	83ms	226ms	2404ms	15,921
TanStack Start	43.8	5	3567ms	4090ms	4593ms	1,353

P99 Latency

P99 Latency at 25 Connections

P99 Latency at 25 Connections chart

P99 Latency at 25 Connections data

Framework	Milliseconds
Baseline HTML	17.00 ms
Astro	30.00 ms
Mastro	44.00 ms
SvelteKit	83.00 ms
SolidStart	101.00 ms
React Router	213.00 ms
Nuxt	1886.00 ms
Next.js	1946.00 ms
TanStack Start	3567.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	66.00 ms
Mastro	112.00 ms
SolidStart	170.00 ms
SvelteKit	226.00 ms
React Router	1637.00 ms
TanStack Start	4090.00 ms
Nuxt	4109.00 ms
Next.js	4807.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	100.00 ms
Astro	279.00 ms
Mastro	1431.00 ms
SolidStart	2083.00 ms
SvelteKit	2404.00 ms
React Router	3959.00 ms
Nuxt	4111.00 ms
TanStack Start	4593.00 ms
Next.js	4672.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	17.00 ms
Astro	23.00 ms
Mastro	44.00 ms
SvelteKit	59.00 ms
SolidStart	66.00 ms
React Router	147.00 ms
Nuxt	342.00 ms
Next.js	712.00 ms
TanStack Start	731.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	31.00 ms
Astro	45.00 ms
Mastro	86.00 ms
SvelteKit	142.00 ms
SolidStart	147.00 ms
React Router	306.00 ms
Nuxt	480.00 ms
TanStack Start	898.00 ms
Next.js	2450.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	77.00 ms
Astro	81.00 ms
SolidStart	177.00 ms
Mastro	181.00 ms
SvelteKit	255.00 ms
React Router	390.00 ms
Nuxt	500.00 ms
TanStack Start	1362.00 ms
Next.js	2764.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	92	88	92	81	98
SolidStart	81	75	100	88	100
SvelteKit	79	78	78	69	95
Next.js	73	71	76	66	94
Nuxt	67	58	70	59	96
React Router	59	60	64	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	%
Astro	92
SolidStart	81
SvelteKit	79
Next.js	73
Nuxt	67
React Router	59

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	88
SvelteKit	78
SolidStart	75
Next.js	71
React Router	60
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	78
Next.js	76
Nuxt	70
React Router	64

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	88
Astro	81
SvelteKit	69
React Router	68
Next.js	66
Nuxt	59

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
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%
SolidStart	80	80	100	87	90
Astro	79	93	72	63	85
SvelteKit	67	80	58	55	74
Next.js	52	71	48	46	58
Nuxt	45	58	43	45	65
React Router	37	63	36	51	53

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	80
Astro	79
SvelteKit	67
Next.js	52
Nuxt	45
React Router	37

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
SolidStart	80
SvelteKit	80
Next.js	71
React Router	63
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	72
SvelteKit	58
Next.js	48
Nuxt	43
React Router	36

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	87
Astro	63
SvelteKit	55
React Router	51
Next.js	46
Nuxt	45

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	90
Astro	85
SvelteKit	74
Nuxt	65
Next.js	58
React Router	53

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

Methodology: Core Web Vitals.