Run Time Stats

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	101.2ms	101.37ms	1.95ms	1.68ms	0.26ms	0ms
Next.js	341ms	340.89ms	19.43ms	1.06ms	6.72ms	11.65ms
Nuxt	167.2ms	167.08ms	11.64ms	0.65ms	2.05ms	8.94ms
React Router	154.6ms	154.63ms	22.25ms	1.43ms	1.91ms	18.9ms
SolidStart	105.6ms	105.51ms	18.83ms	0.82ms	2.86ms	15.14ms
SvelteKit	130.2ms	130.06ms	15.41ms	0.63ms	3.31ms	11.47ms
TanStack Start	134.8ms	134.7ms	26.82ms	1.77ms	13.15ms	11.9ms

First Paint (ms)

First Paint (ms) chart

First Paint (ms) data

Framework	Milliseconds
Astro	101.20 ms
SolidStart	105.60 ms
SvelteKit	130.20 ms
TanStack Start	134.80 ms
React Router	154.60 ms
Nuxt	167.20 ms
Next.js	341.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
Astro	101.37 ms
SolidStart	105.51 ms
SvelteKit	130.06 ms
TanStack Start	134.70 ms
React Router	154.63 ms
Nuxt	167.08 ms
Next.js	340.89 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.83 ms

Median: 18.83 ms

1.95 ms

11.64 ms

15.41 ms

18.83 ms

19.43 ms

22.25 ms

26.82 ms

Interaction Breakdown data

Framework or version	Interaction latency	Input delay	Processing duration	Presentation delay
Astro	1.95 ms	1.68 ms	0.26 ms	0.00 ms
Nuxt	11.64 ms	0.65 ms	2.05 ms	8.94 ms
SvelteKit	15.41 ms	0.63 ms	3.31 ms	11.47 ms
SolidStart	18.83 ms	0.82 ms	2.86 ms	15.14 ms
Next.js	19.43 ms	1.06 ms	6.72 ms	11.65 ms
React Router	22.25 ms	1.43 ms	1.91 ms	18.90 ms
TanStack Start	26.82 ms	1.77 ms	13.15 ms	11.90 ms

Server Side Rendered Tests

Methodology: Server Side Rendered Tests.

Framework	First Paint	FCP	Interaction Latency	Input Delay	Processing Duration	Presentation Delay
Astro	67.8ms	67.72ms	1.39ms	0.72ms	0.67ms	0ms
Next.js	151.4ms	151.45ms	21.07ms	1.42ms	9.46ms	10.19ms
Nuxt	111.8ms	111.73ms	11.55ms	0.89ms	1.96ms	8.69ms
React Router	128.6ms	128.55ms	18.39ms	1.89ms	2.69ms	13.81ms
SolidStart	106.8ms	106.88ms	15.02ms	0.81ms	2.23ms	11.98ms
SvelteKit	87.6ms	87.73ms	14.64ms	0.64ms	2.99ms	11ms
TanStack Start	133.2ms	133.27ms	29.29ms	1.84ms	17.24ms	10.21ms

First Paint (ms)

First Paint (ms) chart

First Paint (ms) data

Framework	Milliseconds
Astro	67.80 ms
SvelteKit	87.60 ms
SolidStart	106.80 ms
Nuxt	111.80 ms
React Router	128.60 ms
TanStack Start	133.20 ms
Next.js	151.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	67.72 ms
SvelteKit	87.73 ms
SolidStart	106.88 ms
Nuxt	111.73 ms
React Router	128.55 ms
TanStack Start	133.27 ms
Next.js	151.45 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.02 ms

Median: 15.02 ms

1.39 ms

11.55 ms

14.64 ms

15.02 ms

18.39 ms

21.07 ms

29.29 ms

Interaction Breakdown data

Framework or version	Interaction latency	Input delay	Processing duration	Presentation delay
Astro	1.39 ms	0.72 ms	0.67 ms	0.00 ms
Nuxt	11.55 ms	0.89 ms	1.96 ms	8.69 ms
SvelteKit	14.64 ms	0.64 ms	2.99 ms	11.00 ms
SolidStart	15.02 ms	0.81 ms	2.23 ms	11.98 ms
React Router	18.39 ms	1.89 ms	2.69 ms	13.81 ms
Next.js	21.07 ms	1.42 ms	9.46 ms	10.19 ms
TanStack Start	29.29 ms	1.84 ms	17.24 ms	10.21 ms

Server Side Throughput Tests

Methodology: Server Side Throughput Tests.

Framework	Ops/sec	Median Latency	Body Size	Duplication
Baseline HTML	845	1.203ms	96.83kb	1x
Astro	641	1.508ms	96.89kb	1x
Next.js	213	4.758ms	199.57kb	2x
Nuxt	366	2.638ms	201.27kb	2x
React Router	340	2.891ms	211.85kb	2x
SolidStart	423	2.268ms	224.17kb	2x
SvelteKit	449	2.142ms	183.53kb	2x
TanStack Start	328	3.035ms	193.62kb	2x

Ops/sec

Ops/sec chart

Ops/sec data

Framework	Operations per second
Baseline HTML	845
Astro	641
SvelteKit	449
SolidStart	423
Nuxt	366
React Router	340
TanStack Start	328
Next.js	213

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	183.53 KB
TanStack Start	193.62 KB
Next.js	199.57 KB
Nuxt	201.27 KB
React Router	211.85 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.51 ms
SvelteKit	2.14 ms
SolidStart	2.27 ms
Nuxt	2.64 ms
React Router	2.89 ms
TanStack Start	3.04 ms
Next.js	4.76 ms

The chart includes a dotted median reference line calculated from the visible framework values.

Server Side Load Test

Methodology: Server Side Load Test.

Framework	Peak req/s	Peak Connections	P99 @ 25	P99 @ 50	P99 @ 100	Total Req.
Baseline HTML	1,617.4	100	20ms	46ms	116ms	46,505
Astro	1,169.6	100	34ms	67ms	276ms	34,875
Next.js	42.8	5	1854ms	4726ms	4755ms	1,217
Nuxt	71.41	5	1881ms	4182ms	4260ms	2,337
React Router	176.6	10	384ms	1666ms	3945ms	5,893
SolidStart	520.21	50	95ms	179ms	2116ms	16,858
SvelteKit	457.2	25	91ms	514ms	2786ms	14,706
TanStack Start	44.2	5	3517ms	4181ms	4446ms	1,335

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	34.00 ms
SvelteKit	91.00 ms
SolidStart	95.00 ms
React Router	384.00 ms
Next.js	1854.00 ms
Nuxt	1881.00 ms
TanStack Start	3517.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	46.00 ms
Astro	67.00 ms
SolidStart	179.00 ms
SvelteKit	514.00 ms
React Router	1666.00 ms
TanStack Start	4181.00 ms
Nuxt	4182.00 ms
Next.js	4726.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	116.00 ms
Astro	276.00 ms
SolidStart	2116.00 ms
SvelteKit	2786.00 ms
React Router	3945.00 ms
Nuxt	4260.00 ms
TanStack Start	4446.00 ms
Next.js	4755.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	19.00 ms
Astro	24.00 ms
SvelteKit	64.00 ms
SolidStart	70.00 ms
React Router	156.00 ms
Nuxt	342.00 ms
Next.js	661.00 ms
TanStack Start	711.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	37.00 ms
Astro	47.00 ms
SvelteKit	144.00 ms
SolidStart	150.00 ms
React Router	279.00 ms
Nuxt	471.00 ms
TanStack Start	877.00 ms
Next.js	2283.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
Baseline HTML	75.00 ms
Astro	88.00 ms
SolidStart	192.00 ms
SvelteKit	227.00 ms
React Router	383.00 ms
Nuxt	589.00 ms
TanStack Start	1297.00 ms
Next.js	2705.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	18.00 ms
Astro	23.00 ms
SvelteKit	58.00 ms
SolidStart	59.00 ms
React Router	138.00 ms
Nuxt	341.00 ms
TanStack Start	607.00 ms
Next.js	653.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	35.00 ms
Astro	44.00 ms
SolidStart	94.00 ms
SvelteKit	120.00 ms
React Router	271.00 ms
Nuxt	446.00 ms
TanStack Start	613.00 ms
Next.js	1097.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	69.00 ms
Astro	85.00 ms
SolidStart	130.00 ms
SvelteKit	165.00 ms
React Router	349.00 ms
Nuxt	451.00 ms
TanStack Start	655.00 ms
Next.js	1051.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	92	88	92	81	98
SolidStart	81	75	100	88	100
SvelteKit	79	78	78	69	95
Next.js	73	71	76	66	94
Nuxt	67	58	70	59	96
React Router	59	60	64	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	%
Astro	92
SolidStart	81
SvelteKit	79
Next.js	73
Nuxt	67
React Router	59

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	88
SvelteKit	78
SolidStart	75
Next.js	71
React Router	60
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	78
Next.js	76
Nuxt	70
React Router	64

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	88
Astro	81
SvelteKit	69
React Router	68
Next.js	66
Nuxt	59

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
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%
SolidStart	80	80	100	87	90
Astro	79	93	72	63	85
SvelteKit	67	80	58	55	74
Next.js	52	71	48	46	58
Nuxt	45	58	43	45	65
React Router	37	63	36	51	53

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	80
Astro	79
SvelteKit	67
Next.js	52
Nuxt	45
React Router	37

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
SolidStart	80
SvelteKit	80
Next.js	71
React Router	63
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	72
SvelteKit	58
Next.js	48
Nuxt	43
React Router	36

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	87
Astro	63
SvelteKit	55
React Router	51
Next.js	46
Nuxt	45

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	90
Astro	85
SvelteKit	74
Nuxt	65
Next.js	58
React Router	53

The chart includes a dotted median reference line calculated from the visible framework values.

Methodology: Core Web Vitals.