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	99.4ms	99.38ms	5.94ms	3.01ms	0.44ms	2.49ms
Next.js	339.2ms	339.12ms	18.7ms	1.41ms	8.03ms	9.25ms
Nuxt	169.6ms	169.6ms	9.37ms	0.44ms	2.11ms	6.82ms
React Router	172.8ms	172.89ms	20.27ms	1.52ms	2.53ms	16.22ms
SolidStart	117ms	116.92ms	17.32ms	0.9ms	2.82ms	13.59ms
SvelteKit	111.8ms	111.84ms	16.91ms	0.65ms	2.38ms	13.87ms
TanStack Start	136ms	136.12ms	27.07ms	1.4ms	14.62ms	11.05ms

First Paint (ms)

First Paint (ms) chart

First Paint (ms) data

Framework	Milliseconds
Astro	99.40 ms
SvelteKit	111.80 ms
SolidStart	117.00 ms
TanStack Start	136.00 ms
Nuxt	169.60 ms
React Router	172.80 ms
Next.js	339.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	99.38 ms
SvelteKit	111.84 ms
SolidStart	116.92 ms
TanStack Start	136.12 ms
Nuxt	169.60 ms
React Router	172.89 ms
Next.js	339.12 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.32 ms

Median: 17.32 ms

5.94 ms

9.37 ms

16.91 ms

17.32 ms

18.70 ms

20.27 ms

27.07 ms

Interaction Breakdown data

Framework or version	Interaction latency	Input delay	Processing duration	Presentation delay
Astro	5.94 ms	3.01 ms	0.44 ms	2.49 ms
Nuxt	9.37 ms	0.44 ms	2.11 ms	6.82 ms
SvelteKit	16.91 ms	0.65 ms	2.38 ms	13.87 ms
SolidStart	17.32 ms	0.90 ms	2.82 ms	13.59 ms
Next.js	18.70 ms	1.41 ms	8.03 ms	9.25 ms
React Router	20.27 ms	1.52 ms	2.53 ms	16.22 ms
TanStack Start	27.07 ms	1.40 ms	14.62 ms	11.05 ms

Server Side Rendered Tests

Methodology: Server Side Rendered Tests.

Framework	First Paint	FCP	Interaction Latency	Input Delay	Processing Duration	Presentation Delay
Astro	74.2ms	74.32ms	1.55ms	0.89ms	0.66ms	0ms
Next.js	151.4ms	151.49ms	19.23ms	1.35ms	7.59ms	10.29ms
Nuxt	110.8ms	110.68ms	12.87ms	0.54ms	1.37ms	10.96ms
React Router	128.2ms	128.25ms	20.61ms	1.46ms	2.56ms	16.58ms
SolidStart	99.8ms	99.66ms	14.57ms	0.87ms	2.68ms	11.02ms
SvelteKit	90.6ms	90.68ms	18.12ms	0.55ms	3.01ms	14.57ms
TanStack Start	116.4ms	116.29ms	36.84ms	1.81ms	15.89ms	19.14ms

First Paint (ms)

First Paint (ms) chart

First Paint (ms) data

Framework	Milliseconds
Astro	74.20 ms
SvelteKit	90.60 ms
SolidStart	99.80 ms
Nuxt	110.80 ms
TanStack Start	116.40 ms
React Router	128.20 ms
Next.js	151.40 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	74.32 ms
SvelteKit	90.68 ms
SolidStart	99.66 ms
Nuxt	110.68 ms
TanStack Start	116.29 ms
React Router	128.25 ms
Next.js	151.49 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.12 ms

Median: 18.12 ms

1.55 ms

12.87 ms

14.57 ms

18.12 ms

19.23 ms

20.61 ms

36.84 ms

Interaction Breakdown data

Framework or version	Interaction latency	Input delay	Processing duration	Presentation delay
Astro	1.55 ms	0.89 ms	0.66 ms	0.00 ms
Nuxt	12.87 ms	0.54 ms	1.37 ms	10.96 ms
SolidStart	14.57 ms	0.87 ms	2.68 ms	11.02 ms
SvelteKit	18.12 ms	0.55 ms	3.01 ms	14.57 ms
Next.js	19.23 ms	1.35 ms	7.59 ms	10.29 ms
React Router	20.61 ms	1.46 ms	2.56 ms	16.58 ms
TanStack Start	36.84 ms	1.81 ms	15.89 ms	19.14 ms

Server Side Throughput Tests

Methodology: Server Side Throughput Tests.

Framework	Ops/sec	Median Latency	Body Size	Duplication
Baseline HTML	845	1.199ms	96.83kb	1x
Astro	723	1.348ms	96.89kb	1x
Next.js	232	4.507ms	199.57kb	2x
Nuxt	378	2.569ms	201.57kb	2x
React Router	348	2.839ms	216.9kb	2x
SolidStart	423	2.281ms	224.17kb	2x
SvelteKit	457	2.117ms	183.53kb	2x
TanStack Start	332	2.98ms	193.62kb	2x

Ops/sec

Ops/sec chart

Ops/sec data

Framework	Operations per second
Baseline HTML	845
Astro	723
SvelteKit	457
SolidStart	423
Nuxt	378
React Router	348
TanStack Start	332
Next.js	232

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.35 ms
SvelteKit	2.12 ms
SolidStart	2.28 ms
Nuxt	2.57 ms
React Router	2.84 ms
TanStack Start	2.98 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,644	100	21ms	46ms	116ms	46,501
Astro	1,562.6	50	24ms	46ms	98ms	46,817
Next.js	45	1	1781ms	4754ms	4745ms	1,271
Nuxt	491.6	10	75ms	422ms	2848ms	16,039
React Router	335.4	10	109ms	578ms	3442ms	11,002
SolidStart	541	10	96ms	340ms	2065ms	17,478
SvelteKit	476.8	5	96ms	460ms	2653ms	15,101
TanStack Start	297.61	25	159ms	1436ms	2861ms	9,767

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	24.00 ms
Nuxt	75.00 ms
SolidStart	96.00 ms
SvelteKit	96.00 ms
React Router	109.00 ms
TanStack Start	159.00 ms
Next.js	1781.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	46.00 ms
Baseline HTML	46.00 ms
SolidStart	340.00 ms
Nuxt	422.00 ms
SvelteKit	460.00 ms
React Router	578.00 ms
TanStack Start	1436.00 ms
Next.js	4754.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	98.00 ms
Baseline HTML	116.00 ms
SolidStart	2065.00 ms
SvelteKit	2653.00 ms
Nuxt	2848.00 ms
TanStack Start	2861.00 ms
React Router	3442.00 ms
Next.js	4745.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	20.00 ms
Nuxt	53.00 ms
SvelteKit	63.00 ms
SolidStart	68.00 ms
React Router	76.00 ms
TanStack Start	107.00 ms
Next.js	645.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	34.00 ms
Baseline HTML	37.00 ms
Nuxt	112.00 ms
SolidStart	149.00 ms
SvelteKit	150.00 ms
React Router	154.00 ms
TanStack Start	248.00 ms
Next.js	2286.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	67.00 ms
Baseline HTML	75.00 ms
SolidStart	151.00 ms
Nuxt	193.00 ms
SvelteKit	223.00 ms
TanStack Start	271.00 ms
React Router	291.00 ms
Next.js	2595.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	18.00 ms
Nuxt	51.00 ms
SolidStart	57.00 ms
SvelteKit	57.00 ms
React Router	74.00 ms
TanStack Start	88.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	35.00 ms
SolidStart	94.00 ms
Nuxt	104.00 ms
SvelteKit	116.00 ms
React Router	149.00 ms
TanStack Start	185.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
Astro	63.00 ms
Baseline HTML	68.00 ms
SolidStart	125.00 ms
Nuxt	175.00 ms
SvelteKit	181.00 ms
TanStack Start	183.00 ms
React Router	271.00 ms
Next.js	1045.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	41.6	1	2001ms	4805ms	4594ms	1,148
Nuxt	74	5	1883ms	4050ms	4128ms	2,401
React Router	174.4	5	228ms	1610ms	3946ms	5,867
TanStack Start	89	10	1431ms	3793ms	3709ms	2,907

P99 Latency

P99 Latency at 25 Connections

P99 Latency at 25 Connections chart

P99 Latency at 25 Connections data

Framework	Milliseconds
React Router	228.00 ms
TanStack Start	1431.00 ms
Nuxt	1883.00 ms
Next.js	2001.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	1610.00 ms
TanStack Start	3793.00 ms
Nuxt	4050.00 ms
Next.js	4805.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
TanStack Start	3709.00 ms
React Router	3946.00 ms
Nuxt	4128.00 ms
Next.js	4594.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	156.00 ms
Nuxt	338.00 ms
TanStack Start	412.00 ms
Next.js	724.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	487.00 ms
TanStack Start	516.00 ms
Next.js	2420.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	397.00 ms
Nuxt	551.00 ms
TanStack Start	585.00 ms
Next.js	2728.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	142.00 ms
TanStack Start	293.00 ms
Nuxt	336.00 ms
Next.js	705.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
TanStack Start	396.00 ms
Nuxt	456.00 ms
Next.js	1147.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	359.00 ms
React Router	364.00 ms
Nuxt	440.00 ms
Next.js	1124.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.