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	94.6ms	94.39ms	5.44ms	2.01ms	0.45ms	2.98ms
Next.js	338.2ms	338.09ms	17.11ms	1.64ms	6.37ms	9.11ms
Nuxt	151.4ms	151.38ms	9.73ms	0.86ms	1.24ms	7.64ms
Pracht	99.2ms	99.11ms	19.33ms	0.98ms	3.22ms	15.14ms
React Router	150.4ms	150.44ms	16.65ms	1.45ms	2.24ms	12.96ms
SolidStart	106.2ms	106.23ms	18.53ms	2.05ms	4.66ms	11.82ms
SvelteKit	125.6ms	125.74ms	17.74ms	0.84ms	1.75ms	15.16ms
TanStack Start	126.6ms	126.56ms	34.67ms	1.41ms	17.4ms	15.86ms

First Paint (ms)

First Paint (ms) chart

First Paint (ms) data

Framework	Milliseconds
Astro	94.60 ms
Pracht	99.20 ms
SolidStart	106.20 ms
SvelteKit	125.60 ms
TanStack Start	126.60 ms
React Router	150.40 ms
Nuxt	151.40 ms
Next.js	338.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	94.39 ms
Pracht	99.11 ms
SolidStart	106.23 ms
SvelteKit	125.74 ms
TanStack Start	126.56 ms
React Router	150.44 ms
Nuxt	151.38 ms
Next.js	338.09 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.42 ms

Median: 17.11 ms

5.44 ms

9.73 ms

16.65 ms

17.11 ms

17.74 ms

18.53 ms

19.33 ms

34.67 ms

Interaction Breakdown data

Framework or version	Interaction latency	Input delay	Processing duration	Presentation delay
Astro	5.44 ms	2.01 ms	0.45 ms	2.98 ms
Nuxt	9.73 ms	0.86 ms	1.24 ms	7.64 ms
React Router	16.65 ms	1.45 ms	2.24 ms	12.96 ms
Next.js	17.11 ms	1.64 ms	6.37 ms	9.11 ms
SvelteKit	17.74 ms	0.84 ms	1.75 ms	15.16 ms
SolidStart	18.53 ms	2.05 ms	4.66 ms	11.82 ms
Pracht	19.33 ms	0.98 ms	3.22 ms	15.14 ms
TanStack Start	34.67 ms	1.41 ms	17.40 ms	15.86 ms

Server Side Rendered Tests

Methodology: Server Side Rendered Tests.

Framework	First Paint	FCP	Interaction Latency	Input Delay	Processing Duration	Presentation Delay
Astro	63ms	63.17ms	1.25ms	0.61ms	0.64ms	0ms
Next.js	129.2ms	129.05ms	19.87ms	1.35ms	8.09ms	10.43ms
Nuxt	90.6ms	90.42ms	10.65ms	0.82ms	1.74ms	8.09ms
Pracht	89.2ms	89.21ms	16.69ms	1.02ms	4.2ms	11.48ms
React Router	95.4ms	95.57ms	19.54ms	1.65ms	2.83ms	15.05ms
SolidStart	94.8ms	94.72ms	17.56ms	1.45ms	3.75ms	12.36ms
SvelteKit	76ms	76.15ms	14ms	0.74ms	2.03ms	11.22ms
TanStack Start	91.2ms	91.05ms	37.53ms	1.57ms	20.98ms	14.97ms

First Paint (ms)

First Paint (ms) chart

First Paint (ms) data

Framework	Milliseconds
Astro	63.00 ms
SvelteKit	76.00 ms
Pracht	89.20 ms
Nuxt	90.60 ms
TanStack Start	91.20 ms
SolidStart	94.80 ms
React Router	95.40 ms
Next.js	129.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.17 ms
SvelteKit	76.15 ms
Pracht	89.21 ms
Nuxt	90.42 ms
TanStack Start	91.05 ms
SolidStart	94.72 ms
React Router	95.57 ms
Next.js	129.05 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.13 ms

Median: 17.56 ms

1.25 ms

10.65 ms

14.00 ms

16.69 ms

17.56 ms

19.54 ms

19.87 ms

37.53 ms

Interaction Breakdown data

Framework or version	Interaction latency	Input delay	Processing duration	Presentation delay
Astro	1.25 ms	0.61 ms	0.64 ms	0.00 ms
Nuxt	10.65 ms	0.82 ms	1.74 ms	8.09 ms
SvelteKit	14.00 ms	0.74 ms	2.03 ms	11.22 ms
Pracht	16.69 ms	1.02 ms	4.20 ms	11.48 ms
SolidStart	17.56 ms	1.45 ms	3.75 ms	12.36 ms
React Router	19.54 ms	1.65 ms	2.83 ms	15.05 ms
Next.js	19.87 ms	1.35 ms	8.09 ms	10.43 ms
TanStack Start	37.53 ms	1.57 ms	20.98 ms	14.97 ms

Server Side Throughput Tests

Methodology: Server Side Throughput Tests.

Framework	Ops/sec	Median Latency	Body Size	Duplication
Baseline HTML	849	1.202ms	96.83kb	1x
Astro	737	1.326ms	96.89kb	1x
Next.js	226	4.585ms	199.57kb	2x
Nuxt	384	2.51ms	201.73kb	2x
Pracht	586	1.643ms	187.02kb	2x
React Router	330	3.007ms	216.9kb	2x
SolidStart	422	2.315ms	224.17kb	2x
SvelteKit	459	2.16ms	184.29kb	2x
TanStack Start	341	2.895ms	191.63kb	2x

Ops/sec

Ops/sec chart

Ops/sec data

Framework	Operations per second
Baseline HTML	849
Astro	737
Pracht	586
SvelteKit	459
SolidStart	422
Nuxt	384
TanStack Start	341
React Router	330
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.29 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.20 ms
Astro	1.33 ms
Pracht	1.64 ms
SvelteKit	2.16 ms
SolidStart	2.31 ms
Nuxt	2.51 ms
TanStack Start	2.90 ms
React Router	3.01 ms
Next.js	4.58 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	55ms	106ms	47,038
Astro	1,499.8	100	27ms	48ms	114ms	45,223
Next.js	43.4	1	1892ms	4670ms	4744ms	1,191
Nuxt	530.21	200	79ms	356ms	2807ms	16,973
Pracht	665	200	64ms	126ms	1034ms	21,403
React Router	341.8	25	102ms	548ms	3501ms	11,076
SolidStart	510.4	5	99ms	440ms	2159ms	16,817
SvelteKit	565.21	25	71ms	185ms	2307ms	18,302
TanStack Start	390.8	10	121ms	746ms	2640ms	12,768

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	27.00 ms
Pracht	64.00 ms
SvelteKit	71.00 ms
Nuxt	79.00 ms
SolidStart	99.00 ms
React Router	102.00 ms
TanStack Start	121.00 ms
Next.js	1892.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	48.00 ms
Baseline HTML	55.00 ms
Pracht	126.00 ms
SvelteKit	185.00 ms
Nuxt	356.00 ms
SolidStart	440.00 ms
React Router	548.00 ms
TanStack Start	746.00 ms
Next.js	4670.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
Baseline HTML	106.00 ms
Astro	114.00 ms
Pracht	1034.00 ms
SolidStart	2159.00 ms
SvelteKit	2307.00 ms
TanStack Start	2640.00 ms
Nuxt	2807.00 ms
React Router	3501.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	39.00 ms
Nuxt	50.00 ms
SvelteKit	58.00 ms
SolidStart	73.00 ms
React Router	74.00 ms
TanStack Start	89.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
Astro	36.00 ms
Baseline HTML	37.00 ms
Pracht	78.00 ms
Nuxt	108.00 ms
SvelteKit	132.00 ms
React Router	151.00 ms
SolidStart	155.00 ms
TanStack Start	167.00 ms
Next.js	2365.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	69.00 ms
Baseline HTML	76.00 ms
Pracht	152.00 ms
SolidStart	155.00 ms
Nuxt	179.00 ms
SvelteKit	197.00 ms
TanStack Start	233.00 ms
React Router	295.00 ms
Next.js	2712.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	18.00 ms
Pracht	38.00 ms
SvelteKit	46.00 ms
Nuxt	49.00 ms
SolidStart	61.00 ms
TanStack Start	70.00 ms
React Router	72.00 ms
Next.js	687.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	34.00 ms
Baseline HTML	36.00 ms
Pracht	76.00 ms
SolidStart	94.00 ms
Nuxt	98.00 ms
SvelteKit	102.00 ms
React Router	148.00 ms
TanStack Start	150.00 ms
Next.js	1082.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	66.00 ms
Baseline HTML	66.00 ms
SolidStart	127.00 ms
SvelteKit	145.00 ms
Pracht	149.00 ms
TanStack Start	164.00 ms
Nuxt	167.00 ms
React Router	261.00 ms
Next.js	1058.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	42.2	1	1874ms	4747ms	4641ms	1,170
Nuxt	181.4	5	503ms	2678ms	3661ms	5,957
Pracht	389	50	95ms	310ms	2597ms	11,850
React Router	173.8	50	304ms	1643ms	3873ms	5,767
TanStack Start	207.6	5	418ms	2394ms	3426ms	6,781

P99 Latency

P99 Latency at 25 Connections

P99 Latency at 25 Connections chart

P99 Latency at 25 Connections data

Framework	Milliseconds
Pracht	95.00 ms
React Router	304.00 ms
TanStack Start	418.00 ms
Nuxt	503.00 ms
Next.js	1874.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	310.00 ms
React Router	1643.00 ms
TanStack Start	2394.00 ms
Nuxt	2678.00 ms
Next.js	4747.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	2597.00 ms
TanStack Start	3426.00 ms
Nuxt	3661.00 ms
React Router	3873.00 ms
Next.js	4641.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
Nuxt	145.00 ms
React Router	164.00 ms
TanStack Start	172.00 ms
Next.js	677.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	134.00 ms
React Router	282.00 ms
Nuxt	289.00 ms
TanStack Start	318.00 ms
Next.js	2354.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	272.00 ms
Nuxt	319.00 ms
TanStack Start	335.00 ms
React Router	397.00 ms
Next.js	2751.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	63.00 ms
TanStack Start	130.00 ms
Nuxt	138.00 ms
React Router	140.00 ms
Next.js	667.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	126.00 ms
TanStack Start	218.00 ms
Nuxt	277.00 ms
React Router	277.00 ms
Next.js	1142.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	247.00 ms
Pracht	257.00 ms
Nuxt	283.00 ms
React Router	358.00 ms
Next.js	1062.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.