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	104ms	104.03ms	1.88ms	1.43ms	0.46ms	0ms
Next.js	339.8ms	339.93ms	18.02ms	1.46ms	5.73ms	10.83ms
Nuxt	158.6ms	158.73ms	9.02ms	0.81ms	2.01ms	6.2ms
Pracht	95ms	95.37ms	20.57ms	0.82ms	2.82ms	16.92ms
React Router	159.8ms	159.81ms	16.07ms	1.59ms	3.7ms	10.78ms
SolidStart	95ms	95.04ms	18.52ms	0.92ms	2.5ms	15.1ms
SvelteKit	118ms	117.89ms	18.23ms	0.92ms	1.84ms	15.47ms
TanStack Start	127.6ms	127.61ms	23.14ms	1.07ms	8.55ms	13.51ms

First Paint (ms)

First Paint (ms) chart

First Paint (ms) data

Framework	Milliseconds
Pracht	95.00 ms
SolidStart	95.00 ms
Astro	104.00 ms
SvelteKit	118.00 ms
TanStack Start	127.60 ms
Nuxt	158.60 ms
React Router	159.80 ms
Next.js	339.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	95.04 ms
Pracht	95.37 ms
Astro	104.03 ms
SvelteKit	117.89 ms
TanStack Start	127.61 ms
Nuxt	158.73 ms
React Router	159.81 ms
Next.js	339.93 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.13 ms

Median: 18.02 ms

1.88 ms

9.02 ms

16.07 ms

18.02 ms

18.23 ms

18.52 ms

20.57 ms

23.14 ms

Interaction Breakdown data

Framework or version	Interaction latency	Input delay	Processing duration	Presentation delay
Astro	1.88 ms	1.43 ms	0.46 ms	0.00 ms
Nuxt	9.02 ms	0.81 ms	2.01 ms	6.20 ms
React Router	16.07 ms	1.59 ms	3.70 ms	10.78 ms
Next.js	18.02 ms	1.46 ms	5.73 ms	10.83 ms
SvelteKit	18.23 ms	0.92 ms	1.84 ms	15.47 ms
SolidStart	18.52 ms	0.92 ms	2.50 ms	15.10 ms
Pracht	20.57 ms	0.82 ms	2.82 ms	16.92 ms
TanStack Start	23.14 ms	1.07 ms	8.55 ms	13.51 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.13ms	3.29ms	0.6ms	0.3ms	2.39ms
Next.js	139.2ms	139.27ms	19.66ms	1.66ms	7.76ms	10.24ms
Nuxt	90.4ms	90.46ms	10.1ms	0.87ms	1.86ms	7.36ms
Pracht	78.8ms	79ms	13.84ms	1.14ms	1.92ms	10.78ms
React Router	125ms	124.88ms	22.7ms	2.01ms	4.21ms	16.47ms
SolidStart	85.8ms	85.94ms	16.84ms	0.81ms	2.28ms	13.74ms
SvelteKit	75ms	75.06ms	15.87ms	0.78ms	2.04ms	13.05ms
TanStack Start	88.4ms	88.46ms	26.68ms	1.41ms	11.21ms	14.05ms

First Paint (ms)

First Paint (ms) chart

First Paint (ms) data

Framework	Milliseconds
Astro	63.20 ms
SvelteKit	75.00 ms
Pracht	78.80 ms
SolidStart	85.80 ms
TanStack Start	88.40 ms
Nuxt	90.40 ms
React Router	125.00 ms
Next.js	139.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	63.13 ms
SvelteKit	75.06 ms
Pracht	79.00 ms
SolidStart	85.94 ms
TanStack Start	88.46 ms
Nuxt	90.46 ms
React Router	124.88 ms
Next.js	139.27 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.36 ms

Median: 16.84 ms

3.29 ms

10.10 ms

13.84 ms

15.87 ms

16.84 ms

19.66 ms

22.70 ms

26.68 ms

Interaction Breakdown data

Framework or version	Interaction latency	Input delay	Processing duration	Presentation delay
Astro	3.29 ms	0.60 ms	0.30 ms	2.39 ms
Nuxt	10.10 ms	0.87 ms	1.86 ms	7.36 ms
Pracht	13.84 ms	1.14 ms	1.92 ms	10.78 ms
SvelteKit	15.87 ms	0.78 ms	2.04 ms	13.05 ms
SolidStart	16.84 ms	0.81 ms	2.28 ms	13.74 ms
Next.js	19.66 ms	1.66 ms	7.76 ms	10.24 ms
React Router	22.70 ms	2.01 ms	4.21 ms	16.47 ms
TanStack Start	26.68 ms	1.41 ms	11.21 ms	14.05 ms

Server Side Throughput Tests

Methodology: Server Side Throughput Tests.

Framework	Ops/sec	Median Latency	Body Size	Duplication
Baseline HTML	840	1.212ms	96.83kb	1x
Astro	729	1.332ms	96.89kb	1x
Next.js	226	4.561ms	199.57kb	2x
Nuxt	405	2.402ms	201.73kb	2x
Pracht	581	1.654ms	187.02kb	2x
React Router	316	3.143ms	216.98kb	2x
SolidStart	380	2.554ms	224.26kb	2x
SvelteKit	441	2.242ms	184.3kb	2x
TanStack Start	352	2.742ms	192.67kb	2x

Ops/sec

Ops/sec chart

Ops/sec data

Framework	Operations per second
Baseline HTML	840
Astro	729
Pracht	581
SvelteKit	441
Nuxt	405
SolidStart	380
TanStack Start	352
React Router	316
Next.js	226

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.30 KB
Pracht	187.02 KB
TanStack Start	192.67 KB
Next.js	199.57 KB
Nuxt	201.73 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.21 ms
Astro	1.33 ms
Pracht	1.65 ms
SvelteKit	2.24 ms
Nuxt	2.40 ms
SolidStart	2.55 ms
TanStack Start	2.74 ms
React Router	3.14 ms
Next.js	4.56 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,629.8	100	21ms	58ms	118ms	47,550
Astro	1,575.4	50	26ms	44ms	100ms	47,052
Next.js	45	5	1794ms	4723ms	4744ms	1,262
Nuxt	498.4	25	74ms	389ms	2850ms	16,302
Pracht	694.8	100	41ms	115ms	961ms	21,728
React Router	335.6	25	107ms	565ms	3442ms	11,000
SolidStart	535	25	90ms	357ms	2102ms	17,247
SvelteKit	541.21	25	84ms	175ms	2034ms	17,513
TanStack Start	402	50	121ms	206ms	2757ms	13,164

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	26.00 ms
Pracht	41.00 ms
Nuxt	74.00 ms
SvelteKit	84.00 ms
SolidStart	90.00 ms
React Router	107.00 ms
TanStack Start	121.00 ms
Next.js	1794.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	44.00 ms
Baseline HTML	58.00 ms
Pracht	115.00 ms
SvelteKit	175.00 ms
TanStack Start	206.00 ms
SolidStart	357.00 ms
Nuxt	389.00 ms
React Router	565.00 ms
Next.js	4723.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	100.00 ms
Baseline HTML	118.00 ms
Pracht	961.00 ms
SvelteKit	2034.00 ms
SolidStart	2102.00 ms
TanStack Start	2757.00 ms
Nuxt	2850.00 ms
React Router	3442.00 ms
Next.js	4744.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
Pracht	38.00 ms
Nuxt	52.00 ms
SvelteKit	58.00 ms
SolidStart	68.00 ms
React Router	74.00 ms
TanStack Start	85.00 ms
Next.js	653.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	37.00 ms
Pracht	78.00 ms
Nuxt	109.00 ms
SvelteKit	131.00 ms
SolidStart	148.00 ms
React Router	153.00 ms
TanStack Start	176.00 ms
Next.js	2302.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	68.00 ms
Baseline HTML	76.00 ms
Pracht	143.00 ms
SolidStart	171.00 ms
Nuxt	193.00 ms
SvelteKit	203.00 ms
TanStack Start	224.00 ms
React Router	292.00 ms
Next.js	2584.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	37.00 ms
SvelteKit	48.00 ms
Nuxt	50.00 ms
SolidStart	58.00 ms
TanStack Start	71.00 ms
React Router	74.00 ms
Next.js	640.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	32.00 ms
Baseline HTML	35.00 ms
Pracht	76.00 ms
SolidStart	92.00 ms
Nuxt	100.00 ms
SvelteKit	109.00 ms
TanStack Start	148.00 ms
React Router	151.00 ms
Next.js	1048.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	68.00 ms
SolidStart	119.00 ms
Pracht	140.00 ms
TanStack Start	164.00 ms
SvelteKit	166.00 ms
Nuxt	171.00 ms
React Router	272.00 ms
Next.js	1051.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	5	2007ms	4751ms	4772ms	1,141
Nuxt	181.2	25	439ms	2651ms	3659ms	5,951
Pracht	398.6	25	73ms	275ms	2698ms	12,158
React Router	167.6	5	188ms	1575ms	4084ms	5,556
TanStack Start	232.4	50	175ms	1734ms	2951ms	7,793

P99 Latency

P99 Latency at 25 Connections

P99 Latency at 25 Connections chart

P99 Latency at 25 Connections data

Framework	Milliseconds
Pracht	73.00 ms
TanStack Start	175.00 ms
React Router	188.00 ms
Nuxt	439.00 ms
Next.js	2007.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	275.00 ms
React Router	1575.00 ms
TanStack Start	1734.00 ms
Nuxt	2651.00 ms
Next.js	4751.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	2698.00 ms
TanStack Start	2951.00 ms
Nuxt	3659.00 ms
React Router	4084.00 ms
Next.js	4772.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	63.00 ms
TanStack Start	133.00 ms
Nuxt	138.00 ms
React Router	155.00 ms
Next.js	714.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	129.00 ms
TanStack Start	258.00 ms
Nuxt	286.00 ms
React Router	305.00 ms
Next.js	2412.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	248.00 ms
TanStack Start	290.00 ms
Nuxt	310.00 ms
React Router	408.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	62.00 ms
TanStack Start	112.00 ms
Nuxt	134.00 ms
React Router	151.00 ms
Next.js	700.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	123.00 ms
TanStack Start	212.00 ms
Nuxt	281.00 ms
React Router	300.00 ms
Next.js	1109.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	222.00 ms
Pracht	242.00 ms
Nuxt	291.00 ms
React Router	388.00 ms
Next.js	1097.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.