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	104.4ms	104.28ms	2.09ms	1.74ms	0.35ms	0ms
Next.js	338.6ms	338.63ms	19.5ms	1.34ms	6.51ms	11.65ms
Nuxt	201.6ms	201.68ms	12.77ms	0.52ms	1.75ms	10.5ms
React Router	163.8ms	163.87ms	23.35ms	2.12ms	2.18ms	19.04ms
SolidStart	111.6ms	111.45ms	19.03ms	0.98ms	2.2ms	15.86ms
SvelteKit	121.6ms	121.54ms	19.01ms	1.16ms	2.24ms	15.61ms
TanStack Start	166.2ms	166.27ms	27.45ms	2.22ms	15.35ms	9.87ms

First Paint (ms)

First Paint (ms) chart

First Paint (ms) data

Framework	Milliseconds
Astro	104.40 ms
SolidStart	111.60 ms
SvelteKit	121.60 ms
React Router	163.80 ms
TanStack Start	166.20 ms
Nuxt	201.60 ms
Next.js	338.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	104.28 ms
SolidStart	111.45 ms
SvelteKit	121.54 ms
React Router	163.87 ms
TanStack Start	166.27 ms
Nuxt	201.68 ms
Next.js	338.63 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: 19.03 ms

Median: 19.03 ms

2.09 ms

12.77 ms

19.01 ms

19.03 ms

19.50 ms

23.35 ms

27.45 ms

Interaction Breakdown data

Framework or version	Interaction latency	Input delay	Processing duration	Presentation delay
Astro	2.09 ms	1.74 ms	0.35 ms	0.00 ms
Nuxt	12.77 ms	0.52 ms	1.75 ms	10.50 ms
SvelteKit	19.01 ms	1.16 ms	2.24 ms	15.61 ms
SolidStart	19.03 ms	0.98 ms	2.20 ms	15.86 ms
Next.js	19.50 ms	1.34 ms	6.51 ms	11.65 ms
React Router	23.35 ms	2.12 ms	2.18 ms	19.04 ms
TanStack Start	27.45 ms	2.22 ms	15.35 ms	9.87 ms

Server Side Rendered Tests

Methodology: Server Side Rendered Tests.

Framework	First Paint	FCP	Interaction Latency	Input Delay	Processing Duration	Presentation Delay
Astro	82.6ms	82.5ms	1.41ms	1.13ms	0.28ms	0ms
Next.js	155ms	155.16ms	21.21ms	1.39ms	8.76ms	11.05ms
Nuxt	113.8ms	113.77ms	14.16ms	0.43ms	1.93ms	11.8ms
React Router	120ms	120.22ms	21.87ms	1.94ms	2.6ms	17.34ms
SolidStart	89.6ms	89.59ms	12.84ms	0.88ms	2.97ms	8.99ms
SvelteKit	88.8ms	88.59ms	17.63ms	0.58ms	3.11ms	13.94ms
TanStack Start	125.4ms	125.28ms	26.41ms	1.74ms	14.46ms	10.21ms

First Paint (ms)

First Paint (ms) chart

First Paint (ms) data

Framework	Milliseconds
Astro	82.60 ms
SvelteKit	88.80 ms
SolidStart	89.60 ms
Nuxt	113.80 ms
React Router	120.00 ms
TanStack Start	125.40 ms
Next.js	155.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	82.50 ms
SvelteKit	88.59 ms
SolidStart	89.59 ms
Nuxt	113.77 ms
React Router	120.22 ms
TanStack Start	125.28 ms
Next.js	155.16 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.63 ms

Median: 17.63 ms

1.41 ms

12.84 ms

14.16 ms

17.63 ms

21.21 ms

21.87 ms

26.41 ms

Interaction Breakdown data

Framework or version	Interaction latency	Input delay	Processing duration	Presentation delay
Astro	1.41 ms	1.13 ms	0.28 ms	0.00 ms
SolidStart	12.84 ms	0.88 ms	2.97 ms	8.99 ms
Nuxt	14.16 ms	0.43 ms	1.93 ms	11.80 ms
SvelteKit	17.63 ms	0.58 ms	3.11 ms	13.94 ms
Next.js	21.21 ms	1.39 ms	8.76 ms	11.05 ms
React Router	21.87 ms	1.94 ms	2.60 ms	17.34 ms
TanStack Start	26.41 ms	1.74 ms	14.46 ms	10.21 ms

Server Side Throughput Tests

Methodology: Server Side Throughput Tests.

Framework	Ops/sec	Median Latency	Body Size	Duplication
Baseline HTML	843	1.203ms	96.83kb	1x
Astro	667	1.436ms	96.89kb	1x
Next.js	225	4.626ms	199.57kb	2x
Nuxt	345	2.804ms	201.57kb	2x
React Router	329	2.99ms	216.91kb	2x
SolidStart	421	2.282ms	224.17kb	2x
SvelteKit	448	2.159ms	183.53kb	2x
TanStack Start	299	3.263ms	193.62kb	2x

Ops/sec

Ops/sec chart

Ops/sec data

Framework	Operations per second
Baseline HTML	843
Astro	667
SvelteKit	448
SolidStart	421
Nuxt	345
React Router	329
TanStack Start	299
Next.js	225

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.91 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.16 ms
SolidStart	2.28 ms
Nuxt	2.80 ms
React Router	2.99 ms
TanStack Start	3.26 ms
Next.js	4.63 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,681.8	100	20ms	46ms	108ms	48,900
Astro	1,225.41	50	30ms	60ms	248ms	37,468
Next.js	39.8	1	1963ms	4649ms	4676ms	1,126
Nuxt	459.4	50	82ms	488ms	2959ms	14,894
React Router	325	200	106ms	641ms	3528ms	10,571
SolidStart	526.4	10	100ms	370ms	2086ms	17,353
SvelteKit	472.4	10	89ms	495ms	2025ms	15,271
TanStack Start	283.2	10	170ms	1831ms	2808ms	9,251

P99 Latency

P99 Latency at 25 Connections

P99 Latency at 25 Connections chart

P99 Latency at 25 Connections data

Framework	Milliseconds
Baseline HTML	20.00 ms
Astro	30.00 ms
Nuxt	82.00 ms
SvelteKit	89.00 ms
SolidStart	100.00 ms
React Router	106.00 ms
TanStack Start	170.00 ms
Next.js	1963.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	46.00 ms
Astro	60.00 ms
SolidStart	370.00 ms
Nuxt	488.00 ms
SvelteKit	495.00 ms
React Router	641.00 ms
TanStack Start	1831.00 ms
Next.js	4649.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	248.00 ms
SvelteKit	2025.00 ms
SolidStart	2086.00 ms
TanStack Start	2808.00 ms
Nuxt	2959.00 ms
React Router	3528.00 ms
Next.js	4676.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	18.00 ms
Astro	22.00 ms
Nuxt	57.00 ms
SvelteKit	62.00 ms
SolidStart	69.00 ms
React Router	80.00 ms
TanStack Start	123.00 ms
Next.js	698.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	37.00 ms
Astro	42.00 ms
Nuxt	116.00 ms
SolidStart	146.00 ms
SvelteKit	150.00 ms
React Router	156.00 ms
TanStack Start	278.00 ms
Next.js	2436.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	74.00 ms
Astro	83.00 ms
SolidStart	170.00 ms
Nuxt	202.00 ms
TanStack Start	256.00 ms
SvelteKit	266.00 ms
React Router	288.00 ms
Next.js	2615.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
SvelteKit	56.00 ms
SolidStart	59.00 ms
React Router	78.00 ms
TanStack Start	105.00 ms
Next.js	686.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	36.00 ms
Astro	41.00 ms
SolidStart	90.00 ms
Nuxt	107.00 ms
SvelteKit	114.00 ms
React Router	153.00 ms
TanStack Start	164.00 ms
Next.js	1113.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	62.00 ms
Astro	81.00 ms
SolidStart	123.00 ms
TanStack Start	178.00 ms
Nuxt	180.00 ms
SvelteKit	197.00 ms
React Router	262.00 ms
Next.js	1082.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	39.6	1	2021ms	4623ms	4651ms	1,090
Nuxt	69.41	5	1982ms	4133ms	4280ms	2,208
React Router	173.4	10	321ms	1619ms	3855ms	5,845
TanStack Start	44	10	3828ms	4092ms	4636ms	1,342

P99 Latency

P99 Latency at 25 Connections

P99 Latency at 25 Connections chart

P99 Latency at 25 Connections data

Framework	Milliseconds
React Router	321.00 ms
Nuxt	1982.00 ms
Next.js	2021.00 ms
TanStack Start	3828.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	1619.00 ms
TanStack Start	4092.00 ms
Nuxt	4133.00 ms
Next.js	4623.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	3855.00 ms
Nuxt	4280.00 ms
TanStack Start	4636.00 ms
Next.js	4651.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	149.00 ms
Nuxt	370.00 ms
Next.js	742.00 ms
TanStack Start	857.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	290.00 ms
Nuxt	514.00 ms
TanStack Start	791.00 ms
Next.js	2391.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	391.00 ms
Nuxt	704.00 ms
TanStack Start	1455.00 ms
Next.js	2859.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
Nuxt	363.00 ms
TanStack Start	559.00 ms
Next.js	730.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	281.00 ms
Nuxt	467.00 ms
TanStack Start	553.00 ms
Next.js	1129.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	359.00 ms
Nuxt	439.00 ms
TanStack Start	562.00 ms
Next.js	1091.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.