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	95.2ms	95.1ms	7.7ms	1.73ms	0.72ms	5.25ms
Next.js	340.8ms	340.85ms	20.15ms	1.52ms	7.69ms	10.94ms
Nuxt	158.8ms	158.89ms	11.73ms	1.14ms	1.38ms	9.21ms
Pracht	93.4ms	93.19ms	18.26ms	0.78ms	2.57ms	14.91ms
React Router	153.4ms	153.48ms	18.23ms	1.56ms	2.03ms	14.63ms
SolidStart	94ms	94.01ms	18.91ms	0.84ms	3.28ms	14.8ms
SvelteKit	116ms	115.96ms	14.16ms	0.62ms	2.8ms	10.74ms
TanStack Start	136.4ms	136.45ms	31.1ms	2.88ms	20.39ms	7.84ms

First Paint (ms)

First Paint (ms) chart

First Paint (ms) data

Framework	Milliseconds
Pracht	93.40 ms
SolidStart	94.00 ms
Astro	95.20 ms
SvelteKit	116.00 ms
TanStack Start	136.40 ms
React Router	153.40 ms
Nuxt	158.80 ms
Next.js	340.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
Pracht	93.19 ms
SolidStart	94.01 ms
Astro	95.10 ms
SvelteKit	115.96 ms
TanStack Start	136.45 ms
React Router	153.48 ms
Nuxt	158.89 ms
Next.js	340.85 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.25 ms

Median: 18.23 ms

7.70 ms

11.73 ms

14.16 ms

18.23 ms

18.26 ms

18.91 ms

20.15 ms

31.10 ms

Interaction Breakdown data

Framework or version	Interaction latency	Input delay	Processing duration	Presentation delay
Astro	7.70 ms	1.73 ms	0.72 ms	5.25 ms
Nuxt	11.73 ms	1.14 ms	1.38 ms	9.21 ms
SvelteKit	14.16 ms	0.62 ms	2.80 ms	10.74 ms
React Router	18.23 ms	1.56 ms	2.03 ms	14.63 ms
Pracht	18.26 ms	0.78 ms	2.57 ms	14.91 ms
SolidStart	18.91 ms	0.84 ms	3.28 ms	14.80 ms
Next.js	20.15 ms	1.52 ms	7.69 ms	10.94 ms
TanStack Start	31.10 ms	2.88 ms	20.39 ms	7.84 ms

Server Side Rendered Tests

Methodology: Server Side Rendered Tests.

Framework	First Paint	FCP	Interaction Latency	Input Delay	Processing Duration	Presentation Delay
Astro	60ms	59.81ms	3.12ms	0.62ms	0.29ms	2.2ms
Next.js	149.8ms	149.73ms	18.73ms	1.32ms	6.69ms	10.71ms
Nuxt	98ms	97.96ms	10.91ms	0.84ms	1.75ms	8.32ms
Pracht	81.4ms	81.27ms	15.83ms	0.85ms	2.12ms	12.86ms
React Router	106.6ms	106.62ms	20.06ms	1.64ms	2.79ms	15.64ms
SolidStart	92.2ms	91.96ms	15.35ms	0.93ms	2.67ms	11.75ms
SvelteKit	90.8ms	90.79ms	21.02ms	0.78ms	2.76ms	17.47ms
TanStack Start	94ms	94.03ms	30.93ms	1.58ms	16.58ms	12.78ms

First Paint (ms)

First Paint (ms) chart

First Paint (ms) data

Framework	Milliseconds
Astro	60.00 ms
Pracht	81.40 ms
SvelteKit	90.80 ms
SolidStart	92.20 ms
TanStack Start	94.00 ms
Nuxt	98.00 ms
React Router	106.60 ms
Next.js	149.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
Astro	59.81 ms
Pracht	81.27 ms
SvelteKit	90.79 ms
SolidStart	91.96 ms
TanStack Start	94.03 ms
Nuxt	97.96 ms
React Router	106.62 ms
Next.js	149.73 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.28 ms

Median: 18.73 ms

3.12 ms

10.91 ms

15.35 ms

15.83 ms

18.73 ms

20.06 ms

21.02 ms

30.93 ms

Interaction Breakdown data

Framework or version	Interaction latency	Input delay	Processing duration	Presentation delay
Astro	3.12 ms	0.62 ms	0.29 ms	2.20 ms
Nuxt	10.91 ms	0.84 ms	1.75 ms	8.32 ms
SolidStart	15.35 ms	0.93 ms	2.67 ms	11.75 ms
Pracht	15.83 ms	0.85 ms	2.12 ms	12.86 ms
Next.js	18.73 ms	1.32 ms	6.69 ms	10.71 ms
React Router	20.06 ms	1.64 ms	2.79 ms	15.64 ms
SvelteKit	21.02 ms	0.78 ms	2.76 ms	17.47 ms
TanStack Start	30.93 ms	1.58 ms	16.58 ms	12.78 ms

Server Side Throughput Tests

Methodology: Server Side Throughput Tests.

Framework	Ops/sec	Median Latency	Body Size	Duplication
Baseline HTML	836	1.212ms	96.83kb	1x
Astro	743	1.311ms	96.89kb	1x
Next.js	233	4.51ms	199.57kb	2x
Nuxt	381	2.53ms	201.73kb	2x
Pracht	592	1.624ms	187.02kb	2x
React Router	342	2.885ms	216.9kb	2x
SolidStart	433	2.233ms	224.17kb	2x
SvelteKit	448	2.161ms	183.53kb	2x
TanStack Start	359	2.753ms	191.63kb	2x

Ops/sec

Ops/sec chart

Ops/sec data

Framework	Operations per second
Baseline HTML	836
Astro	743
Pracht	592
SvelteKit	448
SolidStart	433
Nuxt	381
TanStack Start	359
React Router	342
Next.js	233

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
Pracht	187.02 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.31 ms
Pracht	1.62 ms
SvelteKit	2.16 ms
SolidStart	2.23 ms
Nuxt	2.53 ms
TanStack Start	2.75 ms
React Router	2.88 ms
Next.js	4.51 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,630.4	50	21ms	42ms	107ms	47,464
Astro	1,563.6	100	24ms	47ms	94ms	46,879
Next.js	45.8	1	1731ms	4693ms	4620ms	1,295
Nuxt	536	25	73ms	294ms	2658ms	17,229
Pracht	708.6	25	38ms	103ms	592ms	22,154
React Router	342	25	106ms	513ms	3522ms	11,323
SolidStart	527.4	10	96ms	382ms	2078ms	17,300
SvelteKit	473.8	10	108ms	177ms	2044ms	15,418
TanStack Start	372.8	25	122ms	821ms	2541ms	12,025

P99 Latency

P99 Latency at 25 Connections

P99 Latency at 25 Connections chart

P99 Latency at 25 Connections data

Framework	Milliseconds
Baseline HTML	21.00 ms
Astro	24.00 ms
Pracht	38.00 ms
Nuxt	73.00 ms
SolidStart	96.00 ms
React Router	106.00 ms
SvelteKit	108.00 ms
TanStack Start	122.00 ms
Next.js	1731.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	42.00 ms
Astro	47.00 ms
Pracht	103.00 ms
SvelteKit	177.00 ms
Nuxt	294.00 ms
SolidStart	382.00 ms
React Router	513.00 ms
TanStack Start	821.00 ms
Next.js	4693.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	107.00 ms
Pracht	592.00 ms
SvelteKit	2044.00 ms
SolidStart	2078.00 ms
TanStack Start	2541.00 ms
Nuxt	2658.00 ms
React Router	3522.00 ms
Next.js	4620.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	17.00 ms
Baseline HTML	19.00 ms
Pracht	36.00 ms
Nuxt	48.00 ms
SvelteKit	65.00 ms
SolidStart	68.00 ms
React Router	73.00 ms
TanStack Start	86.00 ms
Next.js	637.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	34.00 ms
Baseline HTML	36.00 ms
Pracht	71.00 ms
Nuxt	100.00 ms
SvelteKit	138.00 ms
SolidStart	146.00 ms
React Router	147.00 ms
TanStack Start	205.00 ms
Next.js	2292.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	67.00 ms
Baseline HTML	87.00 ms
SolidStart	145.00 ms
Pracht	154.00 ms
Nuxt	191.00 ms
TanStack Start	227.00 ms
SvelteKit	261.00 ms
React Router	290.00 ms
Next.js	2382.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	16.00 ms
Baseline HTML	18.00 ms
Pracht	35.00 ms
Nuxt	46.00 ms
SolidStart	56.00 ms
SvelteKit	58.00 ms
TanStack Start	71.00 ms
React Router	72.00 ms
Next.js	627.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	31.00 ms
Astro	32.00 ms
Pracht	70.00 ms
Nuxt	96.00 ms
SolidStart	97.00 ms
SvelteKit	114.00 ms
TanStack Start	138.00 ms
React Router	145.00 ms
Next.js	1053.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
Astro	63.00 ms
Baseline HTML	71.00 ms
SolidStart	120.00 ms
Pracht	138.00 ms
Nuxt	176.00 ms
SvelteKit	179.00 ms
TanStack Start	195.00 ms
React Router	259.00 ms
Next.js	1043.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	1973ms	4766ms	4677ms	1,147
Nuxt	173.4	25	518ms	2748ms	3740ms	5,527
Pracht	376.2	25	98ms	265ms	2942ms	11,693
React Router	164.6	10	270ms	2044ms	4003ms	5,215
TanStack Start	167.2	10	576ms	3276ms	3276ms	5,557

P99 Latency

P99 Latency at 25 Connections

P99 Latency at 25 Connections chart

P99 Latency at 25 Connections data

Framework	Milliseconds
Pracht	98.00 ms
React Router	270.00 ms
Nuxt	518.00 ms
TanStack Start	576.00 ms
Next.js	1973.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	265.00 ms
React Router	2044.00 ms
Nuxt	2748.00 ms
TanStack Start	3276.00 ms
Next.js	4766.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	2942.00 ms
TanStack Start	3276.00 ms
Nuxt	3740.00 ms
React Router	4003.00 ms
Next.js	4677.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	68.00 ms
Nuxt	144.00 ms
React Router	172.00 ms
TanStack Start	196.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
Pracht	138.00 ms
Nuxt	318.00 ms
React Router	345.00 ms
TanStack Start	370.00 ms
Next.js	2387.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	259.00 ms
Nuxt	327.00 ms
TanStack Start	358.00 ms
React Router	411.00 ms
Next.js	2771.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	66.00 ms
Nuxt	142.00 ms
React Router	161.00 ms
TanStack Start	173.00 ms
Next.js	691.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	284.00 ms
Nuxt	290.00 ms
React Router	316.00 ms
Next.js	1158.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
Pracht	245.00 ms
TanStack Start	265.00 ms
Nuxt	304.00 ms
React Router	385.00 ms
Next.js	1056.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.