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	105.4ms	105.29ms	1.79ms	1.48ms	0.32ms	0ms
Next.js	338.8ms	339.13ms	19.63ms	1.43ms	6.11ms	12.09ms
Nuxt	180.8ms	180.81ms	8.28ms	0.87ms	1.27ms	6.14ms
React Router	177.8ms	177.7ms	21.13ms	1.68ms	3.61ms	15.84ms
SolidStart	100.8ms	100.8ms	14.56ms	0.9ms	2.97ms	10.69ms
SvelteKit	112ms	111.86ms	15.62ms	0.95ms	2.85ms	11.83ms
TanStack Start	141.8ms	141.59ms	31.69ms	2.06ms	15.27ms	14.36ms

First Paint (ms)

First Paint (ms) chart

First Paint (ms) data

Framework	Milliseconds
SolidStart	100.80 ms
Astro	105.40 ms
SvelteKit	112.00 ms
TanStack Start	141.80 ms
React Router	177.80 ms
Nuxt	180.80 ms
Next.js	338.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	100.80 ms
Astro	105.29 ms
SvelteKit	111.86 ms
TanStack Start	141.59 ms
React Router	177.70 ms
Nuxt	180.81 ms
Next.js	339.13 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.62 ms

Median: 15.62 ms

1.79 ms

8.28 ms

14.56 ms

15.62 ms

19.63 ms

21.13 ms

31.69 ms

Interaction Breakdown data

Framework or version	Interaction latency	Input delay	Processing duration	Presentation delay
Astro	1.79 ms	1.48 ms	0.32 ms	0.00 ms
Nuxt	8.28 ms	0.87 ms	1.27 ms	6.14 ms
SolidStart	14.56 ms	0.90 ms	2.97 ms	10.69 ms
SvelteKit	15.62 ms	0.95 ms	2.85 ms	11.83 ms
Next.js	19.63 ms	1.43 ms	6.11 ms	12.09 ms
React Router	21.13 ms	1.68 ms	3.61 ms	15.84 ms
TanStack Start	31.69 ms	2.06 ms	15.27 ms	14.36 ms

Server Side Rendered Tests

Methodology: Server Side Rendered Tests.

Framework	First Paint	FCP	Interaction Latency	Input Delay	Processing Duration	Presentation Delay
Astro	80.4ms	80.43ms	0.94ms	0.64ms	0.3ms	0ms
Next.js	163.2ms	163.2ms	17.59ms	1.22ms	7.5ms	8.86ms
Nuxt	113.2ms	113.23ms	13.52ms	1.49ms	1.8ms	10.23ms
React Router	121.8ms	121.76ms	24.7ms	2.67ms	3.55ms	18.47ms
SolidStart	87.8ms	87.76ms	15.05ms	0.94ms	2.66ms	11.45ms
SvelteKit	89ms	88.87ms	17.67ms	0.58ms	2.99ms	14.11ms
TanStack Start	111.2ms	111.32ms	32.29ms	2.39ms	16.09ms	13.81ms

First Paint (ms)

First Paint (ms) chart

First Paint (ms) data

Framework	Milliseconds
Astro	80.40 ms
SolidStart	87.80 ms
SvelteKit	89.00 ms
TanStack Start	111.20 ms
Nuxt	113.20 ms
React Router	121.80 ms
Next.js	163.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	80.43 ms
SolidStart	87.76 ms
SvelteKit	88.87 ms
TanStack Start	111.32 ms
Nuxt	113.23 ms
React Router	121.76 ms
Next.js	163.20 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.59 ms

Median: 17.59 ms

0.94 ms

13.52 ms

15.05 ms

17.59 ms

17.67 ms

24.70 ms

32.29 ms

Interaction Breakdown data

Framework or version	Interaction latency	Input delay	Processing duration	Presentation delay
Astro	0.94 ms	0.64 ms	0.30 ms	0.00 ms
Nuxt	13.52 ms	1.49 ms	1.80 ms	10.23 ms
SolidStart	15.05 ms	0.94 ms	2.66 ms	11.45 ms
Next.js	17.59 ms	1.22 ms	7.50 ms	8.86 ms
SvelteKit	17.67 ms	0.58 ms	2.99 ms	14.11 ms
React Router	24.70 ms	2.67 ms	3.55 ms	18.47 ms
TanStack Start	32.29 ms	2.39 ms	16.09 ms	13.81 ms

Server Side Throughput Tests

Methodology: Server Side Throughput Tests.

Framework	Ops/sec	Median Latency	Body Size	Duplication
Baseline HTML	837	1.213ms	96.83kb	1x
Astro	729	1.327ms	96.89kb	1x
Next.js	228	4.576ms	199.57kb	2x
Nuxt	375	2.586ms	201.73kb	2x
React Router	319	3.052ms	216.9kb	2x
SolidStart	429	2.245ms	224.17kb	2x
SvelteKit	452	2.149ms	183.53kb	2x
TanStack Start	350	2.804ms	191.63kb	2x

Ops/sec

Ops/sec chart

Ops/sec data

Framework	Operations per second
Baseline HTML	837
Astro	729
SvelteKit	452
SolidStart	429
Nuxt	375
TanStack Start	350
React Router	319
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	191.63 KB
Next.js	199.57 KB
Nuxt	201.73 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.33 ms
SvelteKit	2.15 ms
SolidStart	2.25 ms
Nuxt	2.59 ms
TanStack Start	2.80 ms
React Router	3.05 ms
Next.js	4.58 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,675.2	100	22ms	53ms	110ms	48,072
Astro	1,526.8	50	27ms	47ms	84ms	44,848
Next.js	43.6	1	1903ms	4782ms	4703ms	1,218
Nuxt	515	10	71ms	350ms	2855ms	16,970
React Router	333.8	25	105ms	183ms	3475ms	11,112
SolidStart	511.8	5	101ms	523ms	2184ms	16,516
SvelteKit	493.4	10	81ms	438ms	2634ms	15,890
TanStack Start	381.2	5	114ms	893ms	2651ms	12,442

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	27.00 ms
Nuxt	71.00 ms
SvelteKit	81.00 ms
SolidStart	101.00 ms
React Router	105.00 ms
TanStack Start	114.00 ms
Next.js	1903.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	47.00 ms
Baseline HTML	53.00 ms
React Router	183.00 ms
Nuxt	350.00 ms
SvelteKit	438.00 ms
SolidStart	523.00 ms
TanStack Start	893.00 ms
Next.js	4782.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	84.00 ms
Baseline HTML	110.00 ms
SolidStart	2184.00 ms
SvelteKit	2634.00 ms
TanStack Start	2651.00 ms
Nuxt	2855.00 ms
React Router	3475.00 ms
Next.js	4703.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	18.00 ms
Baseline HTML	19.00 ms
Nuxt	50.00 ms
SvelteKit	60.00 ms
React Router	75.00 ms
SolidStart	75.00 ms
TanStack Start	88.00 ms
Next.js	677.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	35.00 ms
Baseline HTML	37.00 ms
Nuxt	103.00 ms
SvelteKit	141.00 ms
React Router	152.00 ms
SolidStart	162.00 ms
TanStack Start	191.00 ms
Next.js	2331.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	69.00 ms
Baseline HTML	80.00 ms
SolidStart	150.00 ms
Nuxt	183.00 ms
SvelteKit	223.00 ms
TanStack Start	251.00 ms
React Router	289.00 ms
Next.js	2675.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	17.00 ms
Baseline HTML	17.00 ms
Nuxt	49.00 ms
SvelteKit	54.00 ms
SolidStart	62.00 ms
TanStack Start	70.00 ms
React Router	73.00 ms
Next.js	666.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	33.00 ms
Baseline HTML	35.00 ms
Nuxt	96.00 ms
SolidStart	100.00 ms
SvelteKit	112.00 ms
React Router	147.00 ms
TanStack Start	155.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
Baseline HTML	62.00 ms
Astro	66.00 ms
SolidStart	124.00 ms
TanStack Start	161.00 ms
Nuxt	167.00 ms
SvelteKit	171.00 ms
React Router	259.00 ms
Next.js	1055.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	40.8	1	1897ms	4687ms	4637ms	1,150
Nuxt	179.6	5	466ms	2646ms	3674ms	5,912
React Router	169.8	5	212ms	1758ms	3823ms	5,724
TanStack Start	165.6	10	569ms	3365ms	3316ms	5,487

P99 Latency

P99 Latency at 25 Connections

P99 Latency at 25 Connections chart

P99 Latency at 25 Connections data

Framework	Milliseconds
React Router	212.00 ms
Nuxt	466.00 ms
TanStack Start	569.00 ms
Next.js	1897.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	1758.00 ms
Nuxt	2646.00 ms
TanStack Start	3365.00 ms
Next.js	4687.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	3316.00 ms
Nuxt	3674.00 ms
React Router	3823.00 ms
Next.js	4637.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
Nuxt	147.00 ms
React Router	172.00 ms
TanStack Start	195.00 ms
Next.js	681.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
Nuxt	292.00 ms
React Router	295.00 ms
TanStack Start	365.00 ms
Next.js	2314.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
Nuxt	316.00 ms
React Router	406.00 ms
TanStack Start	406.00 ms
Next.js	2702.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
Nuxt	137.00 ms
React Router	148.00 ms
TanStack Start	170.00 ms
Next.js	672.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
TanStack Start	257.00 ms
Nuxt	286.00 ms
React Router	291.00 ms
Next.js	1117.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	273.00 ms
Nuxt	293.00 ms
React Router	368.00 ms
Next.js	1073.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.