How the Device Health Score is calculated
See what the score measures, what it cannot measure, and why the same signal can be interpreted differently on a phone and a desktop.
1. Collect browser-exposed signals
DeviceTriage reads web API data such as the operating-system label, browser engine, logical processor count, rounded memory estimate, WebGL state, display dimensions, storage quota, and feature support. It never invents a hidden CPU model, temperature, physical disk health, or exact free memory.
2. Evaluate in the device's context
Phones, tablets, and desktops do not share the same processor thresholds. Four logical processors can be normal on mobile while remaining only a modest resource signal on desktop. This adds context without pretending to be a benchmark database.
3. Build explainable category scores
System carries 20%, Graphics 20%, Browser 20%, Network 15%, and Compatibility 25%. Every deduction maps to a documented rule. Hidden battery data or an unavailable optional API does not create an automatic penalty.
4. Explain findings without alarmism
Each finding includes severity, likely causes, and a low-risk recommendation. A denied permission is not called hardware failure, a hidden GPU name is not called a broken graphics card, and one HTTP route is not presented as a complete measurement of the internet line.