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	107.6ms	107.63ms	2.55ms	2.27ms	0.27ms	0ms
Next.js	341.8ms	341.69ms	19.26ms	1.38ms	8.27ms	9.6ms
Nuxt	163.4ms	163.07ms	13.83ms	0.97ms	1.42ms	11.44ms
React Router	172.2ms	172.36ms	23.29ms	1.71ms	2.1ms	19.49ms
SolidStart	115.2ms	115.27ms	14.08ms	1.16ms	3.38ms	9.54ms
SvelteKit	117ms	116.89ms	17.27ms	1.58ms	2.76ms	12.93ms
TanStack Start	154.6ms	154.72ms	33.81ms	2.08ms	15.95ms	15.78ms

First Paint (ms)

First Paint (ms) chart

First Paint (ms) data

Framework	Milliseconds
Astro	107.60 ms
SolidStart	115.20 ms
SvelteKit	117.00 ms
TanStack Start	154.60 ms
Nuxt	163.40 ms
React Router	172.20 ms
Next.js	341.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	107.63 ms
SolidStart	115.27 ms
SvelteKit	116.89 ms
TanStack Start	154.72 ms
Nuxt	163.07 ms
React Router	172.36 ms
Next.js	341.69 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.27 ms

Median: 17.27 ms

2.55 ms

13.83 ms

14.08 ms

17.27 ms

19.26 ms

23.29 ms

33.81 ms

Interaction Breakdown data

Framework or version	Interaction latency	Input delay	Processing duration	Presentation delay
Astro	2.55 ms	2.27 ms	0.27 ms	0.00 ms
Nuxt	13.83 ms	0.97 ms	1.42 ms	11.44 ms
SolidStart	14.08 ms	1.16 ms	3.38 ms	9.54 ms
SvelteKit	17.27 ms	1.58 ms	2.76 ms	12.93 ms
Next.js	19.26 ms	1.38 ms	8.27 ms	9.60 ms
React Router	23.29 ms	1.71 ms	2.10 ms	19.49 ms
TanStack Start	33.81 ms	2.08 ms	15.95 ms	15.78 ms

Server Side Rendered Tests

Methodology: Server Side Rendered Tests.

Framework	First Paint	FCP	Interaction Latency	Input Delay	Processing Duration	Presentation Delay
Astro	70ms	70.21ms	1.41ms	1.15ms	0.26ms	0ms
Next.js	163.6ms	163.59ms	21.04ms	1.44ms	8.13ms	11.47ms
Nuxt	106.2ms	106.28ms	11.33ms	1.05ms	1.94ms	8.33ms
React Router	106ms	105.84ms	19.58ms	2.21ms	3.04ms	14.34ms
SolidStart	87.6ms	87.46ms	12.73ms	0.96ms	2.63ms	9.14ms
SvelteKit	98.6ms	98.52ms	12.46ms	0.73ms	3.3ms	8.43ms
TanStack Start	133.6ms	133.55ms	28.58ms	1.77ms	16.56ms	10.25ms

First Paint (ms)

First Paint (ms) chart

First Paint (ms) data

Framework	Milliseconds
Astro	70.00 ms
SolidStart	87.60 ms
SvelteKit	98.60 ms
React Router	106.00 ms
Nuxt	106.20 ms
TanStack Start	133.60 ms
Next.js	163.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	70.21 ms
SolidStart	87.46 ms
SvelteKit	98.52 ms
React Router	105.84 ms
Nuxt	106.28 ms
TanStack Start	133.55 ms
Next.js	163.59 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: 12.73 ms

Median: 12.73 ms

1.41 ms

11.33 ms

12.46 ms

12.73 ms

19.58 ms

21.04 ms

28.58 ms

Interaction Breakdown data

Framework or version	Interaction latency	Input delay	Processing duration	Presentation delay
Astro	1.41 ms	1.15 ms	0.26 ms	0.00 ms
Nuxt	11.33 ms	1.05 ms	1.94 ms	8.33 ms
SvelteKit	12.46 ms	0.73 ms	3.30 ms	8.43 ms
SolidStart	12.73 ms	0.96 ms	2.63 ms	9.14 ms
React Router	19.58 ms	2.21 ms	3.04 ms	14.34 ms
Next.js	21.04 ms	1.44 ms	8.13 ms	11.47 ms
TanStack Start	28.58 ms	1.77 ms	16.56 ms	10.25 ms

Server Side Throughput Tests

Methodology: Server Side Throughput Tests.

Framework	Ops/sec	Median Latency	Body Size	Duplication
Baseline HTML	826	1.23ms	96.83kb	1x
Astro	658	1.456ms	96.89kb	1x
Next.js	215	4.78ms	199.52kb	2x
Nuxt	361	2.671ms	201.57kb	2x
React Router	335	2.958ms	216.9kb	2x
SolidStart	430	2.252ms	224.17kb	2x
SvelteKit	455	2.129ms	183.53kb	2x
TanStack Start	321	3.08ms	193.62kb	2x

Ops/sec

Ops/sec chart

Ops/sec data

Framework	Operations per second
Baseline HTML	826
Astro	658
SvelteKit	455
SolidStart	430
Nuxt	361
React Router	335
TanStack Start	321
Next.js	215

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.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.23 ms
Astro	1.46 ms
SvelteKit	2.13 ms
SolidStart	2.25 ms
Nuxt	2.67 ms
React Router	2.96 ms
TanStack Start	3.08 ms
Next.js	4.78 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,745.2	100	21ms	51ms	92ms	48,595
Astro	1,193.41	50	35ms	46ms	382ms	35,632
Next.js	46.6	1	1757ms	4604ms	4723ms	1,300
Nuxt	479	10	79ms	444ms	2841ms	15,571
React Router	334.2	25	103ms	557ms	3444ms	10,842
SolidStart	538.21	10	96ms	346ms	2062ms	17,633
SvelteKit	453	200	94ms	374ms	1755ms	14,851
TanStack Start	301	10	153ms	1564ms	2724ms	9,894

P99 Latency

P99 Latency at 25 Connections

P99 Latency at 25 Connections chart

P99 Latency at 25 Connections data

Framework	Milliseconds
Baseline HTML	21.00 ms
Astro	35.00 ms
Nuxt	79.00 ms
SvelteKit	94.00 ms
SolidStart	96.00 ms
React Router	103.00 ms
TanStack Start	153.00 ms
Next.js	1757.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	46.00 ms
Baseline HTML	51.00 ms
SolidStart	346.00 ms
SvelteKit	374.00 ms
Nuxt	444.00 ms
React Router	557.00 ms
TanStack Start	1564.00 ms
Next.js	4604.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	92.00 ms
Astro	382.00 ms
SvelteKit	1755.00 ms
SolidStart	2062.00 ms
TanStack Start	2724.00 ms
Nuxt	2841.00 ms
React Router	3444.00 ms
Next.js	4723.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	23.00 ms
Nuxt	55.00 ms
SvelteKit	65.00 ms
SolidStart	66.00 ms
React Router	76.00 ms
TanStack Start	120.00 ms
Next.js	625.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	36.00 ms
Astro	43.00 ms
Nuxt	115.00 ms
SolidStart	148.00 ms
SvelteKit	155.00 ms
React Router	156.00 ms
TanStack Start	253.00 ms
Next.js	2135.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	74.00 ms
Astro	88.00 ms
SolidStart	153.00 ms
Nuxt	202.00 ms
SvelteKit	253.00 ms
TanStack Start	266.00 ms
React Router	327.00 ms
Next.js	2562.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	22.00 ms
Nuxt	53.00 ms
SolidStart	55.00 ms
SvelteKit	58.00 ms
React Router	75.00 ms
TanStack Start	104.00 ms
Next.js	620.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	35.00 ms
Astro	42.00 ms
SolidStart	89.00 ms
Nuxt	106.00 ms
SvelteKit	113.00 ms
React Router	151.00 ms
TanStack Start	157.00 ms
Next.js	1051.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	62.00 ms
Astro	85.00 ms
SolidStart	122.00 ms
TanStack Start	178.00 ms
Nuxt	179.00 ms
SvelteKit	191.00 ms
React Router	271.00 ms
Next.js	1043.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.2	1	2003ms	4667ms	4606ms	1,150
Nuxt	69	10	2050ms	4168ms	4305ms	2,210
React Router	176.6	25	284ms	1717ms	3892ms	5,903
TanStack Start	44.6	5	3509ms	3960ms	4448ms	1,389

P99 Latency

P99 Latency at 25 Connections

P99 Latency at 25 Connections chart

P99 Latency at 25 Connections data

Framework	Milliseconds
React Router	284.00 ms
Next.js	2003.00 ms
Nuxt	2050.00 ms
TanStack Start	3509.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	1717.00 ms
TanStack Start	3960.00 ms
Nuxt	4168.00 ms
Next.js	4667.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	3892.00 ms
Nuxt	4305.00 ms
TanStack Start	4448.00 ms
Next.js	4606.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	143.00 ms
Nuxt	367.00 ms
Next.js	706.00 ms
TanStack Start	725.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	293.00 ms
Nuxt	509.00 ms
TanStack Start	741.00 ms
Next.js	2469.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	401.00 ms
Nuxt	735.00 ms
TanStack Start	1263.00 ms
Next.js	2690.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	362.00 ms
TanStack Start	526.00 ms
Next.js	693.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	277.00 ms
Nuxt	455.00 ms
TanStack Start	604.00 ms
Next.js	1114.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	366.00 ms
Nuxt	441.00 ms
TanStack Start	513.00 ms
Next.js	1108.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.