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.07s	1.69s	3.89s	0.86s	0.82s
Mastro	0.52s	0.51s	0.53s	0.30s	0.30s
Next.js	5.66s	3.22s	6.47s	5.88s	5.58s
Nuxt	4.77s	3.07s	5.75s	3.71s	3.52s
React Router	1.90s	1.35s	2.19s	1.63s	1.64s
SolidStart	1.79s	1.47s	1.94s	2.80s	2.68s
SvelteKit	1.42s	1.31s	1.59s	1.77s	1.61s
TanStack Start	4.74s	4.26s	5.48s	5.23s	5.05s

Avg install time

Avg install time chart

Avg install time data

Framework	Seconds
Mastro	0.52s
SvelteKit	1.42s
SolidStart	1.79s
React Router	1.90s
Astro	3.07s
TanStack Start	4.74s
Nuxt	4.77s
Next.js	5.66s

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.86s
React Router	1.63s
SvelteKit	1.77s
SolidStart	2.80s
Nuxt	3.71s
TanStack Start	5.23s
Next.js	5.88s

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.82s
SvelteKit	1.61s
React Router	1.64s
SolidStart	2.68s
Nuxt	3.52s
TanStack Start	5.05s
Next.js	5.58s

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	107.2ms	107.46ms	2.58ms	1.84ms	0.74ms	0ms
Next.js	339.4ms	339.33ms	18.05ms	1.11ms	7.1ms	9.84ms
Nuxt	169.2ms	169.33ms	12.64ms	0.43ms	1.74ms	10.47ms
React Router	158.2ms	158.37ms	20.37ms	1.47ms	2.31ms	16.58ms
SolidStart	105.8ms	105.96ms	12.97ms	0.89ms	2.08ms	10ms
SvelteKit	112.4ms	112.37ms	16.71ms	1.38ms	2.62ms	12.72ms
TanStack Start	159.8ms	159.85ms	23.26ms	1.62ms	13.69ms	7.95ms

First Paint (ms)

First Paint (ms) chart

First Paint (ms) data

Framework	Milliseconds
SolidStart	105.80 ms
Astro	107.20 ms
SvelteKit	112.40 ms
React Router	158.20 ms
TanStack Start	159.80 ms
Nuxt	169.20 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
SolidStart	105.96 ms
Astro	107.46 ms
SvelteKit	112.37 ms
React Router	158.37 ms
TanStack Start	159.85 ms
Nuxt	169.33 ms
Next.js	339.33 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.71 ms

Median: 16.71 ms

2.58 ms

12.64 ms

12.97 ms

16.71 ms

18.05 ms

20.37 ms

23.26 ms

Interaction Breakdown data

Framework or version	Interaction latency	Input delay	Processing duration	Presentation delay
Astro	2.58 ms	1.84 ms	0.74 ms	0.00 ms
Nuxt	12.64 ms	0.43 ms	1.74 ms	10.47 ms
SolidStart	12.97 ms	0.89 ms	2.08 ms	10.00 ms
SvelteKit	16.71 ms	1.38 ms	2.62 ms	12.72 ms
Next.js	18.05 ms	1.11 ms	7.10 ms	9.84 ms
React Router	20.37 ms	1.47 ms	2.31 ms	16.58 ms
TanStack Start	23.26 ms	1.62 ms	13.69 ms	7.95 ms

Server Side Rendered Tests

Methodology: Server Side Rendered Tests.

Framework	First Paint	FCP	Interaction Latency	Input Delay	Processing Duration	Presentation Delay
Astro	66.4ms	66.38ms	1.41ms	1.17ms	0.24ms	0ms
Mastro	90.4ms	90.37ms	3.76ms	0.64ms	0.29ms	2.83ms
Next.js	142.4ms	142.45ms	17.22ms	1.32ms	8.34ms	7.56ms
Nuxt	113.4ms	113.66ms	10.85ms	0.51ms	2.19ms	8.15ms
React Router	112ms	112.03ms	16.09ms	1.5ms	2.73ms	11.86ms
SolidStart	86.2ms	86.13ms	15.12ms	0.92ms	2.47ms	11.73ms
SvelteKit	100.4ms	100.34ms	17.9ms	1.02ms	3.86ms	13.02ms
TanStack Start	126ms	125.99ms	27.78ms	1.5ms	13.54ms	12.74ms

First Paint (ms)

First Paint (ms) chart

First Paint (ms) data

Framework	Milliseconds
Astro	66.40 ms
SolidStart	86.20 ms
Mastro	90.40 ms
SvelteKit	100.40 ms
React Router	112.00 ms
Nuxt	113.40 ms
TanStack Start	126.00 ms
Next.js	142.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	66.38 ms
SolidStart	86.13 ms
Mastro	90.37 ms
SvelteKit	100.34 ms
React Router	112.03 ms
Nuxt	113.66 ms
TanStack Start	125.99 ms
Next.js	142.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.61 ms

Median: 16.09 ms

1.41 ms

M

3.76 ms

10.85 ms

15.12 ms

16.09 ms

17.22 ms

17.90 ms

27.78 ms

Interaction Breakdown data

Framework or version	Interaction latency	Input delay	Processing duration	Presentation delay
Astro	1.41 ms	1.17 ms	0.24 ms	0.00 ms
Mastro	3.76 ms	0.64 ms	0.29 ms	2.83 ms
Nuxt	10.85 ms	0.51 ms	2.19 ms	8.15 ms
SolidStart	15.12 ms	0.92 ms	2.47 ms	11.73 ms
React Router	16.09 ms	1.50 ms	2.73 ms	11.86 ms
Next.js	17.22 ms	1.32 ms	8.34 ms	7.56 ms
SvelteKit	17.90 ms	1.02 ms	3.86 ms	13.02 ms
TanStack Start	27.78 ms	1.50 ms	13.54 ms	12.74 ms

Server Side Throughput Tests

Methodology: Server Side Throughput Tests.

Framework	Ops/sec	Median Latency	Body Size	Duplication
Baseline HTML	845	1.205ms	96.83kb	1x
Astro	665	1.456ms	96.89kb	1x
Mastro	351	2.82ms	327.46kb	1.5x
Next.js	212	4.778ms	199.52kb	2x
Nuxt	357	2.7ms	201.27kb	2x
React Router	347	2.849ms	211.63kb	2x
SolidStart	427	2.264ms	224.17kb	2x
SvelteKit	459	2.113ms	183.53kb	2x
TanStack Start	309	3.21ms	193.62kb	2x

Ops/sec

Ops/sec chart

Ops/sec data

Framework	Operations per second
Baseline HTML	845
Astro	665
SvelteKit	459
SolidStart	427
Nuxt	357
Mastro	351
React Router	347
TanStack Start	309
Next.js	212

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.21 ms
Astro	1.46 ms
SvelteKit	2.11 ms
SolidStart	2.26 ms
Nuxt	2.70 ms
Mastro	2.82 ms
React Router	2.85 ms
TanStack Start	3.21 ms
Next.js	4.78 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,649.6	100	18ms	47ms	100ms	48,817
Astro	1,186	25	30ms	64ms	321ms	35,924
Mastro	352.8	25	73ms	193ms	3086ms	11,393
Next.js	39.4	5	2044ms	4583ms	4789ms	1,119
Nuxt	74	10	1868ms	4127ms	4313ms	2,399
React Router	166.2	10	264ms	1896ms	4030ms	5,481
SolidStart	505.4	100	128ms	466ms	2079ms	15,604
SvelteKit	487.6	5	94ms	208ms	2533ms	15,474
TanStack Start	45	5	3716ms	4149ms	4406ms	1,365

P99 Latency

P99 Latency at 25 Connections

P99 Latency at 25 Connections chart

P99 Latency at 25 Connections data

Framework	Milliseconds
Baseline HTML	18.00 ms
Astro	30.00 ms
Mastro	73.00 ms
SvelteKit	94.00 ms
SolidStart	128.00 ms
React Router	264.00 ms
Nuxt	1868.00 ms
Next.js	2044.00 ms
TanStack Start	3716.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	47.00 ms
Astro	64.00 ms
Mastro	193.00 ms
SvelteKit	208.00 ms
SolidStart	466.00 ms
React Router	1896.00 ms
Nuxt	4127.00 ms
TanStack Start	4149.00 ms
Next.js	4583.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	321.00 ms
SolidStart	2079.00 ms
SvelteKit	2533.00 ms
Mastro	3086.00 ms
React Router	4030.00 ms
Nuxt	4313.00 ms
TanStack Start	4406.00 ms
Next.js	4789.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	22.00 ms
SvelteKit	66.00 ms
Mastro	71.00 ms
SolidStart	78.00 ms
React Router	164.00 ms
Nuxt	334.00 ms
Next.js	711.00 ms
TanStack Start	752.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	32.00 ms
Astro	43.00 ms
SvelteKit	140.00 ms
Mastro	146.00 ms
SolidStart	154.00 ms
React Router	321.00 ms
Nuxt	478.00 ms
TanStack Start	876.00 ms
Next.js	2404.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	84.00 ms
SolidStart	153.00 ms
SvelteKit	220.00 ms
Mastro	290.00 ms
React Router	418.00 ms
Nuxt	509.00 ms
TanStack Start	1306.00 ms
Next.js	2641.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.