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.31ms	2.34ms	2.06ms	0.27ms	0ms
Next.js	338.4ms	338.46ms	19.78ms	1.61ms	6.25ms	11.92ms
Nuxt	156ms	156.1ms	11.52ms	0.86ms	1.82ms	8.84ms
Pracht	85.8ms	85.75ms	15.71ms	0.76ms	2.68ms	12.28ms
React Router	164.4ms	164.48ms	18.79ms	1.49ms	2.34ms	14.96ms
SolidStart	100.2ms	100.24ms	16.97ms	1.04ms	3.07ms	12.86ms
SvelteKit	107.2ms	107.2ms	17.36ms	0.79ms	2.81ms	13.77ms
TanStack Start	121.8ms	121.91ms	19.66ms	1.28ms	2.89ms	15.48ms

First Paint (ms)

First Paint (ms) chart

First Paint (ms) data

Framework	Milliseconds
Pracht	85.80 ms
Astro	87.40 ms
SolidStart	100.20 ms
SvelteKit	107.20 ms
TanStack Start	121.80 ms
Nuxt	156.00 ms
React Router	164.40 ms
Next.js	338.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
Pracht	85.75 ms
Astro	87.31 ms
SolidStart	100.24 ms
SvelteKit	107.20 ms
TanStack Start	121.91 ms
Nuxt	156.10 ms
React Router	164.48 ms
Next.js	338.46 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.16 ms

Median: 17.36 ms

2.34 ms

11.52 ms

15.71 ms

16.97 ms

17.36 ms

18.79 ms

19.66 ms

19.78 ms

Interaction Breakdown data

Framework or version	Interaction latency	Input delay	Processing duration	Presentation delay
Astro	2.34 ms	2.06 ms	0.27 ms	0.00 ms
Nuxt	11.52 ms	0.86 ms	1.82 ms	8.84 ms
Pracht	15.71 ms	0.76 ms	2.68 ms	12.28 ms
SolidStart	16.97 ms	1.04 ms	3.07 ms	12.86 ms
SvelteKit	17.36 ms	0.79 ms	2.81 ms	13.77 ms
React Router	18.79 ms	1.49 ms	2.34 ms	14.96 ms
TanStack Start	19.66 ms	1.28 ms	2.89 ms	15.48 ms
Next.js	19.78 ms	1.61 ms	6.25 ms	11.92 ms

Server Side Rendered Tests

Methodology: Server Side Rendered Tests.

Framework	First Paint	FCP	Interaction Latency	Input Delay	Processing Duration	Presentation Delay
Astro	58.4ms	58.31ms	1.31ms	0.62ms	0.69ms	0ms
Next.js	375.6ms	375.42ms	21.05ms	1.53ms	8.18ms	11.34ms
Nuxt	85.6ms	85.59ms	12.21ms	0.91ms	1.19ms	10.11ms
Pracht	84ms	84.06ms	15.98ms	1.18ms	2ms	12.8ms
React Router	112.8ms	112.79ms	19.17ms	1.54ms	3.4ms	14.23ms
SolidStart	78ms	77.75ms	15.09ms	0.85ms	2.3ms	11.94ms
SvelteKit	84.4ms	84.33ms	14.55ms	0.82ms	1.87ms	11.85ms
TanStack Start	90.2ms	90.39ms	17.18ms	1.83ms	4.07ms	11.28ms

First Paint (ms)

First Paint (ms) chart

First Paint (ms) data

Framework	Milliseconds
Astro	58.40 ms
SolidStart	78.00 ms
Pracht	84.00 ms
SvelteKit	84.40 ms
Nuxt	85.60 ms
TanStack Start	90.20 ms
React Router	112.80 ms
Next.js	375.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	58.31 ms
SolidStart	77.75 ms
Pracht	84.06 ms
SvelteKit	84.33 ms
Nuxt	85.59 ms
TanStack Start	90.39 ms
React Router	112.79 ms
Next.js	375.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: 15.54 ms

Median: 15.09 ms

1.31 ms

12.21 ms

14.55 ms

15.09 ms

15.98 ms

17.18 ms

19.17 ms

21.05 ms

Interaction Breakdown data

Framework or version	Interaction latency	Input delay	Processing duration	Presentation delay
Astro	1.31 ms	0.62 ms	0.69 ms	0.00 ms
Nuxt	12.21 ms	0.91 ms	1.19 ms	10.11 ms
SvelteKit	14.55 ms	0.82 ms	1.87 ms	11.85 ms
SolidStart	15.09 ms	0.85 ms	2.30 ms	11.94 ms
Pracht	15.98 ms	1.18 ms	2.00 ms	12.80 ms
TanStack Start	17.18 ms	1.83 ms	4.07 ms	11.28 ms
React Router	19.17 ms	1.54 ms	3.40 ms	14.23 ms
Next.js	21.05 ms	1.53 ms	8.18 ms	11.34 ms

Server Side Throughput Tests

Methodology: Server Side Throughput Tests.

Framework	Ops/sec	Median Latency	Body Size	Duplication
Baseline HTML	843	1.199ms	96.83kb	1x
Astro	723	1.33ms	96.89kb	1x
Next.js	130	7.502ms	204.56kb	2x
Nuxt	400	2.421ms	201.73kb	2x
Pracht	599	1.606ms	187.02kb	2x
React Router	346	2.809ms	216.98kb	2x
SolidStart	388	2.455ms	224.26kb	2x
SvelteKit	462	2.119ms	184.29kb	2x
TanStack Start	377	2.623ms	192.53kb	2x

Ops/sec

Ops/sec chart

Ops/sec data

Framework	Operations per second
Baseline HTML	843
Astro	723
Pracht	599
SvelteKit	462
Nuxt	400
SolidStart	388
TanStack Start	377
React Router	346
Next.js	130

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.29 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.20 ms
Astro	1.33 ms
Pracht	1.61 ms
SvelteKit	2.12 ms
Nuxt	2.42 ms
SolidStart	2.46 ms
TanStack Start	2.62 ms
React Router	2.81 ms
Next.js	7.50 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,818.6	100	17ms	33ms	88ms	53,111
Astro	1,582.6	50	25ms	48ms	102ms	46,944
Next.js	56.2	5	1158ms	4206ms	4458ms	1,670
Nuxt	539.8	200	70ms	328ms	2663ms	17,671
Pracht	652.4	25	58ms	121ms	1128ms	20,322
React Router	347.8	25	98ms	455ms	3257ms	11,483
SolidStart	567.8	25	93ms	332ms	2024ms	18,641
SvelteKit	601.8	25	73ms	234ms	2080ms	19,378
TanStack Start	408	5	120ms	737ms	2603ms	13,454

P99 Latency

P99 Latency at 25 Connections

P99 Latency at 25 Connections chart

P99 Latency at 25 Connections data

Framework	Milliseconds
Baseline HTML	17.00 ms
Astro	25.00 ms
Pracht	58.00 ms
Nuxt	70.00 ms
SvelteKit	73.00 ms
SolidStart	93.00 ms
React Router	98.00 ms
TanStack Start	120.00 ms
Next.js	1158.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	33.00 ms
Astro	48.00 ms
Pracht	121.00 ms
SvelteKit	234.00 ms
Nuxt	328.00 ms
SolidStart	332.00 ms
React Router	455.00 ms
TanStack Start	737.00 ms
Next.js	4206.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	88.00 ms
Astro	102.00 ms
Pracht	1128.00 ms
SolidStart	2024.00 ms
SvelteKit	2080.00 ms
TanStack Start	2603.00 ms
Nuxt	2663.00 ms
React Router	3257.00 ms
Next.js	4458.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	39.00 ms
Nuxt	47.00 ms
SvelteKit	53.00 ms
SolidStart	62.00 ms
React Router	72.00 ms
TanStack Start	80.00 ms
Next.js	498.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	30.00 ms
Astro	32.00 ms
Pracht	80.00 ms
Nuxt	95.00 ms
SvelteKit	117.00 ms
SolidStart	132.00 ms
React Router	144.00 ms
TanStack Start	165.00 ms
Next.js	1842.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	70.00 ms
SolidStart	159.00 ms
Pracht	162.00 ms
Nuxt	181.00 ms
SvelteKit	191.00 ms
TanStack Start	227.00 ms
React Router	283.00 ms
Next.js	2139.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	14.00 ms
Astro	16.00 ms
Pracht	38.00 ms
SvelteKit	41.00 ms
Nuxt	46.00 ms
SolidStart	53.00 ms
TanStack Start	62.00 ms
React Router	71.00 ms
Next.js	483.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	29.00 ms
Astro	31.00 ms
Pracht	79.00 ms
SolidStart	89.00 ms
Nuxt	90.00 ms
SvelteKit	100.00 ms
TanStack Start	133.00 ms
React Router	142.00 ms
Next.js	951.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	63.00 ms
SolidStart	122.00 ms
SvelteKit	136.00 ms
Pracht	157.00 ms
Nuxt	165.00 ms
TanStack Start	171.00 ms
React Router	263.00 ms
Next.js	949.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	48.4	5	1375ms	4498ms	4741ms	1,476
Nuxt	172.2	10	528ms	2815ms	3787ms	5,645
Pracht	334.4	25	92ms	593ms	3571ms	10,809
React Router	179.2	25	271ms	1662ms	3881ms	5,961
TanStack Start	247.6	50	178ms	1743ms	2882ms	8,207

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
TanStack Start	178.00 ms
React Router	271.00 ms
Nuxt	528.00 ms
Next.js	1375.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	593.00 ms
React Router	1662.00 ms
TanStack Start	1743.00 ms
Nuxt	2815.00 ms
Next.js	4498.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
TanStack Start	2882.00 ms
Pracht	3571.00 ms
Nuxt	3787.00 ms
React Router	3881.00 ms
Next.js	4741.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	82.00 ms
TanStack Start	126.00 ms
React Router	143.00 ms
Nuxt	152.00 ms
Next.js	564.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	159.00 ms
TanStack Start	258.00 ms
React Router	280.00 ms
Nuxt	304.00 ms
Next.js	2257.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
TanStack Start	291.00 ms
Pracht	298.00 ms
Nuxt	328.00 ms
React Router	404.00 ms
Next.js	2343.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	77.00 ms
TanStack Start	102.00 ms
React Router	137.00 ms
Nuxt	143.00 ms
Next.js	516.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	156.00 ms
TanStack Start	202.00 ms
React Router	274.00 ms
Nuxt	297.00 ms
Next.js	991.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	234.00 ms
Pracht	268.00 ms
Nuxt	296.00 ms
React Router	358.00 ms
Next.js	1011.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.