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	108ms	108.13ms	2.59ms	1.87ms	0.73ms	0ms
Next.js	338.6ms	338.64ms	18.66ms	1.27ms	6.66ms	10.72ms
Nuxt	153.8ms	153.83ms	10.7ms	0.46ms	2ms	8.24ms
React Router	153.4ms	153.32ms	22.18ms	1.47ms	2.55ms	18.16ms
SolidStart	104.4ms	104.24ms	17.69ms	1.43ms	2.33ms	13.93ms
SvelteKit	113ms	113.09ms	16.45ms	0.62ms	2.76ms	13.06ms
TanStack Start	145ms	145.03ms	32.86ms	1.64ms	16.42ms	14.8ms

First Paint (ms)

First Paint (ms) chart

First Paint (ms) data

Framework	Milliseconds
SolidStart	104.40 ms
Astro	108.00 ms
SvelteKit	113.00 ms
TanStack Start	145.00 ms
React Router	153.40 ms
Nuxt	153.80 ms
Next.js	338.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	104.24 ms
Astro	108.13 ms
SvelteKit	113.09 ms
TanStack Start	145.03 ms
React Router	153.32 ms
Nuxt	153.83 ms
Next.js	338.64 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.69 ms

Median: 17.69 ms

2.59 ms

10.70 ms

16.45 ms

17.69 ms

18.66 ms

22.18 ms

32.86 ms

Interaction Breakdown data

Framework or version	Interaction latency	Input delay	Processing duration	Presentation delay
Astro	2.59 ms	1.87 ms	0.73 ms	0.00 ms
Nuxt	10.70 ms	0.46 ms	2.00 ms	8.24 ms
SvelteKit	16.45 ms	0.62 ms	2.76 ms	13.06 ms
SolidStart	17.69 ms	1.43 ms	2.33 ms	13.93 ms
Next.js	18.66 ms	1.27 ms	6.66 ms	10.72 ms
React Router	22.18 ms	1.47 ms	2.55 ms	18.16 ms
TanStack Start	32.86 ms	1.64 ms	16.42 ms	14.80 ms

Server Side Rendered Tests

Methodology: Server Side Rendered Tests.

Framework	First Paint	FCP	Interaction Latency	Input Delay	Processing Duration	Presentation Delay
Astro	70.6ms	70.67ms	1.29ms	1.04ms	0.25ms	0ms
Next.js	160.4ms	160.51ms	19.4ms	1.28ms	8.48ms	9.64ms
Nuxt	124.6ms	124.48ms	17.38ms	0.87ms	2.16ms	14.35ms
React Router	119ms	118.94ms	21ms	1.39ms	2.95ms	16.66ms
SolidStart	94.2ms	94.19ms	17.38ms	1.38ms	2.37ms	13.64ms
SvelteKit	85.6ms	85.79ms	17.19ms	1.26ms	4.14ms	11.79ms
TanStack Start	118.6ms	118.5ms	32.87ms	1.69ms	19.26ms	11.93ms

First Paint (ms)

First Paint (ms) chart

First Paint (ms) data

Framework	Milliseconds
Astro	70.60 ms
SvelteKit	85.60 ms
SolidStart	94.20 ms
TanStack Start	118.60 ms
React Router	119.00 ms
Nuxt	124.60 ms
Next.js	160.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	70.67 ms
SvelteKit	85.79 ms
SolidStart	94.19 ms
TanStack Start	118.50 ms
React Router	118.94 ms
Nuxt	124.48 ms
Next.js	160.51 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.38 ms

Median: 17.38 ms

1.29 ms

17.19 ms

17.38 ms

17.38 ms

19.40 ms

21.00 ms

32.87 ms

Interaction Breakdown data

Framework or version	Interaction latency	Input delay	Processing duration	Presentation delay
Astro	1.29 ms	1.04 ms	0.25 ms	0.00 ms
SvelteKit	17.19 ms	1.26 ms	4.14 ms	11.79 ms
Nuxt	17.38 ms	0.87 ms	2.16 ms	14.35 ms
SolidStart	17.38 ms	1.38 ms	2.37 ms	13.64 ms
Next.js	19.40 ms	1.28 ms	8.48 ms	9.64 ms
React Router	21.00 ms	1.39 ms	2.95 ms	16.66 ms
TanStack Start	32.87 ms	1.69 ms	19.26 ms	11.93 ms

Server Side Throughput Tests

Methodology: Server Side Throughput Tests.

Framework	Ops/sec	Median Latency	Body Size	Duplication
Baseline HTML	847	1.201ms	96.83kb	1x
Astro	729	1.333ms	96.89kb	1x
Next.js	240	4.422ms	199.57kb	2x
Nuxt	358	2.718ms	201.57kb	2x
React Router	328	3.031ms	216.9kb	2x
SolidStart	433	2.23ms	224.17kb	2x
SvelteKit	458	2.117ms	183.53kb	2x
TanStack Start	310	3.19ms	193.62kb	2x

Ops/sec

Ops/sec chart

Ops/sec data

Framework	Operations per second
Baseline HTML	847
Astro	729
SvelteKit	458
SolidStart	433
Nuxt	358
React Router	328
TanStack Start	310
Next.js	240

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.57 KB
React Router	216.90 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.33 ms
SvelteKit	2.12 ms
SolidStart	2.23 ms
Nuxt	2.72 ms
React Router	3.03 ms
TanStack Start	3.19 ms
Next.js	4.42 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,698.4	200	19ms	47ms	116ms	48,064
Astro	1,585.6	50	24ms	45ms	103ms	47,206
Next.js	44.6	1	1809ms	4779ms	4676ms	1,251
Nuxt	479.8	100	77ms	447ms	2958ms	15,533
React Router	319	25	110ms	757ms	3532ms	10,337
SolidStart	525.21	5	91ms	466ms	2126ms	17,254
SvelteKit	488.8	5	86ms	196ms	2233ms	15,312
TanStack Start	295.4	25	158ms	1356ms	2690ms	9,705

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	24.00 ms
Nuxt	77.00 ms
SvelteKit	86.00 ms
SolidStart	91.00 ms
React Router	110.00 ms
TanStack Start	158.00 ms
Next.js	1809.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
Astro	45.00 ms
Baseline HTML	47.00 ms
SvelteKit	196.00 ms
Nuxt	447.00 ms
SolidStart	466.00 ms
React Router	757.00 ms
TanStack Start	1356.00 ms
Next.js	4779.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
Astro	103.00 ms
Baseline HTML	116.00 ms
SolidStart	2126.00 ms
SvelteKit	2233.00 ms
TanStack Start	2690.00 ms
Nuxt	2958.00 ms
React Router	3532.00 ms
Next.js	4676.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
Astro	18.00 ms
Baseline HTML	18.00 ms
Nuxt	56.00 ms
SvelteKit	67.00 ms
SolidStart	70.00 ms
React Router	80.00 ms
TanStack Start	116.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
Astro	33.00 ms
Baseline HTML	36.00 ms
Nuxt	113.00 ms
SvelteKit	145.00 ms
SolidStart	146.00 ms
React Router	159.00 ms
TanStack Start	253.00 ms
Next.js	2345.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
Astro	65.00 ms
Baseline HTML	82.00 ms
SolidStart	141.00 ms
Nuxt	197.00 ms
TanStack Start	258.00 ms
SvelteKit	270.00 ms
React Router	308.00 ms
Next.js	2674.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
Astro	17.00 ms
Baseline HTML	17.00 ms
Nuxt	54.00 ms
SvelteKit	58.00 ms
SolidStart	61.00 ms
React Router	78.00 ms
TanStack Start	97.00 ms
Next.js	652.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
Astro	31.00 ms
Baseline HTML	35.00 ms
SolidStart	96.00 ms
Nuxt	107.00 ms
SvelteKit	116.00 ms
React Router	155.00 ms
TanStack Start	160.00 ms
Next.js	1056.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
Astro	63.00 ms
Baseline HTML	69.00 ms
SolidStart	126.00 ms
Nuxt	174.00 ms
TanStack Start	186.00 ms
SvelteKit	210.00 ms
React Router	280.00 ms
Next.js	1057.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	41	1	1899ms	4650ms	4645ms	1,151
Nuxt	72.8	5	1896ms	4221ms	4092ms	2,343
React Router	166.8	25	274ms	1931ms	3904ms	5,398
TanStack Start	82.4	5	2119ms	3951ms	4046ms	2,475

P99 Latency

P99 Latency at 25 Connections

P99 Latency at 25 Connections chart

P99 Latency at 25 Connections data

Framework	Milliseconds
React Router	274.00 ms
Nuxt	1896.00 ms
Next.js	1899.00 ms
TanStack Start	2119.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	1931.00 ms
TanStack Start	3951.00 ms
Nuxt	4221.00 ms
Next.js	4650.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	3904.00 ms
TanStack Start	4046.00 ms
Nuxt	4092.00 ms
Next.js	4645.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	170.00 ms
Nuxt	345.00 ms
TanStack Start	483.00 ms
Next.js	686.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	310.00 ms
Nuxt	484.00 ms
TanStack Start	545.00 ms
Next.js	2411.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	432.00 ms
TanStack Start	613.00 ms
Nuxt	665.00 ms
Next.js	2713.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	148.00 ms
Nuxt	343.00 ms
TanStack Start	422.00 ms
Next.js	671.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	300.00 ms
TanStack Start	386.00 ms
Nuxt	441.00 ms
Next.js	1111.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	378.00 ms
TanStack Start	390.00 ms
Nuxt	445.00 ms
Next.js	1050.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.