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	86.8ms	86.86ms	2.32ms	1.99ms	0.33ms	0ms
Next.js	338.8ms	338.75ms	19.08ms	1.38ms	7.43ms	10.27ms
Nuxt	159.4ms	159.38ms	10.65ms	0.84ms	1.36ms	8.45ms
Pracht	108.6ms	108.57ms	21.52ms	0.84ms	4.19ms	16.49ms
React Router	159.4ms	159.62ms	16.47ms	1.55ms	2.09ms	12.82ms
SolidStart	93.2ms	93.22ms	16.4ms	0.95ms	2.18ms	13.26ms
SvelteKit	114ms	114ms	13.58ms	0.73ms	2.78ms	10.07ms
TanStack Start	125ms	124.94ms	21.03ms	0.99ms	7.36ms	12.68ms

First Paint (ms)

First Paint (ms) chart

First Paint (ms) data

Framework	Milliseconds
Astro	86.80 ms
SolidStart	93.20 ms
Pracht	108.60 ms
SvelteKit	114.00 ms
TanStack Start	125.00 ms
Nuxt	159.40 ms
React Router	159.40 ms
Next.js	338.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	86.86 ms
SolidStart	93.22 ms
Pracht	108.57 ms
SvelteKit	114.00 ms
TanStack Start	124.94 ms
Nuxt	159.38 ms
React Router	159.62 ms
Next.js	338.75 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.40 ms

2.32 ms

10.65 ms

13.58 ms

16.40 ms

16.47 ms

19.08 ms

21.03 ms

21.52 ms

Interaction Breakdown data

Framework or version	Interaction latency	Input delay	Processing duration	Presentation delay
Astro	2.32 ms	1.99 ms	0.33 ms	0.00 ms
Nuxt	10.65 ms	0.84 ms	1.36 ms	8.45 ms
SvelteKit	13.58 ms	0.73 ms	2.78 ms	10.07 ms
SolidStart	16.40 ms	0.95 ms	2.18 ms	13.26 ms
React Router	16.47 ms	1.55 ms	2.09 ms	12.82 ms
Next.js	19.08 ms	1.38 ms	7.43 ms	10.27 ms
TanStack Start	21.03 ms	0.99 ms	7.36 ms	12.68 ms
Pracht	21.52 ms	0.84 ms	4.19 ms	16.49 ms

Server Side Rendered Tests

Methodology: Server Side Rendered Tests.

Framework	First Paint	FCP	Interaction Latency	Input Delay	Processing Duration	Presentation Delay
Astro	55.2ms	55.29ms	0.72ms	0.49ms	0.22ms	0ms
Next.js	126.6ms	126.54ms	15.88ms	1.27ms	6.1ms	8.51ms
Nuxt	83.8ms	83.94ms	13.05ms	0.78ms	2.1ms	10.17ms
Pracht	80.2ms	79.97ms	18.76ms	0.82ms	2.33ms	15.61ms
React Router	112.2ms	112.17ms	18.93ms	2.13ms	2.97ms	13.83ms
SolidStart	86.6ms	86.64ms	19.72ms	1.29ms	3.06ms	15.37ms
SvelteKit	73.8ms	73.92ms	14.76ms	0.73ms	2.56ms	11.47ms
TanStack Start	90.6ms	90.74ms	23.32ms	1.32ms	8.94ms	13.06ms

First Paint (ms)

First Paint (ms) chart

First Paint (ms) data

Framework	Milliseconds
Astro	55.20 ms
SvelteKit	73.80 ms
Pracht	80.20 ms
Nuxt	83.80 ms
SolidStart	86.60 ms
TanStack Start	90.60 ms
React Router	112.20 ms
Next.js	126.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	55.29 ms
SvelteKit	73.92 ms
Pracht	79.97 ms
Nuxt	83.94 ms
SolidStart	86.64 ms
TanStack Start	90.74 ms
React Router	112.17 ms
Next.js	126.54 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.32 ms

Median: 15.88 ms

0.72 ms

13.05 ms

14.76 ms

15.88 ms

18.76 ms

18.93 ms

19.72 ms

23.32 ms

Interaction Breakdown data

Framework or version	Interaction latency	Input delay	Processing duration	Presentation delay
Astro	0.72 ms	0.49 ms	0.22 ms	0.00 ms
Nuxt	13.05 ms	0.78 ms	2.10 ms	10.17 ms
SvelteKit	14.76 ms	0.73 ms	2.56 ms	11.47 ms
Next.js	15.88 ms	1.27 ms	6.10 ms	8.51 ms
Pracht	18.76 ms	0.82 ms	2.33 ms	15.61 ms
React Router	18.93 ms	2.13 ms	2.97 ms	13.83 ms
SolidStart	19.72 ms	1.29 ms	3.06 ms	15.37 ms
TanStack Start	23.32 ms	1.32 ms	8.94 ms	13.06 ms

Server Side Throughput Tests

Methodology: Server Side Throughput Tests.

Framework	Ops/sec	Median Latency	Body Size	Duplication
Baseline HTML	851	1.206ms	96.83kb	1x
Astro	739	1.321ms	96.89kb	1x
Next.js	195	5.098ms	199.57kb	2x
Nuxt	379	2.53ms	201.73kb	2x
Pracht	597	1.627ms	187.02kb	2x
React Router	350	2.824ms	216.9kb	2x
SolidStart	436	2.219ms	224.17kb	2x
SvelteKit	465	2.128ms	184.29kb	2x
TanStack Start	344	2.837ms	192.67kb	2x

Ops/sec

Ops/sec chart

Ops/sec data

Framework	Operations per second
Baseline HTML	851
Astro	739
Pracht	597
SvelteKit	465
SolidStart	436
Nuxt	379
React Router	350
TanStack Start	344
Next.js	195

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.67 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.32 ms
Pracht	1.63 ms
SvelteKit	2.13 ms
SolidStart	2.22 ms
Nuxt	2.53 ms
React Router	2.82 ms
TanStack Start	2.84 ms
Next.js	5.10 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,765.4	200	20ms	46ms	108ms	49,968
Astro	1,568.6	25	24ms	48ms	84ms	46,886
Next.js	41	1	1789ms	4748ms	4749ms	1,224
Nuxt	492.2	10	83ms	421ms	2794ms	15,767
Pracht	684.6	25	40ms	116ms	978ms	21,849
React Router	336.6	50	111ms	515ms	3504ms	10,979
SolidStart	533.21	10	97ms	384ms	2038ms	17,433
SvelteKit	565.4	25	87ms	179ms	1968ms	18,229
TanStack Start	414	50	116ms	450ms	2054ms	13,692

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	24.00 ms
Pracht	40.00 ms
Nuxt	83.00 ms
SvelteKit	87.00 ms
SolidStart	97.00 ms
React Router	111.00 ms
TanStack Start	116.00 ms
Next.js	1789.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	46.00 ms
Astro	48.00 ms
Pracht	116.00 ms
SvelteKit	179.00 ms
SolidStart	384.00 ms
Nuxt	421.00 ms
TanStack Start	450.00 ms
React Router	515.00 ms
Next.js	4748.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	84.00 ms
Baseline HTML	108.00 ms
Pracht	978.00 ms
SvelteKit	1968.00 ms
SolidStart	2038.00 ms
TanStack Start	2054.00 ms
Nuxt	2794.00 ms
React Router	3504.00 ms
Next.js	4749.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	18.00 ms
Pracht	38.00 ms
Nuxt	54.00 ms
SvelteKit	58.00 ms
SolidStart	67.00 ms
React Router	79.00 ms
TanStack Start	80.00 ms
Next.js	641.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	77.00 ms
Nuxt	115.00 ms
SvelteKit	128.00 ms
SolidStart	147.00 ms
React Router	150.00 ms
TanStack Start	171.00 ms
Next.js	2282.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	77.00 ms
Pracht	150.00 ms
SolidStart	164.00 ms
Nuxt	210.00 ms
SvelteKit	214.00 ms
TanStack Start	257.00 ms
React Router	289.00 ms
Next.js	2714.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	17.00 ms
Pracht	37.00 ms
SvelteKit	46.00 ms
Nuxt	52.00 ms
SolidStart	55.00 ms
TanStack Start	63.00 ms
React Router	77.00 ms
Next.js	633.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	75.00 ms
SolidStart	92.00 ms
SvelteKit	104.00 ms
Nuxt	109.00 ms
TanStack Start	134.00 ms
React Router	147.00 ms
Next.js	1084.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	64.00 ms
Baseline HTML	66.00 ms
SolidStart	127.00 ms
Pracht	145.00 ms
SvelteKit	151.00 ms
Nuxt	183.00 ms
TanStack Start	189.00 ms
React Router	264.00 ms
Next.js	1039.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.2	1	2010ms	4695ms	4631ms	1,158
Nuxt	152.81	10	624ms	3250ms	3700ms	5,001
Pracht	342.4	25	90ms	568ms	3371ms	11,314
React Router	172.2	10	304ms	1544ms	3885ms	5,762
TanStack Start	234	50	174ms	1582ms	3226ms	7,866

P99 Latency

P99 Latency at 25 Connections

P99 Latency at 25 Connections chart

P99 Latency at 25 Connections data

Framework	Milliseconds
Pracht	90.00 ms
TanStack Start	174.00 ms
React Router	304.00 ms
Nuxt	624.00 ms
Next.js	2010.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	568.00 ms
React Router	1544.00 ms
TanStack Start	1582.00 ms
Nuxt	3250.00 ms
Next.js	4695.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
TanStack Start	3226.00 ms
Pracht	3371.00 ms
Nuxt	3700.00 ms
React Router	3885.00 ms
Next.js	4631.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	80.00 ms
TanStack Start	132.00 ms
React Router	157.00 ms
Nuxt	172.00 ms
Next.js	696.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	157.00 ms
TanStack Start	287.00 ms
React Router	294.00 ms
Nuxt	325.00 ms
Next.js	2383.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	286.00 ms
TanStack Start	302.00 ms
Nuxt	340.00 ms
React Router	409.00 ms
Next.js	2721.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	76.00 ms
TanStack Start	109.00 ms
React Router	144.00 ms
Nuxt	163.00 ms
Next.js	686.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	151.00 ms
TanStack Start	226.00 ms
React Router	290.00 ms
Nuxt	316.00 ms
Next.js	1097.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	244.00 ms
Pracht	262.00 ms
Nuxt	323.00 ms
React Router	374.00 ms
Next.js	1066.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.