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.05MB	506.22MB	View
Nuxt	2 / 3	694	63	208.81MB	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.81 MB
TanStack Start	234.77 MB
Next.js	560.05 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	1.81s	1.47s	2.46s	1.01s	0.91s	0.03MB
Mastro	0.62s	0.54s	0.77s	0.35s	0.35s	0.01MB
Next.js	3.20s	3.07s	3.57s	5.21s	5.24s	6.05MB
Nuxt	2.88s	2.73s	3.31s	3.84s	3.88s	2.46MB
React Router	1.12s	1.10s	1.14s	1.86s	1.78s	0.38MB
SolidStart	1.25s	1.23s	1.27s	3.01s	3.02s	0.51MB
SvelteKit	1.31s	1.28s	1.34s	1.74s	1.77s	1.44MB
TanStack Start	1.85s	1.81s	1.90s	5.40s	5.29s	2.05MB

Avg install time

Avg install time chart

Avg install time data

Framework	Seconds
Mastro	0.62s
React Router	1.12s
SolidStart	1.25s
SvelteKit	1.31s
Astro	1.81s
TanStack Start	1.85s
Nuxt	2.88s
Next.js	3.20s

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.35s
Astro	1.01s
SvelteKit	1.74s
React Router	1.86s
SolidStart	3.01s
Nuxt	3.84s
Next.js	5.21s
TanStack Start	5.40s

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.35s
Astro	0.91s
SvelteKit	1.77s
React Router	1.78s
SolidStart	3.02s
Nuxt	3.88s
Next.js	5.24s
TanStack Start	5.29s

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.05 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

Client Side Rendered Tests

Methodology: Client Side Rendered Tests.

Framework	First Paint	FCP	Interaction Latency	Input Delay	Processing Duration	Presentation Delay
Astro	188.4ms	188.39ms	4.83ms	2.58ms	1.23ms	1.02ms
Next.js	369.8ms	369.89ms	19.14ms	1.89ms	7.02ms	10.23ms
Nuxt	163.4ms	163.27ms	9.88ms	1.01ms	1.8ms	7.08ms
React Router	238.8ms	238.56ms	17.59ms	2.47ms	2.53ms	12.59ms
SolidStart	191.2ms	191.22ms	14.43ms	1.69ms	2.68ms	10.06ms
SvelteKit	201.6ms	201.56ms	14.32ms	1.71ms	2.59ms	10.02ms
TanStack Start	235.2ms	235.21ms	34.89ms	3.19ms	14.96ms	16.74ms

First Paint (ms)

First Paint (ms) chart

First Paint (ms) data

Framework	Milliseconds
Nuxt	163.40 ms
Astro	188.40 ms
SolidStart	191.20 ms
SvelteKit	201.60 ms
TanStack Start	235.20 ms
React Router	238.80 ms
Next.js	369.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
Nuxt	163.27 ms
Astro	188.39 ms
SolidStart	191.22 ms
SvelteKit	201.56 ms
TanStack Start	235.21 ms
React Router	238.56 ms
Next.js	369.89 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.43 ms

Median: 14.43 ms

4.83 ms

9.88 ms

14.32 ms

14.43 ms

17.59 ms

19.14 ms

34.89 ms

Interaction Breakdown data

Framework or version	Interaction latency	Input delay	Processing duration	Presentation delay
Astro	4.83 ms	2.58 ms	1.23 ms	1.02 ms
Nuxt	9.88 ms	1.01 ms	1.80 ms	7.08 ms
SvelteKit	14.32 ms	1.71 ms	2.59 ms	10.02 ms
SolidStart	14.43 ms	1.69 ms	2.68 ms	10.06 ms
React Router	17.59 ms	2.47 ms	2.53 ms	12.59 ms
Next.js	19.14 ms	1.89 ms	7.02 ms	10.23 ms
TanStack Start	34.89 ms	3.19 ms	14.96 ms	16.74 ms

Server Side Rendered Tests

Methodology: Server Side Rendered Tests.

Framework	First Paint	FCP	Interaction Latency	Input Delay	Processing Duration	Presentation Delay
Astro	121.6ms	121.5ms	3.95ms	1.72ms	0.97ms	1.27ms
Mastro	123.6ms	123.45ms	10.31ms	1.61ms	1.03ms	7.67ms
Next.js	146.6ms	146.61ms	20.73ms	2.6ms	7.39ms	10.73ms
Nuxt	169.2ms	169.15ms	13.18ms	1.55ms	2.14ms	9.5ms
React Router	162ms	161.96ms	22.02ms	2.8ms	3.73ms	15.5ms
SolidStart	131.8ms	131.62ms	17.32ms	1.85ms	2.39ms	13.08ms
SvelteKit	128.2ms	128.03ms	19.69ms	1.74ms	3.43ms	14.52ms
TanStack Start	171.8ms	171.86ms	30.92ms	3.33ms	15.28ms	12.31ms

First Paint (ms)

First Paint (ms) chart

First Paint (ms) data

Framework	Milliseconds
Astro	121.60 ms
Mastro	123.60 ms
SvelteKit	128.20 ms
SolidStart	131.80 ms
Next.js	146.60 ms
React Router	162.00 ms
Nuxt	169.20 ms
TanStack Start	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	121.50 ms
Mastro	123.45 ms
SvelteKit	128.03 ms
SolidStart	131.62 ms
Next.js	146.61 ms
React Router	161.96 ms
Nuxt	169.15 ms
TanStack Start	171.86 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: 18.51 ms

Median: 19.69 ms

3.95 ms

M

10.31 ms

13.18 ms

17.32 ms

19.69 ms

20.73 ms

22.02 ms

30.92 ms

Interaction Breakdown data

Framework or version	Interaction latency	Input delay	Processing duration	Presentation delay
Astro	3.95 ms	1.72 ms	0.97 ms	1.27 ms
Mastro	10.31 ms	1.61 ms	1.03 ms	7.67 ms
Nuxt	13.18 ms	1.55 ms	2.14 ms	9.50 ms
SolidStart	17.32 ms	1.85 ms	2.39 ms	13.08 ms
SvelteKit	19.69 ms	1.74 ms	3.43 ms	14.52 ms
Next.js	20.73 ms	2.60 ms	7.39 ms	10.73 ms
React Router	22.02 ms	2.80 ms	3.73 ms	15.50 ms
TanStack Start	30.92 ms	3.33 ms	15.28 ms	12.31 ms

Server Side Throughput Tests

Methodology: Server Side Throughput Tests.

Framework	Ops/sec	Median Latency	Body Size	Duplication
Baseline HTML	848	1.201ms	96.83kb	1x
Astro	675	1.42ms	96.89kb	1x
Mastro	268	3.703ms	327.46kb	1.5x
Next.js	229	4.58ms	199.57kb	2x
Nuxt	363	2.657ms	201.27kb	2x
React Router	349	2.831ms	211.63kb	2x
SolidStart	420	2.29ms	224.17kb	2x
SvelteKit	433	2.234ms	183.53kb	2x
TanStack Start	329	3.002ms	193.62kb	2x

Ops/sec

Ops/sec chart

Ops/sec data

Framework	Operations per second
Baseline HTML	848
Astro	675
SvelteKit	433
SolidStart	420
Nuxt	363
React Router	349
TanStack Start	329
Mastro	268
Next.js	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.42 ms
SvelteKit	2.23 ms
SolidStart	2.29 ms
Nuxt	2.66 ms
React Router	2.83 ms
TanStack Start	3.00 ms
Mastro	3.70 ms
Next.js	4.58 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,599.8	100	19ms	43ms	106ms	47,358
Astro	1,215.41	25	30ms	61ms	278ms	36,746
Mastro	384.4	50	76ms	387ms	2894ms	12,238
Next.js	36	1	2186ms	4618ms	4636ms	1,001
Nuxt	65	5	2084ms	4094ms	4411ms	2,070
React Router	172.8	25	339ms	1687ms	3848ms	5,639
SolidStart	506.6	25	106ms	389ms	2123ms	16,103
SvelteKit	482.4	25	88ms	402ms	2362ms	15,366
TanStack Start	44.8	5	3903ms	4598ms	4570ms	1,350

P99 Latency

P99 Latency at 25 Connections

P99 Latency at 25 Connections chart

P99 Latency at 25 Connections data

Framework	Milliseconds
Baseline HTML	19.00 ms
Astro	30.00 ms
Mastro	76.00 ms
SvelteKit	88.00 ms
SolidStart	106.00 ms
React Router	339.00 ms
Nuxt	2084.00 ms
Next.js	2186.00 ms
TanStack Start	3903.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	43.00 ms
Astro	61.00 ms
Mastro	387.00 ms
SolidStart	389.00 ms
SvelteKit	402.00 ms
React Router	1687.00 ms
Nuxt	4094.00 ms
TanStack Start	4598.00 ms
Next.js	4618.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	106.00 ms
Astro	278.00 ms
SolidStart	2123.00 ms
SvelteKit	2362.00 ms
Mastro	2894.00 ms
React Router	3848.00 ms
Nuxt	4411.00 ms
TanStack Start	4570.00 ms
Next.js	4636.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	22.00 ms
SvelteKit	60.00 ms
Mastro	66.00 ms
SolidStart	70.00 ms
React Router	148.00 ms
Nuxt	389.00 ms
Next.js	755.00 ms
TanStack Start	870.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	33.00 ms
Astro	42.00 ms
Mastro	130.00 ms
SvelteKit	148.00 ms
SolidStart	152.00 ms
React Router	308.00 ms
Nuxt	524.00 ms
TanStack Start	874.00 ms
Next.js	2539.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	79.00 ms
Astro	84.00 ms
SolidStart	175.00 ms
SvelteKit	195.00 ms
Mastro	282.00 ms
React Router	406.00 ms
Nuxt	661.00 ms
TanStack Start	1325.00 ms
Next.js	2822.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.