Tools for QA: browser, device, keyboard, mouse, reaction
Read User-Agent, CPU/GPU hints, and test keyboard, mouse, gamepad and reaction time in the browser before a session.
Browser info is the UA string, viewport and feature bits you would otherwise paste from DevTools. Handy when a bug is “only on that laptop” and the report has no environment block.
Device info adds hardware hints the browser is willing to share: cores, memory, GPU renderer when exposed. Treat them as clues, not as a full spec sheet; browsers lie or omit on purpose.
Keyboard, mouse and gamepad pages catch stuck keys, wrong button maps and dead sticks before you blame the product under test. The reaction pad is the same idea for input lag: wait for green, click, read milliseconds.
A device pass asks what the browser claims, what the hardware reports, and whether keys, the pointer, a gamepad, and a reaction click behave. Those answers change between a laptop and a phone, so write down the browser string with the result. This page groups the check tools. It does not automate a test suite.
FAQ
Is UA spoofing detected?
We show what the browser reports. Extensions can still fake it.
Why empty GPU?
Some browsers hide the renderer. That is a privacy choice, not a broken page.
Gamepad not listed?
Press a button on the pad so the browser grants the device, then look again.