DEV Community: keyboardTester.Click

Dell MS700 vs Two Portable Bluetooth Mice: Which Travel Mouse Makes Sense?

keyboardTester.Click — Sat, 27 Jun 2026 07:11:53 +0000

Original full guide: Dell MS700 vs portable Bluetooth mice

The Dell Bluetooth Travel Mouse MS700 is not trying to be a gaming mouse or a cheap spare. It is a compact travel mouse built around a twistable body, Bluetooth 5.0 LE, touch scroll, and a bag-first shape.

For the closest practical comparison, I put it against two portable Bluetooth competitors:

Microsoft Surface Arc Mouse
Logitech Pebble Mouse 2 M350s

This is written as a practical desk-check from official product specifications and official images, plus the exact browser tests I would run after pairing. I am not pretending I had a review unit or week-long lab data.

Quick Recommendation

Choose the Dell MS700 if you want the most compact premium travel shape, long stated battery life, and adjustable DPI up to 4000.

Choose the Microsoft Surface Arc Mouse if you like the snap-flat Arc design and full touch-scroll surface, but accept shorter stated battery life and a higher price.

Choose the Logitech Pebble Mouse 2 M350s if value matters most. It is far cheaper, quiet, supports three Easy-Switch Bluetooth channels, and still covers the core travel-mouse job well.

Comparison Table

Mouse	Best for	Battery	DPI	Buttons and scroll	Connection
Dell Bluetooth Travel Mouse MS700	Premium compact travel	Up to 24 months, 2 AAA	1000 / 1600 / 2400 / 4000	2 buttons plus touch scroll	Bluetooth 5.0 LE, Swift Pair
Microsoft Surface Arc Mouse	Snap-flat Arc design	Up to 6 months, 2 AAA	1000 points per inch	2 buttons, full horizontal and vertical scroll plane	Bluetooth
Logitech Pebble Mouse 2 M350s	Budget and multi-device use	Up to 24 months, 1 AA	400-4000 in 100 DPI steps	3 buttons including middle click	Bluetooth LE, 3 Easy-Switch channels, Logi Bolt compatible

What The Dell MS700 Gets Right

The Dell MS700 is the most travel-specific of the three. Its twistable body is the main point: it is shaped to sit in a laptop bag without the bulk of a normal mouse.

The spec sheet also fits travel well:

Bluetooth 5.0 LE
Swift Pair support
2.01 oz weight
up to 24 months battery life
DPI choices from 1000 to 4000

The main tradeoff is the control layout. Two buttons plus touch scroll can feel clean and modern, but it also means no normal middle-click wheel. If your workflow depends on middle-click browser tabs, CAD navigation, or gaming shortcuts, test that behavior before committing.

Where Surface Arc Still Makes Sense

The Surface Arc Mouse is still the familiar premium travel option because it snaps flat. Its biggest advantage is the full scroll plane, including horizontal and vertical scrolling.

The weak points are clear from the specs: it is heavier than the Dell MS700 and Microsoft lists up to 6 months of battery life, while Dell and Logitech list up to 24 months.

Why The Logitech Pebble 2 Is The Value Pick

The Logitech Pebble Mouse 2 M350s is the least expensive of the three and still very practical. It has quiet clicks, 24-month stated battery life, Bluetooth LE, Logi Bolt compatibility, and three Easy-Switch channels.

For people who move between a laptop, tablet, and office desktop, that multi-device switching can matter more than a twistable body.

What To Test After Pairing

After buying any Bluetooth travel mouse, do not stop at "it connected." Run a few quick browser checks:

Use the online mouse tester to confirm left click, right click, middle click if present, and scroll behavior.
Use the mouse DPI tester to see whether the real pointer feel matches the advertised DPI range.
Use the mouse polling rate test if movement feels uneven.
Use the mouse drift test if the pointer moves by itself.
Use the input latency checker if Bluetooth delay feels obvious.

Final Verdict

The Dell MS700 is the best fit if you want a premium, compact Bluetooth travel mouse and you are comfortable with touch scroll instead of a traditional wheel.

The Surface Arc Mouse is the better fit if you specifically like the Arc snap-flat feel and scroll plane.

The Logitech Pebble Mouse 2 M350s is the practical winner for most people on price and multi-device convenience.

Read the full localized guide with product images and source links here:

Dell MS700 vs Microsoft Surface Arc Mouse vs Logitech Pebble Mouse 2

Keyboard CPS Test: How Fast Can You Press the Spacebar?

keyboardTester.Click — Thu, 25 Jun 2026 20:34:15 +0000

Search "keyboard CPS test" or "cps test keyboard" and a lot of the results are mouse click counters. That is the wrong tool. On a keyboard, CPS usually means how fast you can tap the spacebar, and that is a different test with different averages and a different technique.

I put the full guide here:

Keyboard CPS Test: How Fast Can You Press the Spacebar?

Here is the short version for anyone who just wants the numbers and the method.

What the test actually measures

A keyboard CPS test counts presses per second on a single key, almost always the spacebar. You run a short timer, tap as fast as you can, and read your CPS now, best, and average.

The clean flow on the spacebar speed test:

Open it in Speed mode and click the page once so the keyboard has focus.
Pick a length: 5 seconds for a burst, 10 seconds for a standard check, 30-60 seconds for stamina.
Tap only the spacebar. Take the median of three runs, not one lucky spike.

What is a good spacebar CPS?

These are practical browser-test ranges, not lab limits:

Spacebar CPS	Where it sits
3-5	Relaxed single-finger tapping (common on laptops)
6-7	Around the typical single-finger average
8-10	Fast, usually a trained finger or early two-finger rhythm
10-14	Competitive, almost always two-finger technique
14+	Very fast and hard to keep clean; records sit around 12-15 sustained

If your number jumps past ~10, that is the moment to make sure the count is real and not switch chatter inflating it.

How to actually press faster

You do not need to mash harder. The biggest jump comes from technique:

Two-finger method: hold the bar just above its actuation point with one finger, then tap with the next. Because the key only travels the last fraction of its movement, each press is shorter, so you can roughly double your CPS.
Alternating taps: bounce between index and middle finger, like butterfly clicking on a mouse, so neither finger tires as fast.
Hardware helps too: short actuation distance, fast reset, and a high polling rate all let presses register sooner. Linear switches feel quicker for rapid tapping than heavy tactiles.

2-key CPS and bridging (Minecraft, 1v1.lol)

A big chunk of "cps test keyboard 2 keys" searches come from bridging. In Minecraft and 1v1.lol you alternate two inputs fast under pressure, so your effective speed across two keys matters more than one key alone.

Start by measuring clean single-key spacebar CPS for a baseline, then practice the actual jump-and-place rhythm your game needs. A single-key number is the foundation; the alternating pattern is the skill.

The part a plain counter cannot do

This is where a generic spacebar counter falls short. While you measure speed, switch the spacebar test to Diagnostic mode and it pairs each key-down with its key-up to catch faults a counter hides:

Chatter: one tap registers as two presses a few milliseconds apart (a switch double-firing). A fast-but-chattering key inflates your CPS with fake presses.
Missed presses and stuck keys, plus operating-system auto-repeat, so you can tell whether a low score is you or the hardware.

If you see real chatter or double-spacing, that is a hardware problem, not a speed problem. The spacebar repair and double-spacing guide walks through debris, switch wear, and Filter Keys.

Where this fits with the rest of CPS

CPS is a family of tests. If you came here from the mouse side, the click speed test guide covers jitter and butterfly clicking, the drag click test explains how mice reach 20+ CPS, and the right click CPS test explains why your secondary button lags. For raw finger speed turned into real words, there is the typing speed test, and for the whole board, the keyboard tester.

Quick takeaway

Keyboard CPS means the spacebar, the average is about 6-7 CPS, and the two-finger technique is the real speed unlock. Test with a consistent length, take the median of a few runs, and switch to Diagnostic mode to confirm every press is real before you trust a high number.

Full guide: Keyboard CPS Test: How Fast Can You Press the Spacebar?

Right Click CPS Test: Why Your Right Click Is Slower Than Left

keyboardTester.Click — Thu, 25 Jun 2026 19:41:40 +0000

Most people can click faster with the left mouse button than the right. That does not automatically mean the mouse is bad. The left button gets used hundreds of times a day, the index finger is usually better trained, and the right button has one extra browser problem: normal right clicks open the context menu.

The clean way to diagnose it is simple:

Measure right-click CPS in a test area that blocks the browser context menu.
Measure left-click CPS with the same duration.
Check whether the right button misses clicks, double-clicks, or feels inconsistent.

I published the full guide here:

Right Click CPS Test: Why Your Right Click Is Slower Than Left

Why right-click CPS is usually lower

There are three common reasons.

First, the middle finger is usually less practiced. Most desktop actions, web browsing, selections, and game inputs train the left button more than the right button. That makes left-click timing feel easier and more repeatable.

Second, the right mouse button can feel slightly different. Some mice have different shell flex, switch wear, or button angle from side to side. A small feel difference can reduce CPS even when the button is healthy.

Third, right-click testing needs the browser to suppress the contextmenu event while counting clicks. If the test area does not handle that correctly, the menu interrupts the run and the score becomes meaningless.

A practical testing flow

Start with a short run on the right-click CPS test. Keep your wrist and hand position the same for every attempt.

Then run the left-click speed test for the same duration. Do not compare a five-second right-click burst with a ten-second left-click run. Use the same timing window.

If the right side is much slower, test the button itself with the mouse button tester. If one press sometimes becomes two clicks, or if one obvious press is missed, check it again with the ghost click detector.

The useful question is not "Can I force a higher number once?" It is "Does the right button register consistently under normal pressure?"

What counts as normal?

A modest right-vs-left gap is normal. For many users, 6 to 8 CPS on right click is already usable, and 9 to 12 CPS is fast in a clean browser test.

A problem is more likely when one of these happens:

The right button misses obvious presses.
One press sometimes creates two clicks.
The result changes wildly from run to run.
The same behavior appears on another computer.
The button feels physically uneven, sticky, or delayed.

If your score is only lower but the button registers every press cleanly, practice and grip are usually the better explanation.

Why this matters for games

Right-click speed matters in games where secondary actions happen repeatedly, but consistency matters more than a one-time peak. A high score with missed clicks is not useful. A slightly lower score that registers every click is better for aiming, blocking, placing, scoping, or any action that depends on reliable input timing.

If you are comparing right-click performance for Minecraft or another game, also read the drag-click low CPS guide and the broader click speed test guide. They cover technique problems that can look like hardware problems.

Quick takeaway

Right-click CPS is often lower than left-click CPS because the finger is less trained, the button may feel different, and the browser needs special handling for secondary clicks. Test right and left with the same duration, then verify the button before replacing hardware.

Canonical guide: Right Click CPS Test: Why Your Right Click Is Slower Than Left

Bluetooth Keyboard Lag: Why Your Wireless Keyboard Stutters and How to Fix It (2026)

keyboardTester.Click — Wed, 24 Jun 2026 17:39:31 +0000

A wireless keyboard that stutters, repeats a letter, or drops the first keystroke after a pause is one of the most annoying faults to chase, because the keyboard itself is usually fine. The lag lives in the radio link and the power settings around it, not the switches.

I published the full guide on KeyboardTester.click with the live latency test, localized versions (Korean, Russian, Arabic, Indonesian), BlogPosting + HowTo + FAQ + VideoObject schema, and source links:

Bluetooth Keyboard Lag: Why Your Wireless Keyboard Stutters and How to Fix It (2026)

This Dev.to version keeps the practical workflow.

Fast answer

Bluetooth keyboard lag is almost always one of three things: (1) a low battery, (2) Windows letting the Bluetooth adapter sleep to save power, or (3) 2.4 GHz interference weakening the connection. Fix them in that order, and measure the delay in your browser before and after each change so you can see what actually worked.

Measure your lag first (before and after)

Before you change anything, get a number. Open the input-latency checker, switch it to keyboard mode, and tap the same key 20-30 times. Note the average and the jitter. After each fix, run it again on the same machine: a Bluetooth keyboard that drops from 25 ms to 8 ms after you disable adapter power-saving tells you exactly which fix worked.

Honest limit: this browser test measures the JavaScript input-event slice of the chain, from keydown to page processing. It does not measure switch actuation, the keyboard's own scan, USB or Bluetooth polling, debounce, or monitor refresh. It is built for same-machine before/after comparison, not for absolute, lab-grade hardware certification like an LDAT rig. That is exactly what you need here: a consistent yardstick to prove a fix helped.

What is a good keyboard latency?

Use case	Typical latency	Verdict
Competitive / esports (wired)	Under 5 ms	Best case
Casual gaming	5-10 ms	Excellent, no felt delay
Office / typing	10-20 ms	Perfectly fine
Bluetooth (healthy)	15-30 ms	Normal; should feel instant
Failing / laggy	Over 40 ms	You will notice stutter

Why Bluetooth keyboards specifically lag

Wired keyboards send keystrokes over a dedicated USB line that polls hundreds or thousands of times per second. A Bluetooth keyboard is a low-power radio sharing the crowded 2.4 GHz band, and it negotiates a connection interval (how often it is allowed to talk) to save battery. When that interval stretches, signal weakens, or power-saving cuts in, you feel it as stutter and dropped keys.

Connection interval / poll rate - a long interval feels like a tiny stall before keys appear.
Bluetooth version and codec - older host adapters or stacks negotiate slower, less stable links than Bluetooth 5.x.
Onboard adapter vs USB dongle - a laptop's built-in antenna can be weak or shielded by the chassis.
Distance and obstruction - walls, your body, and a desk full of metal absorb 2.4 GHz signal.
2.4 GHz band congestion - Wi-Fi, USB 3.0 ports, phones, and microwaves all crowd the channel.

The 6 fixes, in the order that works

Do these top to bottom and re-measure after each one. Most people are fixed by the time they finish fix 2.

Charge or replace the battery. The number one cause of Bluetooth stutter. As voltage drops, the radio cannot hold a strong, short connection interval. Charge a rechargeable keyboard above 30% or swap in fresh cells, then re-measure.
Stop Windows sleeping the adapter. Press Win + X, open Device Manager, expand Bluetooth, right-click your Bluetooth adapter, Properties, Power Management tab, and uncheck Allow the computer to turn off this device to save power. Then set a high-performance power plan and turn off USB selective suspend.
Unpair and re-pair (or use Swift Pair). A stale pairing causes intermittent lag. Remove the keyboard in Settings > Bluetooth & devices, then add it again. Also remove old Bluetooth devices you no longer use.
Cut 2.4 GHz interference and move closer. Keep the router and phones off the desk, and move USB 3.0 devices and hubs away from a USB Bluetooth dongle, since USB 3.0 is a documented 2.4 GHz noise source. On a desktop, a short USB extension that puts the dongle on the desk surface often fixes stutter alone.
Update or roll back Bluetooth and HID drivers. Update the Bluetooth adapter and the keyboard under Keyboards and Human Interface Devices, then install pending Windows updates. If the lag started right after an update, roll that driver back.
Switch to the 2.4 GHz dongle or wired mode to isolate it. If the lag disappears on the dongle or cable, the fault is the Bluetooth link, not the keyboard. A USB BT 5 dongle or staying on 2.4 GHz is your fix.

Mac and Raspberry Pi quick notes

macOS: charge first, then remove and re-pair in System Settings > Bluetooth. Keep the Mac on AC power while testing, since Low Power Mode can throttle the radio, and move it away from USB-C hubs and displays that radiate 2.4 GHz noise.
Raspberry Pi (Linux): Pi Bluetooth is on the same chip as Wi-Fi, so a busy 2.4 GHz network is the usual culprit. Move the Pi away from the router, use 5 GHz Wi-Fi or Ethernet, and consider a powered USB Bluetooth dongle. In bluetoothctl, remove and re-pair, and update with sudo apt update and full-upgrade for the latest BlueZ stack.

Confirm the fix

Run the keyboard tester to check every key still registers after re-pairing, and a quick typing test to feel the difference in real text. For wired keyboards, repeat delay, sticky keys, and the full fix list, see how to fix keyboard delay, input lag, and sticky keys.

FAQ

Why does my Bluetooth keyboard lag? Almost always a low battery, Windows sleeping the adapter, or 2.4 GHz interference. Charge first, then turn off the adapter power-saving setting, then reduce interference.

Does low battery cause Bluetooth lag? Yes, it is the single most common cause. As the battery drains, the radio cannot hold a short connection interval, so keystrokes repeat, arrive late, or drop.

Is Bluetooth or 2.4 GHz lower latency for keyboards? A 2.4 GHz USB dongle is generally lower latency and more stable. A healthy Bluetooth keyboard still feels instant for typing at roughly 15-30 ms, but for the lowest input delay use the dongle or a wired connection.

How do I stop my wireless keyboard from sleeping? Device Manager > Bluetooth adapter > Properties > Power Management, and uncheck Allow the computer to turn off this device to save power. Also turn off USB selective suspend.

Originally published on KeyboardTester.click, where the latency test runs live in your browser.

APM Test: Measure Actions Per Minute Without Spamming Keys

keyboardTester.Click — Wed, 24 Jun 2026 16:48:30 +0000

APM means actions per minute. It is a quick way to describe how many commands a player can send through the keyboard and mouse, but it is often misunderstood because a high number is easy to fake.

I published the full guide on KeyboardTester.click with the live APM test, localized versions (Korean, Russian, Arabic, Indonesian), BlogPosting + HowTo + FAQ + VideoObject schema, and source links:

APM Test: Measure Actions Per Minute Without Spamming Keys

This Dev.to version keeps the practical workflow.

Fast answer

Use the APM Test for a clean 30 or 60 second run, keep only intentional keyboard and mouse actions, and compare the result with your task quality.

Raw APM counts every action. Useful APM is the part that still helps you move, aim, build, cast, or control the game. If your score rises because you are shaking the mouse or tapping dead keys, you are measuring spam, not skill.

What an APM test measures

An APM tester counts keyboard presses, mouse clicks, and sometimes mouse movement actions inside a timed window. That makes it a speed and control check, not a full gaming skill score.

Keyboard actions: key presses, releases, hotkeys, ability casts, build commands, and control-group switches.
Mouse actions: clicks, selection changes, camera actions, or pointer commands depending on the tool.
Time normalization: a 30 second run is doubled into a per-minute estimate; a 60 second run is already per minute.
Context gap: the number does not know whether the action was smart, mistimed, or wasted.

How to run a clean APM test

The goal is not to inflate the counter. The goal is to get a repeatable number that describes useful input speed.

Choose one test length. Use 30 seconds for warmups and 60 seconds for a steadier score.
Use real actions only. Press keys and click as if you were controlling a game.
Keep posture and device settings fixed. Same keyboard, same mouse, same desk height, same sensitivity.
Repeat three times. Use the median result, not the single best run.
Check quality after speed. If aim, typing accuracy, or command order falls apart, the APM score is above your current useful speed.

What is a good APM score?

APM ranges depend heavily on the game and test rules. Treat these as practical browser-test bands, then compare yourself against the same setup over time.

Clean APM range	What it usually means	Next step
60-120	Casual keyboard and mouse pace	Focus on clean hotkeys and reducing hesitation
120-180	Good general gaming pace	Start measuring accuracy, missed inputs, and timing
180-250	Fast hands and solid coordination	Separate real commands from filler taps
250-350+	Very fast test pace	Audit wasted actions, macro rules, and comfort

Raw APM vs effective APM

Raw APM is the total counter. Effective APM is the portion that changes the game state in a useful way. The gap between them is where spam hides.

Raw APM

Every counted input inside the timer. It is easy to raise by tapping, reselecting, or clicking without intent.

Effective APM

Actions that produce a useful command, movement, selection, cast, build, or correction.

Spam APM

Repeated actions that only raise the score. It can warm up fingers, but it should not be reported as skill.

Sustainable APM

The pace you can hold while still making correct decisions, reading the screen, and staying relaxed.

How to improve APM without spamming

Useful speed improves when the action path gets shorter and more automatic. Train consistency first, then raise the pace.

Warm up with slow perfect runs.
Practice hotkey clusters you actually use in-game.
Pair APM with another metric such as typing speed, click speed, mouse accuracy, or latency.
Record fatigue. Pain or numbness is a stop signal.
Retest weekly, not hourly.

Do not use macros to inflate an APM test

Macro-driven inputs can create superhuman APM numbers, but that is not a valid hand-speed result and can violate game rules.

In 2026, Marvel Rivals warned that players showing action rates beyond normal human hand speed could face penalties. That is a clear reminder that impossible APM is not just a vanity metric.

Use one physical action for one counted action when testing yourself. Do not compare macro-assisted results with hand-played results.

Related tools

Related guides

FAQ

What does APM mean?

APM means actions per minute. In a gaming test, it usually counts keyboard and mouse inputs during a timed run and converts the count into a one-minute rate.

Is high APM always good?

No. High APM is only useful when the actions are intentional and help the task. Random taps, repeated selections, and mouse shaking can raise raw APM without improving play.

What is a good APM for gaming?

For a clean browser test, 120-180 APM is a solid general pace, 180-250 is fast, and 250+ is very fast. The real target depends on the game and whether the actions remain accurate.

Can macros improve my APM score?

Macros can inflate the number, but that is not a hand-speed result and can break game rules. For training and comparison, use one real physical action for each counted action.

Keyboard Sound Test: Check Key Noise, Chatter, and Switch Sound

keyboardTester.Click — Tue, 23 Jun 2026 18:12:23 +0000

A keyboard can sound loud, hollow, clicky, scratchy, or uneven even when every key still works. The useful question is not only "what switch do I have?" It is whether the noise points to a real fault.

I published the full guide on KeyboardTester.click with the live keyboard sound test, localized versions (Korean, Russian, Arabic, Indonesian), BlogPosting + HowTo + FAQ schema, and source links:

Keyboard Sound Test: Check Key Noise, Chatter, and Switch Sound

This Dev.to version keeps the practical workflow.

Fast answer

Open the Keyboard Sound Test, allow the microphone, calibrate room noise, then tap letter keys first.

A clean board has repeatable peaks and similar volume from key to key. Sharp extra spikes usually mean clicky switches, stabilizer rattle, desk echo, or chatter-like contact noise.

If the sound looks wrong but the keyboard tester still shows one input per press, fix sound and mounting. If input counts double, use the repeat or chatter workflow.

Set up a fair test

The microphone hears the keyboard, desk, room, and your fingers. Control those before judging the result.

Place the microphone 15-30 cm from the keys - keep the distance fixed for every run.
Calibrate room noise first - fan noise, speech, and desk hum can mask key sound.
Start with letter keys - large keys use stabilizers, so they often rattle even when the switch is fine.
Tap with the same force - bottoming out hard creates a loud case thud.
Retest one change at a time - desk mat, keycap, switch, foam, and mic position all affect sound.

How to read the result

Do not judge one keystroke. Tap several letter keys, then a large stabilized key such as Space or Enter, and compare the pattern.

What you see or hear	Likely meaning	What to do next
Similar peaks on most letter keys	Normal switch sound and consistent typing force	Use as the baseline before checking bigger keys
One key is much louder or sharper	Loose keycap, uneven switch, desk resonance, or debris	Reseat the keycap, clean around the switch, then retest
Spacebar or Enter rattles while letters sound fine	Stabilizer rattle	Inspect the stabilizer, keycap fit, and desk surface
Sharp high-frequency click on every press	Clicky switches, or a hollow case adding click-like energy	Compare with a switch-identification guide before replacing switches
Sound is messy and input also counts twice	Possible key chatter or switch bounce	Run the key repeat test and full keyboard tester before doing sound mods

What different noises usually mean

Stabilizer rattle

Big keys sound metallic or loose while letter keys are normal. The switch is usually fine; the stabilizer needs seating or tuning.

Case ping or hollow echo

Every key has a ringing tail after the press. Try a desk mat and a different surface before opening the keyboard.

Scratchy switch sound

The downstroke has a rough sliding noise. Cleaning, switch replacement, or lubrication may help, but check warranty first.

Chatter-like click

A key makes two crisp ticks or the input tester counts double. That is an input fault candidate, not just an acoustic issue.

Room or microphone noise

The meter moves before you type, or the spectrum is busy while silent. Recalibrate, mute fans, and choose the correct mic.

Separate sound from input

A noisy key is not automatically a bad key. Confirm whether the computer receives one input per press before replacing parts.

Run the keyboard sound test and find which keys sound different.
Run the keyboard tester and press the same key once.
If it registers once, solve the acoustic problem: keycap, stabilizer, case, desk, or mic setup.
If it registers twice, solve the input problem: debounce, switch chatter, driver, or hardware fault.
If it repeats too quickly, use the key repeat rate test.

Related guides

Full guide with the live test, video, FAQ, and sources: KeyboardTester.click

Spacebar Not Working or Double-Spacing? Test It, Then Fix the Right Cause

keyboardTester.Click — Mon, 22 Jun 2026 16:24:03 +0000

A failing spacebar shows up two opposite ways: it stops registering (words run together), or it registers twice (you get a "double space"). Those are different faults with different fixes, so guessing wastes time.

I published the full guide on KeyboardTester.click with the live spacebar test, localized versions (Korean, Russian, Arabic, Indonesian), HowTo + FAQ schema, and source links:

Spacebar Not Working or Double-Spacing? Test It, Then Fix the Right Cause

This Dev.to version keeps the practical workflow.

Fast answer

Before you blame the keyboard, prove it. Open the spacebar test and press the key once, slowly:

Counts 0 → the key is dead or blocked by debris.
Counts 2 → that is chatter (or a stuck Full-width input mode).
Counts 1 but you still see double spaces in Word or Docs → the cause is software, not the key.

Match the count to the fix below.

10-second triage: hardware or software?

Question	If yes	What it means
Fails in every app (browser, Word, Notepad)?	Hardware, driver, or a system setting	A problem in one app only is that app, not the key
Laptop, and an external USB keyboard works fine?	The laptop key/membrane is the fault	Swapping isolates hardware in seconds
One press adds two spaces?	Chatter or a Full-width input mode	Two events from one press is the double-space signature
One press adds nothing?	Debris, a dead switch, or Filter Keys	Zero events means the press never reached the PC cleanly

What the count means

Count per press	Most likely cause	Where to look
0 (nothing)	Debris, dead switch, or Filter Keys ignoring the press	Hardware fixes + Filter Keys
1 but double spaces appear	Full-width input mode, "two spaces" autocorrect, app setting	Software fixes
2 (registers twice)	Key chatter (contact bounce) or stuck Full-width/IME mode	Hardware fixes + key chatter guide
Intermittent	Partial debris, worn switch, loose stabilizer	Clean and reseat, then replace switch

Software fixes (free, do these first)

Turn off Filter Keys and Sticky Keys — Win + I → Accessibility → Keyboard. Filter Keys can silently ignore short presses; this is the most common "dead key that is not really dead".
Check your input method (CJK/IME) — a Full-width space types a wide double-width space. Switch character width from Full-width to Half-width (often Shift + Space or Alt + =).
Disable "two spaces" autocorrect — Word: File → Options → Proofing → AutoCorrect; Google Docs: Tools → Preferences.
Reinstall the keyboard driver — Device Manager → Keyboards → right-click → Uninstall device → reboot.
Run the keyboard troubleshooter and update Windows — several spacebar bugs were tied to specific builds and cleared after an update.

Hardware fixes (debris, chatter, worn switch)

The spacebar is the longest key with a metal stabilizer bar under it, so it traps debris and wears differently from normal keys.

Compressed air first — hold a laptop at ~75 degrees and blow short bursts around and under the key from a few directions.
Lift the keycap to clean underneath — pry gently from one corner; do not yank straight up or you can bend the stabilizer bar. Wipe contacts with 90%+ isopropyl alcohol, dry, then press the cap back square.
Fix chatter (registers twice) — a free Windows software-debounce tool blocks a repeat press within a few milliseconds; on QMK boards, raise the DEBOUNCE value.
Reseat or replace a worn switch — on a hot-swap board, swap the spacebar switch in minutes.
Stopgaps — On-Screen Keyboard, remap another key to Space, or use an external keyboard.

Confirm the fix

Re-run the spacebar test: a healthy key now reads exactly 1 per press. Then run the full keyboard tester to check every other key while you are at it.

If other keys double up too, that is contact bounce across the board — see the key chatter fix guide. If keys feel delayed or sticky instead, see the keyboard lag and sticky-key fix.

Full guide with the live test, FAQ, and sources: keyboardtester.click

Black Crush Test: Check Monitor Shadow Detail and Fix Crushed Blacks

keyboardTester.Click — Mon, 22 Jun 2026 15:58:25 +0000

Dark scenes should still have detail.

If caves, night scenes, dark clothing, hair, and horror-game corners all collapse into one flat black shape, your monitor may be crushing blacks.

I published the full source-backed version on KeyboardTester.click with the live test, FAQ schema, localized versions, images, source notes, and related monitor tools:

Black Crush Test: Check Monitor Shadow Detail and Fix Crushed Blacks

This DEV.to version keeps the practical diagnostic and fix workflow.

Fast answer

Run a black level test in a dim room and look for the first near-black box you can separate from the background.

If boxes 1-5 disappear but 6-8 are visible, you have mild black crush.
If the first visible box is 9-15, tune brightness, HDMI black level, RGB range, and gamma.
If only 16+ is visible, suspect a severe Full vs Limited RGB mismatch or an aggressive OLED/HDR shadow setting.

The lowest boxes should be barely visible, not bright. You are looking for separation from the background, not a gray-looking screen.

What black crush means

Black crush is when near-black tones are clipped into pure black.

Instead of seeing separate shadow steps, the display makes many dark values look identical. That hides texture in:

night scenes
horror games
dark clothing
hair and skin shadows
caves and interiors
OLED HDR content

This is different from washed-out blacks. Black crush hides detail by making shadows too dark. Washed-out blacks lift the black floor so black looks gray.

Run the test properly

Use one controlled test before changing a dozen settings.

Open the Black Level Test.
Let your eyes adapt for 30-60 seconds.
Use your normal input, monitor mode, and brightness.
Turn off dynamic contrast and extreme black stabilizer modes for the first pass.
Count the lowest numbered patch that separates from the background.

Change one setting, then run the same test again.

That discipline matters. Otherwise you can mistake RGB range, gamma, HDR, and game sliders for the same problem.

How to read the result

First visible box	Meaning	Next action
1-3	Excellent shadow detail, or brightness may be slightly high	Compare with a color range test
4-5	Normal to mild crush	Usually fine if dark scenes still show texture
6-8	Mild black crush	Raise brightness slightly and check gamma
9-15	Moderate crush	Check HDMI black level and GPU RGB range
16+	Severe crush or range mismatch	Reset picture mode and match Full/Limited range

If black becomes gray while trying to reveal the first patches, stop. You may be fixing the wrong problem.

Fix path for crushed blacks

1. Brightness / black level

Raise brightness until patch 2 or 3 barely separates from black, then stop.

If the whole black floor becomes gray, brightness is too high or RGB range is wrong.

2. HDMI black level

Monitor menus use names like:

Black Level
HDMI Black Level
Input Range
RGB Range
Low / Normal
Limited / Full

The exact label varies by brand. The important part is matching the display expectation with the GPU output.

3. GPU output range

For most PC monitors, Full RGB 0-255 is the right output.

Limited range, 16-235, is common in TV/video chains. It is not automatically wrong, but a mismatch causes problems:

GPU output	Display expectation	Result
Full 0-255	Full 0-255	Correct for most PC monitors
Limited 16-235	Limited 16-235	Correct for many TV/video chains
Limited 16-235	Full 0-255	Washed-out gray blacks
Full 0-255	Limited 16-235	Crushed shadow detail

If your blacks are crushed, that fourth row is a common cause.

4. Gamma

High gamma darkens midtones and shadows. Low gamma reveals detail but can make the picture flat.

Use a monitor gamma test after RGB range is correct.

5. HDR and game sliders

Calibrate SDR first.

Then set HDR black point and in-game brightness using the game instruction: the logo should be barely visible, not comfortably bright.

OLED and HDR notes

OLED panels make black crush easier to notice because true black is extremely deep. The jump from black to the first visible step can be abrupt.

HDR tone mapping, VRR behavior, and black stabilizer features can also change near-black detail.

If only one area of the screen loses shadow detail, also run a screen uniformity test. If the whole screen clips evenly, settings are more likely than a panel defect.

Related tests

Black Level Test - count near-black patches
Color Range Test - catch Full vs Limited RGB mismatches
Monitor Gamma Test - check whether gamma is hiding shadows
Screen Uniformity Test - separate panel uniformity from global settings

Sources and deeper notes are in the canonical article:

Black Crush Test: Check Monitor Shadow Detail and Fix Crushed Blacks

What Is a Good Reaction Time for Gaming? Average ms by Age

keyboardTester.Click — Sat, 20 Jun 2026 19:16:39 +0000

You clicked when the screen turned green, you got a number in milliseconds, and you want to know one thing: is that good?

I published the full guide on KeyboardTester.click with the live reaction time test, the average-by-age table, skill tiers, genre requirements, honest latency caveats, FAQ schema, and localized versions (Korean, Russian, Arabic, Indonesian):

What Is a Good Reaction Time for Gaming? Average ms by Age and How to React Faster

This Dev.to version keeps the practical benchmark and improvement workflow.

Fast answer

For a simple visual reaction test, the average adult lands around 200-250 ms (Human Benchmark's in-browser median is about 273 ms).

Under 250 ms is good for gaming.
Under 200 ms is competitive.
Pro FPS players sit around 150-190 ms.

A browser test adds your display and input latency on top of pure nerve-to-muscle time, so the absolute number reads slightly slower than a lab figure. Treat it as a great before-and-after gauge, not a clinical reading. Start with the reaction time test and take the best of 5 clean trials.

Reaction time tiers

Tier	Visual reaction time	Who lands here
Needs work	300 ms or slower	Tired, distracted, slow display, or untrained
Average	250-300 ms	Most casual players and the general adult population
Good for gaming	200-250 ms	Regular gamers with decent gear and a warm-up
Competitive	180-200 ms	Ranked and semi-pro players, well-trained and focused
Pro / elite	150-190 ms	Pro FPS players, fighter pilots, F1 drivers

Average reaction time by age

Age group	Typical visual reaction time
10-19	~210 ms
20-29	~220 ms
30-39	~235 ms
40-49	~250 ms
50-59	~270 ms
60-69	~295 ms
70+	~330 ms

Reaction time is fastest in your late teens and twenties and slows gradually after that.

Test it the right way

Sit ready and wait. Do not hover-click. Clicking before the green appears is a false start, not a fast time.
Take 5 clean trials. React only when the box turns green; ignore early twitches.
Use your best of 5. Your fastest clean trial best represents your true ceiling.
Test on your real gear. A phone over Wi-Fi reads differently than a wired 144Hz setup.
Re-test after one change. Change one variable (sleep, warm-up, refresh rate) so you know what actually moved the number.

Why your number might look slow

Low refresh rate: a 60Hz screen can show the stimulus up to ~16 ms late.
Wireless / Bluetooth lag: Bluetooth input can add 10-40 ms versus wired or 2.4 GHz.
No warm-up or fatigue: cold or sleep-deprived runs read 25-50 ms slower.
Display / TV processing: enable game mode or test on a low-latency monitor.
Browser and background load: heavy tabs, downloads, or recording steal frames.

How to actually react faster (2-4 week plan)

Genetics set a floor, so do not expect to shave 80 ms off. What you can realistically improve is consistency plus a modest amount of raw speed:

Train the response daily with five focused minutes on a reaction test.
Fix your latency stack: highest refresh rate, wired or 2.4 GHz mouse, game mode on a TV.
Warm up before ranked with a few reaction trials and light aim.
Sleep 7-9 hours - tired reactions are measurably slower.
Train anticipation, not just reflex: pre-aim common angles and learn enemy timings.
Track your own trend weekly on the same gear.

Reaction time is not aim score

If you play shooters, a slow result might be aim, not reaction. They are different numbers measured by different tools. Compare your visual and audio reaction, then check whether aim is the real bottleneck:

Reaction Time Test - visual reaction in milliseconds
Auditory Reaction Time Test - sound vs sight on the same device
Mouse Accuracy Test - is aim the real bottleneck?
Refresh Rate Test - confirm your monitor runs at full Hz

Full guide with sources, FAQ, and the genre-requirements table: What Is a Good Reaction Time for Gaming?

Subwoofer Test Online: Is Your Sub Working or Blown?

keyboardTester.Click — Sat, 20 Jun 2026 16:28:19 +0000

You press play and the subwoofer does almost nothing. Is it blown, muted, miswired, or just sitting in a room null?

I published the full guide on KeyboardTester.click with the live 20 Hz to 200 Hz bass sweep, symptom tables, setup checks, source links, FAQ schema, and localized versions:

Subwoofer Test Online: Is Your Sub Working or Blown?

This Dev.to version keeps the practical diagnostic workflow.

Fast answer

Start the Bass Test at low volume, run the 20-200 Hz sweep, and listen for the pattern.

Smooth output means the sub is probably receiving signal and working.
No sound usually points to power, cable, receiver, LFE, crossover, or mute settings first.
Rattling, scraping, burnt smell, or distortion even at low volume can mean driver, amp, or enclosure damage, so stop testing and inspect safely.

A browser sweep can reveal symptoms. It cannot certify the electrical health of a subwoofer by itself.

Run the test safely

Turn volume down first. Set system volume and subwoofer gain low, then raise slowly. If you hear scraping, clack, harsh buzzing, or distress, stop.
Play the 20-200 Hz sweep. Note where sound begins, becomes strongest, disappears, rattles, or changes tone.
Hold a problem frequency. If the issue appears around 40 Hz or 80 Hz, use hold/step mode to repeat that one tone at low volume.
Compare routing and placement. Check LFE/sub output, crossover, phase, cable, receiver mode, and room placement before assuming the driver is blown.

What each result usually means

What you hear	Likely cause	Next check
Smooth bass from about 30-120 Hz	The subwoofer is receiving signal and reproducing the main bass band	Fine-tune placement, crossover, and gain
No sound at any bass frequency	Power, standby, mute, LFE cable, receiver output, PC audio route, or failed amp	Confirm power light, cable, input, receiver sub output, and another source
Bass only above 80-120 Hz	Crossover, tiny speaker pretending to be a sub, high-pass filter, or weak low-end capability	Lower crossover carefully and compare with a frequency-response sweep
A hole around one narrow frequency	Room cancellation, phase mismatch, or placement null	Move the sub or listening seat, flip phase, and retest
Rattle, buzz, or cabinet vibration	Loose grille, loose object, port noise, damaged surround, or driver stress	Remove loose objects and lower volume
Scraping or crackling on gentle movement	Possible voice-coil rub, torn spider/surround, or driver damage	Stop the sweep and use service-safe inspection or warranty support

Settings to check before blaming the driver

Most "dead sub" cases are setup problems before they are hardware failures:

Power and standby: auto-standby may not wake on quiet signals.
LFE/sub cable: a loose RCA, wrong output, or wrong input can make the sub appear dead.
Receiver speaker size: if fronts are set Large and bass management is off, little bass may reach the sub.
Crossover and gain: too low a crossover or very low gain makes the sweep seem weak.
Phase and placement: a sub can cancel with front speakers at the listening seat.
Content mode: Stereo, Pure Direct, night mode, Bluetooth, or TV pass-through can drop LFE.

When to stop testing

Stop if you notice:

Burnt smell from the cabinet or amp plate.
Scraping when the cone moves gently.
Distortion at very low volume.
Sudden silence after a loud event.

Those signs do not prove the exact failure mode, but they are enough reason to stop feeding sine waves into the subwoofer and move to safe inspection, repair, or warranty support.

Small speakers are different

For headphones, use the sweep to learn where bass rolls off, not to decide whether a subwoofer is blown. For laptop and phone speakers, missing 20-60 Hz is normal physics, not a defect.

Full guide with live tool, tables, sources, and FAQs:

Subwoofer Test Online: Is Your Sub Working or Blown?

OLED Burn-In Test: Image Retention vs Permanent Burn-In (and How to Recover It)

keyboardTester.Click — Fri, 19 Jun 2026 18:15:56 +0000

You close a game or quit a long session and notice it: a faint ghost of the HUD, the taskbar, or a channel logo still hovering on your OLED. Cue the panic. Is the panel ruined? Is this the dreaded burn-in? Will it fade, or is it stuck forever? The forums are full of scary photos and conflicting advice, but almost nobody gives you a way to actually test which one you have.

I published the full guide on KeyboardTester.click with the live burn-in test, a temp-vs-permanent comparison table, the recovery refresher step, an RMA decision tree, source links, FAQ schema, and localized versions:

OLED Burn-In Test: Image Retention vs Permanent Burn-In

This Dev.to version keeps the practical test-and-recover workflow.

Fast answer

Image retention is temporary and fades; burn-in is permanent and does not. To tell which you have, show a faint even shade like 50% gray, note the ghost, then run varied content or a scrolling refresher for 10–60 minutes. If the ghost fades, it was retention — no damage. If it stays in exactly the same spot, it is burn-in.

A browser test can reveal visible wear and run a pixel-refresher, but it cannot certify permanent damage on its own, so route the final call and any warranty claim to the manufacturer. Start with the OLED Burn-In Test in fullscreen.

Run the test: what to look for

Open the burn-in test, press Fullscreen, and use three things:

Solid colors (reveal retention and uneven wear) — cycle white, black, red, green, blue, then linger on a mid gray. ~50% gray is the most revealing for faint ghosts.
Checkerboard (expose stuck or dead subpixels) — a different defect from burn-in; follow up with a dead pixel test if you find isolated dots.
Scroll mode (the pixel refresher) — a full-screen scrolling bar pattern that exercises every pixel evenly. It is the on-demand version of your OLED's overnight pixel-refresh, and it is your recovery step.

The honest limit: a browser test shows what is visible right now and lets you run a refresher. It cannot, on its own, certify that damage is permanent — only the fade-or-stay retest plus the manufacturer's panel-care process can.

Image retention vs permanent burn-in

Trait	Image retention	Permanent burn-in
Permanent?	No — temporary	Yes — irreversible
Does it fade?	Fades with varied content or a refresh	Never; stays in the same spot
Typical timeframe	Minutes to about an hour	Thousands of hours of static content
Looks like	Faint, fuzzy ghost of recent content	Fixed, defined logo/HUD/bar, dimmer or color-shifted
Cause	Short-term pixel-state lag	Physical, uneven aging of pixel material
Fixable?	Yes — varied content, refresher, time	No user fix; mitigate or RMA

The one-test rule: show 50% gray, note the ghost, then run varied content or the scrolling refresher for 10–60 minutes and re-check. Faded = retention (no damage). Still there, unchanged = burn-in (permanent).

What causes it

OLED pixels are individual organic light-emitters that dim slightly every hour they run. Burn-in happens when some pixels run far harder than their neighbors and age unevenly:

Static high-contrast HUDs and UI (a fixed game HUD held for hundreds of hours is the classic culprit).
Taskbars, docks, and desktop elements.
Channel logos and news tickers.
High brightness (wear scales with brightness).
Letterbox bars and aspect-ratio borders.

What is not on the list: a few hours of mixed movies, games, or browsing. Long-term testing consistently shows burn-in is uncommon under normal varied use.

Recover it: the scrolling pixel-refresher

If the retest says retention, there is a real recovery step — and it is built into the test:

Show varied content for 10–60 minutes — clears most light retention with no tool.
Run the scrolling refresher in fullscreen; leave an even moving pattern running for a few hours for stubborn retention.
Lower brightness on static content so pixels are not over-driven.
Run the built-in pixel-refresh (often triggered overnight in standby) — the manufacturer's own recovery cycle.

When it is permanent: the RMA decision

If the ghost survives varied content, the scrolling refresher, and a full built-in pixel-refresh cycle, it is most likely permanent burn-in. There is no user fix that restores aged pixels.

An RMA makes sense when the ghost is clearly permanent, visible during normal use, and the panel is still inside its warranty or burn-in coverage window. Run the manufacturer's pixel-refresh first (some require it before honoring a claim), capture evidence, and contact support — the authoritative call on permanent burn-in comes from their panel-care process.

Pair the burn-in test with a screen uniformity test, a color test, and a dead pixel test so you are not chasing the wrong fault. If your worry is motion smear rather than a fixed ghost, that is a different issue — check the monitor ghosting test instead.

Prevent it going forward

Lower brightness for static content.
Enable pixel shift / orbit.
Auto-hide taskbars and docks.
Vary your content.
Let the panel-refresh run in standby.

Full guide with the live test, decision tree, sources, and FAQ: OLED Burn-In Test: Image Retention vs Permanent Burn-In

Monitor Ghosting Test: Find the Right Overdrive Setting

keyboardTester.Click — Fri, 19 Jun 2026 18:07:19 +0000

The fastest response-time label in a monitor menu is not always the cleanest setting.

I published the full guide on KeyboardTester.click with the live monitor ghosting test, localized versions, FAQ schema, source links, and a practical overdrive decision table:

Monitor Ghosting Test: Find the Right Overdrive Setting

This Dev.to version keeps the practical workflow.

Fast answer

Open the Monitor Ghosting Test, set your monitor to the refresh rate you actually use, then compare overdrive Off, Normal, Fast, and Extreme one at a time.

Keep the lowest setting that removes the long same-color trail. If a bright, dark, or opposite-color halo appears, that is inverse ghosting or overshoot, so lower overdrive one step.

Why the fastest mode can look worse

LCD overdrive pushes pixels harder so they reach the target color faster. Push too little and you get normal ghosting: a smeared trail behind motion. Push too much and the pixel overshoots the target, creating coronas or inverse ghosting.

That is why the best setting is often Normal or Medium, not Extreme.

What to look for

Symptom	Likely cause	Change
Same-color trail behind motion	Pixel response is too slow	Raise overdrive one step
Bright, dark, or opposite-color halo	Overdrive overshoot	Lower overdrive one step
Black smear in dark scenes	VA dark-to-dark response limit	Try Normal overdrive, higher Hz, or accept panel limit
Motion jumps instead of smears	Frame pacing or frame skipping	Run a frame skipping test before changing overdrive

Simple test workflow

Confirm the refresh rate with a Refresh Rate Test.
Open the Monitor Ghosting Test.
Start with overdrive Off or Low.
Try Normal, Fast, and Extreme one at a time.
Stop at the highest mode that reduces the trail without halos.
Recheck the same setting in a real game or scrolling workload.

When it is not ghosting

If the object jumps forward instead of leaving a blur trail, you may be seeing dropped frames or physical frame skipping. Compare with the Frame Skipping Test and the frame skipping guide.

Helpful video

Watch Hardware Unboxed explain response time, overshoot, and ghosting:

What Are Response Times? Overshoot? Ghosting? Monitor Testing Overhaul For 2021