Skip to content
uiify

Proof

Each gate below fails a release when a size, speed or accessibility target is missed. Every number on this site comes from one of them.

CI gates

GateTarget
Gzipped bundle sizePer-component limits in .size-limit.json
Tier 0 client JavaScript0 kB — no React hook may be called
No-JavaScript suiteTier 0 passes in full; Tier 1/2 meet a documented degraded contract
Axe violations0 across Chromium, Firefox, and WebKit
Library forced layout0 ms on interaction traces
Interaction latency≤ 200 ms @ 4× CPU throttle (Chromium)
Render count≤ 2 React commits per interaction
Lighthouse (doc routes)≥ 0.95 performance, 1.00 accessibility
Core Web VitalsLCP ≤ 2500 ms, CLS ≤ 0.1, TBT ≤ 200 ms

Local verification

npm run check:layout-reads    # banned geometry reads in packages
npm run checks                  # format, lint, typecheck, unit tests
npx playwright test --config=e2e/playwright-performance.config.ts
npm run bench                   # Radix comparison (local, not CI)

Tier 0 components must also pass the no-JavaScript suite (npm run test:no-js). See Tiers

Accessibility

  • axe-core — zero violations in Playwright across Chromium, Firefox and WebKit, on styled harness routes and every public docs page.
  • APG alignment — ARIA composites follow the WAI-ARIA Authoring Practices.

See Accessibility

Radix benchmark report

Generated by npm run bench from the repository root. The same interaction scripts drive both hosts; absolute numbers are lab measurements only.

Performance Benchmark: uiify/components vs Radix UI

Methodology

  • Hardware: Apple M4 · darwin 25.5.0 · 16.0 GB RAM
  • Node: v24.18.0
  • uiify version: 0.0.0
  • Radix version: 2.3.7
  • Date: 2026-09-11
  • Warmup: 5 iterations (discarded)
  • Recorded: 50 iterations per metric
  • Trim: top/bottom 5%
  • Statistics: mean, stddev (median in results/*.json)
  • Hosts: uiify via apps/site /components/[slug]/test?profiler=true&controls=false (Next.js prod build); Radix via

benchmarks/app (Vite prod build, vite preview)

  • Headed Chromium, workers: 1, CPU throttle = 1 (raw rendering)

Results

React Commit Duration (ms) — lower is better

Componentuiify mean ± σRadix mean ± σΔ (uiify vs Radix)
select0.00 ± 0.000.00 ± 0.00—

Interaction FPS (fps) — higher is better

Componentuiify mean ± σRadix mean ± σΔ (uiify vs Radix)
select59.62 ± 4.1259.64 ± 2.92-0.0%

Forced Style/Layout (ms) — lower is better

Componentuiify mean ± σRadix mean ± σΔ (uiify vs Radix)
select0.00 ± 0.000.15 ± 0.03-100.0%

Heap After GC (MB) — lower is better

Componentuiify mean ± σRadix mean ± σΔ (uiify vs Radix)
select13.62 ± 3.1011.43 ± 3.10+19.2%

Bundle Size (kB, gzipped)

ComponentuiifyRadix
select0.0533.91

Notes

  • All measurements on headed Chrome (full GPU pipeline).
  • Variance reflects OS scheduler, GC, and browser internals.
  • The two hosts differ (Next.js SSR+hydration vs a standalone client app); both

are production builds driven by the same harness and BenchProfiler, but absolute numbers are lab-only and field behavior may differ.

  • Forced style/layout is measured in ms via the e2e CDP trace pipeline

(analyzeForcedLayout).