Browser-based diagnostics are fast and private, but they operate within constraints that hardware-level diagnostics do not have. A browser cannot directly inspect solder joints, measure electrical resistance, or read firmware data from hardware components.
What a browser can do is verify whether a component responds correctly through the operating system and browser stack — the same layer that everyday apps use. A completed check describes this session only. An unsuccessful check can reflect permissions, unsupported APIs, routing or an observed problem; it does not by itself prove hardware damage.
For example, the camera test confirms the browser can access the camera and display a live feed. It cannot detect a cracked lens that only shows subtle flare in bright sunlight. The touch test confirms the digitizer registers touches across the screen. It cannot detect intermittent connection faults that only appear at certain temperatures.
TestMyPhone results should be used as one data point alongside visual inspection, manufacturer specifications, and — when needed — professional hardware diagnostics. For detailed explanations of what each test measures, see our testing methodology page.