Performance

Measurement protocol, baseline outcomes, and release-readiness signal for PE-01 through PE-05.

Owner
Performance Validation
Status
Demo ready
Last updated
2026-03-15

Key points

  • All required checks PE-01 through PE-05 currently pass against locked thresholds.
  • Methodology is reproducible with a single base URL and no API keys.
  • Artifacts are stored and traceable to each reported metric row.
  • Assumptions are explicit to avoid cross-profile interpretation errors.

Measurement protocol summary

AreaMethodSample sizeArtifact
Lighthouse route checksdesktop preset + provided throttling5 runslighthouse-summary.json
API latency checksrepeated endpoint fetch duration capture5 runsapi-latency-runs.json
Dashboard render timingPlaywright visibility timing for critical cards5 runsdashboard-render-runs.json

Baseline results

MetricRoute or endpointThresholdMeasured p75Status
PE-01 LCP p75/profile/pro_001<= 2.5s451.56mspass
PE-01 LCP p75/fundraisers/fun_001<= 2.5s465.99mspass
PE-01 LCP p75/communities/com_001<= 2.5s535.50mspass
PE-02 TTFB p75 proxy/dashboard<= 500ms21.00mspass
PE-03 API latency p75/api/profile/pro_001<= 250ms161.52mspass
PE-04 Route bundle gzip/dashboard<= 220KB93.23KBpass
PE-05 Dashboard first render/dashboard<= 2.0s179.30mspass

Risk and mitigation

  • Risk: network variance in deployed tests. Mitigation: p75 across repeated runs.
  • Risk: profile confusion. Mitigation: desktop + provided throttling called out in page copy.
  • Risk: stale evidence. Mitigation: artifact paths and rerun command are documented.