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	95.2ms	95.01ms	3.77ms	2.42ms	0.42ms	0.93ms
Next.js	340.2ms	340.4ms	21.31ms	1.66ms	7.76ms	11.89ms
Nuxt	147.4ms	147.43ms	8.81ms	0.79ms	1.21ms	6.81ms
Pracht	98.6ms	98.61ms	18.71ms	0.85ms	2.31ms	15.55ms
React Router	152.2ms	152.22ms	22.1ms	2.38ms	2.15ms	17.57ms
SolidStart	89ms	88.79ms	20.83ms	3.35ms	2.99ms	14.49ms
SvelteKit	109.4ms	109.55ms	14.95ms	0.8ms	1.71ms	12.44ms
TanStack Start	119.2ms	119.4ms	41.42ms	2.13ms	28.86ms	10.42ms

First Paint (ms)

First Paint (ms) chart

First Paint (ms) data

Framework	Milliseconds
SolidStart	89.00 ms
Astro	95.20 ms
Pracht	98.60 ms
SvelteKit	109.40 ms
TanStack Start	119.20 ms
Nuxt	147.40 ms
React Router	152.20 ms
Next.js	340.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.79 ms
Astro	95.01 ms
Pracht	98.61 ms
SvelteKit	109.55 ms
TanStack Start	119.40 ms
Nuxt	147.43 ms
React Router	152.22 ms
Next.js	340.40 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: 19.77 ms

Median: 20.83 ms

3.77 ms

8.81 ms

14.95 ms

18.71 ms

20.83 ms

21.31 ms

22.10 ms

41.42 ms

Interaction Breakdown data

Framework or version	Interaction latency	Input delay	Processing duration	Presentation delay
Astro	3.77 ms	2.42 ms	0.42 ms	0.93 ms
Nuxt	8.81 ms	0.79 ms	1.21 ms	6.81 ms
SvelteKit	14.95 ms	0.80 ms	1.71 ms	12.44 ms
Pracht	18.71 ms	0.85 ms	2.31 ms	15.55 ms
SolidStart	20.83 ms	3.35 ms	2.99 ms	14.49 ms
Next.js	21.31 ms	1.66 ms	7.76 ms	11.89 ms
React Router	22.10 ms	2.38 ms	2.15 ms	17.57 ms
TanStack Start	41.42 ms	2.13 ms	28.86 ms	10.42 ms

Server Side Rendered Tests

Methodology: Server Side Rendered Tests.

Framework	First Paint	FCP	Interaction Latency	Input Delay	Processing Duration	Presentation Delay
Astro	60ms	60.21ms	0.79ms	0.5ms	0.29ms	0ms
Next.js	128.8ms	128.82ms	17.87ms	1.82ms	6.69ms	9.36ms
Nuxt	85.6ms	85.44ms	10.75ms	0.87ms	1.36ms	8.52ms
Pracht	78.4ms	78.51ms	14.3ms	0.84ms	2.79ms	10.66ms
React Router	116.6ms	116.35ms	19.19ms	1.59ms	2.71ms	14.89ms
SolidStart	85ms	85.01ms	14.77ms	1.47ms	3.15ms	10.15ms
SvelteKit	75.8ms	75.71ms	15.99ms	0.76ms	2.46ms	12.77ms
TanStack Start	102.6ms	102.72ms	47.93ms	1.85ms	34.42ms	11.66ms

First Paint (ms)

First Paint (ms) chart

First Paint (ms) data

Framework	Milliseconds
Astro	60.00 ms
SvelteKit	75.80 ms
Pracht	78.40 ms
SolidStart	85.00 ms
Nuxt	85.60 ms
TanStack Start	102.60 ms
React Router	116.60 ms
Next.js	128.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	60.21 ms
SvelteKit	75.71 ms
Pracht	78.51 ms
SolidStart	85.01 ms
Nuxt	85.44 ms
TanStack Start	102.72 ms
React Router	116.35 ms
Next.js	128.82 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.38 ms

Median: 15.99 ms

0.79 ms

10.75 ms

14.30 ms

14.77 ms

15.99 ms

17.87 ms

19.19 ms

47.93 ms

Interaction Breakdown data

Framework or version	Interaction latency	Input delay	Processing duration	Presentation delay
Astro	0.79 ms	0.50 ms	0.29 ms	0.00 ms
Nuxt	10.75 ms	0.87 ms	1.36 ms	8.52 ms
Pracht	14.30 ms	0.84 ms	2.79 ms	10.66 ms
SolidStart	14.77 ms	1.47 ms	3.15 ms	10.15 ms
SvelteKit	15.99 ms	0.76 ms	2.46 ms	12.77 ms
Next.js	17.87 ms	1.82 ms	6.69 ms	9.36 ms
React Router	19.19 ms	1.59 ms	2.71 ms	14.89 ms
TanStack Start	47.93 ms	1.85 ms	34.42 ms	11.66 ms

Server Side Throughput Tests

Methodology: Server Side Throughput Tests.

Framework	Ops/sec	Median Latency	Body Size	Duplication
Baseline HTML	851	1.201ms	96.83kb	1x
Astro	742	1.314ms	96.89kb	1x
Next.js	234	4.484ms	199.57kb	2x
Nuxt	405	2.417ms	201.73kb	2x
Pracht	598	1.623ms	187.02kb	2x
React Router	349	2.836ms	216.9kb	2x
SolidStart	441	2.197ms	224.17kb	2x
SvelteKit	448	2.19ms	184.3kb	2x
TanStack Start	344	2.855ms	192.62kb	2x

Ops/sec

Ops/sec chart

Ops/sec data

Framework	Operations per second
Baseline HTML	851
Astro	742
Pracht	598
SvelteKit	448
SolidStart	441
Nuxt	405
React Router	349
TanStack Start	344
Next.js	234

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.62 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.31 ms
Pracht	1.62 ms
SvelteKit	2.19 ms
SolidStart	2.20 ms
Nuxt	2.42 ms
React Router	2.84 ms
TanStack Start	2.85 ms
Next.js	4.48 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,683.2	50	20ms	38ms	111ms	49,090
Astro	1,535	50	25ms	45ms	100ms	45,772
Next.js	45.8	1	1789ms	4728ms	4716ms	1,282
Nuxt	529.21	10	69ms	346ms	2784ms	17,231
Pracht	680.2	25	40ms	117ms	1159ms	21,377
React Router	343	25	99ms	485ms	3482ms	11,341
SolidStart	529	50	101ms	368ms	2146ms	16,866
SvelteKit	579.6	25	76ms	197ms	1961ms	18,704
TanStack Start	384.6	25	128ms	755ms	2732ms	12,716

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	25.00 ms
Pracht	40.00 ms
Nuxt	69.00 ms
SvelteKit	76.00 ms
React Router	99.00 ms
SolidStart	101.00 ms
TanStack Start	128.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	38.00 ms
Astro	45.00 ms
Pracht	117.00 ms
SvelteKit	197.00 ms
Nuxt	346.00 ms
SolidStart	368.00 ms
React Router	485.00 ms
TanStack Start	755.00 ms
Next.js	4728.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	100.00 ms
Baseline HTML	111.00 ms
Pracht	1159.00 ms
SvelteKit	1961.00 ms
SolidStart	2146.00 ms
TanStack Start	2732.00 ms
Nuxt	2784.00 ms
React Router	3482.00 ms
Next.js	4716.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	18.00 ms
Pracht	38.00 ms
Nuxt	50.00 ms
SvelteKit	56.00 ms
SolidStart	71.00 ms
React Router	73.00 ms
TanStack Start	84.00 ms
Next.js	647.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	35.00 ms
Pracht	77.00 ms
Nuxt	100.00 ms
SvelteKit	123.00 ms
React Router	146.00 ms
SolidStart	149.00 ms
TanStack Start	173.00 ms
Next.js	2313.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	77.00 ms
Pracht	148.00 ms
SolidStart	174.00 ms
Nuxt	180.00 ms
SvelteKit	193.00 ms
TanStack Start	236.00 ms
React Router	309.00 ms
Next.js	2564.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	17.00 ms
Pracht	37.00 ms
SvelteKit	44.00 ms
Nuxt	48.00 ms
SolidStart	60.00 ms
TanStack Start	71.00 ms
React Router	72.00 ms
Next.js	639.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	31.00 ms
Astro	33.00 ms
Pracht	75.00 ms
SolidStart	90.00 ms
Nuxt	96.00 ms
SvelteKit	97.00 ms
React Router	144.00 ms
TanStack Start	154.00 ms
Next.js	1051.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	69.00 ms
SolidStart	125.00 ms
SvelteKit	137.00 ms
Pracht	145.00 ms
Nuxt	169.00 ms
TanStack Start	179.00 ms
React Router	258.00 ms
Next.js	1037.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.4	1	1921ms	4636ms	4664ms	1,178
Nuxt	164.8	25	553ms	3238ms	3748ms	5,165
Pracht	329.2	50	95ms	395ms	3511ms	10,792
React Router	173.6	25	302ms	1631ms	3983ms	5,738
TanStack Start	166.2	25	546ms	3338ms	3378ms	5,585

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	302.00 ms
TanStack Start	546.00 ms
Nuxt	553.00 ms
Next.js	1921.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	395.00 ms
React Router	1631.00 ms
Nuxt	3238.00 ms
TanStack Start	3338.00 ms
Next.js	4636.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	3378.00 ms
Pracht	3511.00 ms
Nuxt	3748.00 ms
React Router	3983.00 ms
Next.js	4664.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	83.00 ms
React Router	151.00 ms
Nuxt	158.00 ms
TanStack Start	199.00 ms
Next.js	686.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	163.00 ms
React Router	287.00 ms
Nuxt	336.00 ms
TanStack Start	357.00 ms
Next.js	2350.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	295.00 ms
TanStack Start	343.00 ms
Nuxt	345.00 ms
React Router	406.00 ms
Next.js	2599.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	79.00 ms
React Router	141.00 ms
Nuxt	154.00 ms
TanStack Start	155.00 ms
Next.js	666.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	156.00 ms
TanStack Start	266.00 ms
React Router	282.00 ms
Nuxt	314.00 ms
Next.js	1102.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	240.00 ms
Pracht	258.00 ms
Nuxt	318.00 ms
React Router	365.00 ms
Next.js	1073.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.