Skip to content

All Frameworks

Methodology: Dependency Counts.

These views separate a framework's core package, the direct packages maintained by its ecosystem, and the complete default starter configuration.

First, we look at the direct dependency counts of the meta-framework package itself.

FrameworkDepsDevProdGraph
Astro792653View
Next.js2292236View
Nuxt791366View
React Router512328View
SolidStart29425View
SvelteKit251312View
TanStack Start808View

Metaframework Dependencies

Metaframework Dependencies chart
Metaframework Dependencies data
FrameworkDependency count
TanStack Start8
SvelteKit25
SolidStart29
React Router51
Astro79
Nuxt79
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
Nuxt13
SvelteKit13
React Router23
Astro26
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
Nuxt66

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

Next, we look at the direct framework-maintained packages that each starter declares. This excludes the starter’s third-party setup packages.

FrameworkDeps Dev / ProdAll DepsDup. DepsGraph
Astro1 / 136013View
Next.js1 / 138211View
Nuxt0 / 167879View
React Router1 / 32439View
SolidStart0 / 42126View
SvelteKit5 / 01622View
TanStack Start1 / 62485View

Meta-framework Direct Package Dependencies

Meta-framework Direct Package Dependencies chart
Meta-framework Direct Package Dependencies data
FrameworkDependency count
SvelteKit162
SolidStart212
React Router243
TanStack Start248
Astro360
Next.js382
Nuxt678

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

Meta-framework Direct Package Development Dependencies

Meta-framework Direct Package Development Dependencies chart
Meta-framework Direct Package Development Dependencies data
FrameworkDependency count
Nuxt0
SolidStart0
Astro1
Next.js1
React Router1
TanStack Start1
SvelteKit5

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

Meta-framework Direct Package Production Dependencies

Meta-framework Direct Package Production Dependencies chart
Meta-framework Direct Package Production Dependencies data
FrameworkDependency count
SvelteKit0
Astro1
Next.js1
Nuxt1
React Router3
SolidStart4
TanStack Start6

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

Meta-framework Direct Package Duplicate Dependencies

Meta-framework Direct Package Duplicate Dependencies chart
Meta-framework Direct Package Duplicate Dependencies data
FrameworkDependency count
SvelteKit2
TanStack Start5
SolidStart6
React Router9
Next.js11
Astro13
Nuxt79

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

Finally, we look at the complete dependency footprint of the default starter project, including third-party packages selected by its CLI or documented setup.

FrameworkDeps Dev / ProdAll DepsDup. Depsnode_modulesDep Install SizeGraph
Astro2 / 136013211.58MB190.46MBView
Next.js6 / 342112560.04MB506.22MBView
Nuxt2 / 367879247.30MB208.61MBView
React Router9 / 62699116.27MB111.24MBView
SolidStart1 / 62468130.03MB105.36MBView
SvelteKit8 / 0162298.34MB100.71MBView
TanStack Start11 / 1341512213.75MB178.09MBView

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
SvelteKit2
SolidStart8
React Router9
Next.js12
TanStack Start12
Astro13
Nuxt79

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

Methodology: Node Modules Size.

Node modules size

Node modules size chart
Node modules size data
FrameworkMegabytes
SvelteKit98.34 MB
React Router116.27 MB
SolidStart130.03 MB
Astro211.58 MB
TanStack Start213.75 MB
Nuxt247.30 MB
Next.js560.04 MB

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

Methodology: Build and Install Times.

FrameworkAvg InstallMin InstallMax InstallAvg Cold BuildAvg Warm Build
Astro3.58s1.69s4.53s1.03s0.99s
Next.js6.17s3.31s6.99s5.23s5.03s
Nuxt5.50s3.43s6.67s4.06s3.80s
React Router1.23s1.09s1.45s1.68s1.70s
SolidStart1.98s1.42s2.42s2.90s2.68s
SvelteKit1.60s1.42s1.73s2.59s2.49s
TanStack Start4.41s1.81s5.29s5.27s5.09s

Avg install time

Avg install time chart
Avg install time data
FrameworkSeconds
React Router1.23s
SvelteKit1.60s
SolidStart1.98s
Astro3.58s
TanStack Start4.41s
Nuxt5.50s
Next.js6.17s

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
Astro1.03s
React Router1.68s
SvelteKit2.59s
SolidStart2.90s
Nuxt4.06s
Next.js5.23s
TanStack Start5.27s

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.99s
React Router1.70s
SvelteKit2.49s
SolidStart2.68s
Nuxt3.80s
Next.js5.03s
TanStack Start5.09s

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

Methodology: Dev Server Startup.

FrameworkAvg StartMin StartMax Start
Astro1.43s1.38s1.47s
Next.js2.38s2.26s2.52s
Nuxt2.71s2.56s2.93s
React Router0.84s0.83s0.86s
SolidStart2.54s2.46s2.60s
SvelteKit1.21s1.18s1.27s
TanStack Start2.98s2.90s3.06s

Avg dev server startup time

Avg dev server startup time chart
Avg dev server startup time data
FrameworkSeconds
React Router0.84s
SvelteKit1.21s
Astro1.43s
Next.js2.38s
SolidStart2.54s
Nuxt2.71s
TanStack Start2.98s

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

Methodology: Core-JS Polyfills.

FrameworkCore-JS detectedMatching JS filesModules not needed by target browsers
AstroNo——
Next.jsYes110.0 KB302
NuxtNo——
React RouterNo——
SolidStartNo——
SvelteKitNo——
TanStack StartNo——

Methodology: Browser Baseline.

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

Methodology: Minimum Node Version.

FrameworkMin NodeSet by
Astrov22.19.0undici
Next.jsv20.9.0next
Nuxtv22.22.3@nuxt/nitro-server, @nuxt/vite-builder, @nuxt/vite-server, cssnano, cssnano-preset-default, cssnano-utils, nuxt, postcss-calc, postcss-colormin, postcss-convert-values, postcss-discard-comments, postcss-discard-duplicates, postcss-discard-empty, postcss-discard-overridden, postcss-merge-longhand, postcss-merge-rules, postcss-minify-font-values, postcss-minify-gradients, postcss-minify-params, postcss-minify-selectors, postcss-normalize-charset, postcss-normalize-display-values, postcss-normalize-positions, postcss-normalize-repeat-style, postcss-normalize-string, postcss-normalize-timing-functions, postcss-normalize-unicode, postcss-normalize-url, postcss-normalize-whitespace, postcss-ordered-values, postcss-reduce-initial, postcss-reduce-transforms, postcss-svgo, postcss-unique-selectors, stylehacks
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

Methodology: Client Side Rendered Tests.

FrameworkFirst PaintFCPInteraction LatencyInput DelayProcessing DurationPresentation Delay
Astro105.4ms105.29ms1.79ms1.48ms0.32ms0ms
Next.js338.8ms339.13ms19.63ms1.43ms6.11ms12.09ms
Nuxt180.8ms180.81ms8.28ms0.87ms1.27ms6.14ms
React Router177.8ms177.7ms21.13ms1.68ms3.61ms15.84ms
SolidStart100.8ms100.8ms14.56ms0.9ms2.97ms10.69ms
SvelteKit112ms111.86ms15.62ms0.95ms2.85ms11.83ms
TanStack Start141.8ms141.59ms31.69ms2.06ms15.27ms14.36ms

First Paint (ms)

First Paint (ms) chart
First Paint (ms) data
FrameworkMilliseconds
SolidStart100.80 ms
Astro105.40 ms
SvelteKit112.00 ms
TanStack Start141.80 ms
React Router177.80 ms
Nuxt180.80 ms
Next.js338.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
SolidStart100.80 ms
Astro105.29 ms
SvelteKit111.86 ms
TanStack Start141.59 ms
React Router177.70 ms
Nuxt180.81 ms
Next.js339.13 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.79 ms
8.28 ms
14.56 ms
15.62 ms
19.63 ms
21.13 ms
31.69 ms
Interaction Breakdown data
Framework or versionInteraction latencyInput delayProcessing durationPresentation delay
Astro1.79 ms1.48 ms0.32 ms0.00 ms
Nuxt8.28 ms0.87 ms1.27 ms6.14 ms
SolidStart14.56 ms0.90 ms2.97 ms10.69 ms
SvelteKit15.62 ms0.95 ms2.85 ms11.83 ms
Next.js19.63 ms1.43 ms6.11 ms12.09 ms
React Router21.13 ms1.68 ms3.61 ms15.84 ms
TanStack Start31.69 ms2.06 ms15.27 ms14.36 ms

Methodology: Server Side Rendered Tests.

FrameworkFirst PaintFCPInteraction LatencyInput DelayProcessing DurationPresentation Delay
Astro80.4ms80.43ms0.94ms0.64ms0.3ms0ms
Next.js163.2ms163.2ms17.59ms1.22ms7.5ms8.86ms
Nuxt113.2ms113.23ms13.52ms1.49ms1.8ms10.23ms
React Router121.8ms121.76ms24.7ms2.67ms3.55ms18.47ms
SolidStart87.8ms87.76ms15.05ms0.94ms2.66ms11.45ms
SvelteKit89ms88.87ms17.67ms0.58ms2.99ms14.11ms
TanStack Start111.2ms111.32ms32.29ms2.39ms16.09ms13.81ms

First Paint (ms)

First Paint (ms) chart
First Paint (ms) data
FrameworkMilliseconds
Astro80.40 ms
SolidStart87.80 ms
SvelteKit89.00 ms
TanStack Start111.20 ms
Nuxt113.20 ms
React Router121.80 ms
Next.js163.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
Astro80.43 ms
SolidStart87.76 ms
SvelteKit88.87 ms
TanStack Start111.32 ms
Nuxt113.23 ms
React Router121.76 ms
Next.js163.20 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.
0.94 ms
13.52 ms
15.05 ms
17.59 ms
17.67 ms
24.70 ms
32.29 ms
Interaction Breakdown data
Framework or versionInteraction latencyInput delayProcessing durationPresentation delay
Astro0.94 ms0.64 ms0.30 ms0.00 ms
Nuxt13.52 ms1.49 ms1.80 ms10.23 ms
SolidStart15.05 ms0.94 ms2.66 ms11.45 ms
Next.js17.59 ms1.22 ms7.50 ms8.86 ms
SvelteKit17.67 ms0.58 ms2.99 ms14.11 ms
React Router24.70 ms2.67 ms3.55 ms18.47 ms
TanStack Start32.29 ms2.39 ms16.09 ms13.81 ms

Methodology: Server Side Throughput Tests.

FrameworkOps/secMedian LatencyBody SizeDuplication
Baseline HTML8371.213ms96.83kb1x
Astro7291.327ms96.89kb1x
Next.js2284.576ms199.57kb2x
Nuxt3752.586ms201.73kb2x
React Router3193.052ms216.9kb2x
SolidStart4292.245ms224.17kb2x
SvelteKit4522.149ms183.53kb2x
TanStack Start3502.804ms191.63kb2x

Ops/sec

Ops/sec chart
Ops/sec data
FrameworkOperations per second
Baseline HTML837
Astro729
SvelteKit452
SolidStart429
Nuxt375
TanStack Start350
React Router319
Next.js228

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 Start191.63 KB
Next.js199.57 KB
Nuxt201.73 KB
React Router216.90 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.33 ms
SvelteKit2.15 ms
SolidStart2.25 ms
Nuxt2.59 ms
TanStack Start2.80 ms
React Router3.05 ms
Next.js4.58 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,675.210022ms53ms110ms48,072
Astro1,526.85027ms47ms84ms44,848
Next.js43.611903ms4782ms4703ms1,218
Nuxt5151071ms350ms2855ms16,970
React Router333.825105ms183ms3475ms11,112
SolidStart511.85101ms523ms2184ms16,516
SvelteKit493.41081ms438ms2634ms15,890
TanStack Start381.25114ms893ms2651ms12,442

P99 Latency at 25 Connections

P99 Latency at 25 Connections chart
P99 Latency at 25 Connections data
FrameworkMilliseconds
Baseline HTML22.00 ms
Astro27.00 ms
Nuxt71.00 ms
SvelteKit81.00 ms
SolidStart101.00 ms
React Router105.00 ms
TanStack Start114.00 ms
Next.js1903.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
Astro47.00 ms
Baseline HTML53.00 ms
React Router183.00 ms
Nuxt350.00 ms
SvelteKit438.00 ms
SolidStart523.00 ms
TanStack Start893.00 ms
Next.js4782.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
Astro84.00 ms
Baseline HTML110.00 ms
SolidStart2184.00 ms
SvelteKit2634.00 ms
TanStack Start2651.00 ms
Nuxt2855.00 ms
React Router3475.00 ms
Next.js4703.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
Astro18.00 ms
Baseline HTML19.00 ms
Nuxt50.00 ms
SvelteKit60.00 ms
React Router75.00 ms
SolidStart75.00 ms
TanStack Start88.00 ms
Next.js677.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
Astro35.00 ms
Baseline HTML37.00 ms
Nuxt103.00 ms
SvelteKit141.00 ms
React Router152.00 ms
SolidStart162.00 ms
TanStack Start191.00 ms
Next.js2331.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
Astro69.00 ms
Baseline HTML80.00 ms
SolidStart150.00 ms
Nuxt183.00 ms
SvelteKit223.00 ms
TanStack Start251.00 ms
React Router289.00 ms
Next.js2675.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.js40.811897ms4687ms4637ms1,150
Nuxt179.65466ms2646ms3674ms5,912
React Router169.85212ms1758ms3823ms5,724
TanStack Start165.610569ms3365ms3316ms5,487

P99 Latency at 25 Connections

P99 Latency at 25 Connections chart
P99 Latency at 25 Connections data
FrameworkMilliseconds
React Router212.00 ms
Nuxt466.00 ms
TanStack Start569.00 ms
Next.js1897.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 Router1758.00 ms
Nuxt2646.00 ms
TanStack Start3365.00 ms
Next.js4687.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
TanStack Start3316.00 ms
Nuxt3674.00 ms
React Router3823.00 ms
Next.js4637.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
Nuxt147.00 ms
React Router172.00 ms
TanStack Start195.00 ms
Next.js681.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
Nuxt292.00 ms
React Router295.00 ms
TanStack Start365.00 ms
Next.js2314.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
Nuxt316.00 ms
React Router406.00 ms
TanStack Start406.00 ms
Next.js2702.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.