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	103.4ms	103.66ms	4.25ms	1.77ms	0.81ms	1.66ms
Next.js	337.8ms	337.67ms	18.24ms	1.27ms	8.96ms	8.02ms
Nuxt	165.8ms	165.9ms	11.77ms	0.46ms	2.87ms	8.44ms
React Router	152.8ms	152.55ms	21.26ms	1.41ms	1.91ms	17.94ms
SolidStart	96.6ms	96.38ms	13.22ms	1.07ms	2.15ms	10ms
SvelteKit	121.4ms	121.64ms	17.99ms	0.66ms	2.47ms	14.86ms
TanStack Start	148ms	148.16ms	28.69ms	1.44ms	17.32ms	9.93ms

First Paint (ms)

First Paint (ms) chart

First Paint (ms) data

Framework	Milliseconds
SolidStart	96.60 ms
Astro	103.40 ms
SvelteKit	121.40 ms
TanStack Start	148.00 ms
React Router	152.80 ms
Nuxt	165.80 ms
Next.js	337.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
SolidStart	96.38 ms
Astro	103.66 ms
SvelteKit	121.64 ms
TanStack Start	148.16 ms
React Router	152.55 ms
Nuxt	165.90 ms
Next.js	337.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.99 ms

Median: 17.99 ms

4.25 ms

11.77 ms

13.22 ms

17.99 ms

18.24 ms

21.26 ms

28.69 ms

Interaction Breakdown data

Framework or version	Interaction latency	Input delay	Processing duration	Presentation delay
Astro	4.25 ms	1.77 ms	0.81 ms	1.66 ms
Nuxt	11.77 ms	0.46 ms	2.87 ms	8.44 ms
SolidStart	13.22 ms	1.07 ms	2.15 ms	10.00 ms
SvelteKit	17.99 ms	0.66 ms	2.47 ms	14.86 ms
Next.js	18.24 ms	1.27 ms	8.96 ms	8.02 ms
React Router	21.26 ms	1.41 ms	1.91 ms	17.94 ms
TanStack Start	28.69 ms	1.44 ms	17.32 ms	9.93 ms

Server Side Rendered Tests

Methodology: Server Side Rendered Tests.

Framework	First Paint	FCP	Interaction Latency	Input Delay	Processing Duration	Presentation Delay
Astro	61.6ms	61.83ms	4.78ms	1.01ms	1.04ms	2.74ms
Next.js	152.8ms	152.66ms	18.93ms	1.6ms	8.27ms	9.07ms
Nuxt	106ms	106.09ms	10ms	0.42ms	1.95ms	7.63ms
React Router	123.8ms	123.75ms	17.97ms	1.76ms	2.78ms	13.43ms
SolidStart	86ms	86ms	13.07ms	0.85ms	3.17ms	9.05ms
SvelteKit	83ms	83.01ms	15.64ms	1.28ms	3.15ms	11.21ms
TanStack Start	125.8ms	125.69ms	39.02ms	1.69ms	19.77ms	17.56ms

First Paint (ms)

First Paint (ms) chart

First Paint (ms) data

Framework	Milliseconds
Astro	61.60 ms
SvelteKit	83.00 ms
SolidStart	86.00 ms
Nuxt	106.00 ms
React Router	123.80 ms
TanStack Start	125.80 ms
Next.js	152.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	61.83 ms
SvelteKit	83.01 ms
SolidStart	86.00 ms
Nuxt	106.09 ms
React Router	123.75 ms
TanStack Start	125.69 ms
Next.js	152.66 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.64 ms

Median: 15.64 ms

4.78 ms

10.00 ms

13.07 ms

15.64 ms

17.97 ms

18.93 ms

39.02 ms

Interaction Breakdown data

Framework or version	Interaction latency	Input delay	Processing duration	Presentation delay
Astro	4.78 ms	1.01 ms	1.04 ms	2.74 ms
Nuxt	10.00 ms	0.42 ms	1.95 ms	7.63 ms
SolidStart	13.07 ms	0.85 ms	3.17 ms	9.05 ms
SvelteKit	15.64 ms	1.28 ms	3.15 ms	11.21 ms
React Router	17.97 ms	1.76 ms	2.78 ms	13.43 ms
Next.js	18.93 ms	1.60 ms	8.27 ms	9.07 ms
TanStack Start	39.02 ms	1.69 ms	19.77 ms	17.56 ms

Server Side Throughput Tests

Methodology: Server Side Throughput Tests.

Framework	Ops/sec	Median Latency	Body Size	Duplication
Baseline HTML	842	1.201ms	96.83kb	1x
Astro	743	1.317ms	96.89kb	1x
Next.js	213	4.515ms	199.57kb	2x
Nuxt	357	2.695ms	201.57kb	2x
React Router	346	2.847ms	216.9kb	2x
SolidStart	428	2.253ms	224.17kb	2x
SvelteKit	447	2.169ms	183.53kb	2x
TanStack Start	326	3.039ms	193.62kb	2x

Ops/sec

Ops/sec chart

Ops/sec data

Framework	Operations per second
Baseline HTML	842
Astro	743
SvelteKit	447
SolidStart	428
Nuxt	357
React Router	346
TanStack Start	326
Next.js	213

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.53 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.32 ms
SvelteKit	2.17 ms
SolidStart	2.25 ms
Nuxt	2.69 ms
React Router	2.85 ms
TanStack Start	3.04 ms
Next.js	4.51 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,616.6	25	21ms	43ms	125ms	47,104
Astro	1,578.6	50	25ms	46ms	81ms	46,626
Next.js	44.6	1	1815ms	4726ms	4695ms	1,256
Nuxt	484.6	10	80ms	445ms	2997ms	15,801
React Router	337.4	25	104ms	586ms	3475ms	10,994
SolidStart	511.2	5	103ms	492ms	2267ms	16,391
SvelteKit	483.8	5	86ms	516ms	2323ms	15,260
TanStack Start	291.61	25	159ms	1582ms	2803ms	9,617

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	25.00 ms
Nuxt	80.00 ms
SvelteKit	86.00 ms
SolidStart	103.00 ms
React Router	104.00 ms
TanStack Start	159.00 ms
Next.js	1815.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	43.00 ms
Astro	46.00 ms
Nuxt	445.00 ms
SolidStart	492.00 ms
SvelteKit	516.00 ms
React Router	586.00 ms
TanStack Start	1582.00 ms
Next.js	4726.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	81.00 ms
Baseline HTML	125.00 ms
SolidStart	2267.00 ms
SvelteKit	2323.00 ms
TanStack Start	2803.00 ms
Nuxt	2997.00 ms
React Router	3475.00 ms
Next.js	4695.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
Nuxt	53.00 ms
SvelteKit	64.00 ms
SolidStart	72.00 ms
React Router	74.00 ms
TanStack Start	124.00 ms
Next.js	637.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	33.00 ms
Baseline HTML	37.00 ms
Nuxt	113.00 ms
SvelteKit	133.00 ms
React Router	151.00 ms
SolidStart	153.00 ms
TanStack Start	243.00 ms
Next.js	2315.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	85.00 ms
SolidStart	173.00 ms
Nuxt	193.00 ms
SvelteKit	252.00 ms
TanStack Start	265.00 ms
React Router	287.00 ms
Next.js	2585.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	16.00 ms
Nuxt	51.00 ms
SvelteKit	57.00 ms
SolidStart	60.00 ms
React Router	73.00 ms
TanStack Start	102.00 ms
Next.js	632.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	32.00 ms
Baseline HTML	36.00 ms
SolidStart	98.00 ms
Nuxt	102.00 ms
SvelteKit	114.00 ms
React Router	149.00 ms
TanStack Start	172.00 ms
Next.js	1070.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	64.00 ms
Baseline HTML	69.00 ms
SolidStart	126.00 ms
Nuxt	178.00 ms
SvelteKit	178.00 ms
TanStack Start	183.00 ms
React Router	262.00 ms
Next.js	1119.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	1843ms	4732ms	4697ms	1,187
Nuxt	76	5	1866ms	4025ms	4298ms	2,342
React Router	173.8	25	314ms	1596ms	3889ms	5,750
TanStack Start	83.2	25	1673ms	3735ms	3916ms	2,591

P99 Latency

P99 Latency at 25 Connections

P99 Latency at 25 Connections chart

P99 Latency at 25 Connections data

Framework	Milliseconds
React Router	314.00 ms
TanStack Start	1673.00 ms
Next.js	1843.00 ms
Nuxt	1866.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	1596.00 ms
TanStack Start	3735.00 ms
Nuxt	4025.00 ms
Next.js	4732.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	3889.00 ms
TanStack Start	3916.00 ms
Nuxt	4298.00 ms
Next.js	4697.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	148.00 ms
Nuxt	340.00 ms
TanStack Start	412.00 ms
Next.js	672.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	312.00 ms
Nuxt	519.00 ms
TanStack Start	553.00 ms
Next.js	2251.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	396.00 ms
TanStack Start	567.00 ms
Nuxt	622.00 ms
Next.js	2693.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	143.00 ms
TanStack Start	308.00 ms
Nuxt	336.00 ms
Next.js	661.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	288.00 ms
TanStack Start	394.00 ms
Nuxt	440.00 ms
Next.js	1072.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	343.00 ms
React Router	368.00 ms
Nuxt	456.00 ms
Next.js	1047.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.