How We Built a Browser Based Hardware Diagnostic Suite

Every gamer, remote worker, and IT support technician eventually asks the same question: "Is this actually broken, or am I imagining it?" A controller stick feels like it's drifting. A microphone sounds muffled on a call. A laptop battery seems to drain faster than it used to. The instinctive next step is usually to download a diagnostic tooland that's where the friction begins.
Most hardware testing tools fall into one of two camps: heavyweight desktop software that requires installation, admin permissions, and often an account, or sketchy browser extensions that ask for more access than the job warrants. We built TechTester to sit in neither camp. It's a suite of free, browser based hardware diagnostic toolsgamepad tester, microphone tester, RAM speed checker, keyboard tester, and laptop battery checkerand every single one runs entirely client side. No install, no server round trip, no account, and critically, no data ever leaves the user's machine.
This article covers why we built it this way, the specific browser APIs that made it possible, and the real limitations we ran intobecause being honest about what a browser can't do is just as important as showcasing what it can.

Why client side diagnostics matter more than people realize

There's a privacy argument here that's easy to wave at and harder to actually deliver on. A tool that tests your microphone needs access to raw audio input. A tool that tests your controller needs to read every button press and stick movement in real time. If that data is being sent to a servereven briefly, even "just for processing"you've created a privacy liability for a task that has zero technical reason to leave the browser.
The W3C and WHATWG have spent the last several years standardizing exactly the browser APIs needed to do this work entirely client side:
The Gamepad API reads live button, trigger, and analog stick state from any connected controllerPS5 DualSense, Xbox Series controllers, Nintendo Switch Pro Controllers, generic USB/Bluetooth gamepadswithout any plugin.
The Web Audio API gives access to live microphone input for waveform visualization, decibel level monitoring, and frequency analysis.
The Battery Status API exposes charge level, charging state, and time to full/empty directly from the OS power subsystem.
navigator.deviceMemory and browser performance timing APIs provide approximate RAM and memory bandwidth figures.
None of these require a server. Once the page loads, the entire diagnostic loopread input, render feedback, calculate a resulthappens in memory in the user's browser tab. When the tab closes, nothing persists. There's no database to breach because there's no database.

The implementation challenges nobody warns you about

The Gamepad API in particular looks deceptively simple in documentation and gets genuinely tricky in practice. A few specific problems we had to solve:
Browsers won't report a connected gamepad until the user presses a button. This isn't a bugit's a deliberate privacy/fingerprinting mitigation. It means every gamepad tester needs an explicit "press any button to begin" prompt, and if you don't design for it, your tool just looks broken on first load.
Analog stick "rest" values are never perfectly zero. Every analog stick has a small amount of natural noise even on a healthy controller. We had to establish a practical threshold (roughly 0.05 on a 1 to 1 axis) below which a reading counts as healthy, rather than reporting any non zero value as driftwhich would produce false positives on virtually every controller tested.
Browser measured RAM speed will never match native benchmarking tools, and we say so directly. navigator.deviceMemory returns a rounded approximation (it reports values like 4, 8, or 16 GBnever your exact installed RAM), and JavaScript memory benchmarks run inside a sandboxed engine with overhead that a native tool like MemTest86 simply doesn't have. We built the RAM tester to be genuinely useful for catching obvious problems and tracking relative performance over time, but we explicitly tell users it is not a replacement for boot level memory diagnostics if they suspect a hardware fault.
Safari and Firefox don't expose audio device labels without an explicit permission grant, which means a microphone tester has to handle "Unknown Microphone" gracefully rather than assuming every browser hands over a clean device name.

What a browser genuinely cannot diagnose

This is the part most marketing pages skip, and it's the part we think matters most. A browser based controller tester can tell you a stick is drifting. It cannot tell you whywhether it's dirt under the potentiometer, worn contacts, or a firmware calibration issuebecause that requires either physical inspection or vendor specific diagnostic firmware the browser has no access to. Independent repair data (iFixit has published estimates on this) suggests a standard analog stick potentiometer is rated for roughly two million movement cycles, a number that a few months of daily gaming can realistically reachwhich is genuinely useful context for a user staring at a drift reading, even though the browser itself can't measure cycle count directly.
Similarly, a battery checker reading "87% capacity remaining" from the Battery Status API is reporting what the operating system's power management reportsit is not running a discharge curve analysis the way dedicated tools like CoconutBattery on macOS do at a deeper system level.
We'd rather a user trust our tools because we're upfront about these boundaries than oversell a browser tab's capabilities and lose that trust the first time a reading doesn't match reality.

Where this is headed

The browser API landscape keeps expanding what's feasible client side. WebHID, for instance, opens the door to reading vendor specific controller data (like DualSense adaptive trigger resistance) that the standard Gamepad API doesn't exposesomething we're actively evaluating for future versions of the controller tester. The broader trend across the no install tool space is clear: WebAssembly and modern browser APIs have made "you don't need an account, and you don't need to trust us with your data" a genuinely achievable default, not just a privacy slogan.
If you want to see the working implementation, TechTester's full suitegamepad tester, mic tester, keyboard checker, RAM tester, and laptop battery checker is free to use at techtester.online.