LAUNCH QA · PERFORMANCE + MOTION

Fast enough to feel handmade, not hand-cranked.

ClaraWide now records lightweight page-load evidence locally, keeps external performance-tool runs beside it, and treats animation quality as part of launch performance instead of decoration nobody tests.

TEST NOW — THIS BUILDBrowse real ClaraWide routes so passive samples appear; record one honest device/tool run; test visible motion behavior; log a temporary issue if you want to verify Admin Operations; export the JSON.

PRODUCTION LATER / ONLY WHEN ACTUALLY TESTEDDo not mark a run Production-like on clarawidetest. Do not pass reduced-motion until you really enable that OS/browser preference. Final controlled mobile/network and production evidence comes later.

PASSIVE ROUTE PROBE

Recent real page-load samples

Every ClaraWide HTML route now records a small browser-local sample: TTFB, DOM/load timing, resource count/weight, LCP and CLS where supported, long tasks, viewport, and reduced-motion preference.

CURRENT QA BUDGETS

Guardrails, not magic numbers

LCP ≤ 2.5 sLargest visible content should arrive promptly.

CLS ≤ 0.10Layout should stay put instead of jumping around.

Load ≤ 4 sPrototype guardrail for a complete route load.

Transfer ≤ 2.5 MBFlags oversized route payloads for review.

Long tasks ≤ 500 ms totalFlags main-thread work likely to feel sticky.

A local sample can help find regressions. It cannot replace controlled mobile/network testing or production telemetry.

TOOL / DEVICE RUN

Record controlled performance evidence

Use this after a Lighthouse, WebPageTest, DevTools-throttled, or physical-device run.

ANIMATION + REDUCED MOTION

Motion QA checklist

Premium animation is allowed to feel special. It is not allowed to make the marketplace harder to use.

PERFORMANCE ISSUE LOG

Turn “it feels slow” into a reproducible defect

RECENT EVIDENCE

Passive samples + controlled runs

NEXT LAUNCH LAYER

Security & abuse QA

Performance evidence is only one side of launch readiness. Next, test the protections around roles, abuse, payments, uploads, events and production authorization.

Open Security QA →

Sign-off boundaryPerformance stays In Progress until critical shopper/maker routes have controlled mobile evidence, production-like runs exist, reduced-motion behavior is verified, and unresolved Critical/High performance defects are closed or explicitly launch-waived.