Skip to content
e18eFramework Tracker

All Frameworks

Dependency Counts

Section titled “Dependency Counts”

Methodology: Dependency Counts.

For dependency counts, we start by looking at the dependencies for the meta-framework package directly. For example, how many production, development and overall dependencies does `Nuxt` have? We then look at dependencies for the starter projects specifically. Looking at a project's dependencies is more realistic (like the `starter-*` projects) as meta-frameworks rarely just include the meta-framework package alone. It is also important to look at direct dependencies.

Meta-framework Direct Package Counts

Section titled “Meta-framework Direct Package Counts”
FrameworkDepsDevProdGraph
Astro802753View
Next.js2292236View
Nuxt681157View
React Router512328View
SolidStart29425View
SvelteKit241212View
TanStack Start808View

Metaframework Dependencies

Metaframework Dependencies chart
Metaframework Dependencies data
FrameworkDependency count
TanStack Start8
SvelteKit24
SolidStart29
React Router51
Nuxt68
Astro80
Next.js229

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

Metaframework Development Dependencies

Metaframework Development Dependencies chart
Metaframework Development Dependencies data
FrameworkDependency count
TanStack Start0
SolidStart4
Nuxt11
SvelteKit12
React Router23
Astro27
Next.js223

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

Metaframework Production Dependencies

Metaframework Production Dependencies chart
Metaframework Production Dependencies data
FrameworkDependency count
Next.js6
TanStack Start8
SvelteKit12
SolidStart25
React Router28
Astro53
Nuxt57

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

Starter Projects

Section titled “Starter Projects”
FrameworkDeps Dev / ProdAll DepsDup. Depsnode_modulesDep Install SizeGraph
Astro2 / 138711207.94MB186.65MBView
Next.js6 / 342112560.04MB506.22MBView
Nuxt2 / 369463208.80MB172.24MBView
React Router9 / 62699116.15MB111.11MBView
SolidStart1 / 62278124.34MB99.61MBView
SvelteKit8 / 0158197.02MB99.76MBView
TanStack Start11 / 1342414234.76MB198.52MBView

Starter Project Dev Dependencies

Starter Project Dev Dependencies chart
Starter Project Dev Dependencies data
FrameworkDependency count
SolidStart1
Astro2
Nuxt2
Next.js6
SvelteKit8
React Router9
TanStack Start11

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

Starter Project Production Dependencies

Starter Project Production Dependencies chart
Starter Project Production Dependencies data
FrameworkDependency count
SvelteKit0
Astro1
Next.js3
Nuxt3
React Router6
SolidStart6
TanStack Start13

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

Starter Project Duplicate Dependencies

Starter Project Duplicate Dependencies chart
Starter Project Duplicate Dependencies data
FrameworkDependency count
SvelteKit1
SolidStart8
React Router9
Astro11
Next.js12
TanStack Start14
Nuxt63

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

Node Modules Size

Section titled “Node Modules Size”

Methodology: Node Modules Size.

Node modules size

Node modules size chart
Node modules size data
FrameworkMegabytes
SvelteKit97.02 MB
React Router116.15 MB
SolidStart124.34 MB
Astro207.94 MB
Nuxt208.80 MB
TanStack Start234.76 MB
Next.js560.04 MB

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

Build and Install Times

Section titled “Build and Install Times”

Methodology: Build and Install Times.

FrameworkAvg InstallMin InstallMax InstallAvg Cold BuildAvg Warm Build
Astro3.40s1.87s4.25s0.82s0.89s
Next.js6.06s3.30s6.84s5.39s5.57s
Nuxt4.72s2.98s5.51s3.88s3.62s
React Router1.27s1.14s1.52s1.74s1.64s
SolidStart1.75s1.43s2.12s2.81s2.72s
SvelteKit1.63s1.30s1.87s1.89s1.65s
TanStack Start4.62s1.99s5.50s5.37s5.20s

Avg install time

Avg install time chart
Avg install time data
FrameworkSeconds
React Router1.27s
SvelteKit1.63s
SolidStart1.75s
Astro3.40s
TanStack Start4.62s
Nuxt4.72s
Next.js6.06s

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

Cold build time

Cold build time chart
Cold build time data
FrameworkSeconds
Astro0.82s
React Router1.74s
SvelteKit1.89s
SolidStart2.81s
Nuxt3.88s
TanStack Start5.37s
Next.js5.39s

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

Warm build time

Warm build time chart
Warm build time data
FrameworkSeconds
Astro0.89s
React Router1.64s
SvelteKit1.65s
SolidStart2.72s
Nuxt3.62s
TanStack Start5.20s
Next.js5.57s

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

Dev Server Startup

Section titled “Dev Server Startup”

Methodology: Dev Server Startup.

FrameworkAvg StartMin StartMax Start
Astro1.39s1.28s1.52s
Next.js2.47s2.31s2.54s
Nuxt2.40s2.36s2.47s
React Router0.80s0.77s0.82s
SolidStart2.98s2.90s3.08s
SvelteKit1.23s1.19s1.33s
TanStack Start3.05s2.81s3.28s

Avg dev server startup time

Avg dev server startup time chart
Avg dev server startup time data
FrameworkSeconds
React Router0.80s
SvelteKit1.23s
Astro1.39s
Nuxt2.40s
Next.js2.47s
SolidStart2.98s
TanStack Start3.05s

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

Core-JS Polyfills

Section titled “Core-JS Polyfills”

Methodology: Core-JS Polyfills.

Framework~SizeUnnecessary Modules
Astro——
Next.js110.0 KB302
Nuxt——
React Router——
SolidStart——
SvelteKit——
TanStack Start——

Browser Baseline

Section titled “Browser Baseline”

Methodology: Browser Baseline.

FrameworkBaselineFeatureYearFeatures
Astro———0
Next.jsHigh—202246
NuxtHigh—202339
React RouterHigh—202240
SolidStartHigh—202030
SvelteKitHigh—202042
TanStack StartHigh—202245

Minimum Node Version

Section titled “Minimum Node Version”

Methodology: Minimum Node Version.

FrameworkMin NodeSet by
Astrov22.12.0—
Next.jsv20.9.0next
Nuxtv20.19.0—
React Routerv20.19.0vite
SolidStartv24.0.0@solidjs/start, starter-solid-start
SvelteKitv22.20.0@napi-rs/lzma-linux-x64-gnu
TanStack Startv22.12.0@tanstack/react-start, @tanstack/react-start-client, @tanstack/react-start-server, @tanstack/start-client-core, @tanstack/start-fn-stubs, @tanstack/start-plugin-core, @tanstack/start-server-core, @tanstack/start-storage-context

Client Side Rendered Tests

Section titled “Client Side Rendered Tests”

Methodology: Client Side Rendered Tests.

FrameworkFirst PaintFCPInteraction LatencyInput DelayProcessing DurationPresentation Delay
Astro116.6ms116.68ms4.8ms2.08ms0.39ms2.33ms
Next.js341.6ms341.52ms22.02ms1.45ms8.94ms11.63ms
Nuxt162ms161.96ms12.16ms0.52ms2.33ms9.31ms
React Router185.2ms185.21ms26.28ms1.71ms2.72ms21.86ms
SolidStart125ms125.06ms17.66ms1ms3.74ms12.92ms
SvelteKit126.6ms126.62ms15.87ms0.8ms3.99ms11.08ms
TanStack Start164.4ms164.45ms33.23ms2.12ms18.54ms12.56ms

First Paint (ms)

First Paint (ms) chart
First Paint (ms) data
FrameworkMilliseconds
Astro116.60 ms
SolidStart125.00 ms
SvelteKit126.60 ms
Nuxt162.00 ms
TanStack Start164.40 ms
React Router185.20 ms
Next.js341.60 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
Astro116.68 ms
SolidStart125.06 ms
SvelteKit126.62 ms
Nuxt161.96 ms
TanStack Start164.45 ms
React Router185.21 ms
Next.js341.52 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.80 ms
12.16 ms
15.87 ms
17.66 ms
22.02 ms
26.28 ms
33.23 ms
Interaction Breakdown data
Framework or versionInteraction latencyInput delayProcessing durationPresentation delay
Astro4.80 ms2.08 ms0.39 ms2.33 ms
Nuxt12.16 ms0.52 ms2.33 ms9.31 ms
SvelteKit15.87 ms0.80 ms3.99 ms11.08 ms
SolidStart17.66 ms1.00 ms3.74 ms12.92 ms
Next.js22.02 ms1.45 ms8.94 ms11.63 ms
React Router26.28 ms1.71 ms2.72 ms21.86 ms
TanStack Start33.23 ms2.12 ms18.54 ms12.56 ms

Server Side Rendered Tests

Section titled “Server Side Rendered Tests”

Methodology: Server Side Rendered Tests.

FrameworkFirst PaintFCPInteraction LatencyInput DelayProcessing DurationPresentation Delay
Astro77.6ms77.71ms1.19ms0.76ms0.43ms0ms
Next.js156.2ms155.98ms17.62ms1.26ms7.37ms8.99ms
Nuxt120.4ms120.42ms11.05ms0.48ms1.41ms9.16ms
React Router125.6ms125.44ms17.37ms1.61ms2.69ms13.08ms
SolidStart94ms93.84ms14.71ms0.85ms2.44ms11.42ms
SvelteKit101ms100.97ms16.71ms1.17ms3.92ms11.62ms
TanStack Start130.2ms130.22ms28.58ms1.83ms14.6ms12.16ms

First Paint (ms)

First Paint (ms) chart
First Paint (ms) data
FrameworkMilliseconds
Astro77.60 ms
SolidStart94.00 ms
SvelteKit101.00 ms
Nuxt120.40 ms
React Router125.60 ms
TanStack Start130.20 ms
Next.js156.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
Astro77.71 ms
SolidStart93.84 ms
SvelteKit100.97 ms
Nuxt120.42 ms
React Router125.44 ms
TanStack Start130.22 ms
Next.js155.98 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.19 ms
11.05 ms
14.71 ms
16.71 ms
17.37 ms
17.62 ms
28.58 ms
Interaction Breakdown data
Framework or versionInteraction latencyInput delayProcessing durationPresentation delay
Astro1.19 ms0.76 ms0.43 ms0.00 ms
Nuxt11.05 ms0.48 ms1.41 ms9.16 ms
SolidStart14.71 ms0.85 ms2.44 ms11.42 ms
SvelteKit16.71 ms1.17 ms3.92 ms11.62 ms
React Router17.37 ms1.61 ms2.69 ms13.08 ms
Next.js17.62 ms1.26 ms7.37 ms8.99 ms
TanStack Start28.58 ms1.83 ms14.60 ms12.16 ms

Server Side Throughput Tests

Section titled “Server Side Throughput Tests”

Methodology: Server Side Throughput Tests.

FrameworkOps/secMedian LatencyBody SizeDuplication
Baseline HTML8371.205ms96.83kb1x
Astro6621.449ms96.89kb1x
Next.js2204.606ms199.57kb2x
Nuxt3622.625ms201.27kb2x
React Router3273.007ms212.07kb2x
SolidStart4242.263ms224.17kb2x
SvelteKit4482.158ms183.53kb2x
TanStack Start3153.13ms193.62kb2x

Ops/sec

Ops/sec chart
Ops/sec data
FrameworkOperations per second
Baseline HTML837
Astro662
SvelteKit448
SolidStart424
Nuxt362
React Router327
TanStack Start315
Next.js220

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.45 ms
SvelteKit2.16 ms
SolidStart2.26 ms
Nuxt2.63 ms
React Router3.01 ms
TanStack Start3.13 ms
Next.js4.61 ms

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

SSR Load Test

Section titled “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.

FrameworkPeak req/sPeak ConnectionsP99 @ 25P99 @ 50P99 @ 100Total Req.
Baseline HTML1,692.45020ms39ms106ms48,521
Astro1,123.82533ms74ms425ms33,383
Next.js4551708ms4651ms4662ms1,290
Nuxt490.81077ms404ms2842ms15,996
React Router344.81094ms647ms3354ms11,381
SolidStart5391094ms437ms2277ms17,274
SvelteKit498.4579ms481ms2401ms15,532
TanStack Start280.210176ms1779ms2806ms9,166

P99 Latency

Section titled “P99 Latency”

P99 Latency at 25 Connections

P99 Latency at 25 Connections chart
P99 Latency at 25 Connections data
FrameworkMilliseconds
Baseline HTML20.00 ms
Astro33.00 ms
Nuxt77.00 ms
SvelteKit79.00 ms
React Router94.00 ms
SolidStart94.00 ms
TanStack Start176.00 ms
Next.js1708.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
Astro74.00 ms
Nuxt404.00 ms
SolidStart437.00 ms
SvelteKit481.00 ms
React Router647.00 ms
TanStack Start1779.00 ms
Next.js4651.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
Astro425.00 ms
SolidStart2277.00 ms
SvelteKit2401.00 ms
TanStack Start2806.00 ms
Nuxt2842.00 ms
React Router3354.00 ms
Next.js4662.00 ms

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

P90 Latency

Section titled “P90 Latency”

P90 Latency at 25 Connections

P90 Latency at 25 Connections chart
P90 Latency at 25 Connections data
FrameworkMilliseconds
Baseline HTML18.00 ms
Astro24.00 ms
Nuxt54.00 ms
SvelteKit60.00 ms
SolidStart68.00 ms
React Router74.00 ms
TanStack Start132.00 ms
Next.js659.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 HTML34.00 ms
Astro53.00 ms
Nuxt110.00 ms
React Router146.00 ms
SvelteKit146.00 ms
SolidStart156.00 ms
TanStack Start236.00 ms
Next.js2306.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
Astro98.00 ms
SolidStart168.00 ms
Nuxt188.00 ms
SvelteKit232.00 ms
TanStack Start260.00 ms
React Router276.00 ms
Next.js2376.00 ms

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

Section titled “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.

FrameworkPeak req/sPeak ConnectionsP99 @ 25P99 @ 50P99 @ 100Total Req.
Next.js4012000ms4740ms4772ms1,154
Nuxt73.851921ms4145ms4251ms2,388
React Router180.650309ms310ms3862ms5,944
TanStack Start45.8103819ms4305ms4534ms1,406

P99 Latency

Section titled “P99 Latency”

P99 Latency at 25 Connections

P99 Latency at 25 Connections chart
P99 Latency at 25 Connections data
FrameworkMilliseconds
React Router309.00 ms
Nuxt1921.00 ms
Next.js2000.00 ms
TanStack Start3819.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 Router310.00 ms
Nuxt4145.00 ms
TanStack Start4305.00 ms
Next.js4740.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 Router3862.00 ms
Nuxt4251.00 ms
TanStack Start4534.00 ms
Next.js4772.00 ms

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

P90 Latency

Section titled “P90 Latency”

P90 Latency at 25 Connections

P90 Latency at 25 Connections chart
P90 Latency at 25 Connections data
FrameworkMilliseconds
React Router151.00 ms
Nuxt336.00 ms
Next.js714.00 ms
TanStack Start718.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 Router276.00 ms
Nuxt494.00 ms
TanStack Start718.00 ms
Next.js2409.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 Router405.00 ms
Nuxt582.00 ms
TanStack Start1344.00 ms
Next.js2702.00 ms

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

Core Web Vitals

Section titled “Core Web Vitals”

CWV Desktop

Section titled “CWV Desktop”
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.

CWV Mobile

Section titled “CWV Mobile”
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.