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	103.8ms	103.87ms	4.2ms	1.49ms	0.33ms	2.38ms
Next.js	338.8ms	338.77ms	17.53ms	1.26ms	5.84ms	10.43ms
Nuxt	177ms	177.05ms	8.74ms	1.15ms	2.06ms	5.54ms
React Router	150.4ms	150.28ms	21.02ms	1.23ms	2.57ms	17.21ms
SolidStart	99.8ms	99.84ms	16.99ms	0.97ms	2.32ms	13.7ms
SvelteKit	110.6ms	110.6ms	13.44ms	0.72ms	2.17ms	10.54ms
TanStack Start	144.4ms	144.41ms	24.6ms	1.84ms	12.21ms	10.55ms

First Paint (ms)

First Paint (ms) chart

First Paint (ms) data

Framework	Milliseconds
SolidStart	99.80 ms
Astro	103.80 ms
SvelteKit	110.60 ms
TanStack Start	144.40 ms
React Router	150.40 ms
Nuxt	177.00 ms
Next.js	338.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
SolidStart	99.84 ms
Astro	103.87 ms
SvelteKit	110.60 ms
TanStack Start	144.41 ms
React Router	150.28 ms
Nuxt	177.05 ms
Next.js	338.77 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.99 ms

Median: 16.99 ms

4.20 ms

8.74 ms

13.44 ms

16.99 ms

17.53 ms

21.02 ms

24.60 ms

Interaction Breakdown data

Framework or version	Interaction latency	Input delay	Processing duration	Presentation delay
Astro	4.20 ms	1.49 ms	0.33 ms	2.38 ms
Nuxt	8.74 ms	1.15 ms	2.06 ms	5.54 ms
SvelteKit	13.44 ms	0.72 ms	2.17 ms	10.54 ms
SolidStart	16.99 ms	0.97 ms	2.32 ms	13.70 ms
Next.js	17.53 ms	1.26 ms	5.84 ms	10.43 ms
React Router	21.02 ms	1.23 ms	2.57 ms	17.21 ms
TanStack Start	24.60 ms	1.84 ms	12.21 ms	10.55 ms

Server Side Rendered Tests

Methodology: Server Side Rendered Tests.

Framework	First Paint	FCP	Interaction Latency	Input Delay	Processing Duration	Presentation Delay
Astro	76.6ms	76.71ms	6.46ms	0.63ms	1.24ms	4.59ms
Mastro	82.2ms	82.24ms	5.87ms	0.54ms	1.1ms	4.23ms
Next.js	162.4ms	162.32ms	19.56ms	1.33ms	8.81ms	9.42ms
Nuxt	89.2ms	89.3ms	13.11ms	0.95ms	1.22ms	10.94ms
React Router	131.6ms	131.83ms	19.05ms	1.61ms	2.58ms	14.87ms
SolidStart	103.8ms	103.85ms	16.99ms	0.85ms	2.32ms	13.82ms
SvelteKit	86.2ms	86.13ms	15.37ms	0.57ms	2.76ms	12.03ms
TanStack Start	126.2ms	125.96ms	25.99ms	1.58ms	15.53ms	8.88ms

First Paint (ms)

First Paint (ms) chart

First Paint (ms) data

Framework	Milliseconds
Astro	76.60 ms
Mastro	82.20 ms
SvelteKit	86.20 ms
Nuxt	89.20 ms
SolidStart	103.80 ms
TanStack Start	126.20 ms
React Router	131.60 ms
Next.js	162.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	76.71 ms
Mastro	82.24 ms
SvelteKit	86.13 ms
Nuxt	89.30 ms
SolidStart	103.85 ms
TanStack Start	125.96 ms
React Router	131.83 ms
Next.js	162.32 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.99 ms

M

5.87 ms

6.46 ms

13.11 ms

15.37 ms

16.99 ms

19.05 ms

19.56 ms

25.99 ms

Interaction Breakdown data

Framework or version	Interaction latency	Input delay	Processing duration	Presentation delay
Mastro	5.87 ms	0.54 ms	1.10 ms	4.23 ms
Astro	6.46 ms	0.63 ms	1.24 ms	4.59 ms
Nuxt	13.11 ms	0.95 ms	1.22 ms	10.94 ms
SvelteKit	15.37 ms	0.57 ms	2.76 ms	12.03 ms
SolidStart	16.99 ms	0.85 ms	2.32 ms	13.82 ms
React Router	19.05 ms	1.61 ms	2.58 ms	14.87 ms
Next.js	19.56 ms	1.33 ms	8.81 ms	9.42 ms
TanStack Start	25.99 ms	1.58 ms	15.53 ms	8.88 ms

Server Side Throughput Tests

Methodology: Server Side Throughput Tests.

Framework	Ops/sec	Median Latency	Body Size	Duplication
Baseline HTML	838	1.205ms	96.83kb	1x
Astro	657	1.467ms	96.89kb	1x
Mastro	347	2.863ms	327.46kb	1.5x
Next.js	225	4.615ms	199.52kb	2x
Nuxt	355	2.717ms	201.27kb	2x
React Router	351	2.795ms	211.63kb	2x
SolidStart	419	2.292ms	224.17kb	2x
SvelteKit	454	2.145ms	183.53kb	2x
TanStack Start	315	3.131ms	193.62kb	2x

Ops/sec

Ops/sec chart

Ops/sec data

Framework	Operations per second
Baseline HTML	838
Astro	657
SvelteKit	454
SolidStart	419
Nuxt	355
React Router	351
Mastro	347
TanStack Start	315
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.52 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.21 ms
Astro	1.47 ms
SvelteKit	2.15 ms
SolidStart	2.29 ms
Nuxt	2.72 ms
React Router	2.79 ms
Mastro	2.86 ms
TanStack Start	3.13 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,569	200	33ms	55ms	135ms	43,292
Astro	1,050.2	25	41ms	65ms	558ms	31,475
Mastro	568.4	50	67ms	164ms	1556ms	17,391
Next.js	37.6	1	2137ms	4649ms	4667ms	1,037
Nuxt	67.8	10	2059ms	4211ms	4299ms	2,135
React Router	172	25	332ms	1564ms	3987ms	5,673
SolidStart	504.2	25	108ms	503ms	2211ms	15,907
SvelteKit	483.2	25	89ms	462ms	2488ms	15,418
TanStack Start	43.6	10	3832ms	4129ms	4381ms	1,328

P99 Latency

P99 Latency at 25 Connections

P99 Latency at 25 Connections chart

P99 Latency at 25 Connections data

Framework	Milliseconds
Baseline HTML	33.00 ms
Astro	41.00 ms
Mastro	67.00 ms
SvelteKit	89.00 ms
SolidStart	108.00 ms
React Router	332.00 ms
Nuxt	2059.00 ms
Next.js	2137.00 ms
TanStack Start	3832.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	55.00 ms
Astro	65.00 ms
Mastro	164.00 ms
SvelteKit	462.00 ms
SolidStart	503.00 ms
React Router	1564.00 ms
TanStack Start	4129.00 ms
Nuxt	4211.00 ms
Next.js	4649.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	135.00 ms
Astro	558.00 ms
Mastro	1556.00 ms
SolidStart	2211.00 ms
SvelteKit	2488.00 ms
React Router	3987.00 ms
Nuxt	4299.00 ms
TanStack Start	4381.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	19.00 ms
Astro	26.00 ms
Mastro	49.00 ms
SvelteKit	62.00 ms
SolidStart	73.00 ms
React Router	150.00 ms
Nuxt	376.00 ms
TanStack Start	796.00 ms
Next.js	827.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	35.00 ms
Astro	54.00 ms
Mastro	91.00 ms
SvelteKit	135.00 ms
SolidStart	160.00 ms
React Router	301.00 ms
Nuxt	516.00 ms
TanStack Start	846.00 ms
Next.js	2409.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	85.00 ms
Astro	100.00 ms
SolidStart	171.00 ms
Mastro	206.00 ms
SvelteKit	212.00 ms
React Router	425.00 ms
Nuxt	805.00 ms
TanStack Start	1285.00 ms
Next.js	2879.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	18.00 ms
Astro	24.00 ms
Mastro	45.00 ms
SvelteKit	54.00 ms
SolidStart	61.00 ms
React Router	144.00 ms
Nuxt	367.00 ms
TanStack Start	632.00 ms
Next.js	746.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	33.00 ms
Astro	51.00 ms
Mastro	87.00 ms
SolidStart	100.00 ms
SvelteKit	112.00 ms
React Router	294.00 ms
Nuxt	469.00 ms
TanStack Start	631.00 ms
Next.js	1145.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	70.00 ms
Astro	94.00 ms
SolidStart	138.00 ms
SvelteKit	162.00 ms
Mastro	184.00 ms
React Router	393.00 ms
Nuxt	454.00 ms
TanStack Start	648.00 ms
Next.js	1098.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.