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	93.6ms	93.57ms	5.12ms	2.95ms	0.99ms	1.18ms
Next.js	338.2ms	338.4ms	18.94ms	1.29ms	6.12ms	11.53ms
Nuxt	162ms	162.21ms	13.6ms	0.68ms	1.9ms	11.02ms
React Router	171.6ms	171.63ms	19.73ms	1.52ms	2.86ms	15.35ms
SolidStart	109.8ms	109.84ms	17.48ms	1.87ms	2.14ms	13.47ms
SvelteKit	107.8ms	107.99ms	13.76ms	0.59ms	2.27ms	10.9ms
TanStack Start	160.2ms	160.1ms	28.89ms	2.05ms	15.55ms	11.3ms

First Paint (ms)

First Paint (ms) chart

First Paint (ms) data

Framework	Milliseconds
Astro	93.60 ms
SvelteKit	107.80 ms
SolidStart	109.80 ms
TanStack Start	160.20 ms
Nuxt	162.00 ms
React Router	171.60 ms
Next.js	338.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	93.57 ms
SvelteKit	107.99 ms
SolidStart	109.84 ms
TanStack Start	160.10 ms
Nuxt	162.21 ms
React Router	171.63 ms
Next.js	338.40 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.48 ms

Median: 17.48 ms

5.12 ms

13.60 ms

13.76 ms

17.48 ms

18.94 ms

19.73 ms

28.89 ms

Interaction Breakdown data

Framework or version	Interaction latency	Input delay	Processing duration	Presentation delay
Astro	5.12 ms	2.95 ms	0.99 ms	1.18 ms
Nuxt	13.60 ms	0.68 ms	1.90 ms	11.02 ms
SvelteKit	13.76 ms	0.59 ms	2.27 ms	10.90 ms
SolidStart	17.48 ms	1.87 ms	2.14 ms	13.47 ms
Next.js	18.94 ms	1.29 ms	6.12 ms	11.53 ms
React Router	19.73 ms	1.52 ms	2.86 ms	15.35 ms
TanStack Start	28.89 ms	2.05 ms	15.55 ms	11.30 ms

Server Side Rendered Tests

Methodology: Server Side Rendered Tests.

Framework	First Paint	FCP	Interaction Latency	Input Delay	Processing Duration	Presentation Delay
Astro	64.6ms	64.4ms	1.9ms	1.47ms	0.43ms	0ms
Next.js	165.6ms	165.52ms	19.99ms	1.37ms	9.16ms	9.46ms
Nuxt	124ms	124.05ms	10.15ms	0.82ms	1.46ms	7.87ms
React Router	129.6ms	129.5ms	19.61ms	1.52ms	2.6ms	15.49ms
SolidStart	101.2ms	101.13ms	14.19ms	0.85ms	2.67ms	10.66ms
SvelteKit	88.4ms	88.41ms	16.16ms	1.37ms	2.96ms	11.83ms
TanStack Start	131.8ms	131.73ms	33.95ms	1.65ms	16.66ms	15.63ms

First Paint (ms)

First Paint (ms) chart

First Paint (ms) data

Framework	Milliseconds
Astro	64.60 ms
SvelteKit	88.40 ms
SolidStart	101.20 ms
Nuxt	124.00 ms
React Router	129.60 ms
TanStack Start	131.80 ms
Next.js	165.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	64.40 ms
SvelteKit	88.41 ms
SolidStart	101.13 ms
Nuxt	124.05 ms
React Router	129.50 ms
TanStack Start	131.73 ms
Next.js	165.52 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.16 ms

Median: 16.16 ms

1.90 ms

10.15 ms

14.19 ms

16.16 ms

19.61 ms

19.99 ms

33.95 ms

Interaction Breakdown data

Framework or version	Interaction latency	Input delay	Processing duration	Presentation delay
Astro	1.90 ms	1.47 ms	0.43 ms	0.00 ms
Nuxt	10.15 ms	0.82 ms	1.46 ms	7.87 ms
SolidStart	14.19 ms	0.85 ms	2.67 ms	10.66 ms
SvelteKit	16.16 ms	1.37 ms	2.96 ms	11.83 ms
React Router	19.61 ms	1.52 ms	2.60 ms	15.49 ms
Next.js	19.99 ms	1.37 ms	9.16 ms	9.46 ms
TanStack Start	33.95 ms	1.65 ms	16.66 ms	15.63 ms

Server Side Throughput Tests

Methodology: Server Side Throughput Tests.

Framework	Ops/sec	Median Latency	Body Size	Duplication
Baseline HTML	847	1.203ms	96.83kb	1x
Astro	665	1.441ms	96.89kb	1x
Next.js	229	4.521ms	199.57kb	2x
Nuxt	372	2.591ms	201.57kb	2x
React Router	345	2.855ms	216.9kb	2x
SolidStart	422	2.276ms	224.17kb	2x
SvelteKit	452	2.131ms	183.54kb	2x
TanStack Start	307	3.189ms	193.62kb	2x

Ops/sec

Ops/sec chart

Ops/sec data

Framework	Operations per second
Baseline HTML	847
Astro	665
SvelteKit	452
SolidStart	422
Nuxt	372
React Router	345
TanStack Start	307
Next.js	229

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.54 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
SvelteKit	2.13 ms
SolidStart	2.28 ms
Nuxt	2.59 ms
React Router	2.85 ms
TanStack Start	3.19 ms
Next.js	4.52 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,770.6	200	20ms	43ms	102ms	49,644
Astro	1,220.6	100	28ms	62ms	272ms	37,361
Next.js	46	1	1741ms	4653ms	4785ms	1,295
Nuxt	492.2	10	78ms	435ms	2886ms	15,764
React Router	326.61	25	108ms	187ms	3571ms	10,788
SolidStart	536.8	10	96ms	384ms	2075ms	17,556
SvelteKit	500.4	10	88ms	513ms	2116ms	15,274
TanStack Start	297.4	25	154ms	1553ms	2832ms	9,756

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	28.00 ms
Nuxt	78.00 ms
SvelteKit	88.00 ms
SolidStart	96.00 ms
React Router	108.00 ms
TanStack Start	154.00 ms
Next.js	1741.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	43.00 ms
Astro	62.00 ms
React Router	187.00 ms
SolidStart	384.00 ms
Nuxt	435.00 ms
SvelteKit	513.00 ms
TanStack Start	1553.00 ms
Next.js	4653.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	102.00 ms
Astro	272.00 ms
SolidStart	2075.00 ms
SvelteKit	2116.00 ms
TanStack Start	2832.00 ms
Nuxt	2886.00 ms
React Router	3571.00 ms
Next.js	4785.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	21.00 ms
Nuxt	51.00 ms
SvelteKit	65.00 ms
SolidStart	69.00 ms
React Router	77.00 ms
TanStack Start	113.00 ms
Next.js	631.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	35.00 ms
Astro	42.00 ms
Nuxt	115.00 ms
SvelteKit	136.00 ms
SolidStart	147.00 ms
React Router	160.00 ms
TanStack Start	249.00 ms
Next.js	2288.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	75.00 ms
Astro	82.00 ms
SolidStart	160.00 ms
Nuxt	190.00 ms
SvelteKit	261.00 ms
TanStack Start	277.00 ms
React Router	291.00 ms
Next.js	2489.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	20.00 ms
Nuxt	50.00 ms
SolidStart	56.00 ms
SvelteKit	59.00 ms
React Router	75.00 ms
TanStack Start	96.00 ms
Next.js	625.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	41.00 ms
SolidStart	90.00 ms
Nuxt	108.00 ms
SvelteKit	115.00 ms
React Router	154.00 ms
TanStack Start	159.00 ms
Next.js	1041.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	67.00 ms
Astro	81.00 ms
SolidStart	123.00 ms
TanStack Start	164.00 ms
Nuxt	178.00 ms
SvelteKit	191.00 ms
React Router	264.00 ms
Next.js	1033.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	42	1	1930ms	4688ms	4652ms	1,188
Nuxt	72	10	1921ms	4187ms	4283ms	2,297
React Router	170.2	25	303ms	1647ms	3975ms	5,450
TanStack Start	43.4	5	3322ms	4355ms	4416ms	1,341

P99 Latency

P99 Latency at 25 Connections

P99 Latency at 25 Connections chart

P99 Latency at 25 Connections data

Framework	Milliseconds
React Router	303.00 ms
Nuxt	1921.00 ms
Next.js	1930.00 ms
TanStack Start	3322.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	1647.00 ms
Nuxt	4187.00 ms
TanStack Start	4355.00 ms
Next.js	4688.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	3975.00 ms
Nuxt	4283.00 ms
TanStack Start	4416.00 ms
Next.js	4652.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	153.00 ms
Nuxt	350.00 ms
Next.js	670.00 ms
TanStack Start	779.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	322.00 ms
Nuxt	488.00 ms
TanStack Start	762.00 ms
Next.js	2359.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	419.00 ms
Nuxt	652.00 ms
TanStack Start	1222.00 ms
Next.js	2602.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	348.00 ms
TanStack Start	588.00 ms
Next.js	663.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	317.00 ms
Nuxt	451.00 ms
TanStack Start	583.00 ms
Next.js	1145.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	387.00 ms
Nuxt	454.00 ms
TanStack Start	518.00 ms
Next.js	1061.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.