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	Build Output
Astro	3.04s	1.59s	3.83s	0.83s	0.80s	0.03MB
Mastro	0.48s	0.47s	0.50s	0.30s	0.30s	0.01MB
Next.js	5.49s	2.92s	6.24s	5.01s	5.02s	6.03MB
Nuxt	4.68s	3.01s	5.56s	3.51s	3.40s	2.46MB
React Router	1.42s	1.12s	1.60s	1.69s	1.71s	0.38MB
SolidStart	1.75s	1.42s	1.99s	2.96s	2.81s	0.51MB
SvelteKit	1.49s	1.32s	1.74s	1.83s	1.68s	1.44MB
TanStack Start	4.09s	1.90s	4.78s	5.27s	5.06s	2.05MB

Avg install time

Avg install time chart

Avg install time data

Framework	Seconds
Mastro	0.48s
React Router	1.42s
SvelteKit	1.49s
SolidStart	1.75s
Astro	3.04s
TanStack Start	4.09s
Nuxt	4.68s
Next.js	5.49s

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.83s
React Router	1.69s
SvelteKit	1.83s
SolidStart	2.96s
Nuxt	3.51s
Next.js	5.01s
TanStack Start	5.27s

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	0.80s
SvelteKit	1.68s
React Router	1.71s
SolidStart	2.81s
Nuxt	3.40s
Next.js	5.02s
TanStack Start	5.06s

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

Build output size

Build output size chart

Build output size data

Framework	Megabytes
Mastro	0.01 MB
Astro	0.03 MB
React Router	0.38 MB
SolidStart	0.51 MB
SvelteKit	1.44 MB
TanStack Start	2.05 MB
Nuxt	2.46 MB
Next.js	6.03 MB

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	—	—
Mastro	v24.12.0	starter-mastro
Next.js	—	—
Nuxt	—	—
React Router	—	—
SolidStart	v24.0.0	starter-solid-start
SvelteKit	—	—
TanStack Start	—	—

Client Side Rendered Tests

Methodology: Client Side Rendered Tests.

Framework	First Paint	FCP	Interaction Latency	Input Delay	Processing Duration	Presentation Delay
Astro	111.6ms	111.32ms	6.78ms	1.68ms	0.38ms	4.73ms
Next.js	341.4ms	341.31ms	20.62ms	1.04ms	7.11ms	12.47ms
Nuxt	159.6ms	159.5ms	12.04ms	1.03ms	1.28ms	9.73ms
React Router	147.6ms	147.69ms	21.28ms	1.41ms	2.15ms	17.72ms
SolidStart	111.4ms	111.16ms	16.5ms	0.89ms	2.37ms	13.25ms
SvelteKit	110.6ms	110.85ms	14.54ms	0.58ms	2.08ms	11.88ms
TanStack Start	144.6ms	144.61ms	23.58ms	1.33ms	11.52ms	10.73ms

First Paint (ms)

First Paint (ms) chart

First Paint (ms) data

Framework	Milliseconds
SvelteKit	110.60 ms
SolidStart	111.40 ms
Astro	111.60 ms
TanStack Start	144.60 ms
React Router	147.60 ms
Nuxt	159.60 ms
Next.js	341.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
SvelteKit	110.85 ms
SolidStart	111.16 ms
Astro	111.32 ms
TanStack Start	144.61 ms
React Router	147.69 ms
Nuxt	159.50 ms
Next.js	341.31 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.50 ms

Median: 16.50 ms

6.78 ms

12.04 ms

14.54 ms

16.50 ms

20.62 ms

21.28 ms

23.58 ms

Interaction Breakdown data

Framework or version	Interaction latency	Input delay	Processing duration	Presentation delay
Astro	6.78 ms	1.68 ms	0.38 ms	4.73 ms
Nuxt	12.04 ms	1.03 ms	1.28 ms	9.73 ms
SvelteKit	14.54 ms	0.58 ms	2.08 ms	11.88 ms
SolidStart	16.50 ms	0.89 ms	2.37 ms	13.25 ms
Next.js	20.62 ms	1.04 ms	7.11 ms	12.47 ms
React Router	21.28 ms	1.41 ms	2.15 ms	17.72 ms
TanStack Start	23.58 ms	1.33 ms	11.52 ms	10.73 ms

Server Side Rendered Tests

Methodology: Server Side Rendered Tests.

Framework	First Paint	FCP	Interaction Latency	Input Delay	Processing Duration	Presentation Delay
Astro	73.6ms	73.69ms	1.09ms	0.83ms	0.26ms	0ms
Mastro	81.8ms	81.94ms	11.95ms	0.42ms	0.95ms	10.59ms
Next.js	171.8ms	172.03ms	23.53ms	1.41ms	10.04ms	12.07ms
Nuxt	116.2ms	116.21ms	10.39ms	0.98ms	1.35ms	8.05ms
React Router	118.6ms	118.69ms	19.22ms	1.59ms	2.76ms	14.87ms
SolidStart	91.2ms	91.27ms	16.5ms	0.88ms	1.99ms	13.63ms
SvelteKit	79.6ms	79.7ms	17.13ms	0.71ms	4.16ms	12.25ms
TanStack Start	126ms	126.13ms	29.1ms	1.72ms	16.47ms	10.91ms

First Paint (ms)

First Paint (ms) chart

First Paint (ms) data

Framework	Milliseconds
Astro	73.60 ms
SvelteKit	79.60 ms
Mastro	81.80 ms
SolidStart	91.20 ms
Nuxt	116.20 ms
React Router	118.60 ms
TanStack Start	126.00 ms
Next.js	171.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
Astro	73.69 ms
SvelteKit	79.70 ms
Mastro	81.94 ms
SolidStart	91.27 ms
Nuxt	116.21 ms
React Router	118.69 ms
TanStack Start	126.13 ms
Next.js	172.03 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.81 ms

Median: 17.13 ms

1.09 ms

10.39 ms

M

11.95 ms

16.50 ms

17.13 ms

19.22 ms

23.53 ms

29.10 ms

Interaction Breakdown data

Framework or version	Interaction latency	Input delay	Processing duration	Presentation delay
Astro	1.09 ms	0.83 ms	0.26 ms	0.00 ms
Nuxt	10.39 ms	0.98 ms	1.35 ms	8.05 ms
Mastro	11.95 ms	0.42 ms	0.95 ms	10.59 ms
SolidStart	16.50 ms	0.88 ms	1.99 ms	13.63 ms
SvelteKit	17.13 ms	0.71 ms	4.16 ms	12.25 ms
React Router	19.22 ms	1.59 ms	2.76 ms	14.87 ms
Next.js	23.53 ms	1.41 ms	10.04 ms	12.07 ms
TanStack Start	29.10 ms	1.72 ms	16.47 ms	10.91 ms

Server Side Throughput Tests

Methodology: Server Side Throughput Tests.

Framework	Ops/sec	Median Latency	Body Size	Duplication
Baseline HTML	851	1.196ms	96.83kb	1x
Astro	665	1.458ms	96.89kb	1x
Mastro	348	2.851ms	327.46kb	1.5x
Next.js	226	4.548ms	199.57kb	2x
Nuxt	353	2.773ms	201.27kb	2x
React Router	345	2.867ms	211.63kb	2x
SolidStart	424	2.285ms	224.17kb	2x
SvelteKit	460	2.109ms	183.53kb	2x
TanStack Start	327	3.018ms	193.62kb	2x

Ops/sec

Ops/sec chart

Ops/sec data

Framework	Operations per second
Baseline HTML	851
Astro	665
SvelteKit	460
SolidStart	424
Nuxt	353
Mastro	348
React Router	345
TanStack Start	327
Next.js	226

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.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.46 ms
SvelteKit	2.11 ms
SolidStart	2.29 ms
Nuxt	2.77 ms
Mastro	2.85 ms
React Router	2.87 ms
TanStack Start	3.02 ms
Next.js	4.55 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,557.4	50	21ms	39ms	109ms	46,087
Astro	1,145.8	100	43ms	84ms	328ms	33,579
Mastro	591.6	50	48ms	111ms	1369ms	18,562
Next.js	36.4	1	2157ms	4740ms	4771ms	995
Nuxt	68.8	25	1965ms	4077ms	4448ms	2,155
React Router	139.2	100	274ms	2534ms	4146ms	4,571
SolidStart	503.4	25	109ms	546ms	2183ms	15,523
SvelteKit	495.8	10	84ms	216ms	2384ms	15,597
TanStack Start	42.8	5	3449ms	4349ms	4436ms	1,297

P99 Latency

P99 Latency at 25 Connections

P99 Latency at 25 Connections chart

P99 Latency at 25 Connections data

Framework	Milliseconds
Baseline HTML	21.00 ms
Astro	43.00 ms
Mastro	48.00 ms
SvelteKit	84.00 ms
SolidStart	109.00 ms
React Router	274.00 ms
Nuxt	1965.00 ms
Next.js	2157.00 ms
TanStack Start	3449.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	39.00 ms
Astro	84.00 ms
Mastro	111.00 ms
SvelteKit	216.00 ms
SolidStart	546.00 ms
React Router	2534.00 ms
Nuxt	4077.00 ms
TanStack Start	4349.00 ms
Next.js	4740.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	109.00 ms
Astro	328.00 ms
Mastro	1369.00 ms
SolidStart	2183.00 ms
SvelteKit	2384.00 ms
React Router	4146.00 ms
TanStack Start	4436.00 ms
Nuxt	4448.00 ms
Next.js	4771.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	24.00 ms
Mastro	43.00 ms
SvelteKit	63.00 ms
SolidStart	73.00 ms
React Router	211.00 ms
Nuxt	369.00 ms
TanStack Start	745.00 ms
Next.js	761.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	34.00 ms
Astro	47.00 ms
Mastro	85.00 ms
SvelteKit	135.00 ms
SolidStart	155.00 ms
React Router	365.00 ms
Nuxt	500.00 ms
TanStack Start	826.00 ms
Next.js	2446.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	90.00 ms
Mastro	189.00 ms
SolidStart	192.00 ms
SvelteKit	214.00 ms
React Router	401.00 ms
Nuxt	639.00 ms
TanStack Start	1401.00 ms
Next.js	2932.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	91	87	91	82	97
SolidStart	91	66	91	83	100
SvelteKit	79	77	78	71	94
Next.js	72	69	76	67	94
React Router	61	62	66	70	90
Nuxt	65	57	67	59	95

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	91
SolidStart	91
SvelteKit	79
Next.js	72
Nuxt	65
React Router	61

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	87
SvelteKit	77
Next.js	69
SolidStart	66
React Router	62
Nuxt	57

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	%
Astro	91
SolidStart	91
SvelteKit	78
Next.js	76
Nuxt	67
React Router	66

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	83
Astro	82
SvelteKit	71
React Router	70
Next.js	67
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	97
Nuxt	95
SvelteKit	94
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%
Astro	77	92	71	60	86
SolidStart	90	63	90	81	100
SvelteKit	67	81	60	58	75
Next.js	51	69	50	47	58
Nuxt	45	58	43	45	65
React Router	41	64	41	53	56

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	90
Astro	77
SvelteKit	67
Next.js	51
Nuxt	45
React Router	41

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	92
SvelteKit	81
Next.js	69
React Router	64
SolidStart	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	90
Astro	71
SvelteKit	60
Next.js	50
Nuxt	43
React Router	41

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	81
Astro	60
SvelteKit	58
React Router	53
Next.js	47
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	100
Astro	86
SvelteKit	75
Nuxt	65
Next.js	58
React Router	56

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

Methodology: Core Web Vitals.