Skip to content

Run Time Stats

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.

FrameworkFirst PaintFCPInteraction LatencyInput DelayProcessing DurationPresentation Delay
Astro113.4ms113.25ms6.83ms2.83ms0.83ms3.17ms
Next.js342.8ms342.7ms22.4ms1.52ms8.13ms12.75ms
Nuxt162ms161.89ms12.09ms0.52ms1.49ms10.08ms
React Router160.8ms160.62ms18.64ms1.43ms1.9ms15.3ms
SolidStart99.6ms99.74ms17.16ms1.26ms2.41ms13.49ms
SvelteKit132.6ms132.57ms13.43ms0.68ms4.03ms8.72ms
TanStack Start160.8ms160.97ms30.83ms1.97ms15.38ms13.49ms

First Paint (ms)

First Paint (ms) chart
First Paint (ms) data
FrameworkMilliseconds
SolidStart99.60 ms
Astro113.40 ms
SvelteKit132.60 ms
React Router160.80 ms
TanStack Start160.80 ms
Nuxt162.00 ms
Next.js342.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
FrameworkMilliseconds
SolidStart99.74 ms
Astro113.25 ms
SvelteKit132.57 ms
React Router160.62 ms
TanStack Start160.97 ms
Nuxt161.89 ms
Next.js342.70 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.
6.83 ms
12.09 ms
13.43 ms
17.16 ms
18.64 ms
22.40 ms
30.83 ms
Interaction Breakdown data
Framework or versionInteraction latencyInput delayProcessing durationPresentation delay
Astro6.83 ms2.83 ms0.83 ms3.17 ms
Nuxt12.09 ms0.52 ms1.49 ms10.08 ms
SvelteKit13.43 ms0.68 ms4.03 ms8.72 ms
SolidStart17.16 ms1.26 ms2.41 ms13.49 ms
React Router18.64 ms1.43 ms1.90 ms15.30 ms
Next.js22.40 ms1.52 ms8.13 ms12.75 ms
TanStack Start30.83 ms1.97 ms15.38 ms13.49 ms

Methodology: Server Side Rendered Tests.

FrameworkFirst PaintFCPInteraction LatencyInput DelayProcessing DurationPresentation Delay
Astro71ms70.97ms1.02ms0.75ms0.27ms0ms
Next.js164.2ms164.28ms22.66ms3.1ms10.19ms9.38ms
Nuxt102.6ms102.66ms11.84ms0.43ms1.3ms10.11ms
React Router120.6ms120.65ms19.3ms1.53ms3.64ms14.13ms
SolidStart103.6ms103.63ms17.49ms0.92ms2.13ms14.44ms
SvelteKit86ms85.89ms16.93ms0.68ms3.25ms13.01ms
TanStack Start126.6ms126.44ms24.02ms1.6ms13.64ms8.78ms

First Paint (ms)

First Paint (ms) chart
First Paint (ms) data
FrameworkMilliseconds
Astro71.00 ms
SvelteKit86.00 ms
Nuxt102.60 ms
SolidStart103.60 ms
React Router120.60 ms
TanStack Start126.60 ms
Next.js164.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
FrameworkMilliseconds
Astro70.97 ms
SvelteKit85.89 ms
Nuxt102.66 ms
SolidStart103.63 ms
React Router120.65 ms
TanStack Start126.44 ms
Next.js164.28 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.
1.02 ms
11.84 ms
16.93 ms
17.49 ms
19.30 ms
22.66 ms
24.02 ms
Interaction Breakdown data
Framework or versionInteraction latencyInput delayProcessing durationPresentation delay
Astro1.02 ms0.75 ms0.27 ms0.00 ms
Nuxt11.84 ms0.43 ms1.30 ms10.11 ms
SvelteKit16.93 ms0.68 ms3.25 ms13.01 ms
SolidStart17.49 ms0.92 ms2.13 ms14.44 ms
React Router19.30 ms1.53 ms3.64 ms14.13 ms
Next.js22.66 ms3.10 ms10.19 ms9.38 ms
TanStack Start24.02 ms1.60 ms13.64 ms8.78 ms

Methodology: Server Side Throughput Tests.

FrameworkOps/secMedian LatencyBody SizeDuplication
Baseline HTML8361.206ms96.83kb1x
Astro6631.442ms96.89kb1x
Next.js2234.594ms199.57kb2x
Nuxt3682.644ms201.27kb2x
React Router3272.925ms212.07kb2x
SolidStart4002.463ms224.17kb2x
SvelteKit4412.197ms183.53kb2x
TanStack Start3183.116ms193.62kb2x

Ops/sec

Ops/sec chart
Ops/sec data
FrameworkOperations per second
Baseline HTML836
Astro663
SvelteKit441
SolidStart400
Nuxt368
React Router327
TanStack Start318
Next.js223

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

Body Size

Body Size chart
Body Size data
FrameworkKilobytes
Baseline HTML96.83 KB
Astro96.89 KB
SvelteKit183.53 KB
TanStack Start193.62 KB
Next.js199.57 KB
Nuxt201.27 KB
React Router212.07 KB
SolidStart224.17 KB

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

Median Latency

Median Latency chart
Median Latency data
FrameworkMilliseconds
Baseline HTML1.21 ms
Astro1.44 ms
SvelteKit2.20 ms
SolidStart2.46 ms
Nuxt2.64 ms
React Router2.92 ms
TanStack Start3.12 ms
Next.js4.59 ms

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

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.

FrameworkPeak req/sPeak ConnectionsP99 @ 25P99 @ 50P99 @ 100Total Req.
Baseline HTML1,692.610019ms39ms106ms48,201
Astro1,20110032ms65ms284ms36,227
Next.js45.851733ms4773ms4639ms1,287
Nuxt476.4577ms139ms2931ms15,293
React Router335.625109ms614ms3499ms11,109
SolidStart527.211091ms386ms2060ms17,239
SvelteKit494.41077ms207ms2599ms15,700
TanStack Start298.810172ms1554ms2759ms9,655

P99 Latency at 25 Connections

P99 Latency at 25 Connections chart
P99 Latency at 25 Connections data
FrameworkMilliseconds
Baseline HTML19.00 ms
Astro32.00 ms
Nuxt77.00 ms
SvelteKit77.00 ms
SolidStart91.00 ms
React Router109.00 ms
TanStack Start172.00 ms
Next.js1733.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
FrameworkMilliseconds
Baseline HTML39.00 ms
Astro65.00 ms
Nuxt139.00 ms
SvelteKit207.00 ms
SolidStart386.00 ms
React Router614.00 ms
TanStack Start1554.00 ms
Next.js4773.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
FrameworkMilliseconds
Baseline HTML106.00 ms
Astro284.00 ms
SolidStart2060.00 ms
SvelteKit2599.00 ms
TanStack Start2759.00 ms
Nuxt2931.00 ms
React Router3499.00 ms
Next.js4639.00 ms

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

P90 Latency at 25 Connections

P90 Latency at 25 Connections chart
P90 Latency at 25 Connections data
FrameworkMilliseconds
Baseline HTML19.00 ms
Astro23.00 ms
Nuxt56.00 ms
SvelteKit60.00 ms
SolidStart69.00 ms
React Router75.00 ms
TanStack Start124.00 ms
Next.js641.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
FrameworkMilliseconds
Baseline HTML36.00 ms
Astro44.00 ms
Nuxt121.00 ms
SvelteKit130.00 ms
SolidStart145.00 ms
React Router149.00 ms
TanStack Start244.00 ms
Next.js2324.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
FrameworkMilliseconds
Baseline HTML74.00 ms
Astro84.00 ms
SolidStart172.00 ms
Nuxt204.00 ms
SvelteKit227.00 ms
TanStack Start279.00 ms
React Router280.00 ms
Next.js2536.00 ms

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

P75 Latency at 25 Connections

P75 Latency at 25 Connections chart
P75 Latency at 25 Connections data
FrameworkMilliseconds
Baseline HTML17.00 ms
Astro21.00 ms
Nuxt54.00 ms
SvelteKit55.00 ms
SolidStart58.00 ms
React Router74.00 ms
TanStack Start99.00 ms
Next.js628.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
FrameworkMilliseconds
Baseline HTML34.00 ms
Astro42.00 ms
SolidStart90.00 ms
Nuxt110.00 ms
SvelteKit113.00 ms
React Router146.00 ms
TanStack Start161.00 ms
Next.js1093.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
FrameworkMilliseconds
Baseline HTML67.00 ms
Astro82.00 ms
SolidStart127.00 ms
TanStack Start170.00 ms
SvelteKit173.00 ms
Nuxt177.00 ms
React Router268.00 ms
Next.js1057.00 ms

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

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.

FrameworkPeak req/sPeak ConnectionsP99 @ 25P99 @ 50P99 @ 100Total Req.
Next.js4211833ms4726ms4646ms1,207
Nuxt73.851915ms4123ms4182ms2,390
React Router173.425322ms1793ms3946ms5,718
TanStack Start45.452804ms4058ms4364ms1,415

P99 Latency at 25 Connections

P99 Latency at 25 Connections chart
P99 Latency at 25 Connections data
FrameworkMilliseconds
React Router322.00 ms
Next.js1833.00 ms
Nuxt1915.00 ms
TanStack Start2804.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
FrameworkMilliseconds
React Router1793.00 ms
TanStack Start4058.00 ms
Nuxt4123.00 ms
Next.js4726.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
FrameworkMilliseconds
React Router3946.00 ms
Nuxt4182.00 ms
TanStack Start4364.00 ms
Next.js4646.00 ms

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

P90 Latency at 25 Connections

P90 Latency at 25 Connections chart
P90 Latency at 25 Connections data
FrameworkMilliseconds
React Router149.00 ms
Nuxt336.00 ms
Next.js658.00 ms
TanStack Start822.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
FrameworkMilliseconds
React Router292.00 ms
Nuxt486.00 ms
TanStack Start899.00 ms
Next.js2243.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
FrameworkMilliseconds
React Router392.00 ms
Nuxt531.00 ms
TanStack Start1187.00 ms
Next.js2624.00 ms

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

P75 Latency at 25 Connections

P75 Latency at 25 Connections chart
P75 Latency at 25 Connections data
FrameworkMilliseconds
React Router142.00 ms
Nuxt334.00 ms
TanStack Start532.00 ms
Next.js647.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
FrameworkMilliseconds
React Router284.00 ms
Nuxt450.00 ms
TanStack Start534.00 ms
Next.js1100.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
FrameworkMilliseconds
React Router369.00 ms
Nuxt451.00 ms
TanStack Start512.00 ms
Next.js1069.00 ms

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

FrameworkLCP%CLS%FCP%TTFB%INP%
Astro9389928198
SolidStart1007710085100
SvelteKit7978776895
Next.js7472766694
TanStack Start5581462991
Nuxt6858695996
React Router5961656890

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%
SolidStart100
Astro93
SvelteKit79
Next.js74
Nuxt68
React Router59
TanStack Start55

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%
Astro89
TanStack Start81
SvelteKit78
SolidStart77
Next.js72
React Router61
Nuxt58

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%
SolidStart100
Astro92
SvelteKit77
Next.js76
Nuxt69
React Router65
TanStack Start46

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%
SolidStart85
Astro81
SvelteKit68
React Router68
Next.js66
Nuxt59
TanStack Start29

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%
SolidStart100
Astro98
Nuxt96
SvelteKit95
Next.js94
TanStack Start91
React Router90

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

FrameworkLCP%CLS%FCP%TTFB%INP%
Astro8093736485
SolidStart8866888575
SvelteKit6781585474
Next.js5372484559
Nuxt4659444665
React Router3763375053
TanStack Start3184191351

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%
SolidStart88
Astro80
SvelteKit67
Next.js53
Nuxt46
React Router37
TanStack Start31

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%
Astro93
TanStack Start84
SvelteKit81
Next.js72
SolidStart66
React Router63
Nuxt59

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%
SolidStart88
Astro73
SvelteKit58
Next.js48
Nuxt44
React Router37
TanStack Start19

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%
SolidStart85
Astro64
SvelteKit54
React Router50
Nuxt46
Next.js45
TanStack Start13

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%
Astro85
SolidStart75
SvelteKit74
Nuxt65
Next.js59
React Router53
TanStack Start51

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

Methodology: Core Web Vitals.