Mastro

Version unknown · Measured 6/27/2026

Dev Time Performance

Prod Deps	Dev Deps	Dup. Deps	node_modules	node_modules (prod)	Dep Install Size	Graph
2	2	0	29.16MB	3.36MB	27.39MB	View

Metric	Avg	Min	Max
Install	0.52s	0.51s	0.55s
Cold Build	0.37s	0.36s	0.39s
Warm Build	0.38s	0.37s	0.38s

Build output size: 0.01MB

Framework	First Paint	FCP	INP

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, TanStack Start, and React Router default to SSR with no per-route opt-out. Next.js wraps the client-side rendered table in a dynamic import with ssr: false to prevent build-time prerendering. TanStack Start uses its built-in spa mode. React Router disables SSR entirely via ssr: false in its config. All other frameworks (Nuxt, SvelteKit, SolidStart, Astro) disable SSR per-route without a separate build.
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.

Framework	First Paint	FCP	INP

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.

Framework	Ops/sec	Median Latency	Body Size	Duplication
Baseline HTML	846	1.202ms	96.81kb	1x
Mastro	501	1.99ms	181.95kb	1x

Each framework renders a table of 1000 rows with two UUID columns
Mock HTTP requests bypass TCP overhead for accurate rendering measurement
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
Astro, Nuxt, and SvelteKit handle Node.js HTTP requests natively. React Router, SolidStart, and TanStack Start use Web APIs internally, so benchmarks include the cost of their Node.js adapter layers (@react-router/node, h3, and srvx respectively)
Next.js defaults to React Server Components (RSC), a different rendering model than traditional server-rendered React. To keep the comparison fair, Next.js uses "use client" to opt out of RSC and use traditional server rendering + hydration like most of the other frameworks
Inspired by eknkc/ssr-benchmark

Framework	Peak req/s	Peak Connections	P99 @ 25	P99 @ 50	P99 @ 100	Total Req.
Baseline HTML	5,909.2	100	6ms	10ms	22ms	147,464

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