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.21s	1.81s	4.01s	0.92s	0.87s	0.03MB
Mastro	0.50s	0.50s	0.51s	0.29s	0.28s	0.01MB
Next.js	5.52s	3.04s	6.30s	4.72s	4.72s	6.03MB
Nuxt	4.66s	2.91s	5.54s	3.58s	3.58s	2.46MB
React Router	1.50s	1.24s	1.72s	1.61s	1.60s	0.38MB
SolidStart	1.77s	1.40s	2.01s	2.82s	2.68s	0.51MB
SvelteKit	1.45s	1.22s	1.61s	1.79s	1.58s	1.44MB
TanStack Start	4.20s	1.92s	4.90s	5.25s	4.98s	2.05MB

Avg install time

Avg install time chart

Avg install time data

Framework	Seconds
Mastro	0.50s
SvelteKit	1.45s
React Router	1.50s
SolidStart	1.77s
Astro	3.21s
TanStack Start	4.20s
Nuxt	4.66s
Next.js	5.52s

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.92s
React Router	1.61s
SvelteKit	1.79s
SolidStart	2.82s
Nuxt	3.58s
Next.js	4.72s
TanStack Start	5.25s

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.28s
Astro	0.87s
SvelteKit	1.58s
React Router	1.60s
SolidStart	2.68s
Nuxt	3.58s
Next.js	4.72s
TanStack Start	4.98s

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	103.8ms	103.97ms	2.63ms	2.3ms	0.34ms	0ms
Next.js	339ms	339.02ms	19.22ms	1.31ms	7.67ms	10.24ms
Nuxt	157.4ms	157.27ms	8.69ms	0.59ms	1.25ms	6.85ms
React Router	153.2ms	153.34ms	20.81ms	1.57ms	2.1ms	17.14ms
SolidStart	102.4ms	102.34ms	15.49ms	0.87ms	2.04ms	12.57ms
SvelteKit	117.2ms	117.05ms	17.89ms	0.62ms	2.81ms	14.46ms
TanStack Start	168.6ms	168.26ms	25.52ms	2.01ms	15.07ms	8.45ms

First Paint (ms)

First Paint (ms) chart

First Paint (ms) data

Framework	Milliseconds
SolidStart	102.40 ms
Astro	103.80 ms
SvelteKit	117.20 ms
React Router	153.20 ms
Nuxt	157.40 ms
TanStack Start	168.60 ms
Next.js	339.00 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	102.34 ms
Astro	103.97 ms
SvelteKit	117.05 ms
React Router	153.34 ms
Nuxt	157.27 ms
TanStack Start	168.26 ms
Next.js	339.02 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.89 ms

Median: 17.89 ms

2.63 ms

8.69 ms

15.49 ms

17.89 ms

19.22 ms

20.81 ms

25.52 ms

Interaction Breakdown data

Framework or version	Interaction latency	Input delay	Processing duration	Presentation delay
Astro	2.63 ms	2.30 ms	0.34 ms	0.00 ms
Nuxt	8.69 ms	0.59 ms	1.25 ms	6.85 ms
SolidStart	15.49 ms	0.87 ms	2.04 ms	12.57 ms
SvelteKit	17.89 ms	0.62 ms	2.81 ms	14.46 ms
Next.js	19.22 ms	1.31 ms	7.67 ms	10.24 ms
React Router	20.81 ms	1.57 ms	2.10 ms	17.14 ms
TanStack Start	25.52 ms	2.01 ms	15.07 ms	8.45 ms

Server Side Rendered Tests

Methodology: Server Side Rendered Tests.

Framework	First Paint	FCP	Interaction Latency	Input Delay	Processing Duration	Presentation Delay
Astro	62ms	61.88ms	0.71ms	0.47ms	0.24ms	0ms
Mastro	82.8ms	82.65ms	6.44ms	0.6ms	0.83ms	5.01ms
Next.js	148.2ms	148.25ms	19.59ms	1.55ms	7.72ms	10.32ms
Nuxt	89.6ms	89.39ms	9.84ms	0.46ms	1.22ms	8.16ms
React Router	130.8ms	130.88ms	18.08ms	1.47ms	2.55ms	14.06ms
SolidStart	88.2ms	88.25ms	14.1ms	0.76ms	2.11ms	11.23ms
SvelteKit	90.4ms	90.62ms	12.87ms	0.74ms	3.12ms	9.02ms
TanStack Start	133.2ms	133.23ms	27.05ms	1.69ms	14.2ms	11.16ms

First Paint (ms)

First Paint (ms) chart

First Paint (ms) data

Framework	Milliseconds
Astro	62.00 ms
Mastro	82.80 ms
SolidStart	88.20 ms
Nuxt	89.60 ms
SvelteKit	90.40 ms
React Router	130.80 ms
TanStack Start	133.20 ms
Next.js	148.20 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	61.88 ms
Mastro	82.65 ms
SolidStart	88.25 ms
Nuxt	89.39 ms
SvelteKit	90.62 ms
React Router	130.88 ms
TanStack Start	133.23 ms
Next.js	148.25 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.48 ms

Median: 14.10 ms

0.71 ms

M

6.44 ms

9.84 ms

12.87 ms

14.10 ms

18.08 ms

19.59 ms

27.05 ms

Interaction Breakdown data

Framework or version	Interaction latency	Input delay	Processing duration	Presentation delay
Astro	0.71 ms	0.47 ms	0.24 ms	0.00 ms
Mastro	6.44 ms	0.60 ms	0.83 ms	5.01 ms
Nuxt	9.84 ms	0.46 ms	1.22 ms	8.16 ms
SvelteKit	12.87 ms	0.74 ms	3.12 ms	9.02 ms
SolidStart	14.10 ms	0.76 ms	2.11 ms	11.23 ms
React Router	18.08 ms	1.47 ms	2.55 ms	14.06 ms
Next.js	19.59 ms	1.55 ms	7.72 ms	10.32 ms
TanStack Start	27.05 ms	1.69 ms	14.20 ms	11.16 ms

Server Side Throughput Tests

Methodology: Server Side Throughput Tests.

Framework	Ops/sec	Median Latency	Body Size	Duplication
Baseline HTML	851	1.199ms	96.83kb	1x
Astro	661	1.449ms	96.89kb	1x
Mastro	262	3.781ms	327.46kb	1.5x
Next.js	237	4.461ms	199.57kb	2x
Nuxt	366	2.64ms	201.27kb	2x
React Router	351	2.81ms	211.63kb	2x
SolidStart	423	2.277ms	224.17kb	2x
SvelteKit	447	2.169ms	183.53kb	2x
TanStack Start	328	3.018ms	193.62kb	2x

Ops/sec

Ops/sec chart

Ops/sec data

Framework	Operations per second
Baseline HTML	851
Astro	661
SvelteKit	447
SolidStart	423
Nuxt	366
React Router	351
TanStack Start	328
Mastro	262
Next.js	237

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.45 ms
SvelteKit	2.17 ms
SolidStart	2.28 ms
Nuxt	2.64 ms
React Router	2.81 ms
TanStack Start	3.02 ms
Mastro	3.78 ms
Next.js	4.46 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,658.8	100	19ms	39ms	99ms	49,144
Astro	1,187.41	100	31ms	62ms	317ms	35,916
Mastro	576	25	45ms	124ms	1370ms	18,260
Next.js	39	5	2039ms	4560ms	4791ms	1,090
Nuxt	73	5	1834ms	4224ms	4179ms	2,382
React Router	173.8	25	342ms	1616ms	3968ms	5,795
SolidStart	523.21	10	99ms	421ms	2067ms	16,983
SvelteKit	539.6	10	78ms	176ms	2355ms	16,357
TanStack Start	45	5	3485ms	3753ms	4194ms	1,371

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	31.00 ms
Mastro	45.00 ms
SvelteKit	78.00 ms
SolidStart	99.00 ms
React Router	342.00 ms
Nuxt	1834.00 ms
Next.js	2039.00 ms
TanStack Start	3485.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	62.00 ms
Mastro	124.00 ms
SvelteKit	176.00 ms
SolidStart	421.00 ms
React Router	1616.00 ms
TanStack Start	3753.00 ms
Nuxt	4224.00 ms
Next.js	4560.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	99.00 ms
Astro	317.00 ms
Mastro	1370.00 ms
SolidStart	2067.00 ms
SvelteKit	2355.00 ms
React Router	3968.00 ms
Nuxt	4179.00 ms
TanStack Start	4194.00 ms
Next.js	4791.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	55.00 ms
SolidStart	70.00 ms
React Router	147.00 ms
Nuxt	338.00 ms
TanStack Start	722.00 ms
Next.js	755.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	45.00 ms
Mastro	85.00 ms
SvelteKit	135.00 ms
SolidStart	150.00 ms
React Router	288.00 ms
Nuxt	483.00 ms
TanStack Start	825.00 ms
Next.js	2385.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	73.00 ms
Astro	84.00 ms
SolidStart	154.00 ms
Mastro	173.00 ms
SvelteKit	220.00 ms
React Router	390.00 ms
Nuxt	623.00 ms
TanStack Start	1254.00 ms
Next.js	2837.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.