Architecture & performance
Measured on this page, right now.
Agencies claim performance. The panel below reports the Core Web Vitals of the page you are reading, captured live in your own browser — no lab test, no cherry-picked report.
01 — Rendering
Islands architecture
Static HTML ships first; interactive components hydrate only where they exist. You get server-rendered SEO with single-page responsiveness, without shipping a megabyte of JavaScript to read a paragraph.
AstroNext.js App RouterNuxt 3Partial hydration
02 — Responsiveness
INP under 200 ms at p75
Interaction to Next Paint replaced FID as the responsiveness metric. We budget it explicitly, break long tasks, and fail the build if a release pushes the 75th percentile over the line.
Long-task splittingDeferred hydrationCI budgetsRUM
03 — Delivery
Serverless & headless
Cloud functions that scale to zero and back without anyone paging an ops team, content in a headless CMS your marketing team edits directly, and previews on every branch.
VercelAWS LambdaSanityContentfulEdge cache
04 — Access
WCAG 2.2 AA, built in
Target sizes, focus appearance, keyboard paths and reduced-motion support are acceptance criteria, not a remediation project. Relevant if you sell into the EU under the European Accessibility Act — or just want the other 15% of your market.
WCAG 2.2 AAKeyboard-firstScreen-reader testedAxe in CI