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.34ms	1.42ms	1.13ms	0.3ms	0ms
Next.js	339ms	339.2ms	21.29ms	1.32ms	7.82ms	12.14ms
Nuxt	159ms	158.98ms	11.83ms	0.45ms	2.29ms	9.08ms
React Router	177.6ms	177.77ms	22.33ms	2.33ms	2.34ms	17.65ms
SolidStart	111ms	111.28ms	17.2ms	1.5ms	2.24ms	13.46ms
SvelteKit	109.4ms	109.51ms	16.01ms	0.62ms	3.09ms	12.31ms
TanStack Start	145.6ms	145.45ms	29.87ms	1.58ms	13.52ms	14.77ms

First Paint (ms)

First Paint (ms) chart

First Paint (ms) data

Framework	Milliseconds
SvelteKit	109.40 ms
Astro	110.20 ms
SolidStart	111.00 ms
TanStack Start	145.60 ms
Nuxt	159.00 ms
React Router	177.60 ms
Next.js	339.00 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	109.51 ms
Astro	110.34 ms
SolidStart	111.28 ms
TanStack Start	145.45 ms
Nuxt	158.98 ms
React Router	177.77 ms
Next.js	339.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.20 ms

Median: 17.20 ms

1.42 ms

11.83 ms

16.01 ms

17.20 ms

21.29 ms

22.33 ms

29.87 ms

Interaction Breakdown data

Framework or version	Interaction latency	Input delay	Processing duration	Presentation delay
Astro	1.42 ms	1.13 ms	0.30 ms	0.00 ms
Nuxt	11.83 ms	0.45 ms	2.29 ms	9.08 ms
SvelteKit	16.01 ms	0.62 ms	3.09 ms	12.31 ms
SolidStart	17.20 ms	1.50 ms	2.24 ms	13.46 ms
Next.js	21.29 ms	1.32 ms	7.82 ms	12.14 ms
React Router	22.33 ms	2.33 ms	2.34 ms	17.65 ms
TanStack Start	29.87 ms	1.58 ms	13.52 ms	14.77 ms

Server Side Rendered Tests

Methodology: Server Side Rendered Tests.

Framework	First Paint	FCP	Interaction Latency	Input Delay	Processing Duration	Presentation Delay
Astro	65.4ms	65.22ms	1.46ms	0.59ms	0.87ms	0ms
Next.js	159.2ms	159.09ms	21.55ms	1.96ms	8.22ms	11.38ms
Nuxt	104.8ms	104.72ms	13.63ms	0.46ms	1.75ms	11.42ms
React Router	131ms	131.04ms	18.5ms	2.12ms	2.83ms	13.54ms
SolidStart	98.4ms	98.62ms	14.53ms	0.94ms	2.31ms	11.28ms
SvelteKit	92.8ms	92.63ms	19.8ms	0.73ms	2.62ms	16.45ms
TanStack Start	135.6ms	135.59ms	35.6ms	2.88ms	18.93ms	13.79ms

First Paint (ms)

First Paint (ms) chart

First Paint (ms) data

Framework	Milliseconds
Astro	65.40 ms
SvelteKit	92.80 ms
SolidStart	98.40 ms
Nuxt	104.80 ms
React Router	131.00 ms
TanStack Start	135.60 ms
Next.js	159.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	65.22 ms
SvelteKit	92.63 ms
SolidStart	98.62 ms
Nuxt	104.72 ms
React Router	131.04 ms
TanStack Start	135.59 ms
Next.js	159.09 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.50 ms

Median: 18.50 ms

1.46 ms

13.63 ms

14.53 ms

18.50 ms

19.80 ms

21.55 ms

35.60 ms

Interaction Breakdown data

Framework or version	Interaction latency	Input delay	Processing duration	Presentation delay
Astro	1.46 ms	0.59 ms	0.87 ms	0.00 ms
Nuxt	13.63 ms	0.46 ms	1.75 ms	11.42 ms
SolidStart	14.53 ms	0.94 ms	2.31 ms	11.28 ms
React Router	18.50 ms	2.12 ms	2.83 ms	13.54 ms
SvelteKit	19.80 ms	0.73 ms	2.62 ms	16.45 ms
Next.js	21.55 ms	1.96 ms	8.22 ms	11.38 ms
TanStack Start	35.60 ms	2.88 ms	18.93 ms	13.79 ms

Server Side Throughput Tests

Methodology: Server Side Throughput Tests.

Framework	Ops/sec	Median Latency	Body Size	Duplication
Baseline HTML	838	1.209ms	96.83kb	1x
Astro	661	1.449ms	96.89kb	1x
Next.js	212	4.773ms	199.57kb	2x
Nuxt	265	3.663ms	201.57kb	2x
React Router	332	2.965ms	216.9kb	2x
SolidStart	430	2.238ms	224.17kb	2x
SvelteKit	459	2.12ms	183.53kb	2x
TanStack Start	228	4.289ms	193.62kb	2x

Ops/sec

Ops/sec chart

Ops/sec data

Framework	Operations per second
Baseline HTML	838
Astro	661
SvelteKit	459
SolidStart	430
React Router	332
Nuxt	265
TanStack Start	228
Next.js	212

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.45 ms
SvelteKit	2.12 ms
SolidStart	2.24 ms
React Router	2.96 ms
Nuxt	3.66 ms
TanStack Start	4.29 ms
Next.js	4.77 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,661.8	200	20ms	41ms	116ms	49,001
Astro	1,215.8	25	31ms	65ms	288ms	37,153
Next.js	45	5	1820ms	4764ms	4673ms	1,257
Nuxt	455	50	86ms	491ms	2927ms	14,896
React Router	345.6	50	99ms	488ms	3298ms	11,408
SolidStart	534.21	5	92ms	425ms	2099ms	17,552
SvelteKit	489.4	50	87ms	374ms	2470ms	15,742
TanStack Start	294.2	25	154ms	1501ms	2721ms	9,559

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	31.00 ms
Nuxt	86.00 ms
SvelteKit	87.00 ms
SolidStart	92.00 ms
React Router	99.00 ms
TanStack Start	154.00 ms
Next.js	1820.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	41.00 ms
Astro	65.00 ms
SvelteKit	374.00 ms
SolidStart	425.00 ms
React Router	488.00 ms
Nuxt	491.00 ms
TanStack Start	1501.00 ms
Next.js	4764.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	116.00 ms
Astro	288.00 ms
SolidStart	2099.00 ms
SvelteKit	2470.00 ms
TanStack Start	2721.00 ms
Nuxt	2927.00 ms
React Router	3298.00 ms
Next.js	4673.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	17.00 ms
Astro	21.00 ms
Nuxt	57.00 ms
SvelteKit	60.00 ms
SolidStart	66.00 ms
React Router	73.00 ms
TanStack Start	122.00 ms
Next.js	656.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	119.00 ms
SvelteKit	126.00 ms
SolidStart	143.00 ms
React Router	144.00 ms
TanStack Start	249.00 ms
Next.js	2324.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	78.00 ms
Astro	84.00 ms
SolidStart	198.00 ms
Nuxt	202.00 ms
SvelteKit	215.00 ms
TanStack Start	261.00 ms
React Router	282.00 ms
Next.js	2662.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	16.00 ms
Astro	21.00 ms
SvelteKit	53.00 ms
Nuxt	54.00 ms
SolidStart	56.00 ms
React Router	72.00 ms
TanStack Start	102.00 ms
Next.js	647.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	34.00 ms
Astro	42.00 ms
SolidStart	90.00 ms
SvelteKit	106.00 ms
Nuxt	109.00 ms
React Router	142.00 ms
TanStack Start	167.00 ms
Next.js	1071.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	81.00 ms
SolidStart	121.00 ms
SvelteKit	161.00 ms
TanStack Start	173.00 ms
Nuxt	179.00 ms
React Router	256.00 ms
Next.js	1042.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.8	1	2011ms	4797ms	4783ms	1,152
Nuxt	74	10	1940ms	4120ms	4210ms	2,347
React Router	172.4	10	290ms	1677ms	4001ms	5,738
TanStack Start	45	5	3102ms	4158ms	4721ms	1,404

P99 Latency

P99 Latency at 25 Connections

P99 Latency at 25 Connections chart

P99 Latency at 25 Connections data

Framework	Milliseconds
React Router	290.00 ms
Nuxt	1940.00 ms
Next.js	2011.00 ms
TanStack Start	3102.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	1677.00 ms
Nuxt	4120.00 ms
TanStack Start	4158.00 ms
Next.js	4797.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	4001.00 ms
Nuxt	4210.00 ms
TanStack Start	4721.00 ms
Next.js	4783.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	159.00 ms
Nuxt	345.00 ms
TanStack Start	688.00 ms
Next.js	701.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	290.00 ms
Nuxt	486.00 ms
TanStack Start	747.00 ms
Next.js	2438.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	401.00 ms
Nuxt	533.00 ms
TanStack Start	1340.00 ms
Next.js	2822.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	343.00 ms
TanStack Start	565.00 ms
Next.js	688.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	285.00 ms
Nuxt	444.00 ms
TanStack Start	580.00 ms
Next.js	1132.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	371.00 ms
Nuxt	460.00 ms
TanStack Start	624.00 ms
Next.js	1103.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.