Full Device Check
Work through browser hardware checks in a sensible order, then keep a local checklist of what looks OK and what needs follow-up. No overall health score.
Your checklist
Open each test, return here and mark your observation. Manual checks are not measured by Testpartout.
1. Screen Resolution Test
See the resolution, viewport size, pixel ratio and colour depth your browser reports.
Open Screen Resolution Test →2. Dead Pixel Test
Run full-screen solid colours to reveal dead, stuck or discoloured pixels on your display.
Open Dead Pixel Test →3. Monitor Test
Inspect manually selected colors, gradients, uniformity and geometry patterns without automatic defect claims.
Open Monitor Test →4. Refresh Rate Test
Estimate the refresh rate your display is actually running at, with the limits of the method stated.
Open Refresh Rate Test →5. Keyboard Test
Press keys to confirm every one registers, and find stuck, dead or repeating keys.
Open Keyboard Test →6. Keyboard Ghosting & Key Rollover Test
Hold combinations together and compare browser-observed keys, presets and maximum simultaneous input.
Open Keyboard Ghosting & Key Rollover Test →7. Mouse Test
Check buttons, double-clicks, scrolling and pointer movement for a failing or erratic mouse.
Open Mouse Test →8. Mouse Polling Rate Test
Estimate browser-delivered mouse event rate over ten seconds with median intervals and sample context.
Open Mouse Polling Rate Test →9. Webcam Test
See your camera feed, confirm the right device is selected and check framing before a call.
Open Webcam Test →10. Microphone Test
Check that your microphone is detected and picking up sound, with a live input level meter.
Open Microphone Test →11. Speaker Test
Play left, right and reference tones to check each speaker is working, on the correct side and free of obvious distortion.
Open Speaker Test →12. Left / Right Headphone Test · Optional
Verify stereo channels, wiring and balance by playing audio to the left and right sides separately.
Open Left / Right Headphone Test →13. Touch Screen Test · Optional
Map touch coverage, compare simultaneous contacts and watch for unexpected touch events reported by your browser.
Open Touch Screen Test →14. Gamepad / Controller Test · Optional
Check buttons, triggers and analog sticks, including stick drift and dead-zone behaviour.
Open Gamepad / Controller Test →
Local checklist summary
0 completed checks · 0 need follow-up · 0 not applicable · 14 not checked
View plain-text summary
Full Device Check — local checklist 0 completed · 0 need follow-up · 0 not applicable Screen Resolution Test: Not checked Dead Pixel Test: Not checked Monitor Test: Not checked Refresh Rate Test: Not checked Keyboard Test: Not checked Keyboard Ghosting & Key Rollover Test: Not checked Mouse Test: Not checked Mouse Polling Rate Test: Not checked Webcam Test: Not checked Microphone Test: Not checked Speaker Test: Not checked Left / Right Headphone Test: Not checked Touch Screen Test: Not checked Gamepad / Controller Test: Not checked Browser observations are not hardware certification. https://testpartout.com/full-device-check
Start with the display, then input and communication
Read browser-reported screen and viewport dimensions before testing the display visually. Screen Resolution Test labels CSS pixels and device pixel ratio rather than inventing native-panel specifications. Dead Pixel Test provides solid fields for suspicious individual dots; Monitor Test adds gradients and larger uniformity patterns. Refresh Rate Test estimates visible browser frame cadence and explains why it can differ from operating-system output settings.
Next check keys individually before trying keyboard combinations. Mouse Test checks button and wheel delivery, while Mouse Polling Rate Test estimates the browser-observed event stream during continuous movement. A trackpad can emit mouse-like events, so do not treat its rate as a gaming-mouse specification. Touch Screen and Gamepad steps are optional when the device or peripheral is not present.
A checklist is not a hardware-health score
Mark Looks OK only when the check gives enough evidence for your actual task. Needs follow-up means a symptom needs comparison or a different tool, not that the device has failed a calibrated standard. Not applicable removes a step from your practical workload without pretending a feature was measured. Completed checks and follow-up counts remain separate; they are never combined into a quality percentage.
A working browser input can establish that an event or stream reached this page. It cannot establish long-term reliability, battery health, storage condition, temperature stability or suitability for every application. Use OS reports and manufacturer guidance for those separate questions. A short successful session can miss an intermittent fault.
Used-laptop checks require permission and physical inspection
The used-laptop preset adds clearly labeled manual checks for physical condition, hinges, charger, ports, battery-health evidence, Wi-Fi, keyboard wear and ownership evidence. Testpartout does not measure these. Ask the owner before connecting accessories, changing settings, enabling a camera or microphone or placing the device on a network. Do not open somebody else’s private files.
Inspect the machine in person where safe, repeat any suspicious symptom and record the reason a check needs follow-up. Browser checks cannot establish legal ownership, certify a battery or guarantee a financial decision. Test before paying when possible and rely on agreed inspection or return terms rather than a checklist label.
If a step behaves unexpectedly
Change one setting at a time and repeat the same check. For a missing input, confirm focus, permissions, connection and device selection before assuming electronics are damaged. For display timing, keep the tab visible and compare the active OS refresh setting. For speaker output, lower system volume before tones and verify mono and balance settings.
If a browser result disagrees with a calling app or game, inspect that app’s selected device, bindings and mode. Another supported browser or known-good accessory can provide a useful comparison, but does not turn the tool into manufacturer-grade diagnostics. Persistent issues may need the maker’s support procedure.
Local progress and your summary
Start checklist saves simple step statuses in versioned browser storage on this device. Test pages show a small return link while this workflow is active. You mark each step yourself after returning; test measurements are not silently copied into the checklist. The used-laptop preset shares the same full-check storage key, preserving compatible step statuses.
Copy Summary copies your chosen statuses to the clipboard only after you press it. Nothing is uploaded, and there is no account or cross-device sync. Reset checklist clears the saved progress. If storage is blocked, the page keeps usable progress only for the current visit and tells you it cannot save. No summary statuses or result values are sent to analytics.
Limits, privacy and corrections
Read our methodology and privacy policy. Found an issue with a check or explanation? Report it without sending sensitive device or personal data.