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.76s	1.67s	3.46s	0.80s	0.76s	0.03MB
Mastro	0.49s	0.47s	0.50s	0.30s	0.30s	0.01MB
Next.js	5.38s	2.96s	6.17s	4.97s	4.85s	6.03MB
Nuxt	4.81s	3.06s	5.76s	3.65s	3.40s	2.46MB
React Router	1.56s	1.22s	1.76s	1.59s	1.56s	0.38MB
SolidStart	1.67s	1.46s	2.02s	2.88s	2.72s	0.51MB
SvelteKit	1.38s	1.25s	1.52s	1.75s	1.60s	1.44MB
TanStack Start	4.17s	1.88s	4.87s	5.22s	5.09s	2.05MB

Avg install time

Avg install time chart

Avg install time data

Framework	Seconds
Mastro	0.49s
SvelteKit	1.38s
React Router	1.56s
SolidStart	1.67s
Astro	2.76s
TanStack Start	4.17s
Nuxt	4.81s
Next.js	5.38s

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.80s
React Router	1.59s
SvelteKit	1.75s
SolidStart	2.88s
Nuxt	3.65s
Next.js	4.97s
TanStack Start	5.22s

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.76s
React Router	1.56s
SvelteKit	1.60s
SolidStart	2.72s
Nuxt	3.40s
Next.js	4.85s
TanStack Start	5.09s

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	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	100.2ms	100.31ms	2.11ms	1.85ms	0.26ms	0ms
Next.js	339.4ms	339.19ms	17.78ms	1.26ms	7.78ms	8.74ms
Nuxt	156.2ms	156.29ms	11.44ms	0.85ms	1.62ms	8.97ms
React Router	135ms	135.04ms	17.16ms	1.48ms	2.31ms	13.37ms
SolidStart	91.4ms	91.39ms	15.4ms	1.28ms	2.68ms	11.44ms
SvelteKit	109.4ms	109.33ms	18.12ms	0.75ms	3.5ms	13.87ms
TanStack Start	175.8ms	175.87ms	24.76ms	1.6ms	11.6ms	11.56ms

First Paint (ms)

First Paint (ms) chart

First Paint (ms) data

Framework	Milliseconds
SolidStart	91.40 ms
Astro	100.20 ms
SvelteKit	109.40 ms
React Router	135.00 ms
Nuxt	156.20 ms
TanStack Start	175.80 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	91.39 ms
Astro	100.31 ms
SvelteKit	109.33 ms
React Router	135.04 ms
Nuxt	156.29 ms
TanStack Start	175.87 ms
Next.js	339.19 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.16 ms

Median: 17.16 ms

2.11 ms

11.44 ms

15.40 ms

17.16 ms

17.78 ms

18.12 ms

24.76 ms

Interaction Breakdown data

Framework or version	Interaction latency	Input delay	Processing duration	Presentation delay
Astro	2.11 ms	1.85 ms	0.26 ms	0.00 ms
Nuxt	11.44 ms	0.85 ms	1.62 ms	8.97 ms
SolidStart	15.40 ms	1.28 ms	2.68 ms	11.44 ms
React Router	17.16 ms	1.48 ms	2.31 ms	13.37 ms
Next.js	17.78 ms	1.26 ms	7.78 ms	8.74 ms
SvelteKit	18.12 ms	0.75 ms	3.50 ms	13.87 ms
TanStack Start	24.76 ms	1.60 ms	11.60 ms	11.56 ms

Server Side Rendered Tests

Methodology: Server Side Rendered Tests.

Framework	First Paint	FCP	Interaction Latency	Input Delay	Processing Duration	Presentation Delay
Astro	67.4ms	67.34ms	1.03ms	0.71ms	0.32ms	0ms
Mastro	79.4ms	79.38ms	11.4ms	0.46ms	0.51ms	10.42ms
Next.js	153ms	153.09ms	17.89ms	1.28ms	7.31ms	9.3ms
Nuxt	105.4ms	105.41ms	8.62ms	0.47ms	1.23ms	6.91ms
React Router	118.4ms	118.54ms	22.74ms	1.46ms	2.39ms	18.89ms
SolidStart	91ms	90.96ms	15.86ms	0.81ms	2.06ms	12.98ms
SvelteKit	87ms	87.22ms	16.5ms	0.56ms	2.78ms	13.16ms
TanStack Start	119.8ms	119.64ms	24.24ms	1.65ms	14.22ms	8.37ms

First Paint (ms)

First Paint (ms) chart

First Paint (ms) data

Framework	Milliseconds
Astro	67.40 ms
Mastro	79.40 ms
SvelteKit	87.00 ms
SolidStart	91.00 ms
Nuxt	105.40 ms
React Router	118.40 ms
TanStack Start	119.80 ms
Next.js	153.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
Astro	67.34 ms
Mastro	79.38 ms
SvelteKit	87.22 ms
SolidStart	90.96 ms
Nuxt	105.41 ms
React Router	118.54 ms
TanStack Start	119.64 ms
Next.js	153.09 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.18 ms

Median: 16.50 ms

1.03 ms

8.62 ms

M

11.40 ms

15.86 ms

16.50 ms

17.89 ms

22.74 ms

24.24 ms

Interaction Breakdown data

Framework or version	Interaction latency	Input delay	Processing duration	Presentation delay
Astro	1.03 ms	0.71 ms	0.32 ms	0.00 ms
Nuxt	8.62 ms	0.47 ms	1.23 ms	6.91 ms
Mastro	11.40 ms	0.46 ms	0.51 ms	10.42 ms
SolidStart	15.86 ms	0.81 ms	2.06 ms	12.98 ms
SvelteKit	16.50 ms	0.56 ms	2.78 ms	13.16 ms
Next.js	17.89 ms	1.28 ms	7.31 ms	9.30 ms
React Router	22.74 ms	1.46 ms	2.39 ms	18.89 ms
TanStack Start	24.24 ms	1.65 ms	14.22 ms	8.37 ms

Server Side Throughput Tests

Methodology: Server Side Throughput Tests.

Framework	Ops/sec	Median Latency	Body Size	Duplication
Baseline HTML	849	1.199ms	96.83kb	1x
Astro	669	1.445ms	96.89kb	1x
Mastro	348	2.846ms	327.46kb	1.5x
Next.js	215	4.745ms	199.57kb	2x
Nuxt	364	2.65ms	201.27kb	2x
React Router	350	2.834ms	211.63kb	2x
SolidStart	424	2.28ms	224.17kb	2x
SvelteKit	453	2.145ms	183.53kb	2x
TanStack Start	317	3.096ms	193.62kb	2x

Ops/sec

Ops/sec chart

Ops/sec data

Framework	Operations per second
Baseline HTML	849
Astro	669
SvelteKit	453
SolidStart	424
Nuxt	364
React Router	350
Mastro	348
TanStack Start	317
Next.js	215

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.15 ms
SolidStart	2.28 ms
Nuxt	2.65 ms
React Router	2.83 ms
Mastro	2.85 ms
TanStack Start	3.10 ms
Next.js	4.75 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,667.2	100	17ms	44ms	101ms	49,479
Astro	1,170.8	200	34ms	66ms	345ms	35,610
Mastro	582.6	25	44ms	108ms	1365ms	18,431
Next.js	39.4	1	2080ms	4646ms	4667ms	1,117
Nuxt	74	10	1923ms	4039ms	4260ms	2,332
React Router	173.6	10	332ms	1854ms	3861ms	5,784
SolidStart	525.8	25	99ms	449ms	2098ms	16,822
SvelteKit	514.4	5	81ms	177ms	2302ms	16,288
TanStack Start	45.4	5	3517ms	4374ms	4306ms	1,373

P99 Latency

P99 Latency at 25 Connections

P99 Latency at 25 Connections chart

P99 Latency at 25 Connections data

Framework	Milliseconds
Baseline HTML	17.00 ms
Astro	34.00 ms
Mastro	44.00 ms
SvelteKit	81.00 ms
SolidStart	99.00 ms
React Router	332.00 ms
Nuxt	1923.00 ms
Next.js	2080.00 ms
TanStack Start	3517.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	66.00 ms
Mastro	108.00 ms
SvelteKit	177.00 ms
SolidStart	449.00 ms
React Router	1854.00 ms
Nuxt	4039.00 ms
TanStack Start	4374.00 ms
Next.js	4646.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	101.00 ms
Astro	345.00 ms
Mastro	1365.00 ms
SolidStart	2098.00 ms
SvelteKit	2302.00 ms
React Router	3861.00 ms
Nuxt	4260.00 ms
TanStack Start	4306.00 ms
Next.js	4667.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	58.00 ms
SolidStart	70.00 ms
React Router	161.00 ms
Nuxt	345.00 ms
TanStack Start	622.00 ms
Next.js	713.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	44.00 ms
Mastro	86.00 ms
SvelteKit	136.00 ms
SolidStart	149.00 ms
React Router	286.00 ms
Nuxt	489.00 ms
TanStack Start	841.00 ms
Next.js	2468.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	74.00 ms
Astro	87.00 ms
SolidStart	155.00 ms
Mastro	183.00 ms
SvelteKit	230.00 ms
React Router	405.00 ms
Nuxt	516.00 ms
TanStack Start	1400.00 ms
Next.js	2736.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.