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
Astro99.6ms99.49ms1.85ms1.57ms0.28ms0ms
Next.js342.4ms342.3ms22.4ms1.37ms6.04ms15ms
Nuxt149.4ms149.46ms10.15ms0.46ms1.15ms8.55ms
React Router148.8ms148.67ms21.07ms1.48ms3.28ms16.32ms
SolidStart104ms104.04ms13.28ms0.94ms2.28ms10.05ms
SvelteKit119.4ms119.34ms12.31ms0.65ms2.47ms9.2ms
TanStack Start169ms169.15ms25.86ms1.58ms13.94ms10.34ms

First Paint (ms)

First Paint (ms) chart
First Paint (ms) data
FrameworkMilliseconds
Astro99.60 ms
SolidStart104.00 ms
SvelteKit119.40 ms
React Router148.80 ms
Nuxt149.40 ms
TanStack Start169.00 ms
Next.js342.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
FrameworkMilliseconds
Astro99.49 ms
SolidStart104.04 ms
SvelteKit119.34 ms
React Router148.67 ms
Nuxt149.46 ms
TanStack Start169.15 ms
Next.js342.30 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.85 ms
10.15 ms
12.31 ms
13.28 ms
21.07 ms
22.40 ms
25.86 ms
Interaction Breakdown data
Framework or versionInteraction latencyInput delayProcessing durationPresentation delay
Astro1.85 ms1.57 ms0.28 ms0.00 ms
Nuxt10.15 ms0.46 ms1.15 ms8.55 ms
SvelteKit12.31 ms0.65 ms2.47 ms9.20 ms
SolidStart13.28 ms0.94 ms2.28 ms10.05 ms
React Router21.07 ms1.48 ms3.28 ms16.32 ms
Next.js22.40 ms1.37 ms6.04 ms15.00 ms
TanStack Start25.86 ms1.58 ms13.94 ms10.34 ms

Methodology: Server Side Rendered Tests.

FrameworkFirst PaintFCPInteraction LatencyInput DelayProcessing DurationPresentation Delay
Astro65.6ms65.63ms1.12ms0.88ms0.24ms0ms
Mastro65.4ms65.21ms1.35ms0.52ms0.82ms0ms
Next.js134.4ms134.14ms16.61ms1.24ms8.63ms6.74ms
Nuxt104ms104.15ms9.16ms0.43ms1.19ms7.53ms
React Router113.6ms113.53ms18.18ms1.49ms2.76ms13.92ms
SolidStart97.6ms97.38ms15.84ms0.82ms1.97ms13.04ms
SvelteKit86ms86.11ms13.47ms0.65ms3.69ms9.13ms
TanStack Start114.2ms114.22ms26.66ms1.48ms12.44ms12.74ms

First Paint (ms)

First Paint (ms) chart
First Paint (ms) data
FrameworkMilliseconds
Mastro65.40 ms
Astro65.60 ms
SvelteKit86.00 ms
SolidStart97.60 ms
Nuxt104.00 ms
React Router113.60 ms
TanStack Start114.20 ms
Next.js134.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
FrameworkMilliseconds
Mastro65.21 ms
Astro65.63 ms
SvelteKit86.11 ms
SolidStart97.38 ms
Nuxt104.15 ms
React Router113.53 ms
TanStack Start114.22 ms
Next.js134.14 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.12 ms
1.35 ms
9.16 ms
13.47 ms
15.84 ms
16.61 ms
18.18 ms
26.66 ms
Interaction Breakdown data
Framework or versionInteraction latencyInput delayProcessing durationPresentation delay
Astro1.12 ms0.88 ms0.24 ms0.00 ms
Mastro1.35 ms0.52 ms0.82 ms0.00 ms
Nuxt9.16 ms0.43 ms1.19 ms7.53 ms
SvelteKit13.47 ms0.65 ms3.69 ms9.13 ms
SolidStart15.84 ms0.82 ms1.97 ms13.04 ms
Next.js16.61 ms1.24 ms8.63 ms6.74 ms
React Router18.18 ms1.49 ms2.76 ms13.92 ms
TanStack Start26.66 ms1.48 ms12.44 ms12.74 ms

Methodology: Server Side Throughput Tests.

FrameworkOps/secMedian LatencyBody SizeDuplication
Baseline HTML8471.202ms96.83kb1x
Astro6671.456ms96.89kb1x
Mastro3632.697ms327.46kb1.5x
Next.js2304.541ms199.57kb2x
Nuxt3672.646ms201.27kb2x
React Router3532.812ms211.63kb2x
SolidStart4212.278ms224.17kb2x
SvelteKit4402.188ms183.53kb2x
TanStack Start3312.999ms193.62kb2x

Ops/sec

Ops/sec chart
Ops/sec data
FrameworkOperations per second
Baseline HTML847
Astro667
SvelteKit440
SolidStart421
Nuxt367
Mastro363
React Router353
TanStack Start331
Next.js230

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 Router211.63 KB
SolidStart224.17 KB
Mastro327.46 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.20 ms
Astro1.46 ms
SvelteKit2.19 ms
SolidStart2.28 ms
Nuxt2.65 ms
Mastro2.70 ms
React Router2.81 ms
TanStack Start3.00 ms
Next.js4.54 ms

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

Methodology: Server Side Load Test.

FrameworkPeak req/sPeak ConnectionsP99 @ 25P99 @ 50P99 @ 100Total Req.
Baseline HTML1,656.410018ms44ms103ms49,313
Astro1,197.210031ms65ms279ms35,992
Mastro576.82556ms110ms1342ms18,384
Next.js39.2151998ms4648ms4660ms1,114
Nuxt72101941ms4048ms4133ms2,335
React Router174.610278ms1749ms3957ms5,784
SolidStart525.62597ms394ms2045ms17,078
SvelteKit498.62579ms413ms2168ms16,227
TanStack Start41.653867ms4277ms4752ms1,284

P99 Latency at 25 Connections

P99 Latency at 25 Connections chart
P99 Latency at 25 Connections data
FrameworkMilliseconds
Baseline HTML18.00 ms
Astro31.00 ms
Mastro56.00 ms
SvelteKit79.00 ms
SolidStart97.00 ms
React Router278.00 ms
Nuxt1941.00 ms
Next.js1998.00 ms
TanStack Start3867.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 HTML44.00 ms
Astro65.00 ms
Mastro110.00 ms
SolidStart394.00 ms
SvelteKit413.00 ms
React Router1749.00 ms
Nuxt4048.00 ms
TanStack Start4277.00 ms
Next.js4648.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 HTML103.00 ms
Astro279.00 ms
Mastro1342.00 ms
SolidStart2045.00 ms
SvelteKit2168.00 ms
React Router3957.00 ms
Nuxt4133.00 ms
Next.js4660.00 ms
TanStack Start4752.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 HTML17.00 ms
Astro23.00 ms
Mastro44.00 ms
SvelteKit61.00 ms
SolidStart69.00 ms
React Router168.00 ms
Nuxt362.00 ms
Next.js702.00 ms
TanStack Start800.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 HTML31.00 ms
Astro43.00 ms
Mastro89.00 ms
SvelteKit120.00 ms
SolidStart146.00 ms
React Router297.00 ms
Nuxt476.00 ms
TanStack Start779.00 ms
Next.js2461.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 HTML77.00 ms
Astro82.00 ms
SolidStart158.00 ms
Mastro178.00 ms
SvelteKit241.00 ms
React Router387.00 ms
Nuxt484.00 ms
TanStack Start1584.00 ms
Next.js2740.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 HTML16.00 ms
Astro21.00 ms
Mastro43.00 ms
SvelteKit53.00 ms
SolidStart59.00 ms
React Router143.00 ms
Nuxt342.00 ms
TanStack Start537.00 ms
Next.js693.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 HTML30.00 ms
Astro42.00 ms
Mastro85.00 ms
SolidStart89.00 ms
SvelteKit108.00 ms
React Router277.00 ms
Nuxt440.00 ms
TanStack Start591.00 ms
Next.js1119.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 HTML62.00 ms
Astro82.00 ms
SolidStart126.00 ms
Mastro172.00 ms
SvelteKit174.00 ms
React Router363.00 ms
Nuxt446.00 ms
TanStack Start565.00 ms
Next.js1091.00 ms

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

FrameworkLCP%CLS%FCP%TTFB%INP%
Astro9187918297
SolidStart91669183100
SvelteKit7977787194
Next.js7269766794
React Router6162667090
Nuxt6557675995

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%
Astro91
SolidStart91
SvelteKit79
Next.js72
Nuxt65
React Router61

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%
Astro87
SvelteKit77
Next.js69
SolidStart66
React Router62
Nuxt57

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%
Astro91
SolidStart91
SvelteKit78
Next.js76
Nuxt67
React Router66

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%
SolidStart83
Astro82
SvelteKit71
React Router70
Next.js67
Nuxt59

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
Astro97
Nuxt95
SvelteKit94
Next.js94
React Router90

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

FrameworkLCP%CLS%FCP%TTFB%INP%
Astro7792716086
SolidStart90639081100
SvelteKit6781605875
Next.js5169504758
Nuxt4558434565
React Router4164415356

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%
SolidStart90
Astro77
SvelteKit67
Next.js51
Nuxt45
React Router41

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%
Astro92
SvelteKit81
Next.js69
React Router64
SolidStart63
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%
SolidStart90
Astro71
SvelteKit60
Next.js50
Nuxt43
React Router41

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%
SolidStart81
Astro60
SvelteKit58
React Router53
Next.js47
Nuxt45

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
Astro86
SvelteKit75
Nuxt65
Next.js58
React Router56

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

Methodology: Core Web Vitals.