By Haru · Updated · 2026-08-27
Is My Phone Broken — What a Browser Test Can Prove
A browser test can prove that something works. It is much worse at proving that something is broken, and the difference is the whole reason people get confused by these pages.
When a sensor responds, that settles it: the part exists, it is connected, and the path from the hardware all the way up to a web page is intact. When nothing responds, you have learned that the path is broken somewhere along its length, and the hardware is only one of the places it could be. Between the part and the page sit a driver, an operating system, a permission prompt and a browser that may be withholding things on purpose.
This page sets out what each layer can see, in the order worth trying them, and what to say at the repair counter so the estimate is about your actual fault rather than about a vague complaint.
A response proves a lot. Silence proves very little
Take the two outcomes separately, because they are not symmetrical.
A reading that moves when you move the device is strong evidence. It means the component is physically present and working, the system is talking to it, and permission has been granted. One positive result rules out a long list of possibilities at once, which is why these tools are genuinely useful even though they are simple.
Nothing at all is much weaker evidence. It is consistent with a broken part, and equally consistent with a permission you declined last month, a page loaded over an insecure connection, a browser in a restricted mode, or a device that never had that component in the first place. Treating silence as a diagnosis is the mistake these pages invite, and it is the one worth not making before you pay for a repair.
Three layers, and the order that saves time
Start with the manufacturer's own diagnostic, because it sits closest to the hardware. Samsung phones have one built into the Members app and into device care; carriers run their own; Apple's support flow can run remote checks. These see things a web page cannot, including battery health and internal component status, and they are the right first stop for anything that looks physical.
Then use a browser test, for the one thing the built-in tools do not answer, which is the subject of the next section.
The repair counter comes last, and it goes better when you arrive with the results of the first two. Going straight there is not wrong; it is just slower and more expensive than five minutes of narrowing down.
What a browser test uniquely answers
It tests the path rather than the part. That sounds like a limitation and is actually the useful bit, because a great many complaints turn out to be about the path.
If your camera works in the built-in camera app but a web page cannot see it, the sensor is fine and the problem is a permission or a browser setting. If a game cannot follow your turn but the gyroscope test shows all three axes responding, the sensor is fine and the problem is the game. That is exactly the distinction a manufacturer's diagnostic cannot draw for you, because it never leaves the manufacturer's own software.
The same goes for the microphone, the camera and touch input. When they answer here and fail somewhere else, you have found the layer, and it is not the hardware.
Four ordinary reasons a test shows nothing
Permission is the first and by far the most common. Browsers remember a refusal, so a prompt you dismissed once will not reappear, and the page simply gets nothing. Site settings for that page is where you undo it.
An insecure connection is the second. Sensors, cameras and microphones are only available over https, so the same page on a plain http address is silent by design and not because of your device.
Third, a browser in a private, restricted or data-saving mode may withhold sensors. Trying once in an ordinary window rules this out in seconds.
Fourth, and the most common on a computer, the component may simply not exist. Almost no desktop or laptop has a gyroscope, so an empty reading there is the expected result. A test that does not tell you which of these four applies has left you to guess, which is why ours name them.
What to say at the repair counter
Resolution changes the estimate. The screen does not rotate is a symptom that could be a setting, a sensor, a loose connector or software. Front-back and left-right tilt both respond but turning does not is a fault description, and it points at one axis of one component.
Bring what you actually observed, in the order you observed it: what fails, whether it fails in more than one app, whether it fails after a restart, and what a test showed. If the fault is intermittent, note the times it happened rather than describing it as sometimes, because an intermittent fault that nobody can reproduce at the counter tends to come back unrepaired.
One thing not to bring is a conclusion. Arriving with the part already named narrows what gets checked, and a surprising share of the time the named part is fine.
Warranty, and the cost of waiting
Check whether the device is still covered before you take a screwdriver to it or accept an offer to open it. Opening a phone voids most warranties, and a claim is faster and free where one applies.
Waiting has its own cost, and it is not the same for every fault. A cracked screen that still works can be lived with; a swelling battery, water exposure or a device that gets unusually hot should not be waited out, because those get worse and can take other components with them.
And the honest limit of everything on this page: none of these tests can see the inside of your device. They can tell you which layer to look at, which is often enough to save a trip, and they cannot tell you what a part will cost or whether it is worth fixing.
Frequently asked questions
Is a browser test more accurate than the phone's built-in diagnostic?
No, and it is not trying to be. The built-in one sits closer to the hardware and can read things a web page never sees, including battery health. A browser test answers a different question that the built-in one cannot: whether the path from the hardware out to an ordinary web page is intact. Use both, starting with the built-in one.
Nothing shows up at all. Does that mean it is broken?
Not on its own. Silence is consistent with a broken part and equally consistent with a refused permission, an insecure connection, a restricted browser mode or a device that never had the component. Rule those four out first; they cost a minute each and they explain most cases.
Should I install a diagnostic app instead?
You can, and some are good, but read what they ask for. A full diagnostic app usually wants access to the camera, microphone, location, storage and more, which is a reasonable trade if you need a full report and a poor one if you only wanted to know whether one sensor responds. The built-in tool from the manufacturer asks for nothing extra and is the better first step.
Can I show a repair shop the result from a web page?
You can show them a screenshot, and it is worth doing, but expect them to run their own check. The value is not the printout; it is that you can describe the fault precisely, which changes what they look at first.
Is any of this free, and does it collect anything?
The tests on this site are free, need no account and install nothing, and the readings are used to draw the page rather than recorded or sent anywhere. Manufacturer diagnostics are also free and generally stay on the device. Third-party diagnostic apps vary and are worth reading about before installing.
The fault comes and goes. How do I test that?
Test when it is happening rather than when it is convenient, and write down the time and what you were doing. Intermittent faults are the hardest to get repaired precisely because they behave at the counter, and a short list of timestamps is more persuasive than a description of how often it feels like it happens.