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	2.84s	1.62s	3.54s	0.83s	0.81s	0.03MB
Mastro	0.47s	0.45s	0.49s	0.29s	0.29s	0.01MB
Next.js	5.32s	2.98s	6.15s	5.00s	5.13s	6.03MB
Nuxt	4.81s	3.02s	5.57s	3.59s	3.52s	2.46MB
React Router	1.65s	1.21s	1.79s	1.61s	1.61s	0.38MB
SolidStart	1.71s	1.40s	1.99s	2.76s	2.65s	0.51MB
SvelteKit	1.44s	1.28s	1.59s	1.81s	1.67s	1.44MB
TanStack Start	4.18s	1.82s	4.99s	5.33s	5.16s	2.05MB

Avg install time

Avg install time chart

Avg install time data

Framework	Seconds
Mastro	0.47s
SvelteKit	1.44s
React Router	1.65s
SolidStart	1.71s
Astro	2.84s
TanStack Start	4.18s
Nuxt	4.81s
Next.js	5.32s

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.83s
React Router	1.61s
SvelteKit	1.81s
SolidStart	2.76s
Nuxt	3.59s
Next.js	5.00s
TanStack Start	5.33s

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.81s
React Router	1.61s
SvelteKit	1.67s
SolidStart	2.65s
Nuxt	3.52s
Next.js	5.13s
TanStack Start	5.16s

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	99.6ms	99.49ms	1.85ms	1.57ms	0.28ms	0ms
Next.js	342.4ms	342.3ms	22.4ms	1.37ms	6.04ms	15ms
Nuxt	149.4ms	149.46ms	10.15ms	0.46ms	1.15ms	8.55ms
React Router	148.8ms	148.67ms	21.07ms	1.48ms	3.28ms	16.32ms
SolidStart	104ms	104.04ms	13.28ms	0.94ms	2.28ms	10.05ms
SvelteKit	119.4ms	119.34ms	12.31ms	0.65ms	2.47ms	9.2ms
TanStack Start	169ms	169.15ms	25.86ms	1.58ms	13.94ms	10.34ms

First Paint (ms)

First Paint (ms) chart

First Paint (ms) data

Framework	Milliseconds
Astro	99.60 ms
SolidStart	104.00 ms
SvelteKit	119.40 ms
React Router	148.80 ms
Nuxt	149.40 ms
TanStack Start	169.00 ms
Next.js	342.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	99.49 ms
SolidStart	104.04 ms
SvelteKit	119.34 ms
React Router	148.67 ms
Nuxt	149.46 ms
TanStack Start	169.15 ms
Next.js	342.30 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: 13.28 ms

Median: 13.28 ms

1.85 ms

10.15 ms

12.31 ms

13.28 ms

21.07 ms

22.40 ms

25.86 ms

Interaction Breakdown data

Framework or version	Interaction latency	Input delay	Processing duration	Presentation delay
Astro	1.85 ms	1.57 ms	0.28 ms	0.00 ms
Nuxt	10.15 ms	0.46 ms	1.15 ms	8.55 ms
SvelteKit	12.31 ms	0.65 ms	2.47 ms	9.20 ms
SolidStart	13.28 ms	0.94 ms	2.28 ms	10.05 ms
React Router	21.07 ms	1.48 ms	3.28 ms	16.32 ms
Next.js	22.40 ms	1.37 ms	6.04 ms	15.00 ms
TanStack Start	25.86 ms	1.58 ms	13.94 ms	10.34 ms

Server Side Rendered Tests

Methodology: Server Side Rendered Tests.

Framework	First Paint	FCP	Interaction Latency	Input Delay	Processing Duration	Presentation Delay
Astro	65.6ms	65.63ms	1.12ms	0.88ms	0.24ms	0ms
Mastro	65.4ms	65.21ms	1.35ms	0.52ms	0.82ms	0ms
Next.js	134.4ms	134.14ms	16.61ms	1.24ms	8.63ms	6.74ms
Nuxt	104ms	104.15ms	9.16ms	0.43ms	1.19ms	7.53ms
React Router	113.6ms	113.53ms	18.18ms	1.49ms	2.76ms	13.92ms
SolidStart	97.6ms	97.38ms	15.84ms	0.82ms	1.97ms	13.04ms
SvelteKit	86ms	86.11ms	13.47ms	0.65ms	3.69ms	9.13ms
TanStack Start	114.2ms	114.22ms	26.66ms	1.48ms	12.44ms	12.74ms

First Paint (ms)

First Paint (ms) chart

First Paint (ms) data

Framework	Milliseconds
Mastro	65.40 ms
Astro	65.60 ms
SvelteKit	86.00 ms
SolidStart	97.60 ms
Nuxt	104.00 ms
React Router	113.60 ms
TanStack Start	114.20 ms
Next.js	134.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
Mastro	65.21 ms
Astro	65.63 ms
SvelteKit	86.11 ms
SolidStart	97.38 ms
Nuxt	104.15 ms
React Router	113.53 ms
TanStack Start	114.22 ms
Next.js	134.14 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.66 ms

Median: 15.84 ms

1.12 ms

M

1.35 ms

9.16 ms

13.47 ms

15.84 ms

16.61 ms

18.18 ms

26.66 ms

Interaction Breakdown data

Framework or version	Interaction latency	Input delay	Processing duration	Presentation delay
Astro	1.12 ms	0.88 ms	0.24 ms	0.00 ms
Mastro	1.35 ms	0.52 ms	0.82 ms	0.00 ms
Nuxt	9.16 ms	0.43 ms	1.19 ms	7.53 ms
SvelteKit	13.47 ms	0.65 ms	3.69 ms	9.13 ms
SolidStart	15.84 ms	0.82 ms	1.97 ms	13.04 ms
Next.js	16.61 ms	1.24 ms	8.63 ms	6.74 ms
React Router	18.18 ms	1.49 ms	2.76 ms	13.92 ms
TanStack Start	26.66 ms	1.48 ms	12.44 ms	12.74 ms

Server Side Throughput Tests

Methodology: Server Side Throughput Tests.

Framework	Ops/sec	Median Latency	Body Size	Duplication
Baseline HTML	847	1.202ms	96.83kb	1x
Astro	667	1.456ms	96.89kb	1x
Mastro	363	2.697ms	327.46kb	1.5x
Next.js	230	4.541ms	199.57kb	2x
Nuxt	367	2.646ms	201.27kb	2x
React Router	353	2.812ms	211.63kb	2x
SolidStart	421	2.278ms	224.17kb	2x
SvelteKit	440	2.188ms	183.53kb	2x
TanStack Start	331	2.999ms	193.62kb	2x

Ops/sec

Ops/sec chart

Ops/sec data

Framework	Operations per second
Baseline HTML	847
Astro	667
SvelteKit	440
SolidStart	421
Nuxt	367
Mastro	363
React Router	353
TanStack Start	331
Next.js	230

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.19 ms
SolidStart	2.28 ms
Nuxt	2.65 ms
Mastro	2.70 ms
React Router	2.81 ms
TanStack Start	3.00 ms
Next.js	4.54 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,656.4	100	18ms	44ms	103ms	49,313
Astro	1,197.2	100	31ms	65ms	279ms	35,992
Mastro	576.8	25	56ms	110ms	1342ms	18,384
Next.js	39.21	5	1998ms	4648ms	4660ms	1,114
Nuxt	72	10	1941ms	4048ms	4133ms	2,335
React Router	174.6	10	278ms	1749ms	3957ms	5,784
SolidStart	525.6	25	97ms	394ms	2045ms	17,078
SvelteKit	498.6	25	79ms	413ms	2168ms	16,227
TanStack Start	41.6	5	3867ms	4277ms	4752ms	1,284

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	31.00 ms
Mastro	56.00 ms
SvelteKit	79.00 ms
SolidStart	97.00 ms
React Router	278.00 ms
Nuxt	1941.00 ms
Next.js	1998.00 ms
TanStack Start	3867.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	44.00 ms
Astro	65.00 ms
Mastro	110.00 ms
SolidStart	394.00 ms
SvelteKit	413.00 ms
React Router	1749.00 ms
Nuxt	4048.00 ms
TanStack Start	4277.00 ms
Next.js	4648.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	103.00 ms
Astro	279.00 ms
Mastro	1342.00 ms
SolidStart	2045.00 ms
SvelteKit	2168.00 ms
React Router	3957.00 ms
Nuxt	4133.00 ms
Next.js	4660.00 ms
TanStack Start	4752.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	61.00 ms
SolidStart	69.00 ms
React Router	168.00 ms
Nuxt	362.00 ms
Next.js	702.00 ms
TanStack Start	800.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	43.00 ms
Mastro	89.00 ms
SvelteKit	120.00 ms
SolidStart	146.00 ms
React Router	297.00 ms
Nuxt	476.00 ms
TanStack Start	779.00 ms
Next.js	2461.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	82.00 ms
SolidStart	158.00 ms
Mastro	178.00 ms
SvelteKit	241.00 ms
React Router	387.00 ms
Nuxt	484.00 ms
TanStack Start	1584.00 ms
Next.js	2740.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.