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	126.8ms	126.57ms	2.26ms	1.94ms	0.32ms	0ms
Next.js	343.6ms	343.42ms	17.9ms	1.34ms	6.16ms	10.4ms
Nuxt	191ms	191.21ms	10.38ms	0.64ms	1.25ms	8.49ms
React Router	153ms	153.04ms	20.36ms	1.46ms	2.4ms	16.5ms
SolidStart	104ms	103.95ms	15.64ms	0.91ms	2.19ms	12.55ms
SvelteKit	221.2ms	221.13ms	18.54ms	2.42ms	3.07ms	13.05ms
TanStack Start	167.6ms	167.67ms	22.47ms	1.59ms	11.88ms	8.99ms

First Paint (ms)

First Paint (ms) chart

First Paint (ms) data

Framework	Milliseconds
SolidStart	104.00 ms
Astro	126.80 ms
React Router	153.00 ms
TanStack Start	167.60 ms
Nuxt	191.00 ms
SvelteKit	221.20 ms
Next.js	343.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	103.95 ms
Astro	126.57 ms
React Router	153.04 ms
TanStack Start	167.67 ms
Nuxt	191.21 ms
SvelteKit	221.13 ms
Next.js	343.42 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.90 ms

Median: 17.90 ms

2.26 ms

10.38 ms

15.64 ms

17.90 ms

18.54 ms

20.36 ms

22.47 ms

Interaction Breakdown data

Framework or version	Interaction latency	Input delay	Processing duration	Presentation delay
Astro	2.26 ms	1.94 ms	0.32 ms	0.00 ms
Nuxt	10.38 ms	0.64 ms	1.25 ms	8.49 ms
SolidStart	15.64 ms	0.91 ms	2.19 ms	12.55 ms
Next.js	17.90 ms	1.34 ms	6.16 ms	10.40 ms
SvelteKit	18.54 ms	2.42 ms	3.07 ms	13.05 ms
React Router	20.36 ms	1.46 ms	2.40 ms	16.50 ms
TanStack Start	22.47 ms	1.59 ms	11.88 ms	8.99 ms

Server Side Rendered Tests

Methodology: Server Side Rendered Tests.

Framework	First Paint	FCP	Interaction Latency	Input Delay	Processing Duration	Presentation Delay
Astro	72.4ms	72.44ms	2.13ms	1.46ms	0.67ms	0ms
Next.js	168.8ms	168.71ms	19.47ms	1.37ms	6.79ms	11.3ms
Nuxt	109.6ms	109.65ms	9.87ms	0.49ms	1.44ms	7.94ms
React Router	115.2ms	115.48ms	18.18ms	1.6ms	2.8ms	13.78ms
SolidStart	110.4ms	110.17ms	17.59ms	1.67ms	2.22ms	13.7ms
SvelteKit	96.2ms	96.13ms	15.84ms	0.62ms	4.07ms	11.15ms
TanStack Start	123.4ms	123.39ms	27.29ms	1.65ms	14.53ms	11.11ms

First Paint (ms)

First Paint (ms) chart

First Paint (ms) data

Framework	Milliseconds
Astro	72.40 ms
SvelteKit	96.20 ms
Nuxt	109.60 ms
SolidStart	110.40 ms
React Router	115.20 ms
TanStack Start	123.40 ms
Next.js	168.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	72.44 ms
SvelteKit	96.13 ms
Nuxt	109.65 ms
SolidStart	110.17 ms
React Router	115.48 ms
TanStack Start	123.39 ms
Next.js	168.71 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.59 ms

Median: 17.59 ms

2.13 ms

9.87 ms

15.84 ms

17.59 ms

18.18 ms

19.47 ms

27.29 ms

Interaction Breakdown data

Framework or version	Interaction latency	Input delay	Processing duration	Presentation delay
Astro	2.13 ms	1.46 ms	0.67 ms	0.00 ms
Nuxt	9.87 ms	0.49 ms	1.44 ms	7.94 ms
SvelteKit	15.84 ms	0.62 ms	4.07 ms	11.15 ms
SolidStart	17.59 ms	1.67 ms	2.22 ms	13.70 ms
React Router	18.18 ms	1.60 ms	2.80 ms	13.78 ms
Next.js	19.47 ms	1.37 ms	6.79 ms	11.30 ms
TanStack Start	27.29 ms	1.65 ms	14.53 ms	11.11 ms

Server Side Throughput Tests

Methodology: Server Side Throughput Tests.

Framework	Ops/sec	Median Latency	Body Size	Duplication
Baseline HTML	843	1.203ms	96.83kb	1x
Astro	663	1.452ms	96.89kb	1x
Next.js	226	4.578ms	199.57kb	2x
Nuxt	369	2.634ms	201.27kb	2x
React Router	352	2.795ms	211.63kb	2x
SolidStart	427	2.262ms	224.17kb	2x
SvelteKit	448	2.153ms	183.53kb	2x
TanStack Start	310	3.175ms	193.62kb	2x

Ops/sec

Ops/sec chart

Ops/sec data

Framework	Operations per second
Baseline HTML	843
Astro	663
SvelteKit	448
SolidStart	427
Nuxt	369
React Router	352
TanStack Start	310
Next.js	226

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

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.26 ms
Nuxt	2.63 ms
React Router	2.79 ms
TanStack Start	3.17 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,623.8	100	20ms	48ms	106ms	48,242
Astro	1,106.41	200	30ms	61ms	461ms	34,178
Next.js	38.6	1	2138ms	4754ms	4661ms	1,036
Nuxt	72.2	5	1866ms	4252ms	4208ms	2,331
React Router	169.2	5	362ms	1646ms	3853ms	5,632
SolidStart	529.8	25	106ms	447ms	2051ms	17,049
SvelteKit	503.8	5	87ms	456ms	2481ms	15,952
TanStack Start	44	10	3641ms	4086ms	4145ms	1,362

P99 Latency

P99 Latency at 25 Connections

P99 Latency at 25 Connections chart

P99 Latency at 25 Connections data

Framework	Milliseconds
Baseline HTML	20.00 ms
Astro	30.00 ms
SvelteKit	87.00 ms
SolidStart	106.00 ms
React Router	362.00 ms
Nuxt	1866.00 ms
Next.js	2138.00 ms
TanStack Start	3641.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	48.00 ms
Astro	61.00 ms
SolidStart	447.00 ms
SvelteKit	456.00 ms
React Router	1646.00 ms
TanStack Start	4086.00 ms
Nuxt	4252.00 ms
Next.js	4754.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	461.00 ms
SolidStart	2051.00 ms
SvelteKit	2481.00 ms
React Router	3853.00 ms
TanStack Start	4145.00 ms
Nuxt	4208.00 ms
Next.js	4661.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	59.00 ms
SolidStart	69.00 ms
React Router	149.00 ms
Nuxt	344.00 ms
TanStack Start	788.00 ms
Next.js	792.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	47.00 ms
SvelteKit	140.00 ms
SolidStart	149.00 ms
React Router	313.00 ms
Nuxt	497.00 ms
TanStack Start	822.00 ms
Next.js	2480.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	80.00 ms
Astro	94.00 ms
SolidStart	163.00 ms
SvelteKit	221.00 ms
React Router	403.00 ms
Nuxt	735.00 ms
TanStack Start	1226.00 ms
Next.js	2934.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	23.00 ms
SvelteKit	53.00 ms
SolidStart	57.00 ms
React Router	144.00 ms
Nuxt	340.00 ms
TanStack Start	523.00 ms
Next.js	777.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	31.00 ms
Astro	45.00 ms
SolidStart	91.00 ms
SvelteKit	109.00 ms
React Router	290.00 ms
Nuxt	450.00 ms
TanStack Start	551.00 ms
Next.js	1120.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	92.00 ms
SolidStart	134.00 ms
SvelteKit	165.00 ms
React Router	374.00 ms
Nuxt	428.00 ms
TanStack Start	574.00 ms
Next.js	1196.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	92	88	92	81	98
SolidStart	81	75	100	88	100
SvelteKit	79	78	78	69	95
Next.js	73	71	76	66	94
Nuxt	67	58	70	59	96
React Router	59	60	64	68	90

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	92
SolidStart	81
SvelteKit	79
Next.js	73
Nuxt	67
React Router	59

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	88
SvelteKit	78
SolidStart	75
Next.js	71
React Router	60
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	100
Astro	92
SvelteKit	78
Next.js	76
Nuxt	70
React Router	64

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	88
Astro	81
SvelteKit	69
React Router	68
Next.js	66
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	98
Nuxt	96
SvelteKit	95
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%
SolidStart	80	80	100	87	90
Astro	79	93	72	63	85
SvelteKit	67	80	58	55	74
Next.js	52	71	48	46	58
Nuxt	45	58	43	45	65
React Router	37	63	36	51	53

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	80
Astro	79
SvelteKit	67
Next.js	52
Nuxt	45
React Router	37

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	93
SolidStart	80
SvelteKit	80
Next.js	71
React Router	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	100
Astro	72
SvelteKit	58
Next.js	48
Nuxt	43
React Router	36

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	87
Astro	63
SvelteKit	55
React Router	51
Next.js	46
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	90
Astro	85
SvelteKit	74
Nuxt	65
Next.js	58
React Router	53

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

Methodology: Core Web Vitals.