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
Astro112ms112.04ms5.25ms1.87ms0.49ms2.89ms
Next.js336.2ms336.12ms16.78ms1.23ms7.47ms8.08ms
Nuxt163.6ms163.61ms11.39ms0.49ms1.36ms9.54ms
React Router160.2ms160.16ms21.34ms1.51ms2.78ms17.06ms
SolidStart111.2ms111.39ms14.67ms1.36ms2.89ms10.42ms
SvelteKit123.4ms123.21ms13.33ms1.07ms2.47ms9.79ms
TanStack Start156ms156.22ms28.58ms1.67ms14.82ms12.1ms

First Paint (ms)

First Paint (ms) chart
First Paint (ms) data
FrameworkMilliseconds
SolidStart111.20 ms
Astro112.00 ms
SvelteKit123.40 ms
TanStack Start156.00 ms
React Router160.20 ms
Nuxt163.60 ms
Next.js336.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
SolidStart111.39 ms
Astro112.04 ms
SvelteKit123.21 ms
TanStack Start156.22 ms
React Router160.16 ms
Nuxt163.61 ms
Next.js336.12 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.
5.25 ms
11.39 ms
13.33 ms
14.67 ms
16.78 ms
21.34 ms
28.58 ms
Interaction Breakdown data
Framework or versionInteraction latencyInput delayProcessing durationPresentation delay
Astro5.25 ms1.87 ms0.49 ms2.89 ms
Nuxt11.39 ms0.49 ms1.36 ms9.54 ms
SvelteKit13.33 ms1.07 ms2.47 ms9.79 ms
SolidStart14.67 ms1.36 ms2.89 ms10.42 ms
Next.js16.78 ms1.23 ms7.47 ms8.08 ms
React Router21.34 ms1.51 ms2.78 ms17.06 ms
TanStack Start28.58 ms1.67 ms14.82 ms12.10 ms

Methodology: Server Side Rendered Tests.

FrameworkFirst PaintFCPInteraction LatencyInput DelayProcessing DurationPresentation Delay
Astro129ms129.03ms4.77ms3.76ms1.02ms0ms
Next.js168.8ms168.76ms19.16ms1.49ms6.61ms11.06ms
Nuxt104.6ms104.58ms13.66ms0.67ms2.71ms10.28ms
React Router114ms113.92ms17.35ms1.67ms3.33ms12.34ms
SolidStart92.4ms92.44ms13.29ms0.85ms2.65ms9.8ms
SvelteKit174ms173.96ms18.02ms2.25ms4.73ms11.04ms
TanStack Start122.6ms122.56ms25.24ms1.48ms13.92ms9.85ms

First Paint (ms)

First Paint (ms) chart
First Paint (ms) data
FrameworkMilliseconds
SolidStart92.40 ms
Nuxt104.60 ms
React Router114.00 ms
TanStack Start122.60 ms
Astro129.00 ms
Next.js168.80 ms
SvelteKit174.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
FrameworkMilliseconds
SolidStart92.44 ms
Nuxt104.58 ms
React Router113.92 ms
TanStack Start122.56 ms
Astro129.03 ms
Next.js168.76 ms
SvelteKit173.96 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.
4.77 ms
13.29 ms
13.66 ms
17.35 ms
18.02 ms
19.16 ms
25.24 ms
Interaction Breakdown data
Framework or versionInteraction latencyInput delayProcessing durationPresentation delay
Astro4.77 ms3.76 ms1.02 ms0.00 ms
SolidStart13.29 ms0.85 ms2.65 ms9.80 ms
Nuxt13.66 ms0.67 ms2.71 ms10.28 ms
React Router17.35 ms1.67 ms3.33 ms12.34 ms
SvelteKit18.02 ms2.25 ms4.73 ms11.04 ms
Next.js19.16 ms1.49 ms6.61 ms11.06 ms
TanStack Start25.24 ms1.48 ms13.92 ms9.85 ms

Methodology: Server Side Throughput Tests.

FrameworkOps/secMedian LatencyBody SizeDuplication
Baseline HTML8331.215ms96.83kb1x
Astro6841.41ms96.89kb1x
Next.js2334.483ms199.57kb2x
Nuxt3772.572ms201.27kb2x
React Router3452.862ms212.07kb2x
SolidStart4212.278ms224.17kb2x
SvelteKit4382.207ms183.53kb2x
TanStack Start3283.029ms193.62kb2x

Ops/sec

Ops/sec chart
Ops/sec data
FrameworkOperations per second
Baseline HTML833
Astro684
SvelteKit438
SolidStart421
Nuxt377
React Router345
TanStack Start328
Next.js233

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.22 ms
Astro1.41 ms
SvelteKit2.21 ms
SolidStart2.28 ms
Nuxt2.57 ms
React Router2.86 ms
TanStack Start3.03 ms
Next.js4.48 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,412.220022ms50ms122ms42,163
Astro1,160.4120033ms67ms370ms34,971
Next.js46.251710ms4725ms4649ms1,329
Nuxt437.8583ms557ms2985ms14,229
React Router345.610103ms540ms3449ms11,206
SolidStart538.61088ms417ms2048ms17,485
SvelteKit477.62586ms328ms2534ms15,447
TanStack Start286.6110176ms1864ms2864ms9,358

P99 Latency at 25 Connections

P99 Latency at 25 Connections chart
P99 Latency at 25 Connections data
FrameworkMilliseconds
Baseline HTML22.00 ms
Astro33.00 ms
Nuxt83.00 ms
SvelteKit86.00 ms
SolidStart88.00 ms
React Router103.00 ms
TanStack Start176.00 ms
Next.js1710.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 HTML50.00 ms
Astro67.00 ms
SvelteKit328.00 ms
SolidStart417.00 ms
React Router540.00 ms
Nuxt557.00 ms
TanStack Start1864.00 ms
Next.js4725.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 HTML122.00 ms
Astro370.00 ms
SolidStart2048.00 ms
SvelteKit2534.00 ms
TanStack Start2864.00 ms
Nuxt2985.00 ms
React Router3449.00 ms
Next.js4649.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 HTML21.00 ms
Astro24.00 ms
Nuxt60.00 ms
SvelteKit62.00 ms
SolidStart68.00 ms
React Router73.00 ms
TanStack Start127.00 ms
Next.js609.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 HTML40.00 ms
Astro46.00 ms
Nuxt124.00 ms
SvelteKit140.00 ms
SolidStart146.00 ms
React Router157.00 ms
TanStack Start270.00 ms
Next.js2241.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
Astro88.00 ms
Baseline HTML92.00 ms
SolidStart162.00 ms
Nuxt204.00 ms
SvelteKit223.00 ms
TanStack Start276.00 ms
React Router284.00 ms
Next.js2429.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 HTML19.00 ms
Astro23.00 ms
SvelteKit55.00 ms
Nuxt58.00 ms
SolidStart59.00 ms
React Router72.00 ms
TanStack Start110.00 ms
Next.js604.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 HTML39.00 ms
Astro44.00 ms
SolidStart90.00 ms
Nuxt117.00 ms
SvelteKit118.00 ms
React Router144.00 ms
TanStack Start161.00 ms
Next.js1045.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 HTML77.00 ms
Astro85.00 ms
SolidStart127.00 ms
SvelteKit166.00 ms
TanStack Start173.00 ms
Nuxt186.00 ms
React Router258.00 ms
Next.js1007.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.js4151998ms4646ms4676ms1,157
Nuxt7351872ms4176ms4265ms2,373
React Router168.825329ms1802ms3921ms5,598
TanStack Start45.253505ms4074ms4483ms1,408

P99 Latency at 25 Connections

P99 Latency at 25 Connections chart
P99 Latency at 25 Connections data
FrameworkMilliseconds
React Router329.00 ms
Nuxt1872.00 ms
Next.js1998.00 ms
TanStack Start3505.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 Router1802.00 ms
TanStack Start4074.00 ms
Nuxt4176.00 ms
Next.js4646.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 Router3921.00 ms
Nuxt4265.00 ms
TanStack Start4483.00 ms
Next.js4676.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 Router150.00 ms
Nuxt344.00 ms
Next.js688.00 ms
TanStack Start716.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 Router316.00 ms
Nuxt477.00 ms
TanStack Start697.00 ms
Next.js2338.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 Router396.00 ms
Nuxt626.00 ms
TanStack Start1258.00 ms
Next.js2618.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 Router146.00 ms
Nuxt341.00 ms
TanStack Start604.00 ms
Next.js679.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 Router289.00 ms
Nuxt449.00 ms
TanStack Start564.00 ms
Next.js1116.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 Router370.00 ms
Nuxt444.00 ms
TanStack Start535.00 ms
Next.js1083.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.