Skip to content

Run Time Stats

Run Time benchmarks use purpose-built apps; see the Run Time methodology for setup details.

These CSR browser performance tests use Lighthouse to measure paint timings and a controlled navigation interaction. The interaction is also scored as work to commit from the same trace.

Methodology: Client Side Rendered Tests (Lighthouse).

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.

Client First Paint (Lighthouse)
Client First Paint (Lighthouse) data
FrameworkMilliseconds
Astro86.00 ms
Pracht87.00 ms
SolidStart90.00 ms
SvelteKit98.00 ms
Solid 2.0109.00 ms
TanStack Start117.00 ms
Void126.00 ms
Nuxt142.00 ms
React Router162.00 ms
Next.js338.00 ms
Client FCP (Lighthouse)
Client FCP (Lighthouse) data
FrameworkMilliseconds
Astro86.46 ms
Pracht87.05 ms
SolidStart90.39 ms
SvelteKit98.28 ms
Solid 2.0109.23 ms
TanStack Start116.94 ms
Void125.67 ms
Nuxt141.62 ms
React Router162.47 ms
Next.js338.10 ms
Interaction Breakdown (Lighthouse)

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.
Interaction Breakdown (Lighthouse) data
FrameworkInput delayProcessing durationPresentation delay
Astro1.86 ms0.30 ms0.00 ms
Nuxt0.75 ms1.17 ms10.81 ms
Next.js1.29 ms4.32 ms7.68 ms
SvelteKit0.83 ms1.69 ms11.94 ms
SolidStart0.83 ms2.35 ms11.45 ms
Pracht0.81 ms1.99 ms13.27 ms
Solid 2.00.52 ms2.91 ms13.24 ms
React Router1.35 ms2.29 ms16.72 ms
TanStack Start1.37 ms4.85 ms16.09 ms
Void1.53 ms22.09 ms13.73 ms
Interaction Work to Commit

Work to commit is the sum of three parts, measured from the Chrome trace of the interaction. Idle time waiting for the next frame, and work after the frame is committed, such as raster and presentation, are not included.

  • 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 rendering work, which is the time the main thread is busy after the event callbacks, until the interaction's frame commits. It includes framework updates, style, layout, and paint, but not idle time waiting for the frame.
Interaction Work to Commit data
FrameworkInput delayProcessing durationRendering work
Astro1.63 ms0.76 ms0.00 ms
Nuxt0.75 ms1.17 ms1.10 ms
SvelteKit0.84 ms1.63 ms1.18 ms
Pracht0.81 ms1.99 ms0.87 ms
SolidStart0.81 ms2.28 ms1.35 ms
TanStack Start1.43 ms2.79 ms0.85 ms
Solid 2.00.47 ms3.36 ms1.32 ms
React Router1.39 ms4.04 ms1.11 ms
Next.js1.39 ms4.98 ms0.80 ms
Void1.67 ms23.70 ms1.33 ms

These SSR browser performance tests use Lighthouse to measure paint timings and a controlled navigation interaction. The interaction is also scored as work to commit from the same trace.

Methodology: Server Side Rendered Tests (Lighthouse).

Server First Paint (Lighthouse)
Server First Paint (Lighthouse) data
FrameworkMilliseconds
Astro55.00 ms
Pracht68.00 ms
Solid 2.072.00 ms
TanStack Start75.00 ms
SvelteKit76.00 ms
SolidStart79.00 ms
Void80.00 ms
Next.js83.00 ms
Nuxt86.00 ms
React Router115.00 ms
Server FCP (Lighthouse)
Server FCP (Lighthouse) data
FrameworkMilliseconds
Astro54.68 ms
Pracht67.66 ms
Solid 2.072.28 ms
TanStack Start74.74 ms
SvelteKit75.67 ms
SolidStart78.96 ms
Void79.90 ms
Next.js83.50 ms
Nuxt85.83 ms
React Router114.68 ms
Interaction Breakdown (Lighthouse)

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.
Interaction Breakdown (Lighthouse) data
FrameworkInput delayProcessing durationPresentation delay
Astro0.66 ms0.30 ms0.00 ms
Nuxt0.69 ms1.22 ms7.13 ms
SvelteKit0.90 ms2.07 ms11.39 ms
Solid 2.00.54 ms3.51 ms13.00 ms
React Router1.57 ms3.72 ms13.44 ms
Next.js1.28 ms4.67 ms13.33 ms
Pracht0.66 ms2.96 ms16.16 ms
TanStack Start1.26 ms3.28 ms15.75 ms
SolidStart0.89 ms2.08 ms18.26 ms
Void1.67 ms22.51 ms10.13 ms
Interaction Work to Commit

Work to commit is the sum of three parts, measured from the Chrome trace of the interaction. Idle time waiting for the next frame, and work after the frame is committed, such as raster and presentation, are not included.

  • 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 rendering work, which is the time the main thread is busy after the event callbacks, until the interaction's frame commits. It includes framework updates, style, layout, and paint, but not idle time waiting for the frame.
Interaction Work to Commit data
FrameworkInput delayProcessing durationRendering work
Astro0.57 ms0.56 ms0.00 ms
Nuxt0.81 ms1.11 ms1.14 ms
SvelteKit0.90 ms2.07 ms0.81 ms
Pracht0.73 ms2.53 ms1.28 ms
SolidStart0.85 ms2.29 ms1.89 ms
TanStack Start1.07 ms3.13 ms1.20 ms
Solid 2.00.53 ms3.78 ms1.27 ms
React Router1.81 ms3.43 ms1.75 ms
Next.js1.51 ms5.78 ms1.31 ms
Void1.67 ms22.51 ms1.20 ms

Compare the resources transferred on a first visit to the same small, styled landing page. Sizes include response headers; lower is better. Inline CSS and JavaScript count toward HTML. Other includes images, media, fonts, and remaining resources. See Methodology for collection details.

Initial Load: All Resources
  • HTML
  • CSS
  • JavaScript
  • Other
Initial Load: All Resources data
FrameworkHTMLCSSJavaScriptOther
Astro3.28 KB0.00 KB0.00 KB0.00 KB
Next.js3.74 KB1.05 KB134.76 KB0.00 KB
Nuxt4.74 KB0.88 KB67.44 KB5.48 KB
Pracht1.25 KB0.89 KB18.43 KB0.00 KB
React Router2.45 KB1.00 KB118.19 KB0.00 KB
SolidStart2.65 KB0.88 KB30.04 KB0.00 KB
Solid 2.02.75 KB0.80 KB39.69 KB0.00 KB
SvelteKit3.18 KB0.86 KB35.05 KB0.00 KB
TanStack Start3.72 KB0.94 KB97.43 KB0.00 KB
Void2.31 KB1.88 KB272.36 KB0.00 KB
Initial Load: Excluding JavaScript
  • HTML
  • CSS
  • Other
Initial Load: Excluding JavaScript data
FrameworkHTMLCSSOther
Astro3.28 KB0.00 KB0.00 KB
Next.js3.74 KB1.05 KB0.00 KB
Nuxt4.74 KB0.88 KB5.48 KB
Pracht1.25 KB0.89 KB0.00 KB
React Router2.45 KB1.00 KB0.00 KB
SolidStart2.65 KB0.88 KB0.00 KB
Solid 2.02.75 KB0.80 KB0.00 KB
SvelteKit3.18 KB0.86 KB0.00 KB
TanStack Start3.72 KB0.94 KB0.00 KB
Void2.31 KB1.88 KB0.00 KB

Methodology: Server Side Throughput Tests.

Measures how many requests each framework’s server handler can process per second when rendering a 1,000-row table, and how long each response takes. Requests bypass network overhead to focus on server rendering performance.

Ops/sec
Ops/sec data
FrameworkOperations per second
Baseline HTML836
Astro762
Pracht624
Solid 2.0586
SvelteKit467
Void458
Nuxt411
SolidStart405
TanStack Start385
React Router358
Next.js143
Body Size
Body Size data
FrameworkKiB
Baseline HTML96.83 KiB
Astro96.89 KiB
SvelteKit184.30 KiB
Pracht187.02 KiB
TanStack Start192.78 KiB
Void200.93 KiB
Nuxt201.88 KiB
Next.js203.36 KiB
Solid 2.0216.35 KiB
React Router216.84 KiB
SolidStart224.22 KiB
Median Latency

Median of measured run average latencies; not a pooled request-level median.

Median Latency data
FrameworkMilliseconds
Baseline HTML1.21 ms
Astro1.47 ms
Pracht1.65 ms
SvelteKit2.17 ms
Void2.20 ms
Solid 2.02.23 ms
SolidStart2.52 ms
Nuxt2.54 ms
TanStack Start2.62 ms
React Router2.82 ms
Next.js7.40 ms

Methodology: SSR Load Test.

Measures server throughput and response latency as concurrent connections increase, with each request rendering a 1,000-row table.

This version uses ordinary <a> links to measure server rendering without the extra work of rendering framework router link components.

Compare it with the router link load test to see how framework router link components affect server rendering performance.

P99 Latency by connections
Framework1 connection5 connections10 connections25 connections50 connections100 connections200 connections
Astro3 ms (v7.4.12)6 ms (v7.4.12)11 ms (v7.4.12)25 ms (v7.4.12)48 ms (v7.4.12)111 ms (v7.4.12)1598 ms (v7.4.12)
Baseline HTML2 ms (v24.22.1)6 ms (v24.22.1)8 ms (v24.22.1)17 ms (v24.22.1)34 ms (v24.22.1)94 ms (v24.22.1)531 ms (v24.22.1)
Next.js11 ms (v16.4.6)36 ms (v16.4.6)74 ms (v16.4.6)181 ms (v16.4.6)745 ms (v16.4.6)3204 ms (v16.4.6)4284 ms (v16.4.6)
Nuxt5 ms (v4.6.4)13 ms (v4.6.4)35 ms (v4.6.4)75 ms (v4.6.4)294 ms (v4.6.4)2668 ms (v4.6.4)2854 ms (v4.6.4)
Pracht3 ms (v1.0.0)10 ms (v1.0.0)22 ms (v1.0.0)52 ms (v1.0.0)145 ms (v1.0.0)1865 ms (v1.0.0)2151 ms (v1.0.0)
React Router5 ms (v8.5.1)21 ms (v8.5.1)43 ms (v8.5.1)103 ms (v8.5.1)422 ms (v8.5.1)3447 ms (v8.5.1)3586 ms (v8.5.1)
Solid 2.011 ms (v2.0.0)23 ms (v2.0.0)37 ms (v2.0.0)86 ms (v2.0.0)624 ms (v2.0.0)3103 ms (v2.0.0)3125 ms (v2.0.0)
SolidStart5 ms (v2.2.2)16 ms (v2.2.2)33 ms (v2.2.2)92 ms (v2.2.2)308 ms (v2.2.2)2047 ms (v2.2.2)2149 ms (v2.2.2)
SvelteKit4 ms (v3.2.0)13 ms (v3.2.0)28 ms (v3.2.0)72 ms (v3.2.0)260 ms (v3.2.0)1958 ms (v3.2.0)2160 ms (v3.2.0)
TanStack Start4 ms (v1.169.5)20 ms (v1.169.5)44 ms (v1.169.5)107 ms (v1.169.5)277 ms (v1.169.5)2544 ms (v1.169.5)2631 ms (v1.169.5)
Void4 ms (v1.11.0)19 ms (v1.11.0)40 ms (v1.11.0)95 ms (v1.11.0)208 ms (v1.11.0)2379 ms (v1.11.0)2448 ms (v1.11.0)
P90 Latency by connections
Framework1 connection5 connections10 connections25 connections50 connections100 connections200 connections
Astro1 ms (v7.4.12)4 ms (v7.4.12)8 ms (v7.4.12)18 ms (v7.4.12)32 ms (v7.4.12)67 ms (v7.4.12)109 ms (v7.4.12)
Baseline HTML1 ms (v24.22.1)3 ms (v24.22.1)6 ms (v24.22.1)16 ms (v24.22.1)29 ms (v24.22.1)63 ms (v24.22.1)141 ms (v24.22.1)
Next.js8 ms (v16.4.6)28 ms (v16.4.6)55 ms (v16.4.6)127 ms (v16.4.6)251 ms (v16.4.6)491 ms (v16.4.6)573 ms (v16.4.6)
Nuxt3 ms (v4.6.4)11 ms (v4.6.4)20 ms (v4.6.4)47 ms (v4.6.4)93 ms (v4.6.4)185 ms (v4.6.4)185 ms (v4.6.4)
Pracht2 ms (v1.0.0)7 ms (v1.0.0)15 ms (v1.0.0)41 ms (v1.0.0)102 ms (v1.0.0)172 ms (v1.0.0)172 ms (v1.0.0)
React Router4 ms (v8.5.1)16 ms (v8.5.1)30 ms (v8.5.1)76 ms (v8.5.1)145 ms (v8.5.1)283 ms (v8.5.1)278 ms (v8.5.1)
Solid 2.03 ms (v2.0.0)17 ms (v2.0.0)32 ms (v2.0.0)75 ms (v2.0.0)137 ms (v2.0.0)211 ms (v2.0.0)213 ms (v2.0.0)
SolidStart2 ms (v2.2.2)10 ms (v2.2.2)22 ms (v2.2.2)61 ms (v2.2.2)137 ms (v2.2.2)173 ms (v2.2.2)172 ms (v2.2.2)
SvelteKit2 ms (v3.2.0)9 ms (v3.2.0)18 ms (v3.2.0)54 ms (v3.2.0)123 ms (v3.2.0)180 ms (v3.2.0)200 ms (v3.2.0)
TanStack Start3 ms (v1.169.5)14 ms (v1.169.5)30 ms (v1.169.5)83 ms (v1.169.5)168 ms (v1.169.5)229 ms (v1.169.5)237 ms (v1.169.5)
Void3 ms (v1.11.0)13 ms (v1.11.0)25 ms (v1.11.0)67 ms (v1.11.0)140 ms (v1.11.0)266 ms (v1.11.0)239 ms (v1.11.0)
P75 Latency by connections
Framework1 connection5 connections10 connections25 connections50 connections100 connections200 connections
Astro1 ms (v7.4.12)4 ms (v7.4.12)7 ms (v7.4.12)17 ms (v7.4.12)32 ms (v7.4.12)65 ms (v7.4.12)99 ms (v7.4.12)
Baseline HTML1 ms (v24.22.1)3 ms (v24.22.1)6 ms (v24.22.1)14 ms (v24.22.1)29 ms (v24.22.1)55 ms (v24.22.1)107 ms (v24.22.1)
Next.js8 ms (v16.4.6)23 ms (v16.4.6)43 ms (v16.4.6)115 ms (v16.4.6)229 ms (v16.4.6)477 ms (v16.4.6)505 ms (v16.4.6)
Nuxt2 ms (v4.6.4)9 ms (v4.6.4)20 ms (v4.6.4)46 ms (v4.6.4)90 ms (v4.6.4)168 ms (v4.6.4)169 ms (v4.6.4)
Pracht2 ms (v1.0.0)7 ms (v1.0.0)13 ms (v1.0.0)35 ms (v1.0.0)85 ms (v1.0.0)130 ms (v1.0.0)124 ms (v1.0.0)
React Router3 ms (v8.5.1)15 ms (v8.5.1)29 ms (v8.5.1)70 ms (v8.5.1)141 ms (v8.5.1)260 ms (v8.5.1)257 ms (v8.5.1)
Solid 2.03 ms (v2.0.0)15 ms (v2.0.0)29 ms (v2.0.0)72 ms (v2.0.0)130 ms (v2.0.0)194 ms (v2.0.0)189 ms (v2.0.0)
SolidStart2 ms (v2.2.2)9 ms (v2.2.2)18 ms (v2.2.2)53 ms (v2.2.2)85 ms (v2.2.2)118 ms (v2.2.2)118 ms (v2.2.2)
SvelteKit2 ms (v3.2.0)9 ms (v3.2.0)17 ms (v3.2.0)43 ms (v3.2.0)93 ms (v3.2.0)136 ms (v3.2.0)139 ms (v3.2.0)
TanStack Start3 ms (v1.169.5)12 ms (v1.169.5)24 ms (v1.169.5)65 ms (v1.169.5)141 ms (v1.169.5)173 ms (v1.169.5)164 ms (v1.169.5)
Void3 ms (v1.11.0)11 ms (v1.11.0)22 ms (v1.11.0)56 ms (v1.11.0)115 ms (v1.11.0)215 ms (v1.11.0)203 ms (v1.11.0)

Methodology: SSR Router Link Load Test.

Measures server throughput and response latency as concurrent connections increase, with each request rendering a 1,000-row table using framework router link components.

Compare it with the plain link load test to see how these components affect server rendering performance. These tests make HTTP requests only; they do not measure browser navigation or prefetching.

Frameworks without a router link component are excluded.

P99 Latency by connections
Framework1 connection5 connections10 connections25 connections50 connections100 connections200 connections
Next.js12 ms (v16.4.6)44 ms (v16.4.6)95 ms (v16.4.6)217 ms (v16.4.6)996 ms (v16.4.6)4183 ms (v16.4.6)4325 ms (v16.4.6)
Nuxt8 ms (v4.6.4)43 ms (v4.6.4)82 ms (v4.6.4)493 ms (v4.6.4)2717 ms (v4.6.4)3655 ms (v4.6.4)3797 ms (v4.6.4)
Pracht3 ms (v1.0.0)12 ms (v1.0.0)31 ms (v1.0.0)86 ms (v1.0.0)330 ms (v1.0.0)2457 ms (v1.0.0)2524 ms (v1.0.0)
React Router9 ms (v8.5.1)46 ms (v8.5.1)85 ms (v8.5.1)291 ms (v8.5.1)1668 ms (v8.5.1)3853 ms (v8.5.1)3949 ms (v8.5.1)
TanStack Start6 ms (v1.169.5)31 ms (v1.169.5)66 ms (v1.169.5)219 ms (v1.169.5)1653 ms (v1.169.5)3034 ms (v1.169.5)3007 ms (v1.169.5)
Void6 ms (v1.11.0)44 ms (v1.11.0)78 ms (v1.11.0)192 ms (v1.11.0)688 ms (v1.11.0)1961 ms (v1.11.0)2878 ms (v1.11.0)
P90 Latency by connections
Framework1 connection5 connections10 connections25 connections50 connections100 connections200 connections
Next.js10 ms (v16.4.6)34 ms (v16.4.6)71 ms (v16.4.6)140 ms (v16.4.6)312 ms (v16.4.6)597 ms (v16.4.6)734 ms (v16.4.6)
Nuxt7 ms (v4.6.4)28 ms (v4.6.4)56 ms (v4.6.4)151 ms (v4.6.4)294 ms (v4.6.4)322 ms (v4.6.4)322 ms (v4.6.4)
Pracht2 ms (v1.0.0)9 ms (v1.0.0)21 ms (v1.0.0)59 ms (v1.0.0)137 ms (v1.0.0)212 ms (v1.0.0)205 ms (v1.0.0)
React Router7 ms (v8.5.1)29 ms (v8.5.1)62 ms (v8.5.1)151 ms (v8.5.1)294 ms (v8.5.1)399 ms (v8.5.1)393 ms (v8.5.1)
TanStack Start5 ms (v1.169.5)21 ms (v1.169.5)48 ms (v1.169.5)130 ms (v1.169.5)252 ms (v1.169.5)300 ms (v1.169.5)329 ms (v1.169.5)
Void6 ms (v1.11.0)26 ms (v1.11.0)52 ms (v1.11.0)135 ms (v1.11.0)307 ms (v1.11.0)551 ms (v1.11.0)660 ms (v1.11.0)
P75 Latency by connections
Framework1 connection5 connections10 connections25 connections50 connections100 connections200 connections
Next.js9 ms (v16.4.6)28 ms (v16.4.6)54 ms (v16.4.6)134 ms (v16.4.6)286 ms (v16.4.6)563 ms (v16.4.6)550 ms (v16.4.6)
Nuxt6 ms (v4.6.4)28 ms (v4.6.4)55 ms (v4.6.4)139 ms (v4.6.4)289 ms (v4.6.4)295 ms (v4.6.4)291 ms (v4.6.4)
Pracht2 ms (v1.0.0)9 ms (v1.0.0)19 ms (v1.0.0)47 ms (v1.0.0)108 ms (v1.0.0)162 ms (v1.0.0)159 ms (v1.0.0)
React Router6 ms (v8.5.1)28 ms (v8.5.1)58 ms (v8.5.1)145 ms (v8.5.1)287 ms (v8.5.1)369 ms (v8.5.1)370 ms (v8.5.1)
TanStack Start4 ms (v1.169.5)19 ms (v1.169.5)40 ms (v1.169.5)103 ms (v1.169.5)201 ms (v1.169.5)217 ms (v1.169.5)231 ms (v1.169.5)
Void5 ms (v1.11.0)25 ms (v1.11.0)50 ms (v1.11.0)125 ms (v1.11.0)253 ms (v1.11.0)503 ms (v1.11.0)483 ms (v1.11.0)