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	92.2ms	92.35ms	2.18ms	1.88ms	0.29ms	0ms
Next.js	339.6ms	339.57ms	16.02ms	1.36ms	4.52ms	10.14ms
Nuxt	145ms	144.97ms	12.07ms	1.21ms	1.21ms	9.65ms
Pracht	115.8ms	115.95ms	19.59ms	0.78ms	2.22ms	16.6ms
React Router	156.2ms	156.25ms	17.65ms	1.49ms	3.27ms	12.88ms
SolidStart	93ms	92.97ms	17ms	0.86ms	2.56ms	13.57ms
SvelteKit	108.2ms	108.26ms	16.91ms	0.75ms	1.73ms	14.43ms
TanStack Start	132.4ms	132.42ms	21.68ms	1.44ms	3.57ms	16.67ms

First Paint (ms)

First Paint (ms) chart

First Paint (ms) data

Framework	Milliseconds
Astro	92.20 ms
SolidStart	93.00 ms
SvelteKit	108.20 ms
Pracht	115.80 ms
TanStack Start	132.40 ms
Nuxt	145.00 ms
React Router	156.20 ms
Next.js	339.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	92.35 ms
SolidStart	92.97 ms
SvelteKit	108.26 ms
Pracht	115.95 ms
TanStack Start	132.42 ms
Nuxt	144.97 ms
React Router	156.25 ms
Next.js	339.57 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.95 ms

Median: 16.91 ms

2.18 ms

12.07 ms

16.02 ms

16.91 ms

17.00 ms

17.65 ms

19.59 ms

21.68 ms

Interaction Breakdown data

Framework or version	Interaction latency	Input delay	Processing duration	Presentation delay
Astro	2.18 ms	1.88 ms	0.29 ms	0.00 ms
Nuxt	12.07 ms	1.21 ms	1.21 ms	9.65 ms
Next.js	16.02 ms	1.36 ms	4.52 ms	10.14 ms
SvelteKit	16.91 ms	0.75 ms	1.73 ms	14.43 ms
SolidStart	17.00 ms	0.86 ms	2.56 ms	13.57 ms
React Router	17.65 ms	1.49 ms	3.27 ms	12.88 ms
Pracht	19.59 ms	0.78 ms	2.22 ms	16.60 ms
TanStack Start	21.68 ms	1.44 ms	3.57 ms	16.67 ms

Server Side Rendered Tests

Methodology: Server Side Rendered Tests.

Framework	First Paint	FCP	Interaction Latency	Input Delay	Processing Duration	Presentation Delay
Astro	58.2ms	58.3ms	3.61ms	0.61ms	0.38ms	2.63ms
Next.js	374.2ms	374.25ms	15.94ms	1.25ms	6.11ms	8.58ms
Nuxt	87.8ms	87.88ms	9.81ms	0.83ms	1.55ms	7.42ms
Pracht	83.8ms	83.74ms	18.41ms	0.92ms	2.15ms	15.34ms
React Router	101.8ms	102.06ms	15.88ms	1.53ms	3.11ms	11.24ms
SolidStart	72.2ms	72.21ms	13.67ms	0.84ms	2.42ms	10.41ms
SvelteKit	73ms	73.16ms	15.08ms	0.8ms	2.24ms	12.04ms
TanStack Start	87ms	87.07ms	19.58ms	1.28ms	3.57ms	14.74ms

First Paint (ms)

First Paint (ms) chart

First Paint (ms) data

Framework	Milliseconds
Astro	58.20 ms
SolidStart	72.20 ms
SvelteKit	73.00 ms
Pracht	83.80 ms
TanStack Start	87.00 ms
Nuxt	87.80 ms
React Router	101.80 ms
Next.js	374.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	58.30 ms
SolidStart	72.21 ms
SvelteKit	73.16 ms
Pracht	83.74 ms
TanStack Start	87.07 ms
Nuxt	87.88 ms
React Router	102.06 ms
Next.js	374.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: 15.48 ms

Median: 15.08 ms

3.61 ms

9.81 ms

13.67 ms

15.08 ms

15.88 ms

15.94 ms

18.41 ms

19.58 ms

Interaction Breakdown data

Framework or version	Interaction latency	Input delay	Processing duration	Presentation delay
Astro	3.61 ms	0.61 ms	0.38 ms	2.63 ms
Nuxt	9.81 ms	0.83 ms	1.55 ms	7.42 ms
SolidStart	13.67 ms	0.84 ms	2.42 ms	10.41 ms
SvelteKit	15.08 ms	0.80 ms	2.24 ms	12.04 ms
React Router	15.88 ms	1.53 ms	3.11 ms	11.24 ms
Next.js	15.94 ms	1.25 ms	6.11 ms	8.58 ms
Pracht	18.41 ms	0.92 ms	2.15 ms	15.34 ms
TanStack Start	19.58 ms	1.28 ms	3.57 ms	14.74 ms

Server Side Throughput Tests

Methodology: Server Side Throughput Tests.

Framework	Ops/sec	Median Latency	Body Size	Duplication
Baseline HTML	837	1.208ms	96.83kb	1x
Astro	734	1.328ms	96.89kb	1x
Next.js	136	7.32ms	204.56kb	2x
Nuxt	366	2.667ms	201.73kb	2x
Pracht	572	1.672ms	187.02kb	2x
React Router	341	2.863ms	216.98kb	2x
SolidStart	398	2.399ms	224.26kb	2x
SvelteKit	457	2.142ms	184.29kb	2x
TanStack Start	365	2.69ms	192.48kb	2x

Ops/sec

Ops/sec chart

Ops/sec data

Framework	Operations per second
Baseline HTML	837
Astro	734
Pracht	572
SvelteKit	457
SolidStart	398
Nuxt	366
TanStack Start	365
React Router	341
Next.js	136

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.48 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.33 ms
Pracht	1.67 ms
SvelteKit	2.14 ms
SolidStart	2.40 ms
Nuxt	2.67 ms
TanStack Start	2.69 ms
React Router	2.86 ms
Next.js	7.32 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,808.8	200	17ms	40ms	100ms	53,116
Astro	1,626.4	50	23ms	46ms	99ms	48,090
Next.js	53.6	5	1224ms	4238ms	4503ms	1,641
Nuxt	542	10	69ms	316ms	2556ms	17,753
Pracht	669.8	25	40ms	115ms	1289ms	20,466
React Router	343.2	10	85ms	477ms	3455ms	11,272
SolidStart	571.4	10	93ms	256ms	2035ms	18,535
SvelteKit	600.6	25	69ms	176ms	1945ms	19,138
TanStack Start	406	50	120ms	681ms	2654ms	13,436

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	23.00 ms
Pracht	40.00 ms
Nuxt	69.00 ms
SvelteKit	69.00 ms
React Router	85.00 ms
SolidStart	93.00 ms
TanStack Start	120.00 ms
Next.js	1224.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	46.00 ms
Pracht	115.00 ms
SvelteKit	176.00 ms
SolidStart	256.00 ms
Nuxt	316.00 ms
React Router	477.00 ms
TanStack Start	681.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
Astro	99.00 ms
Baseline HTML	100.00 ms
Pracht	1289.00 ms
SvelteKit	1945.00 ms
SolidStart	2035.00 ms
Nuxt	2556.00 ms
TanStack Start	2654.00 ms
React Router	3455.00 ms
Next.js	4503.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	38.00 ms
Nuxt	46.00 ms
SvelteKit	53.00 ms
SolidStart	61.00 ms
React Router	74.00 ms
TanStack Start	82.00 ms
Next.js	520.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	31.00 ms
Pracht	83.00 ms
Nuxt	100.00 ms
SvelteKit	120.00 ms
SolidStart	140.00 ms
React Router	154.00 ms
TanStack Start	176.00 ms
Next.js	1782.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	62.00 ms
Baseline HTML	63.00 ms
Pracht	161.00 ms
SolidStart	164.00 ms
Nuxt	181.00 ms
SvelteKit	200.00 ms
TanStack Start	233.00 ms
React Router	283.00 ms
Next.js	2316.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	37.00 ms
SvelteKit	41.00 ms
Nuxt	46.00 ms
SolidStart	54.00 ms
TanStack Start	64.00 ms
React Router	73.00 ms
Next.js	485.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	81.00 ms
SolidStart	86.00 ms
Nuxt	91.00 ms
SvelteKit	95.00 ms
TanStack Start	135.00 ms
React Router	145.00 ms
Next.js	970.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	56.00 ms
Astro	61.00 ms
SolidStart	122.00 ms
SvelteKit	136.00 ms
Pracht	159.00 ms
Nuxt	165.00 ms
TanStack Start	171.00 ms
React Router	260.00 ms
Next.js	944.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	50.4	5	1297ms	4602ms	4742ms	1,497
Nuxt	179.8	10	501ms	2694ms	3759ms	5,844
Pracht	396.6	25	93ms	350ms	2691ms	12,383
React Router	177.2	10	304ms	1793ms	3919ms	5,847
TanStack Start	258.61	25	213ms	1477ms	3188ms	8,644

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
TanStack Start	213.00 ms
React Router	304.00 ms
Nuxt	501.00 ms
Next.js	1297.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	350.00 ms
TanStack Start	1477.00 ms
React Router	1793.00 ms
Nuxt	2694.00 ms
Next.js	4602.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	2691.00 ms
TanStack Start	3188.00 ms
Nuxt	3759.00 ms
React Router	3919.00 ms
Next.js	4742.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	63.00 ms
TanStack Start	117.00 ms
Nuxt	147.00 ms
React Router	151.00 ms
Next.js	536.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	131.00 ms
TanStack Start	267.00 ms
React Router	289.00 ms
Nuxt	330.00 ms
Next.js	2223.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	247.00 ms
TanStack Start	294.00 ms
Nuxt	318.00 ms
React Router	401.00 ms
Next.js	2324.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	62.00 ms
TanStack Start	99.00 ms
Nuxt	137.00 ms
React Router	139.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	124.00 ms
TanStack Start	191.00 ms
React Router	283.00 ms
Nuxt	290.00 ms
Next.js	1060.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	216.00 ms
Pracht	235.00 ms
Nuxt	304.00 ms
React Router	371.00 ms
Next.js	1061.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.