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	101.2ms	101.33ms	2.5ms	2.2ms	0.3ms	0ms
Next.js	337ms	337.09ms	21.09ms	1.28ms	8.31ms	11.49ms
Nuxt	173.6ms	173.65ms	9.98ms	0.48ms	1.93ms	7.56ms
React Router	185.4ms	185.16ms	20.34ms	1.81ms	2.49ms	16.04ms
SolidStart	107.6ms	107.6ms	12.91ms	1.46ms	2.22ms	9.23ms
SvelteKit	112.6ms	112.83ms	14.6ms	1.49ms	3.01ms	10.09ms
TanStack Start	159.4ms	159.33ms	31.59ms	2.11ms	18.24ms	11.24ms

First Paint (ms)

First Paint (ms) chart

First Paint (ms) data

Framework	Milliseconds
Astro	101.20 ms
SolidStart	107.60 ms
SvelteKit	112.60 ms
TanStack Start	159.40 ms
Nuxt	173.60 ms
React Router	185.40 ms
Next.js	337.00 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	101.33 ms
SolidStart	107.60 ms
SvelteKit	112.83 ms
TanStack Start	159.33 ms
Nuxt	173.65 ms
React Router	185.16 ms
Next.js	337.09 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: 14.60 ms

Median: 14.60 ms

2.50 ms

9.98 ms

12.91 ms

14.60 ms

20.34 ms

21.09 ms

31.59 ms

Interaction Breakdown data

Framework or version	Interaction latency	Input delay	Processing duration	Presentation delay
Astro	2.50 ms	2.20 ms	0.30 ms	0.00 ms
Nuxt	9.98 ms	0.48 ms	1.93 ms	7.56 ms
SolidStart	12.91 ms	1.46 ms	2.22 ms	9.23 ms
SvelteKit	14.60 ms	1.49 ms	3.01 ms	10.09 ms
React Router	20.34 ms	1.81 ms	2.49 ms	16.04 ms
Next.js	21.09 ms	1.28 ms	8.31 ms	11.49 ms
TanStack Start	31.59 ms	2.11 ms	18.24 ms	11.24 ms

Server Side Rendered Tests

Methodology: Server Side Rendered Tests.

Framework	First Paint	FCP	Interaction Latency	Input Delay	Processing Duration	Presentation Delay
Astro	66ms	66.11ms	4.27ms	0.64ms	0.92ms	2.7ms
Next.js	135.6ms	135.89ms	18.58ms	1.24ms	8.35ms	9ms
Nuxt	109ms	109.15ms	12.09ms	1ms	1.91ms	9.18ms
React Router	121.8ms	121.89ms	17.3ms	3.02ms	3.4ms	10.88ms
SolidStart	91.2ms	91.24ms	15.54ms	0.9ms	2.99ms	11.65ms
SvelteKit	106.2ms	106.02ms	19.35ms	0.69ms	2.63ms	16.03ms
TanStack Start	117.2ms	117.27ms	27.77ms	1.61ms	16.77ms	9.39ms

First Paint (ms)

First Paint (ms) chart

First Paint (ms) data

Framework	Milliseconds
Astro	66.00 ms
SolidStart	91.20 ms
SvelteKit	106.20 ms
Nuxt	109.00 ms
TanStack Start	117.20 ms
React Router	121.80 ms
Next.js	135.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	66.11 ms
SolidStart	91.24 ms
SvelteKit	106.02 ms
Nuxt	109.15 ms
TanStack Start	117.27 ms
React Router	121.89 ms
Next.js	135.89 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.30 ms

Median: 17.30 ms

4.27 ms

12.09 ms

15.54 ms

17.30 ms

18.58 ms

19.35 ms

27.77 ms

Interaction Breakdown data

Framework or version	Interaction latency	Input delay	Processing duration	Presentation delay
Astro	4.27 ms	0.64 ms	0.92 ms	2.70 ms
Nuxt	12.09 ms	1.00 ms	1.91 ms	9.18 ms
SolidStart	15.54 ms	0.90 ms	2.99 ms	11.65 ms
React Router	17.30 ms	3.02 ms	3.40 ms	10.88 ms
Next.js	18.58 ms	1.24 ms	8.35 ms	9.00 ms
SvelteKit	19.35 ms	0.69 ms	2.63 ms	16.03 ms
TanStack Start	27.77 ms	1.61 ms	16.77 ms	9.39 ms

Server Side Throughput Tests

Methodology: Server Side Throughput Tests.

Framework	Ops/sec	Median Latency	Body Size	Duplication
Baseline HTML	848	1.199ms	96.83kb	1x
Astro	668	1.435ms	96.89kb	1x
Next.js	218	4.763ms	199.57kb	2x
Nuxt	351	2.775ms	201.57kb	2x
React Router	351	2.833ms	216.9kb	2x
SolidStart	439	2.199ms	224.17kb	2x
SvelteKit	463	2.092ms	183.54kb	2x
TanStack Start	321	3.082ms	193.62kb	2x

Ops/sec

Ops/sec chart

Ops/sec data

Framework	Operations per second
Baseline HTML	848
Astro	668
SvelteKit	463
SolidStart	439
Nuxt	351
React Router	351
TanStack Start	321
Next.js	218

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	183.54 KB
TanStack Start	193.62 KB
Next.js	199.57 KB
Nuxt	201.57 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.44 ms
SvelteKit	2.09 ms
SolidStart	2.20 ms
Nuxt	2.77 ms
React Router	2.83 ms
TanStack Start	3.08 ms
Next.js	4.76 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,690.6	200	19ms	40ms	108ms	49,901
Astro	1,217.6	50	32ms	63ms	240ms	37,347
Next.js	45	1	1822ms	4775ms	4693ms	1,268
Nuxt	479.6	100	81ms	463ms	2879ms	15,567
React Router	336	10	105ms	608ms	3510ms	11,162
SolidStart	549.21	5	95ms	343ms	2217ms	17,631
SvelteKit	470.4	5	95ms	473ms	2416ms	15,230
TanStack Start	294.8	10	155ms	1559ms	2779ms	9,652

P99 Latency

P99 Latency at 25 Connections

P99 Latency at 25 Connections chart

P99 Latency at 25 Connections data

Framework	Milliseconds
Baseline HTML	19.00 ms
Astro	32.00 ms
Nuxt	81.00 ms
SolidStart	95.00 ms
SvelteKit	95.00 ms
React Router	105.00 ms
TanStack Start	155.00 ms
Next.js	1822.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	63.00 ms
SolidStart	343.00 ms
Nuxt	463.00 ms
SvelteKit	473.00 ms
React Router	608.00 ms
TanStack Start	1559.00 ms
Next.js	4775.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	108.00 ms
Astro	240.00 ms
SolidStart	2217.00 ms
SvelteKit	2416.00 ms
TanStack Start	2779.00 ms
Nuxt	2879.00 ms
React Router	3510.00 ms
Next.js	4693.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	17.00 ms
Astro	22.00 ms
Nuxt	57.00 ms
SvelteKit	66.00 ms
SolidStart	68.00 ms
React Router	75.00 ms
TanStack Start	123.00 ms
Next.js	642.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	35.00 ms
Astro	42.00 ms
Nuxt	114.00 ms
SvelteKit	140.00 ms
SolidStart	151.00 ms
React Router	155.00 ms
TanStack Start	241.00 ms
Next.js	2332.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
Baseline HTML	73.00 ms
Astro	84.00 ms
SolidStart	179.00 ms
Nuxt	194.00 ms
SvelteKit	253.00 ms
TanStack Start	263.00 ms
React Router	285.00 ms
Next.js	2678.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	17.00 ms
Astro	21.00 ms
Nuxt	55.00 ms
SolidStart	56.00 ms
SvelteKit	59.00 ms
React Router	73.00 ms
TanStack Start	101.00 ms
Next.js	639.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	33.00 ms
Astro	41.00 ms
SolidStart	91.00 ms
Nuxt	106.00 ms
SvelteKit	116.00 ms
React Router	147.00 ms
TanStack Start	153.00 ms
Next.js	1054.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	68.00 ms
Astro	82.00 ms
SolidStart	126.00 ms
Nuxt	180.00 ms
SvelteKit	180.00 ms
TanStack Start	180.00 ms
React Router	259.00 ms
Next.js	1046.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	1	1946ms	4778ms	4689ms	1,171
Nuxt	74	10	1927ms	4237ms	4275ms	2,372
React Router	175.6	10	262ms	1648ms	3848ms	5,842
TanStack Start	44.8	10	3703ms	4127ms	4387ms	1,395

P99 Latency

P99 Latency at 25 Connections

P99 Latency at 25 Connections chart

P99 Latency at 25 Connections data

Framework	Milliseconds
React Router	262.00 ms
Nuxt	1927.00 ms
Next.js	1946.00 ms
TanStack Start	3703.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
React Router	1648.00 ms
TanStack Start	4127.00 ms
Nuxt	4237.00 ms
Next.js	4778.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
React Router	3848.00 ms
Nuxt	4275.00 ms
TanStack Start	4387.00 ms
Next.js	4689.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
React Router	161.00 ms
Nuxt	344.00 ms
Next.js	696.00 ms
TanStack Start	798.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
React Router	287.00 ms
Nuxt	481.00 ms
TanStack Start	878.00 ms
Next.js	2429.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
React Router	408.00 ms
Nuxt	639.00 ms
TanStack Start	1314.00 ms
Next.js	2793.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
React Router	144.00 ms
Nuxt	340.00 ms
TanStack Start	498.00 ms
Next.js	682.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
React Router	285.00 ms
Nuxt	449.00 ms
TanStack Start	523.00 ms
Next.js	1122.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
React Router	363.00 ms
Nuxt	456.00 ms
TanStack Start	535.00 ms
Next.js	1102.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.