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	106.2ms	106.32ms	2.65ms	1.97ms	0.68ms	0ms
Next.js	341.8ms	341.72ms	23.69ms	1.37ms	7.02ms	15.3ms
Nuxt	157.6ms	157.52ms	11.21ms	0.49ms	1.79ms	8.93ms
React Router	153.2ms	153.28ms	20.05ms	2.04ms	2.22ms	15.79ms
SolidStart	102.6ms	102.72ms	15.05ms	1.4ms	2.9ms	10.75ms
SvelteKit	111.6ms	111.51ms	15.84ms	1.1ms	3.18ms	11.56ms
TanStack Start	159.8ms	160.03ms	34.86ms	1.69ms	17.61ms	15.57ms

First Paint (ms)

First Paint (ms) chart

First Paint (ms) data

Framework	Milliseconds
SolidStart	102.60 ms
Astro	106.20 ms
SvelteKit	111.60 ms
React Router	153.20 ms
Nuxt	157.60 ms
TanStack Start	159.80 ms
Next.js	341.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	102.72 ms
Astro	106.32 ms
SvelteKit	111.51 ms
React Router	153.28 ms
Nuxt	157.52 ms
TanStack Start	160.03 ms
Next.js	341.72 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.84 ms

Median: 15.84 ms

2.65 ms

11.21 ms

15.05 ms

15.84 ms

20.05 ms

23.69 ms

34.86 ms

Interaction Breakdown data

Framework or version	Interaction latency	Input delay	Processing duration	Presentation delay
Astro	2.65 ms	1.97 ms	0.68 ms	0.00 ms
Nuxt	11.21 ms	0.49 ms	1.79 ms	8.93 ms
SolidStart	15.05 ms	1.40 ms	2.90 ms	10.75 ms
SvelteKit	15.84 ms	1.10 ms	3.18 ms	11.56 ms
React Router	20.05 ms	2.04 ms	2.22 ms	15.79 ms
Next.js	23.69 ms	1.37 ms	7.02 ms	15.30 ms
TanStack Start	34.86 ms	1.69 ms	17.61 ms	15.57 ms

Server Side Rendered Tests

Methodology: Server Side Rendered Tests.

Framework	First Paint	FCP	Interaction Latency	Input Delay	Processing Duration	Presentation Delay
Astro	79ms	78.87ms	3.47ms	1.26ms	1.22ms	1ms
Next.js	168.6ms	168.31ms	20.1ms	1.34ms	7.95ms	10.81ms
Nuxt	120ms	120.1ms	10.83ms	0.43ms	1.34ms	9.06ms
React Router	122.6ms	122.53ms	22.04ms	1.89ms	2.77ms	17.38ms
SolidStart	100ms	100.01ms	13.48ms	1.54ms	2.12ms	9.83ms
SvelteKit	99.2ms	98.99ms	16.97ms	0.9ms	2.84ms	13.24ms
TanStack Start	132.8ms	132.73ms	26.76ms	1.69ms	16.44ms	8.63ms

First Paint (ms)

First Paint (ms) chart

First Paint (ms) data

Framework	Milliseconds
Astro	79.00 ms
SvelteKit	99.20 ms
SolidStart	100.00 ms
Nuxt	120.00 ms
React Router	122.60 ms
TanStack Start	132.80 ms
Next.js	168.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	78.87 ms
SvelteKit	98.99 ms
SolidStart	100.01 ms
Nuxt	120.10 ms
React Router	122.53 ms
TanStack Start	132.73 ms
Next.js	168.31 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: 16.97 ms

Median: 16.97 ms

3.47 ms

10.83 ms

13.48 ms

16.97 ms

20.10 ms

22.04 ms

26.76 ms

Interaction Breakdown data

Framework or version	Interaction latency	Input delay	Processing duration	Presentation delay
Astro	3.47 ms	1.26 ms	1.22 ms	1.00 ms
Nuxt	10.83 ms	0.43 ms	1.34 ms	9.06 ms
SolidStart	13.48 ms	1.54 ms	2.12 ms	9.83 ms
SvelteKit	16.97 ms	0.90 ms	2.84 ms	13.24 ms
Next.js	20.10 ms	1.34 ms	7.95 ms	10.81 ms
React Router	22.04 ms	1.89 ms	2.77 ms	17.38 ms
TanStack Start	26.76 ms	1.69 ms	16.44 ms	8.63 ms

Server Side Throughput Tests

Methodology: Server Side Throughput Tests.

Framework	Ops/sec	Median Latency	Body Size	Duplication
Baseline HTML	850	1.203ms	96.83kb	1x
Astro	668	1.444ms	96.89kb	1x
Next.js	228	4.57ms	199.57kb	2x
Nuxt	368	2.633ms	201.57kb	2x
React Router	312	3.182ms	216.9kb	2x
SolidStart	423	2.297ms	224.17kb	2x
SvelteKit	409	2.347ms	183.53kb	2x
TanStack Start	310	3.185ms	193.62kb	2x

Ops/sec

Ops/sec chart

Ops/sec data

Framework	Operations per second
Baseline HTML	850
Astro	668
SolidStart	423
SvelteKit	409
Nuxt	368
React Router	312
TanStack Start	310
Next.js	228

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.44 ms
SolidStart	2.30 ms
SvelteKit	2.35 ms
Nuxt	2.63 ms
React Router	3.18 ms
TanStack Start	3.19 ms
Next.js	4.57 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,780.6	100	20ms	39ms	87ms	50,128
Astro	1,186	25	29ms	67ms	324ms	36,308
Next.js	45	1	1840ms	4766ms	4678ms	1,262
Nuxt	478.4	5	84ms	141ms	2919ms	15,266
React Router	342.2	25	99ms	558ms	3237ms	11,419
SolidStart	530.8	10	103ms	679ms	2119ms	16,879
SvelteKit	487.2	10	81ms	424ms	2424ms	15,611
TanStack Start	269.61	50	211ms	1842ms	2842ms	8,797

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	29.00 ms
SvelteKit	81.00 ms
Nuxt	84.00 ms
React Router	99.00 ms
SolidStart	103.00 ms
TanStack Start	211.00 ms
Next.js	1840.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	39.00 ms
Astro	67.00 ms
Nuxt	141.00 ms
SvelteKit	424.00 ms
React Router	558.00 ms
SolidStart	679.00 ms
TanStack Start	1842.00 ms
Next.js	4766.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	87.00 ms
Astro	324.00 ms
SolidStart	2119.00 ms
SvelteKit	2424.00 ms
TanStack Start	2842.00 ms
Nuxt	2919.00 ms
React Router	3237.00 ms
Next.js	4678.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
SvelteKit	63.00 ms
Nuxt	65.00 ms
SolidStart	72.00 ms
React Router	75.00 ms
TanStack Start	141.00 ms
Next.js	654.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	36.00 ms
Astro	45.00 ms
Nuxt	127.00 ms
SvelteKit	137.00 ms
React Router	160.00 ms
SolidStart	168.00 ms
TanStack Start	258.00 ms
Next.js	2302.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	69.00 ms
Astro	87.00 ms
SolidStart	161.00 ms
Nuxt	189.00 ms
SvelteKit	225.00 ms
TanStack Start	252.00 ms
React Router	281.00 ms
Next.js	2681.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
SvelteKit	57.00 ms
Nuxt	58.00 ms
SolidStart	62.00 ms
React Router	71.00 ms
TanStack Start	120.00 ms
Next.js	641.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	43.00 ms
SolidStart	104.00 ms
SvelteKit	110.00 ms
Nuxt	117.00 ms
React Router	142.00 ms
TanStack Start	173.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	59.00 ms
Astro	84.00 ms
SolidStart	124.00 ms
SvelteKit	160.00 ms
Nuxt	176.00 ms
TanStack Start	176.00 ms
React Router	264.00 ms
Next.js	1043.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	1	2040ms	4747ms	4630ms	1,090
Nuxt	73	5	1939ms	4132ms	4200ms	2,346
React Router	163.6	10	304ms	1666ms	4102ms	5,476
TanStack Start	41	5	4496ms	4284ms	4523ms	1,259

P99 Latency

P99 Latency at 25 Connections

P99 Latency at 25 Connections chart

P99 Latency at 25 Connections data

Framework	Milliseconds
React Router	304.00 ms
Nuxt	1939.00 ms
Next.js	2040.00 ms
TanStack Start	4496.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	1666.00 ms
Nuxt	4132.00 ms
TanStack Start	4284.00 ms
Next.js	4747.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	4102.00 ms
Nuxt	4200.00 ms
TanStack Start	4523.00 ms
Next.js	4630.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	347.00 ms
TanStack Start	672.00 ms
Next.js	731.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	307.00 ms
Nuxt	474.00 ms
TanStack Start	880.00 ms
Next.js	2449.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	414.00 ms
Nuxt	543.00 ms
TanStack Start	1492.00 ms
Next.js	2817.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	150.00 ms
Nuxt	344.00 ms
TanStack Start	594.00 ms
Next.js	723.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	300.00 ms
Nuxt	449.00 ms
TanStack Start	594.00 ms
Next.js	1146.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	385.00 ms
Nuxt	444.00 ms
TanStack Start	577.00 ms
Next.js	1154.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.