Dev TimeRun Timee18e.devBlog
← All frameworks

Astro

Version 5.16.15 · Measured 6/29/2026

Dev Time Performance

Prod DepsDev DepsDup. Depsnode_modulesnode_modules (prod)Dep Install SizeGraph
1217193.23MB155.98MB163.19MBView
MetricAvgMinMax
Install1.75s1.64s2.16s
Cold Build1.28s1.24s1.37s
Warm Build1.26s1.25s1.29s

Build output size:0.03MB

Duplicate Dependencies

17 duplicate dependencies detected across this starter's node_modules.

View 17 duplicate dependencies
  • chokidar
    [duplicate dependency] chokidar has 2 installed versions:
4.0.3 via the following 1 package(s) @astrojs/check@0.9.6
5.0.0 via the following 1 package(s) unstorage@1.17.4
💡 Suggestions
- Consider upgrading consuming packages as this may resolve this duplicate version.
  • kleur
    [duplicate dependency] kleur has 2 installed versions:
4.1.5 via the following 1 package(s) @astrojs/check@0.9.6
3.0.3 via the following 1 package(s) prompts@2.4.2
💡 Suggestions
- Consider upgrading consuming packages as this may resolve this duplicate version.
  • yaml
    [duplicate dependency] yaml has 2 installed versions:
2.8.2 via the following 2 package(s) vite@6.4.1, @astrojs/yaml2ts@0.2.2
2.7.1 via the following 1 package(s) yaml-language-server@1.19.2
💡 Suggestions
- Consider standardizing on version 2.8.2 as this version is the most commonly used.
- Consider upgrading consuming packages as this may resolve this duplicate version.
  • estree-walker
    [duplicate dependency] estree-walker has 2 installed versions:
2.0.2 via the following 1 package(s) @rollup/pluginutils@5.3.0
3.0.3 via the following 1 package(s) astro@5.16.15
💡 Suggestions
- Consider upgrading consuming packages as this may resolve this duplicate version.
  • picomatch
    [duplicate dependency] picomatch has 2 installed versions:
4.0.3 via the following 5 package(s) @rollup/pluginutils@5.3.0, astro@5.16.15, fdir@6.5.0, tinyglobby@0.2.15, vite@6.4.1
2.3.1 via the following 1 package(s) anymatch@3.1.3
💡 Suggestions
- Consider standardizing on version 4.0.3 as this version is the most commonly used.
- Consider upgrading consuming packages as this may resolve this duplicate version.
  • request-light
    [duplicate dependency] request-light has 2 installed versions:
0.7.0 via the following 1 package(s) @volar/language-server@2.4.28
0.5.8 via the following 1 package(s) yaml-language-server@1.19.2
💡 Suggestions
- Consider upgrading consuming packages as this may resolve this duplicate version.
  • jsonc-parser
    [duplicate dependency] jsonc-parser has 2 installed versions:
2.3.1 via the following 1 package(s) @vscode/emmet-helper@2.11.0
3.3.1 via the following 1 package(s) vscode-json-languageservice@4.1.8
💡 Suggestions
- Consider upgrading consuming packages as this may resolve this duplicate version.
  • string-width
    [duplicate dependency] string-width has 2 installed versions:
4.2.3 via the following 4 package(s) ansi-align@3.0.1, cliui@8.0.1, wrap-ansi@7.0.0, yargs@17.7.2
7.2.0 via the following 3 package(s) boxen@8.0.1, widest-line@5.0.0, wrap-ansi@9.0.2
💡 Suggestions
- Consider standardizing on version 4.2.3 as this version is the most commonly used.
- Consider upgrading consuming packages as this may resolve this duplicate version.
  • ansi-styles
    [duplicate dependency] ansi-styles has 2 installed versions:
4.3.0 via the following 1 package(s) wrap-ansi@7.0.0
6.2.3 via the following 1 package(s) wrap-ansi@9.0.2
💡 Suggestions
- Consider upgrading consuming packages as this may resolve this duplicate version.
  • wrap-ansi
    [duplicate dependency] wrap-ansi has 2 installed versions:
9.0.2 via the following 1 package(s) boxen@8.0.1
7.0.0 via the following 1 package(s) cliui@8.0.1
💡 Suggestions
- Consider upgrading consuming packages as this may resolve this duplicate version.
  • readdirp
    [duplicate dependency] readdirp has 2 installed versions:
4.1.2 via the following 1 package(s) chokidar@4.0.3
5.0.0 via the following 1 package(s) chokidar@5.0.0
💡 Suggestions
- Consider upgrading consuming packages as this may resolve this duplicate version.
  • strip-ansi
    [duplicate dependency] strip-ansi has 2 installed versions:
6.0.1 via the following 3 package(s) string-width@4.2.3, cliui@8.0.1, wrap-ansi@7.0.0
7.1.2 via the following 2 package(s) string-width@7.2.0, wrap-ansi@9.0.2
💡 Suggestions
- Consider standardizing on version 6.0.1 as this version is the most commonly used.
- Consider upgrading consuming packages as this may resolve this duplicate version.
  • css-tree
    [duplicate dependency] css-tree has 2 installed versions:
2.2.1 via the following 1 package(s) csso@5.0.5
3.1.0 via the following 2 package(s) svgo@4.0.0, unifont@0.7.4
💡 Suggestions
- Consider standardizing on version 3.1.0 as this version is the most commonly used.
- Consider upgrading consuming packages as this may resolve this duplicate version.
  • mdn-data
    [duplicate dependency] mdn-data has 2 installed versions:
2.0.28 via the following 1 package(s) css-tree@2.2.1
2.12.2 via the following 1 package(s) css-tree@3.1.0
💡 Suggestions
- Consider upgrading consuming packages as this may resolve this duplicate version.
  • entities
    [duplicate dependency] entities has 2 installed versions:
4.5.0 via the following 1 package(s) dom-serializer@2.0.0
6.0.1 via the following 1 package(s) parse5@7.3.0
💡 Suggestions
- Consider upgrading consuming packages as this may resolve this duplicate version.
  • emoji-regex
    [duplicate dependency] emoji-regex has 2 installed versions:
8.0.0 via the following 1 package(s) string-width@4.2.3
10.6.0 via the following 1 package(s) string-width@7.2.0
💡 Suggestions
- Consider upgrading consuming packages as this may resolve this duplicate version.
  • ansi-regex
    [duplicate dependency] ansi-regex has 2 installed versions:
5.0.1 via the following 1 package(s) strip-ansi@6.0.1
6.2.2 via the following 1 package(s) strip-ansi@7.1.2
💡 Suggestions
- Consider upgrading consuming packages as this may resolve this duplicate version.

Runtime Performance

Client Side Rendered Tests

FrameworkFirst PaintFCPINP
Astro89ms88.93ms1.92ms

Methodology

  • Each framework renders a table of 1000 rows with two UUID columns
  • Measured using Lighthouse flow with Chromium via Puppeteer for accurate browser metrics
  • First Paint and First Contentful Paint are measured on initial navigation
  • Interaction to Next Paint is measured by clicking the first row's detail link
  • Benchmarks run 5 times and results are averaged
  • Next.js wraps the client-side rendered table in a dynamic import with ssr: false to prevent build-time prerendering
  • TanStack Start, Nuxt, SvelteKit, and SolidStart disable SSR per-route
  • React Router uses route-level clientLoader functions with HydrateFallback so the client-rendered routes are not server-rendered
  • Astro uses client-only React islands for client-side rendered routes
  • Client-side rendered tests use each framework's normal production build because SPA-only build modes are not supported consistently across the frameworks being compared
  • Astro uses React for its client-side rendered test: the benchmark table and detail components are React islands rendered with client:only="react", which prevents Astro from server-rendering those components and lets them render only in the browser. Astro's ClientRouter is not used for this CSR test because it enables client-side transitions and soft navigation behavior rather than client-only rendering.

Server Side Rendered Tests

FrameworkFirst PaintFCPINP
Astro69ms68.85ms0.63ms

Methodology

  • Each framework renders a table of 1000 rows with two UUID columns
  • Measured using Lighthouse flow with Chromium via Puppeteer for accurate browser metrics
  • First Paint and First Contentful Paint are measured on initial navigation
  • Interaction to Next Paint is measured by clicking the first row's detail link
  • Benchmarks run 5 times and results are averaged
  • The measured route is /server-side-rendered, and detail navigation uses /server-side-rendered/:id.

Server Side Throughput Tests

FrameworkOps/secMedian LatencyBody SizeDuplication
Baseline HTML8411.206ms96.83kb1x
Astro5291.836ms99.82kb1x

Methodology

  • Each framework renders the dedicated /ssr-throughput route with a table of 1000 rows and UUID id/name columns
  • This route intentionally does not render the exact same table as the browser SSR and load tests: it omits detail links and framework link components so router, prefetch, and navigation metadata do not dominate the request-handler throughput measurement
  • Mock HTTP requests bypass TCP overhead so this measures request-handler rendering throughput rather than full server throughput
  • Data is loaded asynchronously to simulate real-world data fetching
  • Duplication factor indicates how many times each UUID appears in the response (1x = optimal, 2x = includes hydration payload)
  • Benchmarks run for 10 seconds using tinybench
  • Frameworks are invoked through their production request handlers where possible. Web API handlers are called with Request objects; Node.js handlers are called with mock IncomingMessage and ServerResponse objects.
  • Next.js renders the throughput table as a client component, matching the setup from PR #94, so the benchmark compares traditional server-rendered React + hydration work instead of making Next.js render every table row as React Server Components
  • Inspired by eknkc/ssr-benchmark

Server Side Load Test

FrameworkPeak req/sPeak ConnectionsP99 @ 25P99 @ 50P99 @ 100Total Req.
Baseline HTML1,629.85020ms44ms107ms48,210
Astro693.62558ms116ms1710ms21,198

Methodology

  • Each framework serves the server-rendered table route over a real local HTTP server
  • The measured route is /server-side-rendered, using the same 1000-row UUID table as the SSR request throughput and browser rendering tests
  • Load is applied in staged connection counts, from 1 through 200 concurrent connections, with each stage running for approximately 5 seconds
  • Peak requests/sec is the highest successful stage throughput observed during the staged run
  • P90 and P99 latency are compared at the 25-, 50-, and 100-connection stages for every framework, so latency is measured under the same concurrency pressure
  • Total requests cover the full staged load run, not only the peak stage