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	110.2ms	110.15ms	18.57ms	1.84ms	0.64ms	16.09ms
Next.js	342.8ms	342.79ms	19.79ms	1.46ms	8.25ms	10.08ms
Nuxt	175.6ms	175.56ms	11.14ms	1.01ms	1.93ms	8.2ms
React Router	168ms	168.04ms	20.96ms	1.59ms	3.8ms	15.57ms
SolidStart	115.6ms	115.67ms	17.38ms	0.96ms	2.93ms	13.49ms
SvelteKit	121ms	120.85ms	14.84ms	1.82ms	3.21ms	9.81ms
TanStack Start	190.8ms	190.82ms	38.85ms	2.17ms	23.56ms	13.12ms

First Paint (ms)

First Paint (ms) chart

First Paint (ms) data

Framework	Milliseconds
Astro	110.20 ms
SolidStart	115.60 ms
SvelteKit	121.00 ms
React Router	168.00 ms
Nuxt	175.60 ms
TanStack Start	190.80 ms
Next.js	342.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	110.15 ms
SolidStart	115.67 ms
SvelteKit	120.85 ms
React Router	168.04 ms
Nuxt	175.56 ms
TanStack Start	190.82 ms
Next.js	342.79 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.57 ms

Median: 18.57 ms

11.14 ms

14.84 ms

17.38 ms

18.57 ms

19.79 ms

20.96 ms

38.85 ms

Interaction Breakdown data

Framework or version	Interaction latency	Input delay	Processing duration	Presentation delay
Nuxt	11.14 ms	1.01 ms	1.93 ms	8.20 ms
SvelteKit	14.84 ms	1.82 ms	3.21 ms	9.81 ms
SolidStart	17.38 ms	0.96 ms	2.93 ms	13.49 ms
Astro	18.57 ms	1.84 ms	0.64 ms	16.09 ms
Next.js	19.79 ms	1.46 ms	8.25 ms	10.08 ms
React Router	20.96 ms	1.59 ms	3.80 ms	15.57 ms
TanStack Start	38.85 ms	2.17 ms	23.56 ms	13.12 ms

Server Side Rendered Tests

Methodology: Server Side Rendered Tests.

Framework	First Paint	FCP	Interaction Latency	Input Delay	Processing Duration	Presentation Delay
Astro	63ms	62.72ms	0.83ms	0.54ms	0.28ms	0ms
Next.js	149.6ms	149.56ms	20.38ms	1.27ms	10.56ms	8.54ms
Nuxt	123.4ms	123.44ms	11.96ms	0.55ms	1.6ms	9.82ms
React Router	137.6ms	137.69ms	20.85ms	1.57ms	2.8ms	16.48ms
SolidStart	116.4ms	116.34ms	13.88ms	0.96ms	2.38ms	10.54ms
SvelteKit	94.4ms	94.32ms	13.93ms	0.62ms	3.31ms	10ms
TanStack Start	132.2ms	132.1ms	33.76ms	1.9ms	18.47ms	13.38ms

First Paint (ms)

First Paint (ms) chart

First Paint (ms) data

Framework	Milliseconds
Astro	63.00 ms
SvelteKit	94.40 ms
SolidStart	116.40 ms
Nuxt	123.40 ms
TanStack Start	132.20 ms
React Router	137.60 ms
Next.js	149.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	62.72 ms
SvelteKit	94.32 ms
SolidStart	116.34 ms
Nuxt	123.44 ms
TanStack Start	132.10 ms
React Router	137.69 ms
Next.js	149.56 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: 13.93 ms

Median: 13.93 ms

0.83 ms

11.96 ms

13.88 ms

13.93 ms

20.38 ms

20.85 ms

33.76 ms

Interaction Breakdown data

Framework or version	Interaction latency	Input delay	Processing duration	Presentation delay
Astro	0.83 ms	0.54 ms	0.28 ms	0.00 ms
Nuxt	11.96 ms	0.55 ms	1.60 ms	9.82 ms
SolidStart	13.88 ms	0.96 ms	2.38 ms	10.54 ms
SvelteKit	13.93 ms	0.62 ms	3.31 ms	10.00 ms
Next.js	20.38 ms	1.27 ms	10.56 ms	8.54 ms
React Router	20.85 ms	1.57 ms	2.80 ms	16.48 ms
TanStack Start	33.76 ms	1.90 ms	18.47 ms	13.38 ms

Server Side Throughput Tests

Methodology: Server Side Throughput Tests.

Framework	Ops/sec	Median Latency	Body Size	Duplication
Baseline HTML	837	1.207ms	96.83kb	1x
Astro	655	1.455ms	96.89kb	1x
Next.js	234	4.469ms	199.57kb	2x
Nuxt	362	2.681ms	201.57kb	2x
React Router	323	3.015ms	216.9kb	2x
SolidStart	421	2.303ms	224.17kb	2x
SvelteKit	449	2.161ms	183.53kb	2x
TanStack Start	304	3.249ms	193.62kb	2x

Ops/sec

Ops/sec chart

Ops/sec data

Framework	Operations per second
Baseline HTML	837
Astro	655
SvelteKit	449
SolidStart	421
Nuxt	362
React Router	323
TanStack Start	304
Next.js	234

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.21 ms
Astro	1.46 ms
SvelteKit	2.16 ms
SolidStart	2.30 ms
Nuxt	2.68 ms
React Router	3.02 ms
TanStack Start	3.25 ms
Next.js	4.47 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,594.4	200	21ms	42ms	122ms	47,154
Astro	1,217	100	30ms	65ms	249ms	36,331
Next.js	46.4	5	1774ms	4780ms	4813ms	1,267
Nuxt	466.8	50	84ms	427ms	2903ms	15,135
React Router	329.2	25	102ms	567ms	3486ms	10,737
SolidStart	535.8	5	93ms	393ms	2121ms	17,457
SvelteKit	497.2	10	85ms	445ms	2362ms	15,496
TanStack Start	293.61	10	171ms	1682ms	2898ms	9,471

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	30.00 ms
Nuxt	84.00 ms
SvelteKit	85.00 ms
SolidStart	93.00 ms
React Router	102.00 ms
TanStack Start	171.00 ms
Next.js	1774.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	42.00 ms
Astro	65.00 ms
SolidStart	393.00 ms
Nuxt	427.00 ms
SvelteKit	445.00 ms
React Router	567.00 ms
TanStack Start	1682.00 ms
Next.js	4780.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	122.00 ms
Astro	249.00 ms
SolidStart	2121.00 ms
SvelteKit	2362.00 ms
TanStack Start	2898.00 ms
Nuxt	2903.00 ms
React Router	3486.00 ms
Next.js	4813.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	19.00 ms
Astro	24.00 ms
Nuxt	59.00 ms
SvelteKit	64.00 ms
SolidStart	67.00 ms
React Router	77.00 ms
TanStack Start	127.00 ms
Next.js	619.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	44.00 ms
Nuxt	119.00 ms
SvelteKit	131.00 ms
SolidStart	147.00 ms
React Router	157.00 ms
TanStack Start	266.00 ms
Next.js	2295.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	79.00 ms
Astro	84.00 ms
SolidStart	155.00 ms
Nuxt	203.00 ms
SvelteKit	213.00 ms
TanStack Start	273.00 ms
React Router	296.00 ms
Next.js	2778.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	18.00 ms
Astro	22.00 ms
Nuxt	53.00 ms
SvelteKit	57.00 ms
SolidStart	58.00 ms
React Router	75.00 ms
TanStack Start	104.00 ms
Next.js	614.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	35.00 ms
Astro	42.00 ms
SolidStart	93.00 ms
Nuxt	106.00 ms
SvelteKit	114.00 ms
React Router	150.00 ms
TanStack Start	163.00 ms
Next.js	1069.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	69.00 ms
Astro	80.00 ms
SolidStart	127.00 ms
SvelteKit	166.00 ms
Nuxt	184.00 ms
TanStack Start	184.00 ms
React Router	258.00 ms
Next.js	1074.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	43	5	1949ms	4601ms	4660ms	1,180
Nuxt	69.6	5	1969ms	4276ms	4188ms	2,243
React Router	170.8	5	246ms	1698ms	3962ms	5,683
TanStack Start	45	5	3700ms	4061ms	4742ms	1,386

P99 Latency

P99 Latency at 25 Connections

P99 Latency at 25 Connections chart

P99 Latency at 25 Connections data

Framework	Milliseconds
React Router	246.00 ms
Next.js	1949.00 ms
Nuxt	1969.00 ms
TanStack Start	3700.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	1698.00 ms
TanStack Start	4061.00 ms
Nuxt	4276.00 ms
Next.js	4601.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	3962.00 ms
Nuxt	4188.00 ms
Next.js	4660.00 ms
TanStack Start	4742.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	357.00 ms
Next.js	678.00 ms
TanStack Start	723.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	289.00 ms
Nuxt	485.00 ms
TanStack Start	767.00 ms
Next.js	2395.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	402.00 ms
Nuxt	725.00 ms
TanStack Start	1400.00 ms
Next.js	2721.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	145.00 ms
Nuxt	355.00 ms
TanStack Start	575.00 ms
Next.js	667.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
Nuxt	468.00 ms
TanStack Start	633.00 ms
Next.js	1105.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	378.00 ms
Nuxt	444.00 ms
TanStack Start	550.00 ms
Next.js	1062.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.