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	165.6ms	165.34ms	9.99ms	2.37ms	1.56ms	6.05ms
Next.js	396.4ms	396.32ms	21.09ms	2.75ms	6.67ms	11.67ms
Nuxt	266.8ms	266.81ms	13.48ms	1.67ms	2.78ms	9.04ms
React Router	164ms	163.99ms	23.83ms	1.59ms	2.2ms	20.04ms
SolidStart	205.6ms	205.51ms	16.06ms	2.67ms	4.06ms	9.33ms
SvelteKit	118.6ms	118.6ms	17.89ms	0.62ms	2.98ms	14.28ms
TanStack Start	255.8ms	255.77ms	30.22ms	4.21ms	17.06ms	8.95ms

First Paint (ms)

First Paint (ms) chart

First Paint (ms) data

Framework	Milliseconds
SvelteKit	118.60 ms
React Router	164.00 ms
Astro	165.60 ms
SolidStart	205.60 ms
TanStack Start	255.80 ms
Nuxt	266.80 ms
Next.js	396.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
SvelteKit	118.60 ms
React Router	163.99 ms
Astro	165.34 ms
SolidStart	205.51 ms
TanStack Start	255.77 ms
Nuxt	266.81 ms
Next.js	396.32 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.89 ms

Median: 17.89 ms

9.99 ms

13.48 ms

16.06 ms

17.89 ms

21.09 ms

23.83 ms

30.22 ms

Interaction Breakdown data

Framework or version	Interaction latency	Input delay	Processing duration	Presentation delay
Astro	9.99 ms	2.37 ms	1.56 ms	6.05 ms
Nuxt	13.48 ms	1.67 ms	2.78 ms	9.04 ms
SolidStart	16.06 ms	2.67 ms	4.06 ms	9.33 ms
SvelteKit	17.89 ms	0.62 ms	2.98 ms	14.28 ms
Next.js	21.09 ms	2.75 ms	6.67 ms	11.67 ms
React Router	23.83 ms	1.59 ms	2.20 ms	20.04 ms
TanStack Start	30.22 ms	4.21 ms	17.06 ms	8.95 ms

Server Side Rendered Tests

Methodology: Server Side Rendered Tests.

Framework	First Paint	FCP	Interaction Latency	Input Delay	Processing Duration	Presentation Delay
Astro	131.8ms	131.76ms	4.65ms	2.16ms	1.45ms	1.04ms
Next.js	145ms	144.97ms	18.78ms	2.26ms	7.73ms	8.8ms
Nuxt	102.2ms	102.18ms	13.1ms	0.35ms	1.63ms	11.13ms
React Router	191.8ms	191.97ms	19.52ms	2.59ms	4.13ms	12.8ms
SolidStart	82.4ms	82.45ms	14.01ms	0.85ms	2.05ms	11.12ms
SvelteKit	102.6ms	102.61ms	16.14ms	0.71ms	2.84ms	12.59ms
TanStack Start	134.4ms	134.35ms	35.21ms	2.23ms	19.78ms	13.21ms

First Paint (ms)

First Paint (ms) chart

First Paint (ms) data

Framework	Milliseconds
SolidStart	82.40 ms
Nuxt	102.20 ms
SvelteKit	102.60 ms
Astro	131.80 ms
TanStack Start	134.40 ms
Next.js	145.00 ms
React Router	191.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	82.45 ms
Nuxt	102.18 ms
SvelteKit	102.61 ms
Astro	131.76 ms
TanStack Start	134.35 ms
Next.js	144.97 ms
React Router	191.97 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.14 ms

Median: 16.14 ms

4.65 ms

13.10 ms

14.01 ms

16.14 ms

18.78 ms

19.52 ms

35.21 ms

Interaction Breakdown data

Framework or version	Interaction latency	Input delay	Processing duration	Presentation delay
Astro	4.65 ms	2.16 ms	1.45 ms	1.04 ms
Nuxt	13.10 ms	0.35 ms	1.63 ms	11.13 ms
SolidStart	14.01 ms	0.85 ms	2.05 ms	11.12 ms
SvelteKit	16.14 ms	0.71 ms	2.84 ms	12.59 ms
Next.js	18.78 ms	2.26 ms	7.73 ms	8.80 ms
React Router	19.52 ms	2.59 ms	4.13 ms	12.80 ms
TanStack Start	35.21 ms	2.23 ms	19.78 ms	13.21 ms

Server Side Throughput Tests

Methodology: Server Side Throughput Tests.

Framework	Ops/sec	Median Latency	Body Size	Duplication
Baseline HTML	847	1.202ms	96.83kb	1x
Astro	677	1.423ms	96.89kb	1x
Next.js	242	4.391ms	199.52kb	2x
Nuxt	346	2.805ms	201.57kb	2x
React Router	346	2.856ms	216.9kb	2x
SolidStart	419	2.312ms	224.17kb	2x
SvelteKit	463	2.094ms	183.53kb	2x
TanStack Start	315	3.13ms	193.62kb	2x

Ops/sec

Ops/sec chart

Ops/sec data

Framework	Operations per second
Baseline HTML	847
Astro	677
SvelteKit	463
SolidStart	419
Nuxt	346
React Router	346
TanStack Start	315
Next.js	242

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.52 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.42 ms
SvelteKit	2.09 ms
SolidStart	2.31 ms
Nuxt	2.81 ms
React Router	2.86 ms
TanStack Start	3.13 ms
Next.js	4.39 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,416.6	200	22ms	55ms	110ms	42,415
Astro	1,190.6	50	29ms	62ms	295ms	36,339
Next.js	44	1	1798ms	4720ms	4754ms	1,240
Nuxt	434.8	5	83ms	568ms	3038ms	14,221
React Router	341.8	10	106ms	512ms	3311ms	11,371
SolidStart	505	25	99ms	393ms	2144ms	16,552
SvelteKit	505	50	76ms	259ms	2358ms	16,126
TanStack Start	290.8	10	177ms	1824ms	2865ms	9,449

P99 Latency

P99 Latency at 25 Connections

P99 Latency at 25 Connections chart

P99 Latency at 25 Connections data

Framework	Milliseconds
Baseline HTML	22.00 ms
Astro	29.00 ms
SvelteKit	76.00 ms
Nuxt	83.00 ms
SolidStart	99.00 ms
React Router	106.00 ms
TanStack Start	177.00 ms
Next.js	1798.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	55.00 ms
Astro	62.00 ms
SvelteKit	259.00 ms
SolidStart	393.00 ms
React Router	512.00 ms
Nuxt	568.00 ms
TanStack Start	1824.00 ms
Next.js	4720.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	110.00 ms
Astro	295.00 ms
SolidStart	2144.00 ms
SvelteKit	2358.00 ms
TanStack Start	2865.00 ms
Nuxt	3038.00 ms
React Router	3311.00 ms
Next.js	4754.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	20.00 ms
Astro	22.00 ms
SvelteKit	58.00 ms
Nuxt	60.00 ms
SolidStart	71.00 ms
React Router	74.00 ms
TanStack Start	131.00 ms
Next.js	639.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	39.00 ms
Astro	44.00 ms
SvelteKit	113.00 ms
Nuxt	126.00 ms
React Router	152.00 ms
SolidStart	152.00 ms
TanStack Start	269.00 ms
Next.js	2310.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	86.00 ms
Astro	88.00 ms
SolidStart	146.00 ms
Nuxt	206.00 ms
SvelteKit	226.00 ms
TanStack Start	260.00 ms
React Router	286.00 ms
Next.js	2679.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	19.00 ms
Astro	21.00 ms
SvelteKit	52.00 ms
SolidStart	58.00 ms
Nuxt	59.00 ms
React Router	72.00 ms
TanStack Start	106.00 ms
Next.js	634.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	38.00 ms
Astro	42.00 ms
SolidStart	97.00 ms
SvelteKit	102.00 ms
Nuxt	117.00 ms
React Router	143.00 ms
TanStack Start	168.00 ms
Next.js	1056.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	75.00 ms
Astro	84.00 ms
SolidStart	130.00 ms
TanStack Start	178.00 ms
SvelteKit	181.00 ms
Nuxt	184.00 ms
React Router	259.00 ms
Next.js	1077.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.4	1	1965ms	4664ms	4721ms	1,167
Nuxt	72	10	1963ms	4163ms	4126ms	2,293
React Router	173.4	25	258ms	1569ms	3997ms	5,848
TanStack Start	44.2	5	4044ms	4372ms	4541ms	1,354

P99 Latency

P99 Latency at 25 Connections

P99 Latency at 25 Connections chart

P99 Latency at 25 Connections data

Framework	Milliseconds
React Router	258.00 ms
Nuxt	1963.00 ms
Next.js	1965.00 ms
TanStack Start	4044.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	1569.00 ms
Nuxt	4163.00 ms
TanStack Start	4372.00 ms
Next.js	4664.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	3997.00 ms
Nuxt	4126.00 ms
TanStack Start	4541.00 ms
Next.js	4721.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	150.00 ms
Nuxt	349.00 ms
Next.js	686.00 ms
TanStack Start	886.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	292.00 ms
Nuxt	496.00 ms
TanStack Start	838.00 ms
Next.js	2379.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	412.00 ms
Nuxt	606.00 ms
TanStack Start	1262.00 ms
Next.js	2761.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	141.00 ms
Nuxt	347.00 ms
TanStack Start	490.00 ms
Next.js	676.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	286.00 ms
Nuxt	458.00 ms
TanStack Start	570.00 ms
Next.js	1080.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	370.00 ms
Nuxt	455.00 ms
TanStack Start	535.00 ms
Next.js	1095.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.