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.01s	1.78s	3.55s	0.87s	0.84s	0.03MB
Mastro	0.47s	0.45s	0.49s	0.29s	0.29s	0.01MB
Next.js	5.74s	3.12s	6.51s	4.87s	4.90s	6.03MB
Nuxt	4.40s	2.83s	5.26s	3.98s	3.67s	2.46MB
React Router	1.32s	1.12s	1.65s	1.61s	1.57s	0.38MB
SolidStart	1.68s	1.44s	2.03s	2.65s	2.55s	0.51MB
SvelteKit	1.47s	1.30s	1.60s	1.75s	1.73s	1.44MB
TanStack Start	4.19s	1.90s	5.02s	5.21s	4.94s	2.05MB

Avg install time

Avg install time chart

Avg install time data

Framework	Seconds
Mastro	0.47s
React Router	1.32s
SvelteKit	1.47s
SolidStart	1.68s
Astro	3.01s
TanStack Start	4.19s
Nuxt	4.40s
Next.js	5.74s

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.29s
Astro	0.87s
React Router	1.61s
SvelteKit	1.75s
SolidStart	2.65s
Nuxt	3.98s
Next.js	4.87s
TanStack Start	5.21s

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.29s
Astro	0.84s
React Router	1.57s
SvelteKit	1.73s
SolidStart	2.55s
Nuxt	3.67s
Next.js	4.90s
TanStack Start	4.94s

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	—	—
Next.js	—	—
Nuxt	—	—
React Router	—	—
SolidStart	—	—
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	105.4ms	105.47ms	1.93ms	1.67ms	0.26ms	0ms
Next.js	342.8ms	342.81ms	18.57ms	1.29ms	6.23ms	11.05ms
Nuxt	151.6ms	151.77ms	9.19ms	0.61ms	1.5ms	7.09ms
React Router	154.6ms	154.67ms	18.85ms	1.51ms	3ms	14.34ms
SolidStart	108.8ms	108.77ms	17.71ms	0.89ms	2.3ms	14.52ms
SvelteKit	116.8ms	116.61ms	16.37ms	0.63ms	3.65ms	12.09ms
TanStack Start	137.8ms	137.78ms	25.62ms	1.62ms	13.47ms	10.52ms

First Paint (ms)

First Paint (ms) chart

First Paint (ms) data

Framework	Milliseconds
Astro	105.40 ms
SolidStart	108.80 ms
SvelteKit	116.80 ms
TanStack Start	137.80 ms
Nuxt	151.60 ms
React Router	154.60 ms
Next.js	342.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	105.47 ms
SolidStart	108.77 ms
SvelteKit	116.61 ms
TanStack Start	137.78 ms
Nuxt	151.77 ms
React Router	154.67 ms
Next.js	342.81 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: 17.71 ms

Median: 17.71 ms

1.93 ms

9.19 ms

16.37 ms

17.71 ms

18.57 ms

18.85 ms

25.62 ms

Interaction Breakdown data

Framework or version	Interaction latency	Input delay	Processing duration	Presentation delay
Astro	1.93 ms	1.67 ms	0.26 ms	0.00 ms
Nuxt	9.19 ms	0.61 ms	1.50 ms	7.09 ms
SvelteKit	16.37 ms	0.63 ms	3.65 ms	12.09 ms
SolidStart	17.71 ms	0.89 ms	2.30 ms	14.52 ms
Next.js	18.57 ms	1.29 ms	6.23 ms	11.05 ms
React Router	18.85 ms	1.51 ms	3.00 ms	14.34 ms
TanStack Start	25.62 ms	1.62 ms	13.47 ms	10.52 ms

Server Side Rendered Tests

Methodology: Server Side Rendered Tests.

Framework	First Paint	FCP	Interaction Latency	Input Delay	Processing Duration	Presentation Delay
Astro	75.2ms	75.09ms	0.98ms	0.69ms	0.29ms	0ms
Mastro	72.2ms	72.17ms	5.21ms	0.49ms	0.5ms	4.22ms
Next.js	140.8ms	140.59ms	16.83ms	1.22ms	5.45ms	10.17ms
Nuxt	104.4ms	104.42ms	11.33ms	0.43ms	1.16ms	9.75ms
React Router	112.2ms	112.07ms	22.15ms	1.61ms	5.13ms	15.41ms
SolidStart	100.6ms	100.81ms	13.18ms	0.85ms	2.45ms	9.88ms
SvelteKit	86.6ms	86.81ms	15.11ms	0.74ms	2.76ms	11.61ms
TanStack Start	117.6ms	117.72ms	25.61ms	1.6ms	13.66ms	10.35ms

First Paint (ms)

First Paint (ms) chart

First Paint (ms) data

Framework	Milliseconds
Mastro	72.20 ms
Astro	75.20 ms
SvelteKit	86.60 ms
SolidStart	100.60 ms
Nuxt	104.40 ms
React Router	112.20 ms
TanStack Start	117.60 ms
Next.js	140.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
Mastro	72.17 ms
Astro	75.09 ms
SvelteKit	86.81 ms
SolidStart	100.81 ms
Nuxt	104.42 ms
React Router	112.07 ms
TanStack Start	117.72 ms
Next.js	140.59 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.14 ms

Median: 15.11 ms

0.98 ms

M

5.21 ms

11.33 ms

13.18 ms

15.11 ms

16.83 ms

22.15 ms

25.61 ms

Interaction Breakdown data

Framework or version	Interaction latency	Input delay	Processing duration	Presentation delay
Astro	0.98 ms	0.69 ms	0.29 ms	0.00 ms
Mastro	5.21 ms	0.49 ms	0.50 ms	4.22 ms
Nuxt	11.33 ms	0.43 ms	1.16 ms	9.75 ms
SolidStart	13.18 ms	0.85 ms	2.45 ms	9.88 ms
SvelteKit	15.11 ms	0.74 ms	2.76 ms	11.61 ms
Next.js	16.83 ms	1.22 ms	5.45 ms	10.17 ms
React Router	22.15 ms	1.61 ms	5.13 ms	15.41 ms
TanStack Start	25.61 ms	1.60 ms	13.66 ms	10.35 ms

Server Side Throughput Tests

Methodology: Server Side Throughput Tests.

Framework	Ops/sec	Median Latency	Body Size	Duplication
Baseline HTML	845	1.2ms	96.83kb	1x
Astro	670	1.437ms	96.89kb	1x
Mastro	229	4.318ms	327.46kb	1.5x
Next.js	231	4.486ms	199.57kb	2x
Nuxt	371	2.626ms	201.27kb	2x
React Router	326	3.018ms	211.63kb	2x
SolidStart	426	2.253ms	224.17kb	2x
SvelteKit	447	2.168ms	183.53kb	2x
TanStack Start	321	3.066ms	193.62kb	2x

Ops/sec

Ops/sec chart

Ops/sec data

Framework	Operations per second
Baseline HTML	845
Astro	670
SvelteKit	447
SolidStart	426
Nuxt	371
React Router	326
TanStack Start	321
Next.js	231
Mastro	229

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.44 ms
SvelteKit	2.17 ms
SolidStart	2.25 ms
Nuxt	2.63 ms
React Router	3.02 ms
TanStack Start	3.07 ms
Mastro	4.32 ms
Next.js	4.49 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,633.8	50	18ms	38ms	95ms	48,288
Astro	1,185	50	44ms	72ms	259ms	34,260
Mastro	578.6	25	46ms	129ms	1430ms	18,219
Next.js	35.21	1	2282ms	4689ms	4775ms	985
Nuxt	66	10	2011ms	4039ms	4274ms	2,127
React Router	170	100	186ms	1854ms	3909ms	5,411
SolidStart	513.6	25	100ms	509ms	2347ms	15,711
SvelteKit	490.2	10	83ms	436ms	2287ms	15,399
TanStack Start	43	10	3329ms	4610ms	4351ms	1,320

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	44.00 ms
Mastro	46.00 ms
SvelteKit	83.00 ms
SolidStart	100.00 ms
React Router	186.00 ms
Nuxt	2011.00 ms
Next.js	2282.00 ms
TanStack Start	3329.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	72.00 ms
Mastro	129.00 ms
SvelteKit	436.00 ms
SolidStart	509.00 ms
React Router	1854.00 ms
Nuxt	4039.00 ms
TanStack Start	4610.00 ms
Next.js	4689.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	95.00 ms
Astro	259.00 ms
Mastro	1430.00 ms
SvelteKit	2287.00 ms
SolidStart	2347.00 ms
React Router	3909.00 ms
Nuxt	4274.00 ms
TanStack Start	4351.00 ms
Next.js	4775.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	27.00 ms
Mastro	44.00 ms
SvelteKit	62.00 ms
SolidStart	71.00 ms
React Router	166.00 ms
Nuxt	409.00 ms
TanStack Start	738.00 ms
Next.js	855.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
Mastro	91.00 ms
SvelteKit	134.00 ms
SolidStart	162.00 ms
React Router	308.00 ms
Nuxt	493.00 ms
TanStack Start	850.00 ms
Next.js	2636.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
Mastro	184.00 ms
SolidStart	194.00 ms
SvelteKit	223.00 ms
React Router	421.00 ms
Nuxt	610.00 ms
TanStack Start	1424.00 ms
Next.js	2924.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.