pctrouble.help

Display theme

Choose the appearance you find easiest to read.

Choose a display theme

One click. Two responses?

Mouse Test & Double-Click Checker

Check the input.
Understand the response.

Test mouse buttons, unintended double-clicks, wheel input, and assigned side buttons in your browser. Keep a clear record before deciding what to try next.

  • Free · no sign-up
  • No installation
  • Inputs stay on this page
English mouse test interface before a test, with button area, checklist, hold controls, and input log
The English app before starting a test. Select the image to enlarge it.

Look closer before replacing it

When a mouse does something you did not expect.

A single click opens a folder. One button seems unresponsive. Scrolling behaves oddly, or a held button seems to release. Compare what you do with the inputs the browser receives.

Try one action at a time

Start with deliberate single clicks. Review short intervals alongside your own actions rather than treating every flag as a defect.

Check every assignment

A mapped key and a native mouse button take different paths. The app shows them separately so you can compare each button.

Keep useful evidence

Copy the report or log to keep a record. It can help describe your observations when you contact support.

Buttons, wheel, and holds

One place to review the inputs that reach your browser.

Mouse button test

Check left, right, and middle clicks, Back and Forward, and extra button events that reach the page.

Possible double-click detection

Review click intervals and possible repeated inputs. Choose a threshold that suits the comparison you want to make.

Scroll wheel test

Compare upward and downward inputs and review unusually large scroll events in the log.

Keyboard-mapped side buttons

See the keys assigned by your mouse software. Check each assignment, including mice with many side buttons.

Five-second hold test

Check left or right button continuity after a countdown. Review stable and interrupted holds separately.

Results and input log

Follow the eight-item checklist, review the overall result, and copy a report or the input log.

Three steps

Start, try, and review.

  1. 01

    Start the test

    Open the app and choose Start test, or click inside the test area. Keep mouse actions inside that area. You can pause whenever you need.

  2. 02

    Try buttons, keys, and the wheel

    Click each button and scroll up and down. Try assigned side-button keys. For a hold test, choose Test left or Test right, wait for the countdown, then hold the requested button for five seconds.

  3. 03

    Review and keep your results

    Review the checklist, input log, and test results. Choose Copy report or Copy log if you want to keep a record before closing or reloading the page.

Some buttons are handled before they reach the page.

Firefox may handle Back and Forward itself. Chrome and Edge can also miss special functions handled by a mouse driver. A missing input alone does not establish a fault.

Use a separate test profile

Assign a different ordinary key to each button in your mouse settings software, test the assignments, then restore your usual profile.

Check the whole list

One extra-button input completes that checklist item. To check all buttons, press every assignment and review each key’s entry.

Keep the limits in view

The browser cannot count your physical buttons. This app does not measure DPI, polling rate, or sensor tracking accuracy.

After the test

Compare a few simple changes.

  • Try a different USB port or connection, then compare the same deliberate actions.
  • For a wireless mouse, check its battery and connection.
  • Review operating-system double-click settings and mouse-button assignments.
  • Repeat the check in another browser, allowing for its button-handling limits.
  • If the problem persists, follow the manufacturer’s cleaning advice or contact support about inspection or repair.

The result is a record of browser input, not a repair recommendation or warranty decision.

Frequently asked questions

Can I test for unintended double-clicks?

Yes. The tool records the time between button presses and flags intervals below the selected threshold as possible chattering. The default is 80ms, with 40ms and 150ms options. Intentional fast clicks can also be flagged; this is not a hardware diagnosis.

Can I test the scroll wheel?

Yes. The tool counts upward and downward inputs and flags unusually large scroll events. Compare the input log with what you actually did. Scrolling settings and the browser can affect events, and these counts are not a measurement of physical wheel notches.

Can I test gaming mouse side buttons?

Yes, when the browser receives those inputs. Standard Back and Forward buttons and extra mouse-button events can be recorded. Buttons assigned to keys appear in the keyboard-mapped list. A button that the driver handles internally may not reach the page.

Why are some buttons not detected?

The browser only exposes events it receives; it does not enumerate the physical buttons on your mouse. DPI changes, profile changes, and other driver-only actions may not produce events for this page. Check your assignments or use a separate test profile before treating a missing input as a fault.

Does it work in Firefox?

The main button and wheel checks work with inputs received by the page. Firefox may handle Back and Forward before the page receives them. Try Chrome or Edge for those buttons, while remembering that no browser can expose every special mouse function.

How do I test keyboard-mapped buttons?

Keyboard-mapped input is on by default. While testing, press a mapped mouse button to add its assigned key to the list. Modifiers, Tab, and function keys are excluded. The tool cannot distinguish a mapped mouse button from the same key pressed on your keyboard.

How do I make a test profile for driver-only buttons?

In your mouse settings software, create a separate profile and assign a different key to each button you want to check, such as 1, 2, 3, or semicolon. Test each assignment in the mapped-key list, then restore your normal profile. Changing a DPI-only button to a key assignment tests that assignment, not DPI.

Why does one extra-button input complete the checklist item?

The item checks that an extra-button input path works. The browser cannot determine your mouse’s total physical button count. Check every assigned button individually in the mapped-key list. If no extra buttons are used, this item becomes not applicable once the other seven items are complete.

What does the five-second hold test check?

It checks whether the requested left or right button stays reported as pressed during a five-second test. Wait for the three-second countdown, then press inside the highlighted area. A release is recorded as a signal interruption. Press Esc or Cancel to stop; a release can be intentional and does not prove a hardware fault.

Are my input events sent to a server?

No. Test inputs and results are processed on the current page and are not uploaded. Only manually selected language and theme preferences are saved as settings. Copying happens when you choose a copy button. Reloading or closing the page clears the test record.

Does this confirm that my mouse is broken?

No. The results describe inputs received by the browser. Compare a different connection or browser, check batteries and assignments, and review your operating-system double-click settings. The tool does not measure polling rate or DPI, repair a mouse, or decide warranty eligibility.

A useful record, without an account.

See what each action sends.

Open the app and begin with a few single clicks.

Test your mouse

Checking a display too? Open Monitor Check Studio.