Input Latency Test - Measure Your Click Response and System Delay
Click anywhere to start. The Event Timing API splits your click into input delay, JS execution, and render paint, plus jitter and frame loss at 60-240Hz.
What Is Input Latency and Why Does It Matter?
Input latency is a real, measurable phenomenon, but it is widely misunderstood. Here is what it actually is and what it is not.
The Plain Definition
Input latency is the total delay between you performing a physical action, such as pressing a mouse button, moving a joystick, or pressing a key, and your system registering and acting on that input. It is always measured in milliseconds. It is never zero; physics and electronics guarantee that. The goal in high-performance setups is not to eliminate it entirely but to reduce and stabilize it to the point where it stops being a limiting factor.
It Is a Chain, Not a Single Number
Every stage of your setup contributes: your mouse polling rate, USB transmission, OS processing, application tick rate, GPU render time, and monitor display delay all add latency. No single hardware upgrade eliminates the problem. Reducing your total system latency means identifying which part of your chain is the biggest contributor and addressing that first. Often the answer is the monitor refresh rate or GPU frame rate, not the mouse.
What This Browser Test Measures
A browser-based tool cannot measure your hardware-level or game-engine latency. What it measures is your response time to a visual signal, specifically how quickly you click after you see the green zone appear. This combines your biological reaction time with the browser's own event scheduling delay. The result is most useful as a relative benchmark: compare your score before and after changing a setting, not as an absolute hardware measurement.
Why It Matters for Gaming
In competitive games like CS2, Valorant, and Apex Legends, the gap between seeing an opponent and your shot registering can be as short as a single frame at 240 Hz, which is about 4.17ms (or under 2ms at 540 Hz). If your total system latency is 50ms versus 25ms, the 25ms setup effectively gives you slightly more time to react before the opponent can respond to your action. At the professional level, players optimize every component of this chain. At the amateur level, monitor refresh rate and game frame rate matter far more than mouse polling rate.
Reaction Time vs System Latency: The Distinction That Matters
Most browser tests, including this one, are dominated by your biological reaction time, not your system latency. The average visual reaction time for humans is around 200 to 250ms. System hardware latency typically contributes only 5 to 30ms of that total. This means that for most people, training your reaction time will improve your results far more than upgrading hardware. Hardware optimization only becomes impactful when your biological speed has reached its ceiling.
What Jitter Tells You
Jitter, the variation between your fastest and slowest responses, is often more meaningful than your average. A player averaging 180ms with 10ms jitter is more predictably responsive than one averaging 170ms with 40ms jitter. High jitter in a consistent test environment points to system-level inconsistencies, such as background processes, CPU scheduling interruptions, thermal throttling, or browser tab load. Reducing jitter is as important as reducing average latency for competitive gaming.
What Does Your Response Time Result Mean?
These benchmarks apply to the Frame-Perfect reaction test, where your result includes both biological reaction time and system processing delay. The Clicks Monitor badge above uses a separate, narrower scale based on browser event timing alone.
| Average Response Time | Level | What It Reflects | Context |
|---|---|---|---|
| Under 150ms | Elite | Exceptional reflex speed; near the biological lower limit for visual response | Typical of competitive esports players who practice reaction drills regularly |
| 150-200ms | Fast | Above-average human response; consistent gaming practice reflected | Solid for competitive gaming on optimized setups; better than most opponents |
| 200-250ms | Average | Normal human visual reaction range; no issues with reflexes or system | Comfortable for most gaming and everyday use; no hardware concern |
| 250-350ms | Slower | Slightly above average; may be fatigue, distraction, or a slower system | Worth checking system load and monitor settings; close heavy background apps |
| Over 350ms | Investigate | Consistently high results suggest system issues, fatigue, or high jitter | Check background CPU usage, power-saving modes, and browser performance |
Under 150ms
Elite150-200ms
Fast200-250ms
Average250-350ms
SlowerOver 350ms
InvestigateImportant: scores improve naturally across multiple sessions of a single day as your nervous system warms up. First-session scores are typically 15-25ms higher than peak-session scores. Always average across at least two separate sessions before drawing conclusions about your hardware or settings.
Every Stage That Adds Latency Between Click and Screen
Understanding the complete chain of delays helps you identify where your biggest opportunity for improvement actually is.
The honest takeaway:The two highlighted stages, mouse polling and monitor display, are where hardware upgrades have the clearest measurable impact. However, the biggest source of delay for most people is the game engine tick rate, which is directly tied to frame rate. Doubling your frame rate from 60fps to 120fps cuts game-engine latency from ~16ms to ~8ms, a larger improvement than going from 125Hz to 1000Hz mouse polling. This is why monitor refresh rate and GPU performance matter more than polling rate for most players.
Practical Ways to Lower Your System Latency
Ordered from most to least impactful. Start at the top, the largest gains come from the first few steps, not the last.
Raise Your Frame Rate
This is the single most impactful thing most people can do. At 60fps, your game engine processes inputs every ~16ms. At 240fps, that drops to ~4ms. The engine latency reduction from 60fps to 240fps is larger than upgrading your mouse from 125Hz to 1000Hz. Reduce visual quality settings to prioritize frame rate over graphical fidelity if you play competitively.
Use a High-Refresh Monitor
A 240Hz monitor displays a new frame every 4.17ms. A 60Hz monitor displays one every 16.67ms. Even if your GPU delivers frames faster than 60fps, a 60Hz monitor introduces additional latency because it only shows updates 60 times per second. Higher refresh rate also reduces display processing delay on most panels. This upgrade delivers a visible, felt difference in responsiveness for most gaming setups.
Disable V-Sync, Enable G-Sync or FreeSync
Traditional V-Sync synchronizes frames with your monitor's refresh cycle, which adds a full frame of latency (16ms at 60Hz) as a buffer. G-Sync and FreeSync achieve smooth frame delivery without that buffer, eliminating the added latency while preventing screen tearing. If adaptive sync is not available, capping your frame rate 3-5fps below your monitor's maximum often achieves low latency without tearing.
Enable Game Mode and High-Performance Power Plan
Windows Game Mode allocates more CPU and GPU resources to the foreground game and reduces background process interference. Setting your power plan to High Performance (or Ultimate Performance on Windows 11) prevents the CPU from throttling clock speeds, which eliminates a source of variable latency under load. Both settings together typically reduce jitter noticeably in browser-based latency tests.
Close Background Applications
Applications running in the background consume CPU scheduler cycles that would otherwise be available for input processing. Antivirus scans, browser sync operations, cloud backup services, and video conferencing apps that idle in the system tray all contribute to the CPU scheduling jitter that shows up in this test. Closing them before gaming reduces jitter even if it doesn't meaningfully change your average latency.
Set Mouse Polling Rate to 1000Hz
If your mouse ships at 500Hz by default, switching to 1000Hz in your companion software cuts maximum polling delay from 2ms to 1ms. This is real but modest. Check your current rate with the polling rate checker. Going above 1000Hz (to 4000Hz or 8000Hz) produces diminishing returns and adds CPU overhead, for most setups 1000Hz is the practical optimum.
What This Test Can Tell You and What It Can't
Being clear about limitations makes the results more useful, not less. Here is exactly where this tool is valuable and where its boundaries are.
What This Test Is Good For
- Comparing your response time before and after a setting change
- Identifying high jitter that points to system level interference
- Tracking whether your reaction speed improves through practice over weeks
- Checking whether a different browser or tab produces better results
- Giving a general benchmark of your combined reaction and system speed
- Identifying when fatigue is affecting your response time noticeably
What This Test Cannot Measure
- Raw hardware latency, which requires oscilloscope level tools
- Click to photon latency, which needs NVIDIA LDAT or equivalent diagnostic hardware
- Mouse USB polling delay in isolation from your reaction time
- Game engine or render pipeline latency
- Network latency to a game server (ping times)
- Display response time independent of your reaction speed
Getting an Accurate and Useful Result
The way you approach the test affects what it tells you. These habits give you data you can actually act on.
Collect Enough Samples
The Clicks Monitor records latency for every action continuously without limits. We recommend performing 10 to 20 rapid clicks to collect enough data samples for a stable average and a clear jitter distribution histogram.
Click When Green, Not Before
For the Frame-Perfect reaction test, clicking before the screen turns green is ignored and won't register a result. The random delay (1 to 3 seconds) prevents anticipation timing, forcing a true reaction response rather than predictive timing.
Keep Conditions Consistent Between Sessions
For meaningful comparisons, run the test at the same time of day, with the same number of background applications open, and from the same device and browser. Response time varies with alertness, caffeine, fatigue, and system load. Changing two variables at once makes it impossible to know which one caused the difference in your score.
Read Jitter, Not Just Average
Your jitter score shows how consistent your responses were. A jitter above 30ms in a controlled test suggests something is interrupting your system's input processing, often background tasks, power-saving modes, or thermal throttling. Identifying and reducing jitter can improve your gaming feel more noticeably than reducing average latency by the same amount.
Use It for Before/After Comparisons
The test's best use is comparing your score before and after a specific change: switching browsers, enabling Game Mode in Windows, updating mouse firmware, changing polling rate, checking switches for double clicks with a double click test, or disabling background applications. Run a full session, make your change, run another, compare the averages and jitter values. This is more informative than any single absolute reading.
Understand Your Floor
Human visual reaction time has a biological floor around 100 to 120ms that no hardware upgrade can break through. If your best trial is consistently below 150ms, your hardware and setup are not your limiting factor, your reaction speed is. You can test your speed on a reaction time test, or practice cursor precision in a 3D aim trainer rather than tweaking hardware.
Frequently Asked Questions
Clear, honest answers to what people actually ask about input latency, response time, and how to improve both.
The tool provides two modes. The Clicks Monitor measures the pure browser latency chain, estimating input transmission, event loop queuing, JS execution, and composition paint delay in isolation. The Frame-Perfect Test measures your combined visual reaction speed (biology) plus system event processing latency. It does not measure raw hardware latency, game-engine latency, or USB polling delay in isolation. Think of it as a relative benchmark: the same number measured twice under the same conditions is directly comparable.
Since this test combines your reaction time with system delay, the benchmarks differ from pure hardware latency numbers. For this reaction-time style test, a consistent average under 200ms is solid for most gamers, and under 150ms reflects either excellent reflexes or very practiced reaction training. For pure hardware latency, which is the kind measured by tools like NVIDIA LDAT, competitive players in 2026 typically aim for a total system latency below 25ms from click to photon, with sub-10ms considered elite. These are completely different scales because one includes your biology and the other does not.
Biological variability is the main reason. Your nervous system's speed changes throughout the day based on alertness, caffeine intake, fatigue, and focus level. Most people respond fastest in the early-to-mid afternoon when core body temperature peaks, and slowest in the early morning or when tired. System-level factors, such as background CPU load, browser cache state, and power mode, also contribute, but biological variability typically accounts for a larger portion of the day-to-day difference than hardware variation does.
Input lag in games accumulates across your entire hardware and software chain. Your mouse polling rate determines how quickly the click is sent to the OS (1ms at 1000Hz, 8ms at 125Hz). The OS then dispatches the event to the game. The game engine processes it on the next tick: if you are running at 60fps, that can be up to 16.7ms away from when the event arrived. The GPU then renders the frame reflecting that input, which takes additional time depending on GPU load. Finally, the monitor introduces display delay, typically less than 1ms on modern OLED panels and up to 20ms on slower displays. The total of all these stages is your click-to-photon latency, and a typical gaming PC setup in 2026 runs somewhere between 15ms and 60ms depending on hardware quality and configurations.
Yes, but modestly compared to other factors. A gaming mouse at 1000Hz polling rate produces a maximum polling delay of 1ms, compared to 8ms at 125Hz, representing a real difference of 3.5ms on average. Optical switches (found on some gaming mice) eliminate mechanical debounce delay, saving another 1-4ms compared to standard mechanical switches. Together, a high-end gaming mouse might realistically save 4-8ms over a basic office mouse. That is meaningful at the professional level but generally far less impactful than upgrading monitor refresh rate or improving GPU frame rate.
Jitter in this test refers to the inconsistency between individual trial responses (the difference between your fastest and slowest measured times). Some jitter is always present because biological reaction time is not perfectly consistent. However, if your jitter is above 30-40ms in a controlled environment, system-level factors are likely contributing: background processes consuming CPU scheduler time, thermal throttling reducing your CPU's speed mid-session, or power-saving modes introducing variable delays. Testing with minimal background applications and your power plan set to High Performance typically reduces jitter noticeably. If you want to practice your clicking speed under different techniques, check out our Jitter Click Test or the Kohi click test.
Yes, meaningfully, but with realistic expectations. Regular reaction time training using tools like our Reaction Time Test or our 3D Aim Trainer can improve your visual response by 15-30ms over several weeks of consistent daily practice. This improvement comes from your brain becoming more efficient at the specific perceptual and motor sequence involved: detect signal, decide to act, and initiate movement. Improvement plateaus around your biological floor (roughly 100-120ms for most adults with optimal conditions) and cannot be pushed further through training alone. Younger people generally have faster reaction floors than older adults, and this is a physiological fact that no training overrides.
Click-to-photon latency is the total time from a physical button press to the moment that action is visually represented on screen, going from your finger to the photons hitting your eyes. It is measured by hardware tools like NVIDIA LDAT using a light sensor pointed at the monitor and a trigger mechanism that physically presses a button. This measurement is completely independent of your biological reaction time. A typical gaming PC in 2026 shows 20-60ms click-to-photon latency. This test, by contrast, includes your reaction time in the measurement and produces results in the 150-300ms range for most people. The two measurements are apples and oranges, useful for completely different purposes.
Yes, the test registers tap events the same way it registers mouse clicks. However, mobile results tend to show higher latency than desktop results for a few reasons: touchscreen digitizer sampling rates are typically lower than mouse polling rates, mobile browsers apply additional touch event processing, and the tap-to-register pipeline on mobile is generally slower than on a wired desktop mouse. Use mobile results for mobile-to-mobile comparisons, not for comparing your phone against your gaming PC setup.
Yes, fully free, with no account, no sign-up, and no features behind a paywall. All trials run in your browser and no data is sent anywhere.