Run Time Stats

Client Side Rendered Tests

Methodology: Client Side Rendered Tests.

Some frameworks have been moved off their golden path to make client side tests fair when comparing. See the methodology link above for the full details.

Framework	First Paint	FCP	Interaction Latency	Input Delay	Processing Duration	Presentation Delay
Astro	195.4ms	195.42ms	4.6ms	2.92ms	1ms	0.68ms
Next.js	389.6ms	389.58ms	21.05ms	2.59ms	6.43ms	12.03ms
Nuxt	215.2ms	215.24ms	12.07ms	1.36ms	1.8ms	8.92ms
React Router	234.8ms	234.88ms	18.44ms	2.85ms	2.56ms	13.04ms
SolidStart	171.6ms	171.62ms	15.1ms	2.28ms	2.65ms	10.17ms
SvelteKit	197.2ms	197.2ms	15.22ms	2.38ms	2.68ms	10.16ms
TanStack Start	234ms	234.12ms	22.75ms	2.78ms	13.16ms	6.81ms

First Paint (ms)

First Paint (ms) chart

First Paint (ms) data

Framework	Milliseconds
SolidStart	171.60 ms
Astro	195.40 ms
SvelteKit	197.20 ms
Nuxt	215.20 ms
TanStack Start	234.00 ms
React Router	234.80 ms
Next.js	389.60 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	171.62 ms
Astro	195.42 ms
SvelteKit	197.20 ms
Nuxt	215.24 ms
TanStack Start	234.12 ms
React Router	234.88 ms
Next.js	389.58 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: 15.22 ms

Median: 15.22 ms

4.60 ms

12.07 ms

15.10 ms

15.22 ms

18.44 ms

21.05 ms

22.75 ms

Interaction Breakdown data

Framework or version	Interaction latency	Input delay	Processing duration	Presentation delay
Astro	4.60 ms	2.92 ms	1.00 ms	0.68 ms
Nuxt	12.07 ms	1.36 ms	1.80 ms	8.92 ms
SolidStart	15.10 ms	2.28 ms	2.65 ms	10.17 ms
SvelteKit	15.22 ms	2.38 ms	2.68 ms	10.16 ms
React Router	18.44 ms	2.85 ms	2.56 ms	13.04 ms
Next.js	21.05 ms	2.59 ms	6.43 ms	12.03 ms
TanStack Start	22.75 ms	2.78 ms	13.16 ms	6.81 ms

Server Side Rendered Tests

Methodology: Server Side Rendered Tests.

Framework	First Paint	FCP	Interaction Latency	Input Delay	Processing Duration	Presentation Delay
Astro	89.8ms	89.79ms	6.87ms	3.43ms	1ms	2.44ms
Mastro	96.8ms	96.84ms	6.59ms	1.96ms	0.83ms	3.8ms
Next.js	193.4ms	193.36ms	18.59ms	2.3ms	7.54ms	8.75ms
Nuxt	170.2ms	170.29ms	10.91ms	2.1ms	1.98ms	6.84ms
React Router	149.8ms	149.76ms	16.6ms	2.52ms	2.86ms	11.22ms
SolidStart	148.4ms	148.31ms	17.59ms	2.47ms	2.68ms	12.44ms
SvelteKit	109.8ms	109.74ms	14.29ms	2.05ms	2.62ms	9.62ms
TanStack Start	175.2ms	175.06ms	31.63ms	3.17ms	14.23ms	14.23ms

First Paint (ms)

First Paint (ms) chart

First Paint (ms) data

Framework	Milliseconds
Astro	89.80 ms
Mastro	96.80 ms
SvelteKit	109.80 ms
SolidStart	148.40 ms
React Router	149.80 ms
Nuxt	170.20 ms
TanStack Start	175.20 ms
Next.js	193.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	89.79 ms
Mastro	96.84 ms
SvelteKit	109.74 ms
SolidStart	148.31 ms
React Router	149.76 ms
Nuxt	170.29 ms
TanStack Start	175.06 ms
Next.js	193.36 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: 15.45 ms

Median: 16.60 ms

M

6.59 ms

6.87 ms

10.91 ms

14.29 ms

16.60 ms

17.59 ms

18.59 ms

31.63 ms

Interaction Breakdown data

Framework or version	Interaction latency	Input delay	Processing duration	Presentation delay
Mastro	6.59 ms	1.96 ms	0.83 ms	3.80 ms
Astro	6.87 ms	3.43 ms	1.00 ms	2.44 ms
Nuxt	10.91 ms	2.10 ms	1.98 ms	6.84 ms
SvelteKit	14.29 ms	2.05 ms	2.62 ms	9.62 ms
React Router	16.60 ms	2.52 ms	2.86 ms	11.22 ms
SolidStart	17.59 ms	2.47 ms	2.68 ms	12.44 ms
Next.js	18.59 ms	2.30 ms	7.54 ms	8.75 ms
TanStack Start	31.63 ms	3.17 ms	14.23 ms	14.23 ms

Server Side Throughput Tests

Methodology: Server Side Throughput Tests.

Framework	Ops/sec	Median Latency	Body Size	Duplication
Baseline HTML	847	1.2ms	96.83kb	1x
Astro	677	1.429ms	96.89kb	1x
Mastro	278	3.538ms	327.46kb	1.5x
Next.js	225	4.615ms	199.57kb	2x
Nuxt	363	2.681ms	201.27kb	2x
React Router	350	2.825ms	211.63kb	2x
SolidStart	423	2.284ms	224.17kb	2x
SvelteKit	457	2.127ms	183.53kb	2x
TanStack Start	328	3.026ms	193.62kb	2x

Ops/sec

Ops/sec chart

Ops/sec data

Framework	Operations per second
Baseline HTML	847
Astro	677
SvelteKit	457
SolidStart	423
Nuxt	363
React Router	350
TanStack Start	328
Mastro	278
Next.js	225

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.43 ms
SvelteKit	2.13 ms
SolidStart	2.28 ms
Nuxt	2.68 ms
React Router	2.83 ms
TanStack Start	3.03 ms
Mastro	3.54 ms
Next.js	4.62 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,615.8	50	19ms	44ms	118ms	47,988
Astro	1,155.2	100	38ms	72ms	326ms	34,650
Mastro	381.6	25	69ms	408ms	2844ms	12,136
Next.js	38.4	5	2123ms	4671ms	4663ms	1,053
Nuxt	66.8	5	2011ms	4073ms	4188ms	2,170
React Router	146	50	423ms	2058ms	3998ms	4,820
SolidStart	478.8	10	128ms	639ms	2263ms	14,345
SvelteKit	503.6	10	91ms	292ms	2307ms	15,876
TanStack Start	44.2	5	4023ms	3944ms	4403ms	1,360

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	38.00 ms
Mastro	69.00 ms
SvelteKit	91.00 ms
SolidStart	128.00 ms
React Router	423.00 ms
Nuxt	2011.00 ms
Next.js	2123.00 ms
TanStack Start	4023.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	72.00 ms
SvelteKit	292.00 ms
Mastro	408.00 ms
SolidStart	639.00 ms
React Router	2058.00 ms
TanStack Start	3944.00 ms
Nuxt	4073.00 ms
Next.js	4671.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	118.00 ms
Astro	326.00 ms
SolidStart	2263.00 ms
SvelteKit	2307.00 ms
Mastro	2844.00 ms
React Router	3998.00 ms
Nuxt	4188.00 ms
TanStack Start	4403.00 ms
Next.js	4663.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	24.00 ms
SvelteKit	57.00 ms
Mastro	66.00 ms
SolidStart	81.00 ms
React Router	191.00 ms
Nuxt	371.00 ms
TanStack Start	728.00 ms
Next.js	739.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	44.00 ms
Mastro	135.00 ms
SvelteKit	140.00 ms
SolidStart	167.00 ms
React Router	362.00 ms
Nuxt	496.00 ms
TanStack Start	748.00 ms
Next.js	2439.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	89.00 ms
SolidStart	161.00 ms
SvelteKit	226.00 ms
Mastro	277.00 ms
React Router	401.00 ms
Nuxt	578.00 ms
TanStack Start	1337.00 ms
Next.js	2862.00 ms

The chart includes a dotted median reference line calculated from the visible framework values.

P75 Latency

P75 Latency at 25 Connections

P75 Latency at 25 Connections chart

P75 Latency at 25 Connections data

Framework	Milliseconds
Baseline HTML	16.00 ms
Astro	22.00 ms
SvelteKit	53.00 ms
Mastro	65.00 ms
SolidStart	69.00 ms
React Router	182.00 ms
Nuxt	360.00 ms
TanStack Start	545.00 ms
Next.js	725.00 ms

The chart includes a dotted median reference line calculated from the visible framework values.

P75 Latency at 50 Connections

P75 Latency at 50 Connections chart

P75 Latency at 50 Connections data

Framework	Milliseconds
Baseline HTML	32.00 ms
Astro	43.00 ms
SolidStart	107.00 ms
SvelteKit	112.00 ms
Mastro	131.00 ms
React Router	353.00 ms
Nuxt	455.00 ms
TanStack Start	532.00 ms
Next.js	1139.00 ms

The chart includes a dotted median reference line calculated from the visible framework values.

P75 Latency at 100 Connections

P75 Latency at 100 Connections chart

P75 Latency at 100 Connections data

Framework	Milliseconds
Baseline HTML	63.00 ms
Astro	86.00 ms
SolidStart	139.00 ms
SvelteKit	168.00 ms
Mastro	262.00 ms
React Router	379.00 ms
Nuxt	456.00 ms
TanStack Start	476.00 ms
Next.js	1102.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.