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	96ms	95.98ms	4.27ms	1.83ms	0.55ms	1.88ms
Next.js	341.8ms	341.83ms	20.48ms	1.72ms	4.93ms	13.84ms
Nuxt	167.6ms	167.56ms	10.72ms	0.93ms	1.45ms	8.34ms
Pracht	85ms	84.94ms	21.03ms	0.75ms	2.5ms	17.78ms
React Router	153ms	152.87ms	20.64ms	1.55ms	2.67ms	16.42ms
SolidStart	97.8ms	97.95ms	17.15ms	0.85ms	2.47ms	13.83ms
SvelteKit	115ms	114.79ms	16.45ms	0.86ms	3.07ms	12.51ms
TanStack Start	125.6ms	125.64ms	21.81ms	1.26ms	7.03ms	13.52ms

First Paint (ms)

First Paint (ms) chart

First Paint (ms) data

Framework	Milliseconds
Pracht	85.00 ms
Astro	96.00 ms
SolidStart	97.80 ms
SvelteKit	115.00 ms
TanStack Start	125.60 ms
React Router	153.00 ms
Nuxt	167.60 ms
Next.js	341.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	84.94 ms
Astro	95.98 ms
SolidStart	97.95 ms
SvelteKit	114.79 ms
TanStack Start	125.64 ms
React Router	152.87 ms
Nuxt	167.56 ms
Next.js	341.83 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.81 ms

Median: 17.15 ms

4.27 ms

10.72 ms

16.45 ms

17.15 ms

20.48 ms

20.64 ms

21.03 ms

21.81 ms

Interaction Breakdown data

Framework or version	Interaction latency	Input delay	Processing duration	Presentation delay
Astro	4.27 ms	1.83 ms	0.55 ms	1.88 ms
Nuxt	10.72 ms	0.93 ms	1.45 ms	8.34 ms
SvelteKit	16.45 ms	0.86 ms	3.07 ms	12.51 ms
SolidStart	17.15 ms	0.85 ms	2.47 ms	13.83 ms
Next.js	20.48 ms	1.72 ms	4.93 ms	13.84 ms
React Router	20.64 ms	1.55 ms	2.67 ms	16.42 ms
Pracht	21.03 ms	0.75 ms	2.50 ms	17.78 ms
TanStack Start	21.81 ms	1.26 ms	7.03 ms	13.52 ms

Server Side Rendered Tests

Methodology: Server Side Rendered Tests.

Framework	First Paint	FCP	Interaction Latency	Input Delay	Processing Duration	Presentation Delay
Astro	62ms	61.76ms	0.91ms	0.65ms	0.26ms	0ms
Next.js	122.8ms	122.81ms	17.89ms	1.32ms	6.36ms	10.21ms
Nuxt	94.6ms	94.69ms	11.13ms	0.99ms	1.12ms	9.02ms
Pracht	79.8ms	79.75ms	18.07ms	0.95ms	2.54ms	14.58ms
React Router	108.2ms	108.02ms	16.53ms	1.61ms	4.44ms	10.48ms
SolidStart	89.6ms	89.55ms	14.84ms	0.83ms	2.38ms	11.64ms
SvelteKit	78.4ms	78.59ms	16.87ms	0.79ms	1.92ms	14.16ms
TanStack Start	96.2ms	96.06ms	21.25ms	1.5ms	9.94ms	9.82ms

First Paint (ms)

First Paint (ms) chart

First Paint (ms) data

Framework	Milliseconds
Astro	62.00 ms
SvelteKit	78.40 ms
Pracht	79.80 ms
SolidStart	89.60 ms
Nuxt	94.60 ms
TanStack Start	96.20 ms
React Router	108.20 ms
Next.js	122.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	61.76 ms
SvelteKit	78.59 ms
Pracht	79.75 ms
SolidStart	89.55 ms
Nuxt	94.69 ms
TanStack Start	96.06 ms
React Router	108.02 ms
Next.js	122.81 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.70 ms

Median: 16.53 ms

0.91 ms

11.13 ms

14.84 ms

16.53 ms

16.87 ms

17.89 ms

18.07 ms

21.25 ms

Interaction Breakdown data

Framework or version	Interaction latency	Input delay	Processing duration	Presentation delay
Astro	0.91 ms	0.65 ms	0.26 ms	0.00 ms
Nuxt	11.13 ms	0.99 ms	1.12 ms	9.02 ms
SolidStart	14.84 ms	0.83 ms	2.38 ms	11.64 ms
React Router	16.53 ms	1.61 ms	4.44 ms	10.48 ms
SvelteKit	16.87 ms	0.79 ms	1.92 ms	14.16 ms
Next.js	17.89 ms	1.32 ms	6.36 ms	10.21 ms
Pracht	18.07 ms	0.95 ms	2.54 ms	14.58 ms
TanStack Start	21.25 ms	1.50 ms	9.94 ms	9.82 ms

Server Side Throughput Tests

Methodology: Server Side Throughput Tests.

Framework	Ops/sec	Median Latency	Body Size	Duplication
Baseline HTML	837	1.204ms	96.83kb	1x
Astro	749	1.311ms	96.89kb	1x
Next.js	302	3.506ms	199.92kb	2x
Nuxt	395	2.446ms	201.73kb	2x
Pracht	597	1.625ms	187.02kb	2x
React Router	329	3.027ms	216.98kb	2x
SolidStart	389	2.475ms	224.26kb	2x
SvelteKit	464	2.125ms	184.3kb	2x
TanStack Start	351	2.813ms	192.67kb	2x

Ops/sec

Ops/sec chart

Ops/sec data

Framework	Operations per second
Baseline HTML	837
Astro	749
Pracht	597
SvelteKit	464
Nuxt	395
SolidStart	389
TanStack Start	351
React Router	329
Next.js	302

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.92 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.20 ms
Astro	1.31 ms
Pracht	1.63 ms
SvelteKit	2.13 ms
Nuxt	2.45 ms
SolidStart	2.48 ms
TanStack Start	2.81 ms
React Router	3.03 ms
Next.js	3.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,536.6	100	22ms	59ms	127ms	44,212
Astro	1,507.6	50	28ms	51ms	111ms	44,563
Next.js	68.8	5	1164ms	4405ms	4553ms	1,932
Nuxt	520	50	76ms	128ms	2739ms	17,067
Pracht	684.6	25	40ms	119ms	875ms	21,678
React Router	336.8	50	95ms	494ms	3522ms	11,136
SolidStart	545.8	10	93ms	365ms	2178ms	17,890
SvelteKit	577.4	25	81ms	331ms	2070ms	18,455
TanStack Start	403.4	5	121ms	787ms	2647ms	13,301

P99 Latency

P99 Latency at 25 Connections

P99 Latency at 25 Connections chart

P99 Latency at 25 Connections data

Framework	Milliseconds
Baseline HTML	22.00 ms
Astro	28.00 ms
Pracht	40.00 ms
Nuxt	76.00 ms
SvelteKit	81.00 ms
SolidStart	93.00 ms
React Router	95.00 ms
TanStack Start	121.00 ms
Next.js	1164.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	51.00 ms
Baseline HTML	59.00 ms
Pracht	119.00 ms
Nuxt	128.00 ms
SvelteKit	331.00 ms
SolidStart	365.00 ms
React Router	494.00 ms
TanStack Start	787.00 ms
Next.js	4405.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	111.00 ms
Baseline HTML	127.00 ms
Pracht	875.00 ms
SvelteKit	2070.00 ms
SolidStart	2178.00 ms
TanStack Start	2647.00 ms
Nuxt	2739.00 ms
React Router	3522.00 ms
Next.js	4553.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	19.00 ms
Baseline HTML	20.00 ms
Pracht	37.00 ms
Nuxt	49.00 ms
SvelteKit	53.00 ms
SolidStart	67.00 ms
React Router	76.00 ms
TanStack Start	79.00 ms
Next.js	490.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	35.00 ms
Baseline HTML	39.00 ms
Pracht	75.00 ms
Nuxt	103.00 ms
SvelteKit	128.00 ms
SolidStart	140.00 ms
React Router	148.00 ms
TanStack Start	163.00 ms
Next.js	1560.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	70.00 ms
Baseline HTML	82.00 ms
Pracht	159.00 ms
SolidStart	180.00 ms
Nuxt	191.00 ms
SvelteKit	195.00 ms
TanStack Start	236.00 ms
React Router	280.00 ms
Next.js	2038.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	17.00 ms
Baseline HTML	19.00 ms
Pracht	37.00 ms
SvelteKit	44.00 ms
Nuxt	48.00 ms
SolidStart	56.00 ms
TanStack Start	65.00 ms
React Router	74.00 ms
Next.js	482.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	33.00 ms
Baseline HTML	38.00 ms
Pracht	73.00 ms
SolidStart	89.00 ms
SvelteKit	94.00 ms
Nuxt	95.00 ms
TanStack Start	133.00 ms
React Router	146.00 ms
Next.js	892.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	65.00 ms
Baseline HTML	72.00 ms
SolidStart	125.00 ms
SvelteKit	141.00 ms
Pracht	146.00 ms
Nuxt	163.00 ms
TanStack Start	180.00 ms
React Router	257.00 ms
Next.js	887.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	62.8	1	1273ms	4625ms	4510ms	1,725
Nuxt	172.6	10	509ms	2972ms	3804ms	5,566
Pracht	382.6	25	97ms	303ms	2467ms	12,523
React Router	179	25	169ms	1576ms	3876ms	6,005
TanStack Start	233.4	50	213ms	1924ms	3137ms	7,833

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
React Router	169.00 ms
TanStack Start	213.00 ms
Nuxt	509.00 ms
Next.js	1273.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	303.00 ms
React Router	1576.00 ms
TanStack Start	1924.00 ms
Nuxt	2972.00 ms
Next.js	4625.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	2467.00 ms
TanStack Start	3137.00 ms
Nuxt	3804.00 ms
React Router	3876.00 ms
Next.js	4510.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	66.00 ms
TanStack Start	132.00 ms
React Router	143.00 ms
Nuxt	159.00 ms
Next.js	525.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	133.00 ms
TanStack Start	259.00 ms
React Router	277.00 ms
Nuxt	312.00 ms
Next.js	1867.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	264.00 ms
TanStack Start	313.00 ms
Nuxt	329.00 ms
React Router	391.00 ms
Next.js	2157.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	65.00 ms
TanStack Start	115.00 ms
React Router	137.00 ms
Nuxt	148.00 ms
Next.js	505.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	130.00 ms
TanStack Start	212.00 ms
React Router	272.00 ms
Nuxt	301.00 ms
Next.js	956.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	214.00 ms
Pracht	256.00 ms
Nuxt	296.00 ms
React Router	361.00 ms
Next.js	925.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.