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	104.4ms	104.33ms	6.33ms	2.1ms	0.49ms	3.74ms
Next.js	339.8ms	339.73ms	20.73ms	1.38ms	6.26ms	13.09ms
Nuxt	204ms	203.85ms	12.85ms	1.5ms	1.59ms	9.76ms
Pracht	88ms	87.96ms	19.93ms	0.93ms	2.38ms	16.62ms
React Router	154.6ms	154.58ms	17.66ms	1.52ms	2.83ms	13.31ms
SolidStart	99.6ms	99.73ms	17.07ms	1.62ms	3.6ms	11.85ms
SvelteKit	110.2ms	110.29ms	17.32ms	1.09ms	2.4ms	13.82ms
TanStack Start	136.8ms	137.01ms	21.01ms	1.41ms	8.56ms	11.04ms

First Paint (ms)

First Paint (ms) chart

First Paint (ms) data

Framework	Milliseconds
Pracht	88.00 ms
SolidStart	99.60 ms
Astro	104.40 ms
SvelteKit	110.20 ms
TanStack Start	136.80 ms
React Router	154.60 ms
Nuxt	204.00 ms
Next.js	339.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
Pracht	87.96 ms
SolidStart	99.73 ms
Astro	104.33 ms
SvelteKit	110.29 ms
TanStack Start	137.01 ms
React Router	154.58 ms
Nuxt	203.85 ms
Next.js	339.73 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.49 ms

Median: 17.32 ms

6.33 ms

12.85 ms

17.07 ms

17.32 ms

17.66 ms

19.93 ms

20.73 ms

21.01 ms

Interaction Breakdown data

Framework or version	Interaction latency	Input delay	Processing duration	Presentation delay
Astro	6.33 ms	2.10 ms	0.49 ms	3.74 ms
Nuxt	12.85 ms	1.50 ms	1.59 ms	9.76 ms
SolidStart	17.07 ms	1.62 ms	3.60 ms	11.85 ms
SvelteKit	17.32 ms	1.09 ms	2.40 ms	13.82 ms
React Router	17.66 ms	1.52 ms	2.83 ms	13.31 ms
Pracht	19.93 ms	0.93 ms	2.38 ms	16.62 ms
Next.js	20.73 ms	1.38 ms	6.26 ms	13.09 ms
TanStack Start	21.01 ms	1.41 ms	8.56 ms	11.04 ms

Server Side Rendered Tests

Methodology: Server Side Rendered Tests.

Framework	First Paint	FCP	Interaction Latency	Input Delay	Processing Duration	Presentation Delay
Astro	58.6ms	58.62ms	0.88ms	0.63ms	0.25ms	0ms
Next.js	151.2ms	151.26ms	20.98ms	2.2ms	9.41ms	9.37ms
Nuxt	102.4ms	102.5ms	13.83ms	0.93ms	1.78ms	11.12ms
Pracht	89.6ms	89.44ms	18.75ms	1.24ms	2.62ms	14.89ms
React Router	117.8ms	117.69ms	22.68ms	1.7ms	3.78ms	17.2ms
SolidStart	76.8ms	76.64ms	18.96ms	0.94ms	2.82ms	15.19ms
SvelteKit	78.6ms	78.82ms	19.68ms	0.89ms	2.43ms	16.36ms
TanStack Start	85.8ms	85.73ms	20.94ms	1.34ms	9.07ms	10.53ms

First Paint (ms)

First Paint (ms) chart

First Paint (ms) data

Framework	Milliseconds
Astro	58.60 ms
SolidStart	76.80 ms
SvelteKit	78.60 ms
TanStack Start	85.80 ms
Pracht	89.60 ms
Nuxt	102.40 ms
React Router	117.80 ms
Next.js	151.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	58.62 ms
SolidStart	76.64 ms
SvelteKit	78.82 ms
TanStack Start	85.73 ms
Pracht	89.44 ms
Nuxt	102.50 ms
React Router	117.69 ms
Next.js	151.26 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.32 ms

Median: 19.68 ms

0.88 ms

13.83 ms

18.75 ms

18.96 ms

19.68 ms

20.94 ms

20.98 ms

22.68 ms

Interaction Breakdown data

Framework or version	Interaction latency	Input delay	Processing duration	Presentation delay
Astro	0.88 ms	0.63 ms	0.25 ms	0.00 ms
Nuxt	13.83 ms	0.93 ms	1.78 ms	11.12 ms
Pracht	18.75 ms	1.24 ms	2.62 ms	14.89 ms
SolidStart	18.96 ms	0.94 ms	2.82 ms	15.19 ms
SvelteKit	19.68 ms	0.89 ms	2.43 ms	16.36 ms
TanStack Start	20.94 ms	1.34 ms	9.07 ms	10.53 ms
Next.js	20.98 ms	2.20 ms	9.41 ms	9.37 ms
React Router	22.68 ms	1.70 ms	3.78 ms	17.20 ms

Server Side Throughput Tests

Methodology: Server Side Throughput Tests.

Framework	Ops/sec	Median Latency	Body Size	Duplication
Baseline HTML	830	1.222ms	96.83kb	1x
Astro	736	1.325ms	96.89kb	1x
Next.js	234	4.479ms	199.57kb	2x
Nuxt	398	2.441ms	201.73kb	2x
Pracht	574	1.682ms	187.02kb	2x
React Router	340	2.906ms	216.98kb	2x
SolidStart	390	2.474ms	224.26kb	2x
SvelteKit	461	2.151ms	184.3kb	2x
TanStack Start	343	2.883ms	192.67kb	2x

Ops/sec

Ops/sec chart

Ops/sec data

Framework	Operations per second
Baseline HTML	830
Astro	736
Pracht	574
SvelteKit	461
Nuxt	398
SolidStart	390
TanStack Start	343
React Router	340
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.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.22 ms
Astro	1.32 ms
Pracht	1.68 ms
SvelteKit	2.15 ms
Nuxt	2.44 ms
SolidStart	2.47 ms
TanStack Start	2.88 ms
React Router	2.91 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,740.2	100	21ms	48ms	104ms	48,122
Astro	1,581.6	50	24ms	41ms	92ms	47,107
Next.js	44	1	1787ms	4771ms	4821ms	1,239
Nuxt	510.6	10	73ms	336ms	2919ms	16,717
Pracht	705.8	25	38ms	97ms	867ms	21,891
React Router	326.8	50	95ms	462ms	3455ms	10,704
SolidStart	535.4	25	98ms	376ms	2144ms	17,315
SvelteKit	530.4	200	89ms	177ms	2107ms	16,967
TanStack Start	376.8	200	147ms	891ms	2534ms	12,206

P99 Latency

P99 Latency at 25 Connections

P99 Latency at 25 Connections chart

P99 Latency at 25 Connections data

Framework	Milliseconds
Baseline HTML	21.00 ms
Astro	24.00 ms
Pracht	38.00 ms
Nuxt	73.00 ms
SvelteKit	89.00 ms
React Router	95.00 ms
SolidStart	98.00 ms
TanStack Start	147.00 ms
Next.js	1787.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
Astro	41.00 ms
Baseline HTML	48.00 ms
Pracht	97.00 ms
SvelteKit	177.00 ms
Nuxt	336.00 ms
SolidStart	376.00 ms
React Router	462.00 ms
TanStack Start	891.00 ms
Next.js	4771.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	92.00 ms
Baseline HTML	104.00 ms
Pracht	867.00 ms
SvelteKit	2107.00 ms
SolidStart	2144.00 ms
TanStack Start	2534.00 ms
Nuxt	2919.00 ms
React Router	3455.00 ms
Next.js	4821.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	20.00 ms
Pracht	36.00 ms
Nuxt	51.00 ms
SolidStart	67.00 ms
SvelteKit	67.00 ms
React Router	79.00 ms
TanStack Start	96.00 ms
Next.js	662.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	39.00 ms
Pracht	72.00 ms
Nuxt	102.00 ms
SvelteKit	129.00 ms
SolidStart	146.00 ms
React Router	156.00 ms
TanStack Start	188.00 ms
Next.js	2291.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	67.00 ms
Baseline HTML	70.00 ms
Pracht	155.00 ms
SolidStart	159.00 ms
SvelteKit	182.00 ms
Nuxt	188.00 ms
TanStack Start	236.00 ms
React Router	282.00 ms
Next.js	2659.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	16.00 ms
Baseline HTML	18.00 ms
Pracht	35.00 ms
Nuxt	49.00 ms
SvelteKit	53.00 ms
SolidStart	56.00 ms
TanStack Start	76.00 ms
React Router	77.00 ms
Next.js	651.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	32.00 ms
Baseline HTML	35.00 ms
Pracht	70.00 ms
SolidStart	91.00 ms
Nuxt	98.00 ms
SvelteKit	110.00 ms
TanStack Start	144.00 ms
React Router	154.00 ms
Next.js	1075.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	58.00 ms
Astro	64.00 ms
SolidStart	123.00 ms
SvelteKit	147.00 ms
Pracht	153.00 ms
Nuxt	173.00 ms
TanStack Start	174.00 ms
React Router	273.00 ms
Next.js	1036.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.4	1	1979ms	4753ms	4713ms	1,071
Nuxt	178.8	5	487ms	2725ms	3714ms	5,866
Pracht	390.2	50	83ms	223ms	2560ms	11,952
React Router	164.6	5	288ms	1982ms	3929ms	5,429
TanStack Start	230.2	25	284ms	2057ms	3161ms	7,732

P99 Latency

P99 Latency at 25 Connections

P99 Latency at 25 Connections chart

P99 Latency at 25 Connections data

Framework	Milliseconds
Pracht	83.00 ms
TanStack Start	284.00 ms
React Router	288.00 ms
Nuxt	487.00 ms
Next.js	1979.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	223.00 ms
React Router	1982.00 ms
TanStack Start	2057.00 ms
Nuxt	2725.00 ms
Next.js	4753.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	2560.00 ms
TanStack Start	3161.00 ms
Nuxt	3714.00 ms
React Router	3929.00 ms
Next.js	4713.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	69.00 ms
TanStack Start	139.00 ms
Nuxt	154.00 ms
React Router	168.00 ms
Next.js	747.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	129.00 ms
TanStack Start	282.00 ms
Nuxt	292.00 ms
React Router	330.00 ms
Next.js	2476.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	257.00 ms
TanStack Start	325.00 ms
Nuxt	330.00 ms
React Router	414.00 ms
Next.js	2878.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	64.00 ms
TanStack Start	114.00 ms
Nuxt	141.00 ms
React Router	154.00 ms
Next.js	712.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	126.00 ms
TanStack Start	217.00 ms
Nuxt	286.00 ms
React Router	302.00 ms
Next.js	1138.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	218.00 ms
Pracht	245.00 ms
Nuxt	290.00 ms
React Router	379.00 ms
Next.js	1196.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.