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	108.8ms	108.68ms	2.46ms	2.13ms	0.33ms	0ms
Next.js	341.2ms	341.15ms	20.38ms	1.61ms	8.03ms	10.75ms
Nuxt	187.2ms	187.17ms	16.33ms	0.57ms	2ms	13.75ms
React Router	207.4ms	207.31ms	20.12ms	1.71ms	2.35ms	16.06ms
SolidStart	112.4ms	112.78ms	14.07ms	1ms	2.37ms	10.7ms
SvelteKit	138.2ms	138.3ms	16.91ms	0.75ms	3.3ms	12.86ms
TanStack Start	162.4ms	162.58ms	34.2ms	2.24ms	18.45ms	13.51ms

First Paint (ms)

First Paint (ms) chart

First Paint (ms) data

Framework	Milliseconds
Astro	108.80 ms
SolidStart	112.40 ms
SvelteKit	138.20 ms
TanStack Start	162.40 ms
Nuxt	187.20 ms
React Router	207.40 ms
Next.js	341.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	108.68 ms
SolidStart	112.78 ms
SvelteKit	138.30 ms
TanStack Start	162.58 ms
Nuxt	187.17 ms
React Router	207.31 ms
Next.js	341.15 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.91 ms

Median: 16.91 ms

2.46 ms

14.07 ms

16.33 ms

16.91 ms

20.12 ms

20.38 ms

34.20 ms

Interaction Breakdown data

Framework or version	Interaction latency	Input delay	Processing duration	Presentation delay
Astro	2.46 ms	2.13 ms	0.33 ms	0.00 ms
SolidStart	14.07 ms	1.00 ms	2.37 ms	10.70 ms
Nuxt	16.33 ms	0.57 ms	2.00 ms	13.75 ms
SvelteKit	16.91 ms	0.75 ms	3.30 ms	12.86 ms
React Router	20.12 ms	1.71 ms	2.35 ms	16.06 ms
Next.js	20.38 ms	1.61 ms	8.03 ms	10.75 ms
TanStack Start	34.20 ms	2.24 ms	18.45 ms	13.51 ms

Server Side Rendered Tests

Methodology: Server Side Rendered Tests.

Framework	First Paint	FCP	Interaction Latency	Input Delay	Processing Duration	Presentation Delay
Astro	72ms	72.01ms	0.96ms	0.68ms	0.28ms	0ms
Next.js	163ms	163.02ms	22.46ms	1.56ms	7.8ms	13.1ms
Nuxt	125ms	124.97ms	11.14ms	0.48ms	1.92ms	8.74ms
React Router	140.2ms	140.27ms	21.88ms	1.64ms	2.9ms	17.35ms
SolidStart	107.4ms	107.55ms	16.88ms	1.3ms	3ms	12.58ms
SvelteKit	99ms	98.99ms	14.71ms	0.69ms	3.15ms	10.87ms
TanStack Start	147ms	146.98ms	40.24ms	2ms	23.28ms	14.96ms

First Paint (ms)

First Paint (ms) chart

First Paint (ms) data

Framework	Milliseconds
Astro	72.00 ms
SvelteKit	99.00 ms
SolidStart	107.40 ms
Nuxt	125.00 ms
React Router	140.20 ms
TanStack Start	147.00 ms
Next.js	163.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	72.01 ms
SvelteKit	98.99 ms
SolidStart	107.55 ms
Nuxt	124.97 ms
React Router	140.27 ms
TanStack Start	146.98 ms
Next.js	163.02 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.88 ms

Median: 16.88 ms

0.96 ms

11.14 ms

14.71 ms

16.88 ms

21.88 ms

22.46 ms

40.24 ms

Interaction Breakdown data

Framework or version	Interaction latency	Input delay	Processing duration	Presentation delay
Astro	0.96 ms	0.68 ms	0.28 ms	0.00 ms
Nuxt	11.14 ms	0.48 ms	1.92 ms	8.74 ms
SvelteKit	14.71 ms	0.69 ms	3.15 ms	10.87 ms
SolidStart	16.88 ms	1.30 ms	3.00 ms	12.58 ms
React Router	21.88 ms	1.64 ms	2.90 ms	17.35 ms
Next.js	22.46 ms	1.56 ms	7.80 ms	13.10 ms
TanStack Start	40.24 ms	2.00 ms	23.28 ms	14.96 ms

Server Side Throughput Tests

Methodology: Server Side Throughput Tests.

Framework	Ops/sec	Median Latency	Body Size	Duplication
Baseline HTML	838	1.218ms	96.83kb	1x
Astro	660	1.441ms	96.89kb	1x
Next.js	231	4.533ms	199.57kb	2x
Nuxt	372	2.619ms	201.57kb	2x
React Router	341	2.884ms	216.9kb	2x
SolidStart	417	2.31ms	224.17kb	2x
SvelteKit	451	2.162ms	183.53kb	2x
TanStack Start	288	3.378ms	193.62kb	2x

Ops/sec

Ops/sec chart

Ops/sec data

Framework	Operations per second
Baseline HTML	838
Astro	660
SvelteKit	451
SolidStart	417
Nuxt	372
React Router	341
TanStack Start	288
Next.js	231

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.57 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.22 ms
Astro	1.44 ms
SvelteKit	2.16 ms
SolidStart	2.31 ms
Nuxt	2.62 ms
React Router	2.88 ms
TanStack Start	3.38 ms
Next.js	4.53 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,509.6	200	28ms	55ms	123ms	44,174
Astro	1,135.8	100	34ms	68ms	335ms	34,635
Next.js	46	5	1716ms	4798ms	4668ms	1,312
Nuxt	492.8	10	79ms	426ms	2828ms	15,993
React Router	326.4	25	105ms	589ms	3509ms	10,579
SolidStart	524	5	97ms	436ms	2179ms	17,140
SvelteKit	483	5	87ms	211ms	2414ms	15,092
TanStack Start	279.61	50	197ms	1771ms	2828ms	9,333

P99 Latency

P99 Latency at 25 Connections

P99 Latency at 25 Connections chart

P99 Latency at 25 Connections data

Framework	Milliseconds
Baseline HTML	28.00 ms
Astro	34.00 ms
Nuxt	79.00 ms
SvelteKit	87.00 ms
SolidStart	97.00 ms
React Router	105.00 ms
TanStack Start	197.00 ms
Next.js	1716.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	55.00 ms
Astro	68.00 ms
SvelteKit	211.00 ms
Nuxt	426.00 ms
SolidStart	436.00 ms
React Router	589.00 ms
TanStack Start	1771.00 ms
Next.js	4798.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	123.00 ms
Astro	335.00 ms
SolidStart	2179.00 ms
SvelteKit	2414.00 ms
Nuxt	2828.00 ms
TanStack Start	2828.00 ms
React Router	3509.00 ms
Next.js	4668.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	21.00 ms
Astro	23.00 ms
Nuxt	52.00 ms
SvelteKit	65.00 ms
SolidStart	70.00 ms
React Router	77.00 ms
TanStack Start	128.00 ms
Next.js	624.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	40.00 ms
Astro	46.00 ms
Nuxt	112.00 ms
SvelteKit	135.00 ms
SolidStart	148.00 ms
React Router	159.00 ms
TanStack Start	262.00 ms
Next.js	2260.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	90.00 ms
Baseline HTML	92.00 ms
SolidStart	180.00 ms
Nuxt	194.00 ms
TanStack Start	256.00 ms
SvelteKit	269.00 ms
React Router	294.00 ms
Next.js	2580.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	20.00 ms
Astro	22.00 ms
Nuxt	50.00 ms
SvelteKit	58.00 ms
SolidStart	59.00 ms
React Router	75.00 ms
TanStack Start	106.00 ms
Next.js	612.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	36.00 ms
Astro	44.00 ms
SolidStart	93.00 ms
Nuxt	105.00 ms
SvelteKit	116.00 ms
React Router	154.00 ms
TanStack Start	157.00 ms
Next.js	1050.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	75.00 ms
Astro	87.00 ms
SolidStart	121.00 ms
SvelteKit	164.00 ms
Nuxt	179.00 ms
TanStack Start	182.00 ms
React Router	276.00 ms
Next.js	1024.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	39	5	2041ms	4756ms	4695ms	1,097
Nuxt	73.8	10	1926ms	4160ms	4183ms	2,369
React Router	170.6	25	258ms	1525ms	3873ms	5,658
TanStack Start	44.6	5	3371ms	4149ms	4337ms	1,380

P99 Latency

P99 Latency at 25 Connections

P99 Latency at 25 Connections chart

P99 Latency at 25 Connections data

Framework	Milliseconds
React Router	258.00 ms
Nuxt	1926.00 ms
Next.js	2041.00 ms
TanStack Start	3371.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
React Router	1525.00 ms
TanStack Start	4149.00 ms
Nuxt	4160.00 ms
Next.js	4756.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
React Router	3873.00 ms
Nuxt	4183.00 ms
TanStack Start	4337.00 ms
Next.js	4695.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
React Router	151.00 ms
Nuxt	341.00 ms
TanStack Start	717.00 ms
Next.js	727.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
React Router	297.00 ms
Nuxt	471.00 ms
TanStack Start	773.00 ms
Next.js	2537.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
React Router	396.00 ms
Nuxt	545.00 ms
TanStack Start	1314.00 ms
Next.js	2920.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
React Router	144.00 ms
Nuxt	338.00 ms
TanStack Start	618.00 ms
Next.js	718.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
React Router	287.00 ms
Nuxt	445.00 ms
TanStack Start	603.00 ms
Next.js	1114.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
React Router	379.00 ms
Nuxt	452.00 ms
TanStack Start	574.00 ms
Next.js	1185.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.