Blog
ONLINE DIAGNOSTICS

What do you want to do?

Choose a tester or describe the problem — ACC64 will take you straight to the right tool.

Game FPS TestCheck requirements, predicted FPS and a smoothness simulation
HOW IT WORKS

Check your hardware without installing extra software

ACC64 helps you check a mouse, keyboard, headphones, microphone, webcam, monitor, gamepad, steering wheel, touchscreen, MIDI devices, battery status, connected devices, system information and your internet connection. It also includes Game FPS Test and an FPS game library to quickly estimate how a game may run on your PC.

Pick a tester and you immediately see the device response or the information exposed by the browser. Tests run locally in the browser, so recordings, camera video and input data stay on your device. Treat the results as practical diagnostics before gaming, a call, buying new hardware or continuing deeper troubleshooting.

Mouse testKeyboard testHeadphone testMicrophone testWebcam testMonitor testGamepad testerSteering wheel testTouchscreen testMIDI testerBattery testConnected devicesSystem InfoSpeed TestGame FPS TestFPS game library

Latest from the blog

Practical guides for solving specific hardware problems.

View all guides →
HARDWARE DIAGNOSTICS

How to diagnose hardware problems?

ACC64 helps you diagnose hardware problems step by step. A symptom does not always reveal the cause: the issue may be the device, USB or Bluetooth connection, system settings, a driver, or a specific game or app.

01

Start with a simple test

First check whether the problem also occurs outside the app where you noticed it. If double clicks, stick movement or a missing microphone signal also appear in an independent browser test, you can narrow down the cause. Reconnect the device, try another USB port, or check the wireless connection and battery.

02

Compare symptoms and results

A single unusual reading does not necessarily mean a fault. Repeated double clicks may indicate a mouse-switch problem, constant stick deflection may suggest stick drift, and a missing audio channel can come from either the headphones or balance settings. For internet connections, watch both speed and ping stability. Repeatable results are the most useful.

03

Check the system and drivers

If the device works correctly in the test but fails in a specific app, check that app's settings, permissions and drivers. Make sure the system and the app use the same input or output device. With controllers, API support, button mapping or manufacturer software may also matter.

What does an abnormal result mean?

An abnormal result in an independent test is a clue, not always a final diagnosis. Repeat the test after reconnecting the device and, if possible, using another port or computer. If the same symptom appears in several environments, a hardware problem becomes more likely.

When is an online test not enough?

A browser has limited hardware access and cannot inspect every electronic component, mechanical condition or driver parameter. Online tests are useful for initial troubleshooting, but unstable operation, physical damage or a problem reproduced on multiple devices may require deeper diagnostics or service.

FAQ

Frequently asked questions

Do I need to install anything?

No. The testers work in a modern browser. Access to the microphone or camera only requires the permission shown by your browser.

Does ACC64 save microphone recordings or camera video?

No. Video, audio and input data used by the hardware testers remain locally on your device.

Why can’t the tester see my device?

First check the USB or Bluetooth connection, refresh the page and accept the required permissions. Some device names and parameters may be hidden by the browser.

Does ACC64 work on phones?

Yes. Some testers also work on phones and tablets, although available features depend on the device, operating system, browser and supported interfaces.

Can a browser test detect every fault?

No. An online test shows only the data and responses the browser can read. It can reveal many common problems, but it does not replace driver diagnostics, hardware measurements or a physical inspection of the device.

🔒 Hardware tests do not send recordings or input data to the server. Speed Test sends only measurement data and does not store it.
HEADPHONES

Headphone test

Check channels, frequency range and playback stability.

Headphone test

Ready
0 / 6Ready to test
🎧
DEVICE UNDER TEST
MICROPHONE

Microphone test

Check the signal level and background noise, record a sample, then play it back.

Microphone test

Ready
RMS—
PEAK—
BACKGROUND NOISE—
SIGNAL—
SNR—
SAMPLE RATE—
CHANNELS—
PROCESSING—
CLIPPING EVENTS0
Background noise
Signal level

After the test you will see a simple assessment of background noise and voice level.

Levels are shown in dBFS, not sound-pressure decibels. SNR compares the opening moment of silence with the speech that follows, so start the test somewhere quiet.

Click Start Test and speak normally. The test continues until you click Stop Test.

MOUSE

Mouse test

Click normally. The tester looks for a very fast unintended second signal typical of a faulty switch.

TOTAL CLICKS0
LAST INTERVAL— ms
DOUBLE CLICKS0
CURRENT RESULTTEST
Left button0—
Middle / wheel0—
Right button0—
Side button 40—
Side button 50—

Click reaction test

Best: —

Click Start, wait until the area turns green, then click it as quickly as possible. This tests reflexes and click reaction, not mouse hardware latency.

Ready?— ms

Scroll test

Ready
UP0
DOWN0
SUSPECTED BOUNCES0
Scroll here

Scroll for as long as you like in either direction. Statistics update live and the tester detects suspicious wheel bounce.

Horizontal scroll test

Ready
LEFT0
RIGHT0
SUSPECTED BOUNCES0
Tilt the wheel or use the side scroll wheel

If your mouse has a tilt wheel or a separate side scroll wheel, use it in this area.

The browser detects horizontal scroll events here. Support depends on the mouse, driver and operating system.

Polling rate

Move the mouse
AVERAGE— Hz
MIN— Hz
MAX— Hz
STABILITY—

Move the mouse smoothly in the main test area.

This is not a direct USB reading. It shows how often the browser receives mouse movement, so the system and current computer load can change the result.

🖱️
DEVICE UNDER TESTChrome/Edge can read the name after you grant permission.

Faulty switch test

≤ 80 ms

If the same button sends a second signal within 80 ms or less, it will be counted as a suspected double click and the corresponding part of the mouse diagram will turn red.

A normal intentional double-click slower than 80 ms does not trigger the alarm. Test with single clicks — if DOUBLE CLICKS increases despite single presses, the switch may be bouncing.

Event log

Waiting for clicks…
KEYBOARD

Keyboard test

Pressed keys light up blue. After release they remain marked as tested.

TESTED0 / 0
CURRENTLY PRESSED0
LAST KEY—
RESULTTEST
Pressed Tested Untested

Ghosting / N-Key Rollover

0 keys
MAX SIMULTANEOUS0detected keys
PRESSED NOW
Hold several keys at the same time…

Hold several keys at once. If a key you are physically holding does not light up on the keyboard above, the device may have a rollover or ghosting limitation.

⌨️
DEVICE UNDER TESTChrome/Edge can read the name after you grant permission.

Recent events

0 simultaneous
Press any key…
CAMERA

Webcam test

Check live video, smoothness, resolution and camera sharpness.

LIVE preview

Ready
0 / 3Ready to test
📷Camera is offClick “Start Test” to begin.
LIVE
— × — • — FPS
📷
CAMERA UNDER TEST

The page will ask your browser for camera access. Video stays on this device.

Test snapshot

No snapshot

Camera audio test

After permission is granted, we will try to automatically select the microphone belonging to the same camera.

AVERAGE LEVEL—
PEAK—

Click Start Test and speak normally — the graph reacts to live audio.

Video parameters

—
RESOLUTION—
FPS—
ASPECT—
STATUSOFF

FPS is measured from frames actually displayed. The value may briefly change after starting or switching cameras.

Available camera parameters

Start the camera to read parameters exposed by the browser.
GAMEPAD

Gamepad test

Complete test of buttons, sticks, triggers, D-pad, drift and vibration.

Controller

WAITING
🎮
DEVICENo controller detectedConnect a controller and press any button.
MAPPING—
CONNECTION—
BUTTONS—
AXES—
How to start the test? Connect the controller to your computer, then press any button or move a stick. ACC64 will detect it automatically and select it for testing.

If the controller was previously allowed by the browser, it will also be detected automatically when you reconnect it.

Controller preview

LIVE
LT / L2 RT / R2 Y X B A L3 R3
LT / L2
0%
RT / R2
0%

Sticks and drift

0.0%
Left stickX 0.00 • Y 0.00Drift 0.0%OK
Right stickX 0.00 • Y 0.00Drift 0.0%OK

Calibration: default center position.

Release the sticks. If drift remains high without touching them, the stick may be worn or need calibration.

All buttons

0 active
TESTED BUTTONS0 / 00%
Buttons will appear after a controller is detected.

Raw axes

— Hz
Data will appear after the controller is detected.

This is the update rate seen by the browser, not the controller’s exact USB polling rate.

DEVICES

Connected devices

See the hardware your browser can detect on this computer — in one place.

Device scan

READY
▣Displays—
⌁USB—
◉Controllers / HID—
◌Audio / video—
♫MIDI—

ACC64 only shows hardware exposed to the website by your browser. This is not a full Windows Device Manager. The same physical device can appear in more than one category.

Counts refer to entries visible to the browser, not the complete system hardware list.

Detected devices

LIVE
Click “Scan devices” to collect the available information.

Monitors and displays

DISPLAYS

An exact display count requires Window Management API support and permission. Mirrored/duplicated displays may appear as a single display. Dimensions are reported in CSS pixels, so OS scaling can make them differ from the panel’s native resolution.

API—
Displays—
Logical size—
HTTPS—
Click “Scan devices” to collect the available information.

USB device details

WEBUSB
USBNo device selectedSelect a device to view its details.

The USB list includes attached devices previously authorized for this site and a device selected with the button above.

Manufacturer—
Vendor ID—
Product ID—
USB protocol—
Device version—
Configurations—
Interfaces—
Serial number—

USB connection history

LOCAL
Waiting for a USB device…

Which devices can this scan detect?

BROWSER API
VISIBLE

Displays, accessible USB/HID devices, gamepads, MIDI, and audio/video devices — within the limits exposed by the browser.

LIMITATIONS

A website cannot show the complete OS Device Manager, drivers, or every mouse and keyboard. It also cannot reliably tell HDMI from DisplayPort or USB-C.

Data is read locally in the browser. ACC64 does not send commands to USB devices during this scan.

DEVICE DIAGNOSTICS

How to check devices connected to your computer

The ACC64 connected devices tester helps you see which hardware your browser can detect without installing extra software. In one place you can collect information about displays, USB and HID devices, controllers, audio and video hardware, and MIDI devices. It is a quick way to confirm whether the browser can see a connected device before you continue troubleshooting the operating system, driver, cable, port, or the hardware itself.

Online USB tester – what can it check?

After you grant permission, a compatible USB device may expose its product name, manufacturer, Vendor ID, Product ID, USB protocol version, configurations, interfaces, and sometimes a serial number. The test does not measure the real transfer speed of a USB port and it is not a replacement for Windows Device Manager. If a device is missing, it does not automatically mean that it is faulty — browsers hide some hardware or require explicit permission.

How can you check how many monitors are connected?

In supported browsers ACC64 can read the display list exposed by the Window Management API. This makes it possible to count available screens, identify the primary screen, and show logical dimensions. Mirrored or duplicated displays may appear as one logical screen. A website cannot reliably tell whether a monitor is physically connected through HDMI, DisplayPort, or USB-C.

Controllers, HID, audio, video and MIDI

The scan can also collect devices exposed through the Gamepad API, WebHID, MediaDevices, and Web MIDI. This can include gamepads and some controllers, microphones, audio outputs, cameras, MIDI interfaces, and MIDI controllers. Some device names only become available after the relevant permission has been granted. That is a browser privacy rule, not a failure of the tester.

Why does the scan not show every device in the computer?

A browser has much less hardware access than the operating system. It cannot read the full driver list, every PCIe device, all mice and keyboards, or hardware hidden by browser security policies. ACC64 therefore shows devices that web APIs make available to the page. If something is missing, check the connection, USB port, browser permissions, and the operating system's device manager.

Common questions about device detection

Will the tester show every USB device?

No. It can show devices that the browser is allowed to access or that you have explicitly authorized. Some system devices are intentionally hidden.

Can it test an HDMI cable or HDMI version?

Not directly. The page can inspect available displays and logical screen information, but it cannot reliably read the physical connector type or the HDMI cable version.

Why do I see one screen when two monitors are connected?

If the displays are set to mirror or duplicate the image, the browser may treat them as one logical screen. A complete display list also requires support for the relevant API and user permission.

Does the scan send my device information to a server?

The tester reads and presents these device details locally in the browser. Access to selected hardware categories is controlled by permission prompts shown by the browser.

BATTERY

Battery test

Check battery level, charging state and changes over time — no software installation required.

Battery status

READING
—%
Unknown

Live reading is active. Values depend on what the operating system and browser expose.

LEVEL—
STATE—
TIME—
API—

Battery test over time

TIMED TEST

Start the test and keep using the device in a similar way. For a discharge test, unplug the charger; for a charging test, keep the device connected.

RECOMMENDED TEST30 min
TEST TIME00:00
START—
CHANGE—
CHANGE / H—
ESTIMATED TIME—

Waiting for the battery level to change…

Change history

LIVE
Waiting for battery data…

What can a browser actually check?

WEB API
AVAILABLE

Charge level, charging state and — when the system provides them — time to full charge or estimated discharge time.

NOT AVAILABLE

Capacity in mAh/Wh, cycle count, temperature, cell wear and true Battery Health %. A normal website cannot access those values.

Battery data is read locally in your browser. ACC64 does not upload the session history.

How to interpret the battery test

The test is most useful when it runs for 20–30 minutes or longer under similar usage. Very short tests may show no change because browsers often report battery level in steps.

Common questions

Can ACC64 show battery health as a percentage?

No. Browsers do not expose design capacity and current full-charge capacity, so a Battery Health % would be a guess.

Why does the tester not work in my browser?

Battery Status API is not available in every browser. Chromium-based browsers such as Chrome and Edge currently provide the best support.

Does the test work on phones?

Yes in supported browsers such as Chrome on Android. Safari on iPhone and iPad does not expose the Battery Status API.

Why can the tester show 100% and “plugged in”?

The Battery Status API also uses 100% and “plugged in” as default values when the browser cannot report detailed battery data or when no battery is present. ACC64 marks this reading as limited; unplugging power helps confirm whether the data is real.

STEERING WHEEL

Steering wheel test

Check steering, pedals, buttons, axis range, centering, and signal stability.

Wheel / controller

WAITING
DEVICENo steering wheel detectedConnect the wheel by USB, then move it or press a button.
Rig devices0

Axis mapping

MULTI-DEVICE

Different wheels expose inputs on different axes. The tester watches axis movement automatically; if throttle, brake, or clutch is mapped incorrectly, select the correct axes manually.

ACC64 reads every controller exposed by the Gamepad API. Pedals or a shifter may appear as separate devices. Pedal mapping can use any axis or analog button from the whole rig; +/− also supports pedals sharing one axis.

Live input

LIVE
Gamepad API
Buttons / paddles / shifter0
-100%+100%
Steering—
Steering—
Center offset—
Center jitter—
Steering range—
Throttle—
Brake—
Clutch—

Signal history

10 s

Last 10 seconds. The graph can reveal signal jumps, jitter, and irregular axis movement.

Raw axis data

-1.000 → +1.000

Buttons / paddles / shifter

LIVE

Shifter positions are often exposed as regular buttons. Without a model-specific profile, ACC64 does not guess gear numbers.

Test result

DIAGNOSTIC
—/100SCORE
The report will appear automatically after the tester collects the first data.

This result is a diagnostic assessment based on signals exposed through the Gamepad API. It does not verify mechanical condition, Force Feedback strength, or internal electronics that the browser cannot access.

MIDI

MIDI tester

Connect a MIDI controller and inspect exactly the messages the device actually sends to the browser.

MIDI device

NOT CONNECTED

The tester uses the Web MIDI API. Device detection starts automatically when you open the MIDI tester. If permission is required, the browser will ask for it.

No MIDI device has been detected yet.

Last message

LIVE
TYPE—
CHANNEL—
NUMBER / CC—
VALUE—
—Press a key or pad, or move a controller.
RAW MIDI BYTES—

Active notes

0
No active notes

Controllers

CC / BEND
LAST CC——
PITCH BEND——
AFTERTOUCH——

MIDI pads

12 PADS · MPC

Pads use a fixed MPC-style layout: higher notes are shown on the upper row and lower notes on the bottom row. The same Note number always maps to the same position.

Use pad mode when your controller sends pads as Note 36–47. If the keyboard uses the same range, switch to keyboard mode.

MIDI keyboard

A0–C8 · 88 KEYS

A physically played note highlights the matching key. Highlight intensity is based on the received velocity.

A0 – C80 Note On · 0 active

Knobs / faders

8 CC · AUTO

The first 8 different Control Change messages are mapped automatically. Knobs and faders that send CC will show their 0–127 value here.

Velocity

0–127
—last
MIN —MAX —AVG —

Pitch Bend

14-BIT
-81920+8191

Mod Wheel

CC1
—/ 127
If a knob and the modulation wheel send the same CC1, choose which physical control you are testing.

Sustain

CC64
—
No CC64 received

MIDI port

INPUT / OUTPUT

The output is used only when you click an on-screen key. The tester never sends data automatically.

Last Control Change

CC
No CC messages received

Program / Aftertouch

LIVE
PROGRAM CHANGE——
CHANNEL AT—0–127
POLY AT——

MIDI event log

0 messages
Waiting for MIDI data…

ACC64 does not calculate artificial scores or parameters that the device does not transmit. Only messages received through the Web MIDI API and the values contained in those messages are shown.

TOUCH

Touch screen test

Move your fingers across the whole surface to test multi-touch and dead zones.

ACTIVE TOUCHES0
MAX SIMULTANEOUS0
TOTAL STARTS0
☝️Touch and drag across the screenColored trails show each active touch point.

If the line always breaks in the same place, that area may not register touch correctly.

SYSTEM INFO

System information

See browser, display and hardware information exposed to the site by your device.

🌐BROWSER——
💻SYSTEM——
🖥️DISPLAY——
⚙️CPU LOGICAL THREADS—Value reported by the browser. Websites cannot access the CPU model.
🧠RAM—If the browser exposes this information
🗣️SYSTEM LANGUAGE——
🕒TIME ZONE——
🔥 CPU STABILITY

Sustained performance test

Check whether your computer can maintain performance during a longer load.

The test loads the processor in your browser for about 75 seconds and tracks how compute speed changes over time.

✓ Close demanding apps✓ Keep this tab active
TEST TIME~75 s
LOADHigh
Warm-up→Calibration→Stability measurement→Result

ACC64 does not read CPU temperature in °C. The test detects performance loss and can only indicate possible thermal/power throttling.

🎨GPU REPORTED BY THE BROWSER——
VENDOR—
HARDWARE ACCELERATION—
WEBGL 2—
WEBGPU—
WEBGL VERSION—
SHADING LANGUAGE—
MAX TEXTURE SIZE—
MAX VIEWPORT—
ANTIALIASING—

The name comes from a browser interface and may describe a compatibility layer, virtual machine or another GPU. It does not confirm the physical model.

Your GPU compared with other cards

Approximate comparison of the detected model with popular graphics cards. This is not a benchmark run on this computer.

GPU
GPU IDENTIFICATION——
PERFORMANCE CLASS—
Lower performanceApproximate performance positionHigher performance

The position is an approximate ACC64 classification, not a benchmark result. It does not account for a specific game, drivers, power limits or temperatures.

How to read this chart?

← Horizontal position →

The farther right a point is, the higher the GPU’s approximate performance class. This is a reference comparison, not an FPS benchmark result.

NVIDIA / AMD / Intel rows

Each row groups GPUs from one manufacturer, making it easier to compare them with competing models.

Red points

Each point represents one GPU model in the ACC64 database. Hover over a point to see the card name.

Your detected GPU

If the browser provides an exact model, ACC64 highlights it on the chart. If only a generic name or GPU family is available, ACC64 leaves the position unassigned rather than guessing.

The chart is for quick orientation. Real performance also depends on the game or application, drivers, CPU, memory, power limits and temperatures.

MONITOR

Monitor test

Check dead pixels, banding, backlight uniformity and the estimated refresh rate.

Dead and stuck pixels

FULLSCREEN

Show a solid color fullscreen and look for pixels that do not change color or remain dark.

Banding / gradient

GRADIENT

The gradient should look smooth. Visible bands instead of a smooth transition may indicate banding.

Backlight bleed

DARK

In a dark room, display a black screen. Bright patches near the edges may indicate uneven backlighting.

Screen uniformity

UNIFORMITY

A gray background helps reveal brighter, darker or tinted areas of the panel.

Grayscale levels

STEPS

Each rectangle should be distinguishable from the next. This test helps reveal light or dark levels that blend together.

Sharpness and pixels

SHARPNESS

Alternating black and white fields should remain crisp, without colored fringes or blur.

Motion blur / ghosting

MOTION

Watch the moving object. Sharper edges during motion mean less visible display blur.

ACC64

Refresh rate

LIVE
—Hz

Measurement starts when you open this test. Keep this tab active for a moment.

This is an estimate based on frames shown by the browser. Power saving, an inactive tab or a system under load can make the reading lower.

How to test?

Clean the screen, use the native resolution and view the test from a normal distance. For backlight bleed, darken the room. ESC exits fullscreen testing.

INTERNET

Internet speed test

Measure ping, jitter, download and upload speed.

Online speed testThe best server is selected automatically
Preparing the tester…