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	87.4ms	87.52ms	3.3ms	3.03ms	0.28ms	0ms
Next.js	338.8ms	338.67ms	21.53ms	1.29ms	6.88ms	13.36ms
Nuxt	139.6ms	139.37ms	12.38ms	0.78ms	1.57ms	10.02ms
Pracht	92.8ms	92.64ms	20.68ms	0.86ms	3.67ms	16.15ms
React Router	159.4ms	159.35ms	16.21ms	2.09ms	2.18ms	11.94ms
SolidStart	96.4ms	96.38ms	16.78ms	1.22ms	2.9ms	12.66ms
SvelteKit	112.8ms	112.92ms	18.81ms	0.87ms	3.15ms	14.79ms
TanStack Start	169.6ms	169.61ms	28.66ms	1.71ms	18.93ms	8.01ms

First Paint (ms)

First Paint (ms) chart

First Paint (ms) data

Framework	Milliseconds
Astro	87.40 ms
Pracht	92.80 ms
SolidStart	96.40 ms
SvelteKit	112.80 ms
Nuxt	139.60 ms
React Router	159.40 ms
TanStack Start	169.60 ms
Next.js	338.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	87.52 ms
Pracht	92.64 ms
SolidStart	96.38 ms
SvelteKit	112.92 ms
Nuxt	139.37 ms
React Router	159.35 ms
TanStack Start	169.61 ms
Next.js	338.67 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.80 ms

Median: 16.78 ms

3.30 ms

12.38 ms

16.21 ms

16.78 ms

18.81 ms

20.68 ms

21.53 ms

28.66 ms

Interaction Breakdown data

Framework or version	Interaction latency	Input delay	Processing duration	Presentation delay
Astro	3.30 ms	3.03 ms	0.28 ms	0.00 ms
Nuxt	12.38 ms	0.78 ms	1.57 ms	10.02 ms
React Router	16.21 ms	2.09 ms	2.18 ms	11.94 ms
SolidStart	16.78 ms	1.22 ms	2.90 ms	12.66 ms
SvelteKit	18.81 ms	0.87 ms	3.15 ms	14.79 ms
Pracht	20.68 ms	0.86 ms	3.67 ms	16.15 ms
Next.js	21.53 ms	1.29 ms	6.88 ms	13.36 ms
TanStack Start	28.66 ms	1.71 ms	18.93 ms	8.01 ms

Server Side Rendered Tests

Methodology: Server Side Rendered Tests.

Framework	First Paint	FCP	Interaction Latency	Input Delay	Processing Duration	Presentation Delay
Astro	62.2ms	62.06ms	0.82ms	0.55ms	0.27ms	0ms
Next.js	134.2ms	134.25ms	18.89ms	1.53ms	7.5ms	9.86ms
Nuxt	90.6ms	90.74ms	10.56ms	0.8ms	1.63ms	8.13ms
Pracht	92.8ms	92.82ms	17.6ms	1.59ms	2.39ms	13.62ms
React Router	104.8ms	104.73ms	18.41ms	1.77ms	3.39ms	13.25ms
SolidStart	89ms	89.02ms	17.75ms	1.5ms	2.45ms	13.8ms
SvelteKit	82.8ms	82.59ms	16.29ms	0.83ms	1.97ms	13.48ms
TanStack Start	90.6ms	90.57ms	27.42ms	1.76ms	18.1ms	7.55ms

First Paint (ms)

First Paint (ms) chart

First Paint (ms) data

Framework	Milliseconds
Astro	62.20 ms
SvelteKit	82.80 ms
SolidStart	89.00 ms
Nuxt	90.60 ms
TanStack Start	90.60 ms
Pracht	92.80 ms
React Router	104.80 ms
Next.js	134.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	62.06 ms
SvelteKit	82.59 ms
SolidStart	89.02 ms
TanStack Start	90.57 ms
Nuxt	90.74 ms
Pracht	92.82 ms
React Router	104.73 ms
Next.js	134.25 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.68 ms

Median: 17.75 ms

0.82 ms

10.56 ms

16.29 ms

17.60 ms

17.75 ms

18.41 ms

18.89 ms

27.42 ms

Interaction Breakdown data

Framework or version	Interaction latency	Input delay	Processing duration	Presentation delay
Astro	0.82 ms	0.55 ms	0.27 ms	0.00 ms
Nuxt	10.56 ms	0.80 ms	1.63 ms	8.13 ms
SvelteKit	16.29 ms	0.83 ms	1.97 ms	13.48 ms
Pracht	17.60 ms	1.59 ms	2.39 ms	13.62 ms
SolidStart	17.75 ms	1.50 ms	2.45 ms	13.80 ms
React Router	18.41 ms	1.77 ms	3.39 ms	13.25 ms
Next.js	18.89 ms	1.53 ms	7.50 ms	9.86 ms
TanStack Start	27.42 ms	1.76 ms	18.10 ms	7.55 ms

Server Side Throughput Tests

Methodology: Server Side Throughput Tests.

Framework	Ops/sec	Median Latency	Body Size	Duplication
Baseline HTML	843	1.2ms	96.83kb	1x
Astro	725	1.342ms	96.89kb	1x
Next.js	216	4.744ms	199.57kb	2x
Nuxt	373	2.606ms	201.73kb	2x
Pracht	585	1.65ms	187.02kb	2x
React Router	329	3.003ms	216.9kb	2x
SolidStart	420	2.308ms	224.17kb	2x
SvelteKit	449	2.205ms	184.3kb	2x
TanStack Start	318	3.1ms	191.92kb	2x

Ops/sec

Ops/sec chart

Ops/sec data

Framework	Operations per second
Baseline HTML	843
Astro	725
Pracht	585
SvelteKit	449
SolidStart	420
Nuxt	373
React Router	329
TanStack Start	318
Next.js	216

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	191.92 KB
Next.js	199.57 KB
Nuxt	201.73 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.34 ms
Pracht	1.65 ms
SvelteKit	2.21 ms
SolidStart	2.31 ms
Nuxt	2.61 ms
React Router	3.00 ms
TanStack Start	3.10 ms
Next.js	4.74 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,647	200	21ms	40ms	114ms	48,356
Astro	1,534.4	25	24ms	50ms	100ms	46,109
Next.js	44.8	1	1870ms	4705ms	4730ms	1,245
Nuxt	520	100	79ms	338ms	2692ms	16,975
Pracht	663.8	25	43ms	113ms	1161ms	20,577
React Router	342	25	105ms	503ms	3437ms	11,297
SolidStart	515	10	111ms	614ms	2352ms	15,777
SvelteKit	566.21	25	77ms	217ms	2187ms	18,065
TanStack Start	390.4	50	126ms	768ms	2456ms	12,942

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	24.00 ms
Pracht	43.00 ms
SvelteKit	77.00 ms
Nuxt	79.00 ms
React Router	105.00 ms
SolidStart	111.00 ms
TanStack Start	126.00 ms
Next.js	1870.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	40.00 ms
Astro	50.00 ms
Pracht	113.00 ms
SvelteKit	217.00 ms
Nuxt	338.00 ms
React Router	503.00 ms
SolidStart	614.00 ms
TanStack Start	768.00 ms
Next.js	4705.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	100.00 ms
Baseline HTML	114.00 ms
Pracht	1161.00 ms
SvelteKit	2187.00 ms
SolidStart	2352.00 ms
TanStack Start	2456.00 ms
Nuxt	2692.00 ms
React Router	3437.00 ms
Next.js	4730.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
Pracht	39.00 ms
Nuxt	50.00 ms
SvelteKit	55.00 ms
React Router	73.00 ms
SolidStart	78.00 ms
TanStack Start	86.00 ms
Next.js	650.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	35.00 ms
Baseline HTML	36.00 ms
Pracht	80.00 ms
Nuxt	102.00 ms
SvelteKit	127.00 ms
React Router	147.00 ms
SolidStart	175.00 ms
TanStack Start	175.00 ms
Next.js	2271.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	68.00 ms
Baseline HTML	82.00 ms
Pracht	157.00 ms
SolidStart	173.00 ms
Nuxt	181.00 ms
SvelteKit	194.00 ms
TanStack Start	226.00 ms
React Router	285.00 ms
Next.js	2671.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	16.00 ms
Baseline HTML	17.00 ms
Pracht	38.00 ms
SvelteKit	45.00 ms
Nuxt	49.00 ms
SolidStart	62.00 ms
TanStack Start	69.00 ms
React Router	72.00 ms
Next.js	646.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	77.00 ms
Nuxt	96.00 ms
SvelteKit	101.00 ms
SolidStart	109.00 ms
TanStack Start	139.00 ms
React Router	145.00 ms
Next.js	1061.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	65.00 ms
Baseline HTML	71.00 ms
SolidStart	131.00 ms
SvelteKit	152.00 ms
Pracht	153.00 ms
TanStack Start	158.00 ms
Nuxt	169.00 ms
React Router	262.00 ms
Next.js	1056.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	42	5	2007ms	4734ms	4644ms	1,166
Nuxt	168	5	518ms	2855ms	3767ms	5,540
Pracht	397	50	92ms	272ms	2480ms	12,102
React Router	169.8	10	339ms	1716ms	3883ms	5,649
TanStack Start	156	50	695ms	3292ms	3460ms	5,247

P99 Latency

P99 Latency at 25 Connections

P99 Latency at 25 Connections chart

P99 Latency at 25 Connections data

Framework	Milliseconds
Pracht	92.00 ms
React Router	339.00 ms
Nuxt	518.00 ms
TanStack Start	695.00 ms
Next.js	2007.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	272.00 ms
React Router	1716.00 ms
Nuxt	2855.00 ms
TanStack Start	3292.00 ms
Next.js	4734.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	2480.00 ms
TanStack Start	3460.00 ms
Nuxt	3767.00 ms
React Router	3883.00 ms
Next.js	4644.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	74.00 ms
Nuxt	157.00 ms
React Router	162.00 ms
TanStack Start	197.00 ms
Next.js	697.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	128.00 ms
React Router	296.00 ms
Nuxt	304.00 ms
TanStack Start	420.00 ms
Next.js	2380.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	256.00 ms
Nuxt	332.00 ms
TanStack Start	368.00 ms
React Router	407.00 ms
Next.js	2729.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
React Router	146.00 ms
Nuxt	149.00 ms
TanStack Start	162.00 ms
Next.js	683.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	123.00 ms
TanStack Start	273.00 ms
React Router	289.00 ms
Nuxt	294.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
Pracht	241.00 ms
TanStack Start	277.00 ms
Nuxt	309.00 ms
React Router	378.00 ms
Next.js	1077.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.