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	97ms	97.13ms	8.13ms	1.89ms	0.63ms	5.61ms
Next.js	338.2ms	338.11ms	16.32ms	1.32ms	4.11ms	10.88ms
Nuxt	138ms	137.87ms	10.77ms	0.68ms	1.14ms	8.95ms
Pracht	91.8ms	91.93ms	18.19ms	0.9ms	2.96ms	14.33ms
React Router	153.2ms	153.17ms	16.95ms	1.4ms	2.86ms	12.69ms
SolidStart	88.2ms	88.1ms	14.62ms	0.88ms	2.43ms	11.31ms
SvelteKit	103.4ms	103.33ms	17.58ms	0.8ms	1.93ms	14.86ms
TanStack Start	126.6ms	126.39ms	21.38ms	1.35ms	2.96ms	17.07ms

First Paint (ms)

First Paint (ms) chart

First Paint (ms) data

Framework	Milliseconds
SolidStart	88.20 ms
Pracht	91.80 ms
Astro	97.00 ms
SvelteKit	103.40 ms
TanStack Start	126.60 ms
Nuxt	138.00 ms
React Router	153.20 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
SolidStart	88.10 ms
Pracht	91.93 ms
Astro	97.13 ms
SvelteKit	103.33 ms
TanStack Start	126.39 ms
Nuxt	137.87 ms
React Router	153.17 ms
Next.js	338.11 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.63 ms

Median: 16.32 ms

8.13 ms

10.77 ms

14.62 ms

16.32 ms

16.95 ms

17.58 ms

18.19 ms

21.38 ms

Interaction Breakdown data

Framework or version	Interaction latency	Input delay	Processing duration	Presentation delay
Astro	8.13 ms	1.89 ms	0.63 ms	5.61 ms
Nuxt	10.77 ms	0.68 ms	1.14 ms	8.95 ms
SolidStart	14.62 ms	0.88 ms	2.43 ms	11.31 ms
Next.js	16.32 ms	1.32 ms	4.11 ms	10.88 ms
React Router	16.95 ms	1.40 ms	2.86 ms	12.69 ms
SvelteKit	17.58 ms	0.80 ms	1.93 ms	14.86 ms
Pracht	18.19 ms	0.90 ms	2.96 ms	14.33 ms
TanStack Start	21.38 ms	1.35 ms	2.96 ms	17.07 ms

Server Side Rendered Tests

Methodology: Server Side Rendered Tests.

Framework	First Paint	FCP	Interaction Latency	Input Delay	Processing Duration	Presentation Delay
Astro	55.6ms	55.57ms	1.22ms	0.54ms	0.68ms	0ms
Next.js	384.4ms	384.44ms	17.74ms	1.67ms	7.86ms	8.21ms
Nuxt	88.4ms	88.41ms	11.1ms	0.85ms	1.26ms	8.99ms
Pracht	79.4ms	79.48ms	16.74ms	0.82ms	2.07ms	13.85ms
React Router	107.8ms	107.74ms	17.37ms	1.12ms	2.83ms	13.42ms
SolidStart	96.2ms	96.14ms	13.65ms	0.89ms	2.6ms	10.16ms
SvelteKit	79ms	79.18ms	15.02ms	0.81ms	2.02ms	12.19ms
TanStack Start	87ms	86.91ms	21.77ms	1.34ms	4.59ms	15.84ms

First Paint (ms)

First Paint (ms) chart

First Paint (ms) data

Framework	Milliseconds
Astro	55.60 ms
SvelteKit	79.00 ms
Pracht	79.40 ms
TanStack Start	87.00 ms
Nuxt	88.40 ms
SolidStart	96.20 ms
React Router	107.80 ms
Next.js	384.40 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.57 ms
SvelteKit	79.18 ms
Pracht	79.48 ms
TanStack Start	86.91 ms
Nuxt	88.41 ms
SolidStart	96.14 ms
React Router	107.74 ms
Next.js	384.44 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: 15.88 ms

Median: 15.02 ms

1.22 ms

11.10 ms

13.65 ms

15.02 ms

16.74 ms

17.37 ms

17.74 ms

21.77 ms

Interaction Breakdown data

Framework or version	Interaction latency	Input delay	Processing duration	Presentation delay
Astro	1.22 ms	0.54 ms	0.68 ms	0.00 ms
Nuxt	11.10 ms	0.85 ms	1.26 ms	8.99 ms
SolidStart	13.65 ms	0.89 ms	2.60 ms	10.16 ms
SvelteKit	15.02 ms	0.81 ms	2.02 ms	12.19 ms
Pracht	16.74 ms	0.82 ms	2.07 ms	13.85 ms
React Router	17.37 ms	1.12 ms	2.83 ms	13.42 ms
Next.js	17.74 ms	1.67 ms	7.86 ms	8.21 ms
TanStack Start	21.77 ms	1.34 ms	4.59 ms	15.84 ms

Server Side Throughput Tests

Methodology: Server Side Throughput Tests.

Framework	Ops/sec	Median Latency	Body Size	Duplication
Baseline HTML	848	1.201ms	96.83kb	1x
Astro	738	1.311ms	96.89kb	1x
Next.js	124	7.747ms	204.56kb	2x
Nuxt	398	2.418ms	201.73kb	2x
Pracht	584	1.63ms	187.02kb	2x
React Router	343	2.86ms	216.98kb	2x
SolidStart	396	2.411ms	224.26kb	2x
SvelteKit	454	2.154ms	184.29kb	2x
TanStack Start	356	2.748ms	192.53kb	2x

Ops/sec

Ops/sec chart

Ops/sec data

Framework	Operations per second
Baseline HTML	848
Astro	738
Pracht	584
SvelteKit	454
Nuxt	398
SolidStart	396
TanStack Start	356
React Router	343
Next.js	124

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.53 KB
Nuxt	201.73 KB
Next.js	204.56 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.15 ms
SolidStart	2.41 ms
Nuxt	2.42 ms
TanStack Start	2.75 ms
React Router	2.86 ms
Next.js	7.75 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,801	100	17ms	34ms	92ms	52,905
Astro	1,550.8	50	27ms	48ms	100ms	46,580
Next.js	55.4	10	1191ms	4131ms	4607ms	1,668
Nuxt	549.8	50	70ms	282ms	2538ms	17,970
Pracht	688	25	40ms	106ms	1161ms	21,361
React Router	344.8	100	104ms	512ms	3262ms	11,461
SolidStart	570.6	50	89ms	330ms	2082ms	18,676
SvelteKit	601.4	25	75ms	237ms	2089ms	19,226
TanStack Start	409.8	50	105ms	657ms	2503ms	13,585

P99 Latency

P99 Latency at 25 Connections

P99 Latency at 25 Connections chart

P99 Latency at 25 Connections data

Framework	Milliseconds
Baseline HTML	17.00 ms
Astro	27.00 ms
Pracht	40.00 ms
Nuxt	70.00 ms
SvelteKit	75.00 ms
SolidStart	89.00 ms
React Router	104.00 ms
TanStack Start	105.00 ms
Next.js	1191.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	34.00 ms
Astro	48.00 ms
Pracht	106.00 ms
SvelteKit	237.00 ms
Nuxt	282.00 ms
SolidStart	330.00 ms
React Router	512.00 ms
TanStack Start	657.00 ms
Next.js	4131.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	92.00 ms
Astro	100.00 ms
Pracht	1161.00 ms
SolidStart	2082.00 ms
SvelteKit	2089.00 ms
TanStack Start	2503.00 ms
Nuxt	2538.00 ms
React Router	3262.00 ms
Next.js	4607.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
Baseline HTML	16.00 ms
Astro	18.00 ms
Pracht	37.00 ms
Nuxt	46.00 ms
SvelteKit	53.00 ms
SolidStart	62.00 ms
React Router	74.00 ms
TanStack Start	80.00 ms
Next.js	509.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
Baseline HTML	30.00 ms
Astro	33.00 ms
Pracht	77.00 ms
Nuxt	95.00 ms
SvelteKit	111.00 ms
SolidStart	135.00 ms
React Router	145.00 ms
TanStack Start	162.00 ms
Next.js	1701.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	65.00 ms
Baseline HTML	70.00 ms
Pracht	152.00 ms
SolidStart	162.00 ms
Nuxt	176.00 ms
SvelteKit	182.00 ms
TanStack Start	206.00 ms
React Router	287.00 ms
Next.js	2159.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
Baseline HTML	14.00 ms
Astro	17.00 ms
Pracht	36.00 ms
SvelteKit	41.00 ms
Nuxt	46.00 ms
SolidStart	53.00 ms
TanStack Start	63.00 ms
React Router	73.00 ms
Next.js	487.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	29.00 ms
Astro	32.00 ms
Pracht	75.00 ms
SolidStart	85.00 ms
Nuxt	88.00 ms
SvelteKit	96.00 ms
TanStack Start	124.00 ms
React Router	142.00 ms
Next.js	946.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
Baseline HTML	56.00 ms
Astro	63.00 ms
SolidStart	124.00 ms
SvelteKit	146.00 ms
Pracht	149.00 ms
Nuxt	166.00 ms
TanStack Start	174.00 ms
React Router	260.00 ms
Next.js	1011.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	50	5	1334ms	4442ms	4739ms	1,520
Nuxt	180.2	5	473ms	2751ms	3607ms	5,866
Pracht	339	25	91ms	480ms	3403ms	11,039
React Router	177.8	50	288ms	1515ms	4033ms	5,915
TanStack Start	246.6	50	240ms	1812ms	2894ms	8,222

P99 Latency

P99 Latency at 25 Connections

P99 Latency at 25 Connections chart

P99 Latency at 25 Connections data

Framework	Milliseconds
Pracht	91.00 ms
TanStack Start	240.00 ms
React Router	288.00 ms
Nuxt	473.00 ms
Next.js	1334.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	480.00 ms
React Router	1515.00 ms
TanStack Start	1812.00 ms
Nuxt	2751.00 ms
Next.js	4442.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	2894.00 ms
Pracht	3403.00 ms
Nuxt	3607.00 ms
React Router	4033.00 ms
Next.js	4739.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	135.00 ms
Nuxt	140.00 ms
React Router	157.00 ms
Next.js	545.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	155.00 ms
TanStack Start	262.00 ms
React Router	273.00 ms
Nuxt	298.00 ms
Next.js	2034.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	290.00 ms
Nuxt	324.00 ms
TanStack Start	349.00 ms
React Router	377.00 ms
Next.js	2392.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	75.00 ms
TanStack Start	107.00 ms
Nuxt	138.00 ms
React Router	140.00 ms
Next.js	516.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	194.00 ms
React Router	269.00 ms
Nuxt	288.00 ms
Next.js	1023.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	254.00 ms
Pracht	266.00 ms
Nuxt	303.00 ms
React Router	350.00 ms
Next.js	965.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.