Performance
Budgets, measured on every release
Components declare performance budgets in their metadata. The end-to-end suite measures them in a production build under a strict CSP and fails the release when one is exceeded.
Summary
85 / 85Measurements within budget
12Measured suites
0Third-party runtime dependencies
8 coresIntel Core i7-10510U CPU @ 1.80GHz
Results by suite
Headroom is how far the slowest measurement in a suite stays under its budget.
| Suite | Measurements | Within budget | Smallest headroom |
|---|---|---|---|
| Chart performance | 5 | 5 | 81% |
| Data table performance | 9 | 9 | 49% |
| Perf-designer | 2 | 2 | 61% |
| R1 form performance budgets | 9 | 9 | 78% |
| R2 navigation and overlay performance budgets | 8 | 8 | 88% |
| R2 picker performance budgets | 6 | 6 | 89% |
| R3 performance | 16 | 16 | 53% |
| R3 phase 2 performance | 6 | 6 | 59% |
| R3 phase 3a performance | 6 | 6 | 63% |
| R3 phase 3b performance | 6 | 6 | 64% |
| R2 upload and auth performance budgets | 7 | 7 | 62% |
| Performance budgets | 5 | 5 | 89% |
Recorded 29 September 2026 at commit f9ec31d: win32 10.0.26200 (x64), Node.js v22.18.0, Chromium bundled with Playwright (headless, Desktop Chrome profile). Times are comparable across releases on similar hardware, not with numbers published by other libraries.