mygearcheck
Guided flow

Full hardware check

All 11 tests in the order that finds the expensive faults first. About fifteen minutes.

This is the sequence to use when you are inspecting a whole machine rather than chasing one fault, which usually means buying something second-hand. Work down the list, marking each test as you finish it. Arrange one thing before you start: the screen tests near the end need a dim room, and in bright light they show you nothing.

0 of 11 tests done

Keyboard TestPress every key, including both Shift, Control and Alt keys and the function row.not run
Key Code ViewerOptional. Useful when a key registers but produces the wrong character.not run
Mouse TestClick each button twenty times, slowly, and watch for a double count.not run
Touchpad TestMove to all four corners, click, two-finger scroll and pinch.not run
Gamepad TestOnly if a controller is part of the deal. Leave both sticks alone and read the resting values.not run
Microphone TestSpeak normally and watch the meter move.not run
Webcam TestCheck the preview appears, and note the resolution actually received.not run
Speaker TestLeft, then right, then both. Use the tones, not music.not run
Dead Pixel TestDim the room first. Solid black for stuck pixels, solid white for dead ones.not run
Monitor TestStill in dim light: black for backlight bleed, gradient for banding, grid for scaling.not run
Screen InfoConfirm the display is running at its native resolution and note the device pixel ratio.not run

Your progress is stored in this browser only, in localStorage. It is never uploaded and there is nowhere for it to be uploaded to. Clear stored results removes it completely, and you can see it for yourself under Application in your browser's developer tools.

Why this order

The keyboard is first because it takes two minutes and finds the fault that most often means replacing an entire top-case assembly, which is the single most expensive thing you can discover in a hurry. The trackpad follows because on many laptops it is part of that same assembly, so the two answers combine into one repair decision.

Audio and camera sit in the middle: quick, and each rules out a component you would otherwise have to take on trust. The display tests are last because they need the room conditions to change, and doing that once at the end beats doing it twice.

What this flow cannot check

Three things matter as much as anything on the list and none of them is testable from a browser: battery health against design capacity, drive health and powered-on hours, and how the machine behaves thermally under load. Ask for the first two directly, because every operating system can report them and a seller who will not show you is telling you something. The third needs the machine running something demanding for several minutes, which is worth asking for on any laptop you plan to work on.

Also worth thirty seconds and not on this list: plug something into every port, and check the hinges and the charger. A browser has nothing to say about any of them.

Where your progress is stored

In this browser, in localStorage, and nowhere else. There is no account, no sync and no server that could receive it. Clearing it removes it completely, and you can see the entry yourself under Application in your browser's developer tools. That is the same promise the tests themselves make, and it is why this flow has no sign-in.

Reading the results

Each test tells you what it found; the guides tell you what it costs. Start with how to check a second-hand laptop before you buy it for the negotiating view, or how to check a used monitor if the display is the whole purchase.