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.6ms	92.68ms	2.08ms	1.75ms	0.33ms	0ms
Next.js	339.6ms	339.47ms	19.21ms	1.4ms	4.63ms	13.18ms
Nuxt	177.2ms	177.13ms	10.67ms	0.85ms	1.7ms	8.12ms
Pracht	95.4ms	95.05ms	19.17ms	1.37ms	3.03ms	14.76ms
React Router	171.4ms	171.47ms	18.83ms	1.65ms	3.07ms	14.12ms
SolidStart	81ms	80.86ms	11.84ms	0.84ms	2.26ms	8.73ms
SvelteKit	106.2ms	106.25ms	17.68ms	0.78ms	1.74ms	15.16ms
TanStack Start	136.2ms	136.29ms	19.75ms	1.37ms	3.08ms	15.3ms

First Paint (ms)

First Paint (ms) chart

First Paint (ms) data

Framework	Milliseconds
SolidStart	81.00 ms
Astro	92.60 ms
Pracht	95.40 ms
SvelteKit	106.20 ms
TanStack Start	136.20 ms
React Router	171.40 ms
Nuxt	177.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
SolidStart	80.86 ms
Astro	92.68 ms
Pracht	95.05 ms
SvelteKit	106.25 ms
TanStack Start	136.29 ms
React Router	171.47 ms
Nuxt	177.13 ms
Next.js	339.47 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: 18.25 ms

Median: 17.68 ms

2.08 ms

10.67 ms

11.84 ms

17.68 ms

18.83 ms

19.17 ms

19.21 ms

19.75 ms

Interaction Breakdown data

Framework or version	Interaction latency	Input delay	Processing duration	Presentation delay
Astro	2.08 ms	1.75 ms	0.33 ms	0.00 ms
Nuxt	10.67 ms	0.85 ms	1.70 ms	8.12 ms
SolidStart	11.84 ms	0.84 ms	2.26 ms	8.73 ms
SvelteKit	17.68 ms	0.78 ms	1.74 ms	15.16 ms
React Router	18.83 ms	1.65 ms	3.07 ms	14.12 ms
Pracht	19.17 ms	1.37 ms	3.03 ms	14.76 ms
Next.js	19.21 ms	1.40 ms	4.63 ms	13.18 ms
TanStack Start	19.75 ms	1.37 ms	3.08 ms	15.30 ms

Server Side Rendered Tests

Methodology: Server Side Rendered Tests.

Framework	First Paint	FCP	Interaction Latency	Input Delay	Processing Duration	Presentation Delay
Astro	59.2ms	59.23ms	0.72ms	0.49ms	0.22ms	0ms
Next.js	377.8ms	377.83ms	18.33ms	1.44ms	6.96ms	9.93ms
Nuxt	92.6ms	92.79ms	9.36ms	0.89ms	1.26ms	7.21ms
Pracht	86.4ms	86.42ms	17.05ms	0.79ms	2.22ms	14.04ms
React Router	120.2ms	120.19ms	21.29ms	1.58ms	3.2ms	16.51ms
SolidStart	82.6ms	82.6ms	14.88ms	0.88ms	2.51ms	11.48ms
SvelteKit	80.6ms	80.43ms	11.86ms	0.82ms	2.46ms	8.58ms
TanStack Start	91.6ms	91.64ms	17.79ms	1.45ms	4.6ms	11.73ms

First Paint (ms)

First Paint (ms) chart

First Paint (ms) data

Framework	Milliseconds
Astro	59.20 ms
SvelteKit	80.60 ms
SolidStart	82.60 ms
Pracht	86.40 ms
TanStack Start	91.60 ms
Nuxt	92.60 ms
React Router	120.20 ms
Next.js	377.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	59.23 ms
SvelteKit	80.43 ms
SolidStart	82.60 ms
Pracht	86.42 ms
TanStack Start	91.64 ms
Nuxt	92.79 ms
React Router	120.19 ms
Next.js	377.83 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.96 ms

Median: 14.88 ms

0.72 ms

9.36 ms

11.86 ms

14.88 ms

17.05 ms

17.79 ms

18.33 ms

21.29 ms

Interaction Breakdown data

Framework or version	Interaction latency	Input delay	Processing duration	Presentation delay
Astro	0.72 ms	0.49 ms	0.22 ms	0.00 ms
Nuxt	9.36 ms	0.89 ms	1.26 ms	7.21 ms
SvelteKit	11.86 ms	0.82 ms	2.46 ms	8.58 ms
SolidStart	14.88 ms	0.88 ms	2.51 ms	11.48 ms
Pracht	17.05 ms	0.79 ms	2.22 ms	14.04 ms
TanStack Start	17.79 ms	1.45 ms	4.60 ms	11.73 ms
Next.js	18.33 ms	1.44 ms	6.96 ms	9.93 ms
React Router	21.29 ms	1.58 ms	3.20 ms	16.51 ms

Server Side Throughput Tests

Methodology: Server Side Throughput Tests.

Framework	Ops/sec	Median Latency	Body Size	Duplication
Baseline HTML	837	1.209ms	96.83kb	1x
Astro	725	1.324ms	96.89kb	1x
Next.js	128	7.54ms	204.56kb	2x
Nuxt	403	2.406ms	201.73kb	2x
Pracht	581	1.652ms	187.02kb	2x
React Router	346	2.823ms	216.98kb	2x
SolidStart	392	2.433ms	224.26kb	2x
SvelteKit	458	2.143ms	184.3kb	2x
TanStack Start	362	2.697ms	192.53kb	2x

Ops/sec

Ops/sec chart

Ops/sec data

Framework	Operations per second
Baseline HTML	837
Astro	725
Pracht	581
SvelteKit	458
Nuxt	403
SolidStart	392
TanStack Start	362
React Router	346
Next.js	128

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.14 ms
Nuxt	2.41 ms
SolidStart	2.43 ms
TanStack Start	2.70 ms
React Router	2.82 ms
Next.js	7.54 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,673	100	22ms	47ms	104ms	48,458
Astro	1,615	50	25ms	44ms	97ms	47,344
Next.js	51.4	5	1242ms	4161ms	4464ms	1,597
Nuxt	539.4	50	68ms	307ms	2625ms	17,614
Pracht	710.2	25	38ms	113ms	984ms	22,100
React Router	349.6	100	104ms	429ms	3268ms	11,631
SolidStart	554.4	10	95ms	312ms	2082ms	18,074
SvelteKit	581.6	25	78ms	260ms	1921ms	18,257
TanStack Start	404.6	50	107ms	598ms	2373ms	13,434

P99 Latency

P99 Latency at 25 Connections

P99 Latency at 25 Connections chart

P99 Latency at 25 Connections data

Framework	Milliseconds
Baseline HTML	22.00 ms
Astro	25.00 ms
Pracht	38.00 ms
Nuxt	68.00 ms
SvelteKit	78.00 ms
SolidStart	95.00 ms
React Router	104.00 ms
TanStack Start	107.00 ms
Next.js	1242.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	44.00 ms
Baseline HTML	47.00 ms
Pracht	113.00 ms
SvelteKit	260.00 ms
Nuxt	307.00 ms
SolidStart	312.00 ms
React Router	429.00 ms
TanStack Start	598.00 ms
Next.js	4161.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	97.00 ms
Baseline HTML	104.00 ms
Pracht	984.00 ms
SvelteKit	1921.00 ms
SolidStart	2082.00 ms
TanStack Start	2373.00 ms
Nuxt	2625.00 ms
React Router	3268.00 ms
Next.js	4464.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	17.00 ms
Baseline HTML	18.00 ms
Pracht	36.00 ms
Nuxt	47.00 ms
SvelteKit	56.00 ms
SolidStart	65.00 ms
React Router	72.00 ms
TanStack Start	79.00 ms
Next.js	525.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	31.00 ms
Baseline HTML	33.00 ms
Pracht	73.00 ms
Nuxt	92.00 ms
SvelteKit	128.00 ms
SolidStart	143.00 ms
React Router	145.00 ms
TanStack Start	169.00 ms
Next.js	1777.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	63.00 ms
Baseline HTML	72.00 ms
Pracht	147.00 ms
SolidStart	176.00 ms
Nuxt	185.00 ms
SvelteKit	193.00 ms
TanStack Start	231.00 ms
React Router	271.00 ms
Next.js	2229.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	35.00 ms
SvelteKit	43.00 ms
Nuxt	46.00 ms
SolidStart	56.00 ms
TanStack Start	64.00 ms
React Router	71.00 ms
Next.js	504.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	31.00 ms
Baseline HTML	32.00 ms
Pracht	72.00 ms
SolidStart	87.00 ms
Nuxt	91.00 ms
SvelteKit	105.00 ms
TanStack Start	125.00 ms
React Router	144.00 ms
Next.js	959.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	62.00 ms
Baseline HTML	62.00 ms
SolidStart	121.00 ms
Pracht	144.00 ms
SvelteKit	155.00 ms
Nuxt	165.00 ms
TanStack Start	190.00 ms
React Router	252.00 ms
Next.js	971.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	49.8	5	1322ms	4481ms	4854ms	1,496
Nuxt	174.4	5	514ms	3062ms	3848ms	5,634
Pracht	392.4	25	85ms	265ms	2624ms	12,187
React Router	172.4	50	271ms	1614ms	3955ms	5,749
TanStack Start	254.8	25	196ms	1647ms	2824ms	8,600

P99 Latency

P99 Latency at 25 Connections

P99 Latency at 25 Connections chart

P99 Latency at 25 Connections data

Framework	Milliseconds
Pracht	85.00 ms
TanStack Start	196.00 ms
React Router	271.00 ms
Nuxt	514.00 ms
Next.js	1322.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	265.00 ms
React Router	1614.00 ms
TanStack Start	1647.00 ms
Nuxt	3062.00 ms
Next.js	4481.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	2624.00 ms
TanStack Start	2824.00 ms
Nuxt	3848.00 ms
React Router	3955.00 ms
Next.js	4854.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	64.00 ms
TanStack Start	114.00 ms
Nuxt	150.00 ms
React Router	152.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
Pracht	140.00 ms
TanStack Start	254.00 ms
React Router	290.00 ms
Nuxt	320.00 ms
Next.js	2116.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	253.00 ms
Nuxt	327.00 ms
TanStack Start	340.00 ms
React Router	403.00 ms
Next.js	2466.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	63.00 ms
TanStack Start	98.00 ms
Nuxt	141.00 ms
React Router	144.00 ms
Next.js	501.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	200.00 ms
React Router	285.00 ms
Nuxt	302.00 ms
Next.js	1025.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	243.00 ms
TanStack Start	247.00 ms
Nuxt	297.00 ms
React Router	369.00 ms
Next.js	1034.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.