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	96.4ms	96.28ms	2.3ms	1.98ms	0.33ms	0ms
Next.js	340ms	339.96ms	22.94ms	1.83ms	9.06ms	12.05ms
Nuxt	157ms	157.01ms	12.81ms	0.82ms	1.38ms	10.62ms
Pracht	98ms	97.85ms	18.44ms	0.96ms	4.05ms	13.43ms
React Router	165.4ms	165.33ms	19.31ms	1.78ms	2.64ms	14.9ms
SolidStart	91.4ms	91.37ms	17.05ms	0.94ms	2.52ms	13.59ms
SvelteKit	104.2ms	104.05ms	14.49ms	0.83ms	2.17ms	11.49ms
TanStack Start	128.2ms	128.01ms	22.37ms	1.37ms	7.72ms	13.28ms

First Paint (ms)

First Paint (ms) chart

First Paint (ms) data

Framework	Milliseconds
SolidStart	91.40 ms
Astro	96.40 ms
Pracht	98.00 ms
SvelteKit	104.20 ms
TanStack Start	128.20 ms
Nuxt	157.00 ms
React Router	165.40 ms
Next.js	340.00 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	91.37 ms
Astro	96.28 ms
Pracht	97.85 ms
SvelteKit	104.05 ms
TanStack Start	128.01 ms
Nuxt	157.01 ms
React Router	165.33 ms
Next.js	339.96 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.75 ms

Median: 17.05 ms

2.30 ms

12.81 ms

14.49 ms

17.05 ms

18.44 ms

19.31 ms

22.37 ms

22.94 ms

Interaction Breakdown data

Framework or version	Interaction latency	Input delay	Processing duration	Presentation delay
Astro	2.30 ms	1.98 ms	0.33 ms	0.00 ms
Nuxt	12.81 ms	0.82 ms	1.38 ms	10.62 ms
SvelteKit	14.49 ms	0.83 ms	2.17 ms	11.49 ms
SolidStart	17.05 ms	0.94 ms	2.52 ms	13.59 ms
Pracht	18.44 ms	0.96 ms	4.05 ms	13.43 ms
React Router	19.31 ms	1.78 ms	2.64 ms	14.90 ms
TanStack Start	22.37 ms	1.37 ms	7.72 ms	13.28 ms
Next.js	22.94 ms	1.83 ms	9.06 ms	12.05 ms

Server Side Rendered Tests

Methodology: Server Side Rendered Tests.

Framework	First Paint	FCP	Interaction Latency	Input Delay	Processing Duration	Presentation Delay
Astro	63.4ms	63.46ms	1.09ms	0.77ms	0.32ms	0ms
Next.js	143.8ms	143.84ms	18.07ms	1.44ms	6.14ms	10.49ms
Nuxt	92ms	91.93ms	11.89ms	1.19ms	1.2ms	9.5ms
Pracht	87ms	86.98ms	15.93ms	0.84ms	2.79ms	12.3ms
React Router	105.8ms	105.65ms	19.48ms	2.37ms	3.17ms	13.93ms
SolidStart	85.2ms	84.97ms	17.06ms	1.29ms	3.88ms	11.89ms
SvelteKit	84.8ms	84.73ms	18.82ms	0.88ms	3.79ms	14.15ms
TanStack Start	93ms	92.95ms	20.4ms	1.07ms	9.56ms	9.76ms

First Paint (ms)

First Paint (ms) chart

First Paint (ms) data

Framework	Milliseconds
Astro	63.40 ms
SvelteKit	84.80 ms
SolidStart	85.20 ms
Pracht	87.00 ms
Nuxt	92.00 ms
TanStack Start	93.00 ms
React Router	105.80 ms
Next.js	143.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	63.46 ms
SvelteKit	84.73 ms
SolidStart	84.97 ms
Pracht	86.98 ms
Nuxt	91.93 ms
TanStack Start	92.95 ms
React Router	105.65 ms
Next.js	143.84 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.56 ms

Median: 18.07 ms

1.09 ms

11.89 ms

15.93 ms

17.06 ms

18.07 ms

18.82 ms

19.48 ms

20.40 ms

Interaction Breakdown data

Framework or version	Interaction latency	Input delay	Processing duration	Presentation delay
Astro	1.09 ms	0.77 ms	0.32 ms	0.00 ms
Nuxt	11.89 ms	1.19 ms	1.20 ms	9.50 ms
Pracht	15.93 ms	0.84 ms	2.79 ms	12.30 ms
SolidStart	17.06 ms	1.29 ms	3.88 ms	11.89 ms
Next.js	18.07 ms	1.44 ms	6.14 ms	10.49 ms
SvelteKit	18.82 ms	0.88 ms	3.79 ms	14.15 ms
React Router	19.48 ms	2.37 ms	3.17 ms	13.93 ms
TanStack Start	20.40 ms	1.07 ms	9.56 ms	9.76 ms

Server Side Throughput Tests

Methodology: Server Side Throughput Tests.

Framework	Ops/sec	Median Latency	Body Size	Duplication
Baseline HTML	847	1.204ms	96.83kb	1x
Astro	734	1.325ms	96.89kb	1x
Next.js	218	4.798ms	199.57kb	2x
Nuxt	389	2.492ms	201.73kb	2x
Pracht	598	1.619ms	187.02kb	2x
React Router	328	2.969ms	216.98kb	2x
SolidStart	397	2.432ms	224.26kb	2x
SvelteKit	459	2.144ms	184.3kb	2x
TanStack Start	375	2.654ms	192.67kb	2x

Ops/sec

Ops/sec chart

Ops/sec data

Framework	Operations per second
Baseline HTML	847
Astro	734
Pracht	598
SvelteKit	459
SolidStart	397
Nuxt	389
TanStack Start	375
React Router	328
Next.js	218

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.20 ms
Astro	1.32 ms
Pracht	1.62 ms
SvelteKit	2.14 ms
SolidStart	2.43 ms
Nuxt	2.49 ms
TanStack Start	2.65 ms
React Router	2.97 ms
Next.js	4.80 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,736	200	20ms	42ms	113ms	49,036
Astro	1,478.2	100	31ms	51ms	104ms	44,022
Next.js	43	5	1949ms	4720ms	4661ms	1,179
Nuxt	509.8	50	78ms	359ms	2845ms	15,844
Pracht	664.8	25	40ms	101ms	974ms	20,990
React Router	332.4	25	105ms	583ms	3434ms	11,017
SolidStart	513.6	10	100ms	390ms	2115ms	16,852
SvelteKit	535	25	84ms	162ms	2061ms	17,179
TanStack Start	377.2	50	102ms	857ms	2652ms	12,434

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	31.00 ms
Pracht	40.00 ms
Nuxt	78.00 ms
SvelteKit	84.00 ms
SolidStart	100.00 ms
TanStack Start	102.00 ms
React Router	105.00 ms
Next.js	1949.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	42.00 ms
Astro	51.00 ms
Pracht	101.00 ms
SvelteKit	162.00 ms
Nuxt	359.00 ms
SolidStart	390.00 ms
React Router	583.00 ms
TanStack Start	857.00 ms
Next.js	4720.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	104.00 ms
Baseline HTML	113.00 ms
Pracht	974.00 ms
SvelteKit	2061.00 ms
SolidStart	2115.00 ms
TanStack Start	2652.00 ms
Nuxt	2845.00 ms
React Router	3434.00 ms
Next.js	4661.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	17.00 ms
Astro	19.00 ms
Pracht	38.00 ms
Nuxt	51.00 ms
SvelteKit	61.00 ms
SolidStart	71.00 ms
React Router	76.00 ms
TanStack Start	87.00 ms
Next.js	690.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	36.00 ms
Pracht	77.00 ms
Nuxt	99.00 ms
SvelteKit	135.00 ms
React Router	151.00 ms
SolidStart	155.00 ms
TanStack Start	179.00 ms
Next.js	2374.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	71.00 ms
Baseline HTML	78.00 ms
Pracht	159.00 ms
SolidStart	166.00 ms
Nuxt	195.00 ms
SvelteKit	201.00 ms
TanStack Start	235.00 ms
React Router	292.00 ms
Next.js	2726.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	16.00 ms
Astro	17.00 ms
Pracht	38.00 ms
Nuxt	49.00 ms
SvelteKit	50.00 ms
SolidStart	59.00 ms
TanStack Start	71.00 ms
React Router	74.00 ms
Next.js	683.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	35.00 ms
Pracht	74.00 ms
SolidStart	92.00 ms
Nuxt	96.00 ms
SvelteKit	107.00 ms
TanStack Start	142.00 ms
React Router	148.00 ms
Next.js	1149.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	67.00 ms
Baseline HTML	69.00 ms
SolidStart	128.00 ms
SvelteKit	146.00 ms
Pracht	152.00 ms
TanStack Start	171.00 ms
Nuxt	180.00 ms
React Router	270.00 ms
Next.js	1067.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	5	2007ms	4603ms	4752ms	1,151
Nuxt	178	25	455ms	2701ms	3704ms	5,908
Pracht	376.2	25	82ms	365ms	3005ms	11,298
React Router	169.6	5	315ms	2030ms	3985ms	5,527
TanStack Start	214	5	306ms	2229ms	3054ms	7,099

P99 Latency

P99 Latency at 25 Connections

P99 Latency at 25 Connections chart

P99 Latency at 25 Connections data

Framework	Milliseconds
Pracht	82.00 ms
TanStack Start	306.00 ms
React Router	315.00 ms
Nuxt	455.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	365.00 ms
React Router	2030.00 ms
TanStack Start	2229.00 ms
Nuxt	2701.00 ms
Next.js	4603.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	3005.00 ms
TanStack Start	3054.00 ms
Nuxt	3704.00 ms
React Router	3985.00 ms
Next.js	4752.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	68.00 ms
Nuxt	147.00 ms
TanStack Start	153.00 ms
React Router	175.00 ms
Next.js	703.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	140.00 ms
Nuxt	292.00 ms
TanStack Start	296.00 ms
React Router	314.00 ms
Next.js	2308.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	260.00 ms
Nuxt	315.00 ms
TanStack Start	356.00 ms
React Router	431.00 ms
Next.js	2799.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	67.00 ms
TanStack Start	121.00 ms
Nuxt	137.00 ms
React Router	159.00 ms
Next.js	693.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	135.00 ms
TanStack Start	225.00 ms
Nuxt	283.00 ms
React Router	303.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
Pracht	246.00 ms
TanStack Start	250.00 ms
Nuxt	294.00 ms
React Router	390.00 ms
Next.js	1084.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.