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	94.6ms	94.53ms	2.84ms	1.97ms	0.87ms	0ms
Next.js	338.4ms	338.36ms	15.61ms	1.38ms	4.45ms	9.78ms
Nuxt	160.6ms	160.43ms	12.25ms	1.06ms	1.27ms	9.92ms
Pracht	100.8ms	100.75ms	18.88ms	0.98ms	3.63ms	14.28ms
React Router	169.6ms	169.88ms	21.61ms	1.52ms	2.63ms	17.46ms
SolidStart	103ms	103.19ms	16.51ms	1.04ms	3.63ms	11.83ms
SvelteKit	111.8ms	111.74ms	14.13ms	0.73ms	2.07ms	11.33ms
TanStack Start	131.8ms	131.62ms	22.23ms	1.45ms	3.13ms	17.65ms

Client First Paint

Client First Paint chart

Client First Paint data

Framework	Milliseconds
Astro	94.60 ms
Pracht	100.80 ms
SolidStart	103.00 ms
SvelteKit	111.80 ms
TanStack Start	131.80 ms
Nuxt	160.60 ms
React Router	169.60 ms
Next.js	338.40 ms

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

Client FCP

Client FCP chart

Client FCP data

Framework	Milliseconds
Astro	94.53 ms
Pracht	100.75 ms
SolidStart	103.19 ms
SvelteKit	111.74 ms
TanStack Start	131.62 ms
Nuxt	160.43 ms
React Router	169.88 ms
Next.js	338.36 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.06 ms

Median: 15.61 ms

2.84 ms

12.25 ms

14.13 ms

15.61 ms

16.51 ms

18.88 ms

21.61 ms

22.23 ms

Interaction Breakdown data

Framework or version	Interaction latency	Input delay	Processing duration	Presentation delay
Astro	2.84 ms	1.97 ms	0.87 ms	0.00 ms
Nuxt	12.25 ms	1.06 ms	1.27 ms	9.92 ms
SvelteKit	14.13 ms	0.73 ms	2.07 ms	11.33 ms
Next.js	15.61 ms	1.38 ms	4.45 ms	9.78 ms
SolidStart	16.51 ms	1.04 ms	3.63 ms	11.83 ms
Pracht	18.88 ms	0.98 ms	3.63 ms	14.28 ms
React Router	21.61 ms	1.52 ms	2.63 ms	17.46 ms
TanStack Start	22.23 ms	1.45 ms	3.13 ms	17.65 ms

Server Side Rendered Tests

Methodology: Server Side Rendered Tests.

Framework	First Paint	FCP	Interaction Latency	Input Delay	Processing Duration	Presentation Delay
Astro	59.4ms	59.4ms	0.94ms	0.69ms	0.25ms	0ms
Next.js	384.4ms	384.42ms	18.21ms	1.55ms	6.55ms	10.12ms
Nuxt	98.6ms	98.67ms	12.56ms	0.75ms	1.31ms	10.51ms
Pracht	89.8ms	89.71ms	17.29ms	0.86ms	3.35ms	13.08ms
React Router	114ms	114.09ms	17.43ms	1.71ms	3.48ms	12.24ms
SolidStart	87.2ms	87.34ms	17.34ms	1.63ms	2.55ms	13.15ms
SvelteKit	92.2ms	92.24ms	15.97ms	0.98ms	2.31ms	12.68ms
TanStack Start	105.4ms	105.42ms	20.91ms	2.09ms	5.53ms	13.29ms

Server First Paint

Server First Paint chart

Server First Paint data

Framework	Milliseconds
Astro	59.40 ms
SolidStart	87.20 ms
Pracht	89.80 ms
SvelteKit	92.20 ms
Nuxt	98.60 ms
TanStack Start	105.40 ms
React Router	114.00 ms
Next.js	384.40 ms

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

Server FCP

Server FCP chart

Server FCP data

Framework	Milliseconds
Astro	59.40 ms
SolidStart	87.34 ms
Pracht	89.71 ms
SvelteKit	92.24 ms
Nuxt	98.67 ms
TanStack Start	105.42 ms
React Router	114.09 ms
Next.js	384.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.31 ms

Median: 17.34 ms

0.94 ms

12.56 ms

15.97 ms

17.29 ms

17.34 ms

17.43 ms

18.21 ms

20.91 ms

Interaction Breakdown data

Framework or version	Interaction latency	Input delay	Processing duration	Presentation delay
Astro	0.94 ms	0.69 ms	0.25 ms	0.00 ms
Nuxt	12.56 ms	0.75 ms	1.31 ms	10.51 ms
SvelteKit	15.97 ms	0.98 ms	2.31 ms	12.68 ms
Pracht	17.29 ms	0.86 ms	3.35 ms	13.08 ms
SolidStart	17.34 ms	1.63 ms	2.55 ms	13.15 ms
React Router	17.43 ms	1.71 ms	3.48 ms	12.24 ms
Next.js	18.21 ms	1.55 ms	6.55 ms	10.12 ms
TanStack Start	20.91 ms	2.09 ms	5.53 ms	13.29 ms

Server Side Throughput Tests

Methodology: Server Side Throughput Tests.

Framework	Ops/sec	Median Latency	Body Size	Duplication
Baseline HTML	840	1.208ms	96.83kb	1x
Astro	732	1.321ms	96.89kb	1x
Next.js	133	7.348ms	204.56kb	2x
Nuxt	383	2.504ms	201.73kb	2x
Pracht	580	1.647ms	187.02kb	2x
React Router	325	3.002ms	216.98kb	2x
SolidStart	365	2.638ms	224.26kb	2x
SvelteKit	437	2.247ms	184.3kb	2x
TanStack Start	360	2.706ms	192.53kb	2x

Ops/sec

Ops/sec chart

Ops/sec data

Framework	Operations per second
Baseline HTML	840
Astro	732
Pracht	580
SvelteKit	437
Nuxt	383
SolidStart	365
TanStack Start	360
React Router	325
Next.js	133

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	184.30 KB
Pracht	187.02 KB
TanStack Start	192.53 KB
Nuxt	201.73 KB
Next.js	204.56 KB
React Router	216.98 KB
SolidStart	224.26 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.32 ms
Pracht	1.65 ms
SvelteKit	2.25 ms
Nuxt	2.50 ms
SolidStart	2.64 ms
TanStack Start	2.71 ms
React Router	3.00 ms
Next.js	7.35 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,749	100	18ms	57ms	91ms	50,461
Astro	1,520.6	25	27ms	49ms	173ms	45,359
Next.js	51.2	5	1234ms	4238ms	4592ms	1,567
Nuxt	519.6	5	76ms	382ms	3091ms	16,786
Pracht	688.2	25	42ms	107ms	1065ms	21,408
React Router	350.2	25	101ms	565ms	3097ms	11,508
SolidStart	533.6	10	99ms	464ms	2173ms	17,215
SvelteKit	584.8	25	74ms	157ms	2265ms	18,860
TanStack Start	393.4	100	119ms	707ms	2763ms	12,811

P99 Latency

P99 Latency at 25 Connections

P99 Latency at 25 Connections chart

P99 Latency at 25 Connections data

Framework	Milliseconds
Baseline HTML	18.00 ms
Astro	27.00 ms
Pracht	42.00 ms
SvelteKit	74.00 ms
Nuxt	76.00 ms
SolidStart	99.00 ms
React Router	101.00 ms
TanStack Start	119.00 ms
Next.js	1234.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	49.00 ms
Baseline HTML	57.00 ms
Pracht	107.00 ms
SvelteKit	157.00 ms
Nuxt	382.00 ms
SolidStart	464.00 ms
React Router	565.00 ms
TanStack Start	707.00 ms
Next.js	4238.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	91.00 ms
Astro	173.00 ms
Pracht	1065.00 ms
SolidStart	2173.00 ms
SvelteKit	2265.00 ms
TanStack Start	2763.00 ms
Nuxt	3091.00 ms
React Router	3097.00 ms
Next.js	4592.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	16.00 ms
Astro	17.00 ms
Pracht	37.00 ms
Nuxt	50.00 ms
SvelteKit	52.00 ms
SolidStart	70.00 ms
React Router	73.00 ms
TanStack Start	89.00 ms
Next.js	516.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	34.00 ms
Baseline HTML	38.00 ms
Pracht	77.00 ms
Nuxt	109.00 ms
SvelteKit	117.00 ms
React Router	146.00 ms
SolidStart	151.00 ms
TanStack Start	178.00 ms
Next.js	1802.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	67.00 ms
Baseline HTML	71.00 ms
Pracht	150.00 ms
SolidStart	169.00 ms
Nuxt	185.00 ms
SvelteKit	188.00 ms
TanStack Start	219.00 ms
React Router	290.00 ms
Next.js	2326.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	17.00 ms
Pracht	36.00 ms
SvelteKit	43.00 ms
Nuxt	48.00 ms
SolidStart	58.00 ms
React Router	71.00 ms
TanStack Start	72.00 ms
Next.js	508.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	33.00 ms
Baseline HTML	33.00 ms
Pracht	73.00 ms
SolidStart	93.00 ms
Nuxt	97.00 ms
SvelteKit	101.00 ms
TanStack Start	133.00 ms
React Router	143.00 ms
Next.js	987.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	58.00 ms
Astro	65.00 ms
SolidStart	126.00 ms
Pracht	147.00 ms
SvelteKit	148.00 ms
Nuxt	159.00 ms
TanStack Start	174.00 ms
React Router	269.00 ms
Next.js	1003.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	46	10	1399ms	4790ms	4702ms	1,408
Nuxt	178.6	5	500ms	2744ms	3682ms	5,832
Pracht	387	25	93ms	453ms	2900ms	12,016
React Router	178.6	25	174ms	1521ms	4015ms	5,990
TanStack Start	255.8	50	219ms	1201ms	3028ms	8,495

P99 Latency

P99 Latency at 25 Connections

P99 Latency at 25 Connections chart

P99 Latency at 25 Connections data

Framework	Milliseconds
Pracht	93.00 ms
React Router	174.00 ms
TanStack Start	219.00 ms
Nuxt	500.00 ms
Next.js	1399.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
Pracht	453.00 ms
TanStack Start	1201.00 ms
React Router	1521.00 ms
Nuxt	2744.00 ms
Next.js	4790.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
Pracht	2900.00 ms
TanStack Start	3028.00 ms
Nuxt	3682.00 ms
React Router	4015.00 ms
Next.js	4702.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
Pracht	65.00 ms
TanStack Start	128.00 ms
React Router	143.00 ms
Nuxt	152.00 ms
Next.js	569.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
Pracht	135.00 ms
TanStack Start	254.00 ms
React Router	280.00 ms
Nuxt	294.00 ms
Next.js	2270.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
Pracht	262.00 ms
Nuxt	318.00 ms
TanStack Start	322.00 ms
React Router	403.00 ms
Next.js	2408.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
Pracht	64.00 ms
TanStack Start	103.00 ms
React Router	138.00 ms
Nuxt	142.00 ms
Next.js	552.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
Pracht	127.00 ms
TanStack Start	219.00 ms
React Router	273.00 ms
Nuxt	289.00 ms
Next.js	1077.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
TanStack Start	230.00 ms
Pracht	240.00 ms
Nuxt	289.00 ms
React Router	376.00 ms
Next.js	1056.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.