Phone How Phone Test tests work and what results mean
Our browser-based test method, evidence limits, content sourcing and correction process.
Published 24 October 2026 · English · Our method & limitations
Guided observations, not certification
Phone Test combines browser-provided signals with your own observations. Solid colours help you inspect the display; contact events help you inspect touch coverage; browser media streams support camera and microphone checks. The user decides whether the observed behaviour is expected. We do not describe these results as manufacturer certification or laboratory measurements.
What each outcome records
Working means that the function behaved as expected during the check you performed. Issue records an unexpected observation worth investigating. Skipped and unsupported outcomes mean the feature was not assessed. They must not be interpreted as passes or hardware failures. A completed sequence can still contain tests that were not verified.
Keep measurements in context
Refresh-rate results estimate browser animation timing. Multitouch results count observed contacts. Location values describe the browser’s estimate. Browser, operating system, permissions, accessories and settings can change these observations. Repeat a suspicious result and compare with an independent device function before drawing a conclusion.
How to use our guides
These guides explain the checks available in Phone Test and provide repeatable inspection steps. Technical browser limitations are linked to developer documentation below. We have not claimed a laboratory test programme, repair qualification or independent expert review. Instructions cannot cover every device and browser combination.
Corrections and updates
If an instruction conflicts with your device’s behaviour, use the Contact page to report the guide title, browser and observed behaviour. Please exclude private recordings, passwords and exact location data. Publication dates describe the article revision, not a guarantee that every browser version was tested. Material changes to the checks should be reflected in the corresponding guide.
Data handling
Review the Privacy Policy before granting permissions or sharing reports. Test results and recordings should be treated as observations about your own device, and saved reports should be checked before you pass them to another person.
Technical references
Continue learning
Phone refresh-rate test: understand your result
Understand estimated browser frame rate, why a 120 Hz screen can show a lower reading, and how to repeat a useful test.
Read guide →Camera & connectivityCamera, GPS and Bluetooth checks: understand browser limits
Separate unavailable browser features from phone faults when checking cameras, location, Bluetooth, motion and flashlight.
Read guide →Buying a used phoneA practical used-phone inspection checklist
A structured visual and browser-based inspection, with clear gaps that a phone test cannot verify.
Read guide →Found an error? Send a correction with this guide’s title and the behaviour you observed.