keyboardtest.io

Open keyboardtest.io in a modern browser and you can run a full keyboard health check without installing drivers or software — the page states all tests run locally in your browser and that it does not record key content or upload input data. Use it when a key feels unresponsive, when multiple keys pressed at once don't all register, when a switch fires twice from one press, or when you want to measure input lag for gaming. The tool covers four checks: basic function (dead keys), rollover/ghosting, chatter (double-click detection), and latency.

Step 1: Basic Function Test — Find Dead Keys

Press each physical key on your keyboard one at a time and watch the on-screen virtual keyboard.

• Expected result: the matching virtual key lights up (the page distinguishes "Untested," "Tested," and "Pressed" states, so you can see which keys you've already covered).
• If a key doesn't light up: that switch or contact is likely dead or unresponsive.
• If a key stays lit after release: it may be stuck or registering a held state.

Work through the full layout systematically — main block, function row, numpad, and modifier keys (Ctrl, Alt, Shift, Win, Menu) — so you don't skip a section.

Step 2: Rollover and Ghosting Test

Press several keys simultaneously — the page's own example is WASD + Space — and check whether every key lights up at once.

• All keys register: your keyboard handles that combination correctly.
• Some keys don't light up: you may be hitting a ghosting or key-loss limit, common on membrane and budget boards.

The tool supports both 6KRO and NKRO testing and describes real-time visual key-conflict detection. This matters most in games where you hold movement keys while triggering actions.

What NKRO and 6KRO mean

If your board fails the rollover test but you need it for gaming, that's a hardware limitation — check whether your keyboard supports NKRO (often via a switch or software setting) or consider a board that does.

Step 3: Chatter / Double-Click Detection

Mechanical switches can develop "chatter" — one physical press triggers two or more electrical signals, so a single keystroke types twice. The page describes a high-sensitivity chatter detection algorithm that identifies abnormal secondary triggers to help you judge switch life.

• Run the chatter test and press suspect keys repeatedly at normal speed.
• Expected result: one press = one registered input.
• If you see duplicate triggers: the switch is aging or worn. On hot-swappable boards you can replace the individual switch; on soldered boards it may mean a repair or replacement decision.

Chatter typically appears on the keys you use most, so test your heaviest-used keys first.

Step 4: Latency Test

The latency test measures system-to-browser input delay using event timestamps, which the page frames as useful for gamers troubleshooting input lag.

• What it measures: the time between your keypress and the browser registering the event — not the full end-to-end chain through your game or OS.
• How to read it: lower is better; compare results across configurations (different USB ports, polling rate settings, wired vs. wireless) to see what changes your response time.

Because this is a browser-side measurement, treat it as a relative comparison tool rather than an absolute hardware benchmark.

Troubleshooting: When Results Look Wrong

• Nothing registers at all: click the page first so it has focus, and confirm the browser tab is active.
• Keys register in the wrong place: check your OS keyboard layout — the virtual keyboard reflects the layout the browser reports.
• Wireless keyboard drops keys: low battery or a weak connection can mimic ghosting; retest with a fresh battery or closer receiver.
• A key works sometimes: intermittent faults often point to a worn switch or loose connection rather than a software issue.

What to Do With Your Results

• Dead key confirmed: replace the switch (if hot-swappable) or the keyboard.
• Ghosting on multi-key presses: verify whether NKRO is available and enabled; if not, upgrade if gaming depends on it.
• Chatter detected: replace the affected switch or plan a keyboard replacement.
• High latency: test alternate ports and connection types before assuming the keyboard is at fault.

Run all four tests in one session so you get a complete picture of your keyboard's health rather than diagnosing one symptom in isolation.

If you're new to Ahrefs and want to run your first SEO audit, the fastest path is: open Site Explorer, enter your target URL, review the Overview for a health snapshot, then dig into Organic Keywords, Top Pages, and Site Audit to find specific problems. From there, build a short prioritized to-do list instead of trying to fix everything at once.

This tutorial walks through that workflow using a realistic starting scenario, explains what the numbers mean, and shows how to turn findings into actions.

Before You Start: Pick a Narrow Scope

A common beginner mistake is auditing an entire large website on day one. The reports become overwhelming, and you can't tell which issues matter.

Instead, choose one of these starting points:

• A single important page (your homepage or a key product/service page)
• A small site (under ~50 pages, e.g., a personal blog or small business site)
• One section of a bigger site (e.g., /blog/)

For this tutorial, assume you're auditing a small business site with about 30 pages. The same steps scale up later.

You'll need an Ahrefs account to follow along. Ahrefs offers paid plans, and pricing and feature limits change over time, so check the current Pricing page for what's included in each tier before committing.

Step 1: Enter Your Target in Site Explorer

Site Explorer is Ahrefs' core tool for analyzing any website or URL.

1. Open Site Explorer from the top navigation.
2. In the search box, paste your domain (e.g., example.com).
3. Choose the Exact URL or Domain mode depending on scope. For a full-site view, use Domain or Prefix; for a single page, use Exact URL.
4. Press Enter.

You'll land on the Overview report. Don't try to absorb everything — focus on four numbers first.

Reading the Overview Snapshot

Important caveat: Ahrefs' traffic and keyword numbers are estimates based on its own data. They won't match Google Search Console or your analytics exactly. Treat them as directional, not absolute.

Step 2: See What You Already Rank For

Go to Organic Keywords in the left sidebar. This shows queries where your site appears in search results.

Sort by Traffic (descending) to see which pages bring the most estimated visitors. Then look for:

• Keywords ranking in positions 4–15 — these are often the easiest wins. A small content or on-page improvement can push them onto page one.
• Keywords with high volume but low position — potential opportunities if the topic is relevant.
• Irrelevant keywords — if you rank for something off-topic, it may signal thin or mismatched content.

Write down 5–10 of the position 4–15 keywords. These become your first optimization targets.

Step 3: Find Your Best and Weakest Pages

Open Top Pages. This ranks your URLs by estimated organic traffic.

Look for two things:

1. Your top performers — understand what topics and formats work. Can you create more content like this?
2. Pages with traffic but poor rankings — these may need on-page fixes (title, headings, internal links).

If a page gets zero traffic and targets a topic you care about, it's a candidate for a rewrite or consolidation.

Step 4: Run a Technical Site Audit

Now move to Site Audit. This crawls your site and flags technical and on-page issues.

1. Click Site Audit → New project.
2. Enter your domain and set crawl settings (default is usually fine for a small site).
3. Start the crawl and wait for it to finish.

Once complete, you'll see a Health Score and a list of issues grouped by category.

Which Issues to Fix First

Not all issues are equal. Prioritize in this order:

Ignore low-impact warnings (like minor meta description length) until the big items are handled.

Step 5: Turn Findings Into a To-Do List

You now have raw data. Convert it into a short, actionable list. Example:

1. Fix 3 broken links found in Site Audit.
2. Rewrite title tags on 5 pages with duplicate titles.
3. Improve 4 pages ranking in positions 6–12 by adding missing subtopics and internal links.
4. Remove or update 2 thin pages with no traffic.

Keep the list to 5–10 items max for your first audit. Finishing a short list beats starting a long one.

Common Beginner Mistakes

• Chasing every red flag. Site Audit flags many minor issues. Fix what affects rankings and users first.
• Trusting estimates as exact numbers. Ahrefs data is modeled, not measured from your analytics.
• Auditing a huge site too early. Start small to learn the interface.
• Ignoring search intent. A page can be technically perfect but still fail if it doesn't match what searchers want.
• Forgetting to re-crawl. After fixes, run Site Audit again to confirm improvements.

Where to Go Next

Once your first audit is done:

• Compare with competitors using Site Explorer's Competing Domains and Content Gap reports.
• Track keyword rankings over time with Rank Tracker.
• Explore backlink opportunities in the Backlinks and Link Intersect reports.
• Set up recurring Site Audit crawls so new issues surface automatically.

Your first audit isn't about perfection — it's about building a repeatable habit: enter a target, read the key reports, pick the highest-impact fixes, and act. Do that once a month and your site's health compounds.

Keyboard latency is the delay between pressing a physical key and that input registering in your system or browser. You can measure it with a browser-based tool that reads event timestamps, but the number you get reflects the whole chain—switch actuation, debounce, polling rate, connection type, OS/driver processing, and browser event handling—not just the keyboard. If you're troubleshooting lag, measure first, then reduce the biggest contributor; if you're diagnosing missed or doubled inputs instead, you're looking at ghosting or chatter, not latency.

What actually contributes to keyboard latency

Latency is cumulative. Each stage adds time before the keystroke reaches an application.

Polling rate is often the largest controllable factor. A 125Hz keyboard checks its state every 8ms; a 1000Hz keyboard every 1ms. That difference is measurable and matters most in fast games where a single frame of delay changes outcomes.

How to measure keyboard latency with a browser tool

Browser-based testers use high-precision event timestamps to estimate input latency without installing drivers or software. KeyboardTest.io, for example, describes "Low Latency Detection" that measures system-to-browser input latency from event timestamps, and states all tests run locally in the browser with no key content recorded or uploaded.

A practical measurement flow:

1. Open the latency test in a modern browser on the machine you actually use.
2. Press keys repeatedly and watch the reported latency values. Expect variation between presses—single readings are noise, not signal.
3. Compare conditions, not absolutes: test wired vs. wireless, 125Hz vs. 1000Hz, or before vs. after a firmware update, and look at the trend.
4. Repeat enough times to see a stable range rather than one number.

What the numbers realistically mean

• Treat the reading as system-to-browser latency, not pure keyboard latency. It includes OS and browser handling, so it will be higher than a lab measurement of the keyboard alone.
• Use it for relative comparison. If switching from wireless to wired drops your readings consistently, that's a real signal.
• Don't chase a single millisecond. Human perception and game frame times usually dominate once you're in the low single-digit millisecond range.

How to reduce keyboard latency

Work from the largest contributor down:

• Raise the polling rate to 1000Hz if your keyboard and connection support it.
• Use wired USB, or a low-latency wireless mode if your board offers one. Avoid congested 2.4GHz environments.
• Disable input filtering or smoothing in keyboard software if it's enabled—these add processing delay.
• Update firmware, since debounce and polling behavior are set there.
• Reduce system load during testing so OS and browser scheduling don't inflate readings.

Latency vs. chatter vs. ghosting: diagnose the right problem

These are different faults with different tests. Measuring latency won't fix a chatter or ghosting issue.

• Latency — input arrives, just later than you want. Test with a latency/timestamp tool.
• Chatter / double-click — one press registers as two. KeyboardTest.io describes a high-sensitivity chatter detection algorithm that identifies abnormal secondary triggers to help judge switch life.
• Ghosting / rollover — some keys don't register when several are pressed at once. The same site offers an N-Key Rollover (NKRO) test with real-time key-conflict detection supporting 6KRO and NKRO, so you can check for ghosting or key loss under complex input.

If keys are missing during multi-key presses, run the rollover test. If single keys fire twice, run the chatter test. If everything registers but feels slow, measure latency.

Quick decision guide

• "My inputs feel delayed." Measure latency, then raise polling rate and switch to wired/low-latency connection.
• "A key sometimes doesn't register." Run the basic function test and rollover test for dead switches or ghosting.
• "One press types two characters." Run the chatter test; this points to switch wear, not latency.
• "I want a before/after number." Test the same way under both conditions and compare ranges, not single readings.

Open keyboardtest.io in a modern browser and press each physical key while watching the on-screen layout. That single pass tells you whether any key is dead or unresponsive. From there, the same page lets you check multi-key rollover (ghosting), switch chatter (double-clicking), and input latency — no drivers or software installation required, and all testing runs locally in your browser.

Before You Start

• Use a Chromium-based browser or a current Firefox/Safari build so the high-precision timing APIs the tool relies on are available.
• Close apps that grab global hotkeys (screen recorders, macro utilities, game overlays) so they don't swallow your keypresses before the page sees them.
• If you're testing a laptop, decide whether you want the built-in keyboard or an external one — test only one at a time.

Step 1: Basic Function Test (Dead Keys)

1. Look at the virtual keyboard on the page. Every key starts in an "Untested" state.
2. Press each physical key once, one at a time.
3. Watch the corresponding on-screen key. It should change to "Tested," and flash "Pressed" while you hold it.

Expected result: every key you press lights up and stays marked as tested.

If a key doesn't light up:

• Try it a second time — a single missed press can be a timing fluke.
• Test the same key on another device or with another keyboard to confirm whether the fault is the switch or the connection.
• On a mechanical board, a key that never registers usually means a failing switch or a broken trace; on a membrane board it often points to worn contact pads.

Step 2: Rollover and Ghosting Test (NKRO)

N-Key Rollover means the keyboard registers every key you press simultaneously. Cheaper or older keyboards may only handle 6KRO, and some drop keys entirely under complex input — that's ghosting.

1. Press and hold a realistic gaming cluster, e.g. W + A + S + D + Space.
2. Add more keys (Shift, Ctrl, another letter) while holding the first set.
3. Watch which keys light up on the virtual board.

Expected result: all held keys stay lit at once. The page supports both 6KRO and NKRO testing.

If some keys don't light up: your keyboard is hitting its rollover limit or blocking combinations. This matters most for games that need many simultaneous inputs; for typing it rarely causes problems.

Step 3: Chatter / Double-Click Detection

Chatter is when a single physical press registers as two or more inputs — a common sign of an aging or dirty switch.

1. Open the Chatter Test.
2. Type normally on the keys you suspect (often the most-used letters or your spacebar).
3. Let the high-sensitivity detection algorithm flag any abnormal secondary triggers.

Expected result: one press = one registered input.

If the tool flags repeated triggers: the switch is double-clicking. On a mechanical keyboard this usually means the switch is near end of life or needs cleaning/resoldering; on a hot-swap board you can simply replace the switch.

Step 4: Input Latency Test

Latency here measures the delay from the system event to the browser, based on event timestamps — useful if you're chasing input lag for gaming.

1. Open the Latency Test.
2. Press keys repeatedly as instructed and read the reported latency figures.

Expected result: consistent, low numbers with little variation. Large or erratic spikes suggest something in the chain — USB polling, background load, or the browser — is adding delay.

Note that this measures system-to-browser latency, not the full end-to-end latency of a game. Use it to compare configurations (different ports, polling settings, background apps) rather than as an absolute figure.

What the Specs Mean

Troubleshooting

• Nothing lights up at all: click inside the page first so it has focus, then check the browser isn't blocking the page.
• A key works elsewhere but not here: another app may be capturing that key as a shortcut.
• Inconsistent results: retest with background apps closed; timing APIs are sensitive to system load.
• Privacy: all tests run locally in your browser — the tool states it does not record your key content or upload input data.

Run the four steps in order — function, rollover, chatter, latency — and you'll have a complete picture of whether your keyboard has dead keys, ghosting, switch chatter, or lag before you decide to repair or replace it.

Polling rate is how many times per second your keyboard reports its key states to the computer, measured in Hz. A 1000Hz keyboard sends a report every 1ms; a 125Hz keyboard sends one every 8ms. Higher polling rate reduces the maximum delay between a keypress and the computer receiving it, but it does not eliminate input latency on its own — the total delay also includes switch debounce, firmware processing, USB transfer, OS handling, and display refresh. If you are troubleshooting lag, test polling rate alongside latency, rollover, and chatter rather than treating it as the single cause.

Polling rate vs. input latency: what actually changes

Polling rate sets the interval at which reports are sent. Latency is the total time from physical actuation to the effect appearing on screen.

The key word is worst-case. If a keypress lands just after a report is sent, it waits nearly a full interval before the next one. At 1000Hz that wait is at most 1ms; at 125Hz it can be 8ms. That 7ms difference is real but small compared with other links in the chain — a 60Hz monitor alone adds up to ~16.7ms between frames, and switch debounce commonly adds several milliseconds.

So a higher polling rate shrinks one component of latency. It does not make a slow keyboard fast if the bottleneck is elsewhere.

Polling rate is not the same as NKRO or ghosting

These three terms get mixed up constantly, and they describe different things:

• Polling rate — how often the keyboard reports to the host. A timing/spec number in Hz.
• NKRO (N-Key Rollover) — how many keys the keyboard can register simultaneously without dropping any. A 6KRO board may fail when you hold many keys at once; an NKRO board registers them all.
• Ghosting — phantom or missing key registrations caused by the keyboard's matrix wiring when multiple keys are pressed together. It is a correctness problem, not a timing one.

A keyboard can have 1000Hz polling and still ghost. It can have full NKRO and only 125Hz polling. When you test, check them separately: press keys one at a time for dead switches, press combinations (e.g. WASD + Space) for rollover and ghosting, and use a latency or polling measurement for timing.

How to check polling rate and latency with an online tester

KeyboardTest.io runs in the browser with no drivers or software, and states that all tests are performed locally — key content is not recorded or uploaded. Its suite covers rollover (NKRO), input latency, polling rate, and chatter detection.

A practical sequence:

1. Basic function test — press each physical key and confirm the matching on-screen key lights up. This catches dead switches and unresponsive keys.
2. Rollover detection — hold several keys at once (e.g. WASD + Space). If some keys don't light up, the board may have ghosting or a rollover limit.
3. Latency / polling measurement — use the latency test to evaluate input response speed. The tool measures system-to-browser input latency from event timestamps, which is the practical number that matters for gaming.
4. Chatter test — if a single press registers twice, the switch may be aging. The chatter detection flags abnormal secondary triggers.

Expected result: a healthy keyboard lights every key, registers all simultaneous presses you make, and shows stable timing without double-triggers. If a key fails to light, that points to hardware; if timing is erratic, that points to polling, firmware, or a busy system.

Does a higher polling rate actually help gaming?

Sometimes, and less than marketing suggests.

• Where it helps: competitive play where every millisecond of input delay compounds with reaction time, and on high-refresh displays (144Hz+) where frame times are short enough that a 1ms vs. 8ms reporting gap is a meaningful fraction of a frame.
• Where it doesn't: if your monitor is 60Hz, your total latency is dominated by frame pacing, and going from 1000Hz to 8000Hz changes almost nothing perceptible. CPU load also rises with very high polling rates, which can increase latency if the system is already busy.
• Diminishing returns: the jump from 125Hz to 1000Hz is the big one (8ms → 1ms worst case). Beyond 1000Hz the gains shrink fast and depend on the rest of your chain.

A reasonable rule: 1000Hz is plenty for most users. Consider higher only if you have a high-refresh monitor, a fast CPU, and you're chasing the last fraction of a millisecond in competitive titles. If your current board already polls at 1000Hz, upgrading for polling rate alone is rarely worth it — check latency, chatter, and rollover first, since those often cause more noticeable problems.