Run Time Stats

Setup

Runtime apps implement comparable benchmark routes across frameworks. See Default Benchmark Setup for the shared environment and each framework’s build tool and adapter. Test-specific differences are documented in the linked methodology sections below.

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	116.6ms	116.68ms	4.8ms	2.08ms	0.39ms	2.33ms
Next.js	341.6ms	341.52ms	22.02ms	1.45ms	8.94ms	11.63ms
Nuxt	162ms	161.96ms	12.16ms	0.52ms	2.33ms	9.31ms
React Router	185.2ms	185.21ms	26.28ms	1.71ms	2.72ms	21.86ms
SolidStart	125ms	125.06ms	17.66ms	1ms	3.74ms	12.92ms
SvelteKit	126.6ms	126.62ms	15.87ms	0.8ms	3.99ms	11.08ms
TanStack Start	164.4ms	164.45ms	33.23ms	2.12ms	18.54ms	12.56ms

First Paint (ms)

First Paint (ms) chart

First Paint (ms) data

Framework	Milliseconds
Astro	116.60 ms
SolidStart	125.00 ms
SvelteKit	126.60 ms
Nuxt	162.00 ms
TanStack Start	164.40 ms
React Router	185.20 ms
Next.js	341.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
Astro	116.68 ms
SolidStart	125.06 ms
SvelteKit	126.62 ms
Nuxt	161.96 ms
TanStack Start	164.45 ms
React Router	185.21 ms
Next.js	341.52 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.66 ms

Median: 17.66 ms

4.80 ms

12.16 ms

15.87 ms

17.66 ms

22.02 ms

26.28 ms

33.23 ms

Interaction Breakdown data

Framework or version	Interaction latency	Input delay	Processing duration	Presentation delay
Astro	4.80 ms	2.08 ms	0.39 ms	2.33 ms
Nuxt	12.16 ms	0.52 ms	2.33 ms	9.31 ms
SvelteKit	15.87 ms	0.80 ms	3.99 ms	11.08 ms
SolidStart	17.66 ms	1.00 ms	3.74 ms	12.92 ms
Next.js	22.02 ms	1.45 ms	8.94 ms	11.63 ms
React Router	26.28 ms	1.71 ms	2.72 ms	21.86 ms
TanStack Start	33.23 ms	2.12 ms	18.54 ms	12.56 ms

Server Side Rendered Tests

Methodology: Server Side Rendered Tests.

Framework	First Paint	FCP	Interaction Latency	Input Delay	Processing Duration	Presentation Delay
Astro	77.6ms	77.71ms	1.19ms	0.76ms	0.43ms	0ms
Next.js	156.2ms	155.98ms	17.62ms	1.26ms	7.37ms	8.99ms
Nuxt	120.4ms	120.42ms	11.05ms	0.48ms	1.41ms	9.16ms
React Router	125.6ms	125.44ms	17.37ms	1.61ms	2.69ms	13.08ms
SolidStart	94ms	93.84ms	14.71ms	0.85ms	2.44ms	11.42ms
SvelteKit	101ms	100.97ms	16.71ms	1.17ms	3.92ms	11.62ms
TanStack Start	130.2ms	130.22ms	28.58ms	1.83ms	14.6ms	12.16ms

First Paint (ms)

First Paint (ms) chart

First Paint (ms) data

Framework	Milliseconds
Astro	77.60 ms
SolidStart	94.00 ms
SvelteKit	101.00 ms
Nuxt	120.40 ms
React Router	125.60 ms
TanStack Start	130.20 ms
Next.js	156.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	77.71 ms
SolidStart	93.84 ms
SvelteKit	100.97 ms
Nuxt	120.42 ms
React Router	125.44 ms
TanStack Start	130.22 ms
Next.js	155.98 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.71 ms

Median: 16.71 ms

1.19 ms

11.05 ms

14.71 ms

16.71 ms

17.37 ms

17.62 ms

28.58 ms

Interaction Breakdown data

Framework or version	Interaction latency	Input delay	Processing duration	Presentation delay
Astro	1.19 ms	0.76 ms	0.43 ms	0.00 ms
Nuxt	11.05 ms	0.48 ms	1.41 ms	9.16 ms
SolidStart	14.71 ms	0.85 ms	2.44 ms	11.42 ms
SvelteKit	16.71 ms	1.17 ms	3.92 ms	11.62 ms
React Router	17.37 ms	1.61 ms	2.69 ms	13.08 ms
Next.js	17.62 ms	1.26 ms	7.37 ms	8.99 ms
TanStack Start	28.58 ms	1.83 ms	14.60 ms	12.16 ms

Server Side Throughput Tests

Methodology: Server Side Throughput Tests.

Framework	Ops/sec	Median Latency	Body Size	Duplication
Baseline HTML	837	1.205ms	96.83kb	1x
Astro	662	1.449ms	96.89kb	1x
Next.js	220	4.606ms	199.57kb	2x
Nuxt	362	2.625ms	201.27kb	2x
React Router	327	3.007ms	212.07kb	2x
SolidStart	424	2.263ms	224.17kb	2x
SvelteKit	448	2.158ms	183.53kb	2x
TanStack Start	315	3.13ms	193.62kb	2x

Ops/sec

Ops/sec chart

Ops/sec data

Framework	Operations per second
Baseline HTML	837
Astro	662
SvelteKit	448
SolidStart	424
Nuxt	362
React Router	327
TanStack Start	315
Next.js	220

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	212.07 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.21 ms
Astro	1.45 ms
SvelteKit	2.16 ms
SolidStart	2.26 ms
Nuxt	2.63 ms
React Router	3.01 ms
TanStack Start	3.13 ms
Next.js	4.61 ms

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

SSR Load Test

Methodology: SSR Load Test.

All eight frameworks render the same 1,000-row, three-column table using ordinary <a> links. This compares server rendering under HTTP load without the extra work of rendering framework router link components. Requests still pass through each framework’s server routing. No browser runs and no links are clicked.

Framework	Peak req/s	Peak Connections	P99 @ 25	P99 @ 50	P99 @ 100	Total Req.
Baseline HTML	1,692.4	50	20ms	39ms	106ms	48,521
Astro	1,123.8	25	33ms	74ms	425ms	33,383
Next.js	45	5	1708ms	4651ms	4662ms	1,290
Nuxt	490.8	10	77ms	404ms	2842ms	15,996
React Router	344.8	10	94ms	647ms	3354ms	11,381
SolidStart	539	10	94ms	437ms	2277ms	17,274
SvelteKit	498.4	5	79ms	481ms	2401ms	15,532
TanStack Start	280.2	10	176ms	1779ms	2806ms	9,166

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	33.00 ms
Nuxt	77.00 ms
SvelteKit	79.00 ms
React Router	94.00 ms
SolidStart	94.00 ms
TanStack Start	176.00 ms
Next.js	1708.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	74.00 ms
Nuxt	404.00 ms
SolidStart	437.00 ms
SvelteKit	481.00 ms
React Router	647.00 ms
TanStack Start	1779.00 ms
Next.js	4651.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	425.00 ms
SolidStart	2277.00 ms
SvelteKit	2401.00 ms
TanStack Start	2806.00 ms
Nuxt	2842.00 ms
React Router	3354.00 ms
Next.js	4662.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	18.00 ms
Astro	24.00 ms
Nuxt	54.00 ms
SvelteKit	60.00 ms
SolidStart	68.00 ms
React Router	74.00 ms
TanStack Start	132.00 ms
Next.js	659.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	34.00 ms
Astro	53.00 ms
Nuxt	110.00 ms
React Router	146.00 ms
SvelteKit	146.00 ms
SolidStart	156.00 ms
TanStack Start	236.00 ms
Next.js	2306.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	77.00 ms
Astro	98.00 ms
SolidStart	168.00 ms
Nuxt	188.00 ms
SvelteKit	232.00 ms
TanStack Start	260.00 ms
React Router	276.00 ms
Next.js	2376.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	17.00 ms
Astro	22.00 ms
Nuxt	51.00 ms
SvelteKit	54.00 ms
SolidStart	58.00 ms
React Router	73.00 ms
TanStack Start	115.00 ms
Next.js	638.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	30.00 ms
Astro	49.00 ms
Nuxt	101.00 ms
SolidStart	102.00 ms
SvelteKit	117.00 ms
React Router	144.00 ms
TanStack Start	171.00 ms
Next.js	1039.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	125.00 ms
SvelteKit	160.00 ms
Nuxt	173.00 ms
TanStack Start	176.00 ms
React Router	258.00 ms
Next.js	1050.00 ms

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

SSR Router Link Load Test

Methodology: SSR Router Link Load Test.

The same load test using framework router link components, showing how rendering those components affects server performance compared with ordinary HTML links.

Framework	Peak req/s	Peak Connections	P99 @ 25	P99 @ 50	P99 @ 100	Total Req.
Next.js	40	1	2000ms	4740ms	4772ms	1,154
Nuxt	73.8	5	1921ms	4145ms	4251ms	2,388
React Router	180.6	50	309ms	310ms	3862ms	5,944
TanStack Start	45.8	10	3819ms	4305ms	4534ms	1,406

P99 Latency

P99 Latency at 25 Connections

P99 Latency at 25 Connections chart

P99 Latency at 25 Connections data

Framework	Milliseconds
React Router	309.00 ms
Nuxt	1921.00 ms
Next.js	2000.00 ms
TanStack Start	3819.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
React Router	310.00 ms
Nuxt	4145.00 ms
TanStack Start	4305.00 ms
Next.js	4740.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
React Router	3862.00 ms
Nuxt	4251.00 ms
TanStack Start	4534.00 ms
Next.js	4772.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
React Router	151.00 ms
Nuxt	336.00 ms
Next.js	714.00 ms
TanStack Start	718.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
React Router	276.00 ms
Nuxt	494.00 ms
TanStack Start	718.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
React Router	405.00 ms
Nuxt	582.00 ms
TanStack Start	1344.00 ms
Next.js	2702.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
React Router	139.00 ms
Nuxt	332.00 ms
TanStack Start	572.00 ms
Next.js	707.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
React Router	271.00 ms
Nuxt	456.00 ms
TanStack Start	570.00 ms
Next.js	1119.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
React Router	362.00 ms
Nuxt	441.00 ms
TanStack Start	501.00 ms
Next.js	1087.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	93	89	92	81	98
SolidStart	100	77	100	85	100
SvelteKit	79	78	77	68	95
Next.js	74	72	76	66	94
TanStack Start	55	81	46	29	91
Nuxt	68	58	69	59	96
React Router	59	61	65	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	%
SolidStart	100
Astro	93
SvelteKit	79
Next.js	74
Nuxt	68
React Router	59
TanStack Start	55

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	89
TanStack Start	81
SvelteKit	78
SolidStart	77
Next.js	72
React Router	61
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	77
Next.js	76
Nuxt	69
React Router	65
TanStack Start	46

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	85
Astro	81
SvelteKit	68
React Router	68
Next.js	66
Nuxt	59
TanStack Start	29

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
TanStack Start	91
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	80	93	73	64	85
SolidStart	88	66	88	85	75
SvelteKit	67	81	58	54	74
Next.js	53	72	48	45	59
Nuxt	46	59	44	46	65
React Router	37	63	37	50	53
TanStack Start	31	84	19	13	51

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	88
Astro	80
SvelteKit	67
Next.js	53
Nuxt	46
React Router	37
TanStack Start	31

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
TanStack Start	84
SvelteKit	81
Next.js	72
SolidStart	66
React Router	63
Nuxt	59

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	88
Astro	73
SvelteKit	58
Next.js	48
Nuxt	44
React Router	37
TanStack Start	19

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	85
Astro	64
SvelteKit	54
React Router	50
Nuxt	46
Next.js	45
TanStack Start	13

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	%
Astro	85
SolidStart	75
SvelteKit	74
Nuxt	65
Next.js	59
React Router	53
TanStack Start	51

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

Methodology: Core Web Vitals.