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	102.2ms	102.17ms	2.26ms	1.96ms	0.3ms	0ms
Next.js	340.2ms	340.14ms	17.5ms	1.45ms	4.93ms	11.12ms
Nuxt	150.4ms	150.21ms	9.67ms	0.89ms	1.24ms	7.54ms
Pracht	107.2ms	107.16ms	22.86ms	0.96ms	3.14ms	18.77ms
React Router	162ms	162.16ms	17.72ms	1.51ms	3.01ms	13.2ms
SolidStart	101ms	100.96ms	20.58ms	2.2ms	2.77ms	15.6ms
SvelteKit	118.2ms	117.93ms	16.05ms	1.22ms	1.97ms	12.86ms
TanStack Start	130.6ms	130.64ms	21.8ms	1.31ms	3.02ms	17.46ms

First Paint (ms)

First Paint (ms) chart

First Paint (ms) data

Framework	Milliseconds
SolidStart	101.00 ms
Astro	102.20 ms
Pracht	107.20 ms
SvelteKit	118.20 ms
TanStack Start	130.60 ms
Nuxt	150.40 ms
React Router	162.00 ms
Next.js	340.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
SolidStart	100.96 ms
Astro	102.17 ms
Pracht	107.16 ms
SvelteKit	117.93 ms
TanStack Start	130.64 ms
Nuxt	150.21 ms
React Router	162.16 ms
Next.js	340.14 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.61 ms

Median: 17.50 ms

2.26 ms

9.67 ms

16.05 ms

17.50 ms

17.72 ms

20.58 ms

21.80 ms

22.86 ms

Interaction Breakdown data

Framework or version	Interaction latency	Input delay	Processing duration	Presentation delay
Astro	2.26 ms	1.96 ms	0.30 ms	0.00 ms
Nuxt	9.67 ms	0.89 ms	1.24 ms	7.54 ms
SvelteKit	16.05 ms	1.22 ms	1.97 ms	12.86 ms
Next.js	17.50 ms	1.45 ms	4.93 ms	11.12 ms
React Router	17.72 ms	1.51 ms	3.01 ms	13.20 ms
SolidStart	20.58 ms	2.20 ms	2.77 ms	15.60 ms
TanStack Start	21.80 ms	1.31 ms	3.02 ms	17.46 ms
Pracht	22.86 ms	0.96 ms	3.14 ms	18.77 ms

Server Side Rendered Tests

Methodology: Server Side Rendered Tests.

Framework	First Paint	FCP	Interaction Latency	Input Delay	Processing Duration	Presentation Delay
Astro	63.2ms	63.25ms	0.89ms	0.64ms	0.26ms	0ms
Next.js	367.4ms	367.4ms	18.46ms	1.41ms	6.6ms	10.45ms
Nuxt	84.2ms	84.26ms	11.02ms	1.14ms	1.21ms	8.67ms
Pracht	81.2ms	81.18ms	15.99ms	1.46ms	2.49ms	12.04ms
React Router	112.6ms	112.51ms	16.87ms	1.49ms	2.78ms	12.6ms
SolidStart	85.4ms	85.61ms	13.19ms	0.88ms	2.64ms	9.66ms
SvelteKit	89.4ms	89.46ms	17.55ms	1.11ms	1.71ms	14.73ms
TanStack Start	96.8ms	96.76ms	19.43ms	1.44ms	3.7ms	14.29ms

First Paint (ms)

First Paint (ms) chart

First Paint (ms) data

Framework	Milliseconds
Astro	63.20 ms
Pracht	81.20 ms
Nuxt	84.20 ms
SolidStart	85.40 ms
SvelteKit	89.40 ms
TanStack Start	96.80 ms
React Router	112.60 ms
Next.js	367.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
Astro	63.25 ms
Pracht	81.18 ms
Nuxt	84.26 ms
SolidStart	85.61 ms
SvelteKit	89.46 ms
TanStack Start	96.76 ms
React Router	112.51 ms
Next.js	367.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: 16.43 ms

Median: 16.87 ms

0.89 ms

11.02 ms

13.19 ms

15.99 ms

16.87 ms

17.55 ms

18.46 ms

19.43 ms

Interaction Breakdown data

Framework or version	Interaction latency	Input delay	Processing duration	Presentation delay
Astro	0.89 ms	0.64 ms	0.26 ms	0.00 ms
Nuxt	11.02 ms	1.14 ms	1.21 ms	8.67 ms
SolidStart	13.19 ms	0.88 ms	2.64 ms	9.66 ms
Pracht	15.99 ms	1.46 ms	2.49 ms	12.04 ms
React Router	16.87 ms	1.49 ms	2.78 ms	12.60 ms
SvelteKit	17.55 ms	1.11 ms	1.71 ms	14.73 ms
Next.js	18.46 ms	1.41 ms	6.60 ms	10.45 ms
TanStack Start	19.43 ms	1.44 ms	3.70 ms	14.29 ms

Server Side Throughput Tests

Methodology: Server Side Throughput Tests.

Framework	Ops/sec	Median Latency	Body Size	Duplication
Baseline HTML	830	1.218ms	96.83kb	1x
Astro	724	1.341ms	96.89kb	1x
Next.js	130	7.423ms	204.56kb	2x
Nuxt	389	2.49ms	201.73kb	2x
Pracht	570	1.692ms	187.02kb	2x
React Router	349	2.834ms	216.98kb	2x
SolidStart	376	2.62ms	224.26kb	2x
SvelteKit	436	2.272ms	184.29kb	2x
TanStack Start	362	2.728ms	192.48kb	2x

Ops/sec

Ops/sec chart

Ops/sec data

Framework	Operations per second
Baseline HTML	830
Astro	724
Pracht	570
SvelteKit	436
Nuxt	389
SolidStart	376
TanStack Start	362
React Router	349
Next.js	130

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	184.29 KB
Pracht	187.02 KB
TanStack Start	192.48 KB
Nuxt	201.73 KB
Next.js	204.56 KB
React Router	216.98 KB
SolidStart	224.26 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.22 ms
Astro	1.34 ms
Pracht	1.69 ms
SvelteKit	2.27 ms
Nuxt	2.49 ms
SolidStart	2.62 ms
TanStack Start	2.73 ms
React Router	2.83 ms
Next.js	7.42 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,764.4	50	16ms	40ms	95ms	52,619
Astro	1,569	50	24ms	50ms	94ms	46,344
Next.js	54.2	5	1174ms	4128ms	4695ms	1,633
Nuxt	530	50	73ms	341ms	2755ms	17,281
Pracht	657	25	44ms	116ms	1181ms	20,326
React Router	339.8	25	107ms	509ms	3445ms	11,296
SolidStart	560.6	50	96ms	257ms	2021ms	17,497
SvelteKit	597.4	25	71ms	249ms	1897ms	19,042
TanStack Start	397.8	5	144ms	425ms	2788ms	11,931

P99 Latency

P99 Latency at 25 Connections

P99 Latency at 25 Connections chart

P99 Latency at 25 Connections data

Framework	Milliseconds
Baseline HTML	16.00 ms
Astro	24.00 ms
Pracht	44.00 ms
SvelteKit	71.00 ms
Nuxt	73.00 ms
SolidStart	96.00 ms
React Router	107.00 ms
TanStack Start	144.00 ms
Next.js	1174.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	40.00 ms
Astro	50.00 ms
Pracht	116.00 ms
SvelteKit	249.00 ms
SolidStart	257.00 ms
Nuxt	341.00 ms
TanStack Start	425.00 ms
React Router	509.00 ms
Next.js	4128.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	94.00 ms
Baseline HTML	95.00 ms
Pracht	1181.00 ms
SvelteKit	1897.00 ms
SolidStart	2021.00 ms
Nuxt	2755.00 ms
TanStack Start	2788.00 ms
React Router	3445.00 ms
Next.js	4695.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	15.00 ms
Astro	17.00 ms
Pracht	39.00 ms
Nuxt	49.00 ms
SvelteKit	54.00 ms
SolidStart	66.00 ms
React Router	74.00 ms
TanStack Start	93.00 ms
Next.js	497.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	30.00 ms
Astro	32.00 ms
Pracht	81.00 ms
Nuxt	95.00 ms
SvelteKit	126.00 ms
SolidStart	132.00 ms
React Router	151.00 ms
TanStack Start	255.00 ms
Next.js	1654.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	65.00 ms
Baseline HTML	71.00 ms
Pracht	160.00 ms
SvelteKit	173.00 ms
SolidStart	175.00 ms
Nuxt	189.00 ms
TanStack Start	250.00 ms
React Router	280.00 ms
Next.js	2302.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	15.00 ms
Astro	16.00 ms
Pracht	38.00 ms
SvelteKit	43.00 ms
Nuxt	48.00 ms
SolidStart	54.00 ms
TanStack Start	72.00 ms
React Router	73.00 ms
Next.js	481.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	28.00 ms
Astro	31.00 ms
Pracht	79.00 ms
SolidStart	90.00 ms
Nuxt	91.00 ms
SvelteKit	101.00 ms
React Router	148.00 ms
TanStack Start	209.00 ms
Next.js	948.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	64.00 ms
SolidStart	125.00 ms
SvelteKit	135.00 ms
Pracht	157.00 ms
Nuxt	168.00 ms
TanStack Start	190.00 ms
React Router	265.00 ms
Next.js	999.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	43.8	5	1624ms	4774ms	4808ms	1,278
Nuxt	182.2	5	415ms	2624ms	3650ms	5,997
Pracht	376.8	50	97ms	427ms	2810ms	11,626
React Router	178.4	50	324ms	1617ms	3829ms	5,948
TanStack Start	236	25	177ms	1889ms	3069ms	7,816

P99 Latency

P99 Latency at 25 Connections

P99 Latency at 25 Connections chart

P99 Latency at 25 Connections data

Framework	Milliseconds
Pracht	97.00 ms
TanStack Start	177.00 ms
React Router	324.00 ms
Nuxt	415.00 ms
Next.js	1624.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
Pracht	427.00 ms
React Router	1617.00 ms
TanStack Start	1889.00 ms
Nuxt	2624.00 ms
Next.js	4774.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
Pracht	2810.00 ms
TanStack Start	3069.00 ms
Nuxt	3650.00 ms
React Router	3829.00 ms
Next.js	4808.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
Pracht	78.00 ms
TanStack Start	133.00 ms
Nuxt	142.00 ms
React Router	144.00 ms
Next.js	705.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
Pracht	136.00 ms
TanStack Start	268.00 ms
Nuxt	280.00 ms
React Router	280.00 ms
Next.js	2499.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
Pracht	279.00 ms
TanStack Start	306.00 ms
Nuxt	315.00 ms
React Router	399.00 ms
Next.js	2792.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
Pracht	70.00 ms
TanStack Start	111.00 ms
Nuxt	134.00 ms
React Router	139.00 ms
Next.js	671.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
Pracht	133.00 ms
TanStack Start	217.00 ms
Nuxt	274.00 ms
React Router	274.00 ms
Next.js	1110.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	227.00 ms
Pracht	267.00 ms
Nuxt	289.00 ms
React Router	375.00 ms
Next.js	1070.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.