Make performance verification reproducible
The practical problem
A single successful Lighthouse result is insufficient evidence for a commercially usable game across mobile hardware and browser caches.
Implementation protocol
Keep a fixed scenario, device profile, network throttle, warm-up instructions, test data and commit SHA. Compare repeated cold and warm runs, and retain median and tail timings.
Worked scenario
Record five cold navigations and five cached navigations to the same release, instead of quoting the fastest run as a promised customer outcome.
What could go wrong
Browser upgrades and background tabs can change timings.
Acceptance criteria
Attach tool versions, failures and the exact public URL to the acceptance record.
Source material and evidence boundaries
For the topic Make performance verification reproducible, use the sources listed below to check relevant methods. Any worked figures illustrate a scenario, not measured MojPlayWin performance. Consult the shared evidence standards before applying the method.