EN
TestYourSetup / Monitor / Input lag test

Input lag test

A latency test for the whole chain, from your finger to the screen. Click or press a key and the box flashes white at once. Film it with your phone in slow motion, count the frames from your finger to the flash, and the calculator turns that into milliseconds.

Frame 0
0.0ms

Click, tap or press any key here

No press yet

Works withMouse buttons, keys, touch and controller buttons

Using a controller? Press any button once so the browser can see it.

1. Film it Check

  1. Set your phone to slow motion at 240 fps or faster. Turn the screen brightness up and the room lights on.
  2. Frame the mouse button (or key, or controller button) and the box in one shot, close together.
  3. Start recording, click in the box about 10 times with a second between clicks, then stop.
  4. Step through the video frame by frame. For each click, count the frames from the first frame where the button is fully down to the first frame where the box is white.

2. Turn frames into milliseconds Check

Total input lag-Enter your frame counts
Range-One video frame is 4.17 ms

Enter one count, or several separated by spaces to get the average. The result is your own count turned into time, so it is as good as the video and the counting.

3. What the browser itself sees Estimated

Click or press a key in the box to see what the browser itself sees.

Event to next frame-median, ms, browser side only
Last press-ms, browser side only
Presses0mouse, touch and keys
Refresh rate Measured-from frame timing
Timer step-ms, browser clock

From the time stamp the browser puts on your click to the start of the next animation frame, the first chance to draw the flash. It leaves out everything before the stamp and everything after the frame starts, so it is only a small slice of your input lag. Controller presses are polled once per frame and are not timed here.

Where input lag comes from

  1. Mouse or keyboardSwitch travel, debounce and the device's own processing. From about 1 ms on fast gaming mice to well over 10 ms on some office devices.Camera only
  2. USB polling or wirelessThe device waits for the next poll: up to 8 ms at 125 Hz, 1 ms at 1000 Hz. Bluetooth often adds more. See the polling rate test.Camera only
  3. Operating systemDrivers pass the input on. Usually well under 1 ms.Camera only
  4. Browser or gameThe app handles the input and waits for the next frame. The browser part is shown above.Estimated
  5. Rendering and display processingThe frame is drawn, composed and sent; the monitor scales and processes it. One or more frames, plus tens of ms on a TV outside game mode.Camera only
  6. Pixel responseThe pixels change from dark to bright. A few ms on most gaming monitors.Camera only

Ranges are rough, from public measurements, not a result for your devices. The camera method measures all six parts together.

No permissions needed. Everything runs in your browser and nothing is uploaded.

Why this input lag test uses your camera

Input lag is the time from your finger pressing a button to the result appearing on the screen, sometimes called click to photon latency. Most of it happens where a web page cannot look: inside the mouse, on the USB link, in the graphics driver and inside the monitor. A browser only knows when it received the click and when it started a frame. Any website that prints a full mouse latency or monitor input lag figure from the page alone is guessing.

A camera sees the whole chain. Phones can film at 240 frames per second, which is one picture every 4.2 ms. Put the mouse and the screen in the same shot, click, and count the video frames between the button going down and the box turning white. The flash is triggered in the same moment the browser hands the click to this page, with no animation, so the only delays left are the real ones.

How to get a clean result

  • Click at least 10 times and average the counts. Single clicks vary by a frame or two, and the average is far more reliable than any one count.
  • Count from the same moment every time. The first frame where the button is fully pressed is easiest to see; mark it the same way for every click.
  • Keep the box near the top of the screen if your monitor draws from top to bottom. The lower part of the screen updates a little later in every frame.
  • Use the frame counter and the strip of 8 cells in the box to check the video: each refresh lights the next cell, so you can see how many screen refreshes your count covers.
  • The millisecond counter also helps: read it in the video at the press and at the flash, and the difference is roughly the delay, to within one screen refresh.
  • Check the real frame rate of your video in its file details. Some phones label clips as slow motion but record at a lower rate.

Mouse latency test, keyboard and controller input lag

For a mouse latency test, film the mouse button. For a keyboard input lag test, click the box once so it has focus, then film a key; any key flashes it. For a controller input lag test, press a controller button once so the browser can see the controller, then film the button. Keep the computer, browser and monitor the same and only swap the device, and the difference between the averages is the difference between the devices. Browsers read controllers about once per frame, so a controller result here includes up to one extra frame compared with a game that polls it faster.

For the parts a browser can time on its own, use the keyboard latency test, the mouse polling rate test and the keyboard polling rate test.

Monitor input lag

To compare monitors or TVs, keep the mouse and computer the same and only change the screen. Turn on game mode, low latency mode or the PC input setting first: picture processing on many TVs adds a lot of delay. Higher refresh rates help twice, because each frame is shorter and the screen shows new frames sooner. Check the rate you are really running with the refresh rate test, and motion clarity with the UFO test.

Remember that a browser is not a game. It usually adds a frame or more of its own on top of the screen, so a click to flash result here is a fair comparison between setups, not the exact delay you get in a competitive game.

How to reduce input lag

  1. Turn on game mode or the monitor's low latency setting, and turn off extra picture processing such as motion smoothing.
  2. Turn V-Sync off in fast games, or use variable refresh rate with a frame cap a few fps below the refresh rate. Low latency modes in the graphics driver or the game help too.
  3. Use a cable or a 2.4 GHz receiver rather than Bluetooth, and set the polling rate to 1000 Hz.
  4. Use a high refresh rate and make sure it is really on. A 144 Hz screen shows each new frame up to 10 ms sooner than a 60 Hz one.
  5. Keep the frame rate high: lower graphics settings that limit the frame rate, and close heavy background apps.

Audio latency

This page is about the delay between input and picture. For the delay of sound, such as Bluetooth headphones lagging behind video, use the audio latency test.

Questions

How do I test input lag?

Film your mouse and this page together with your phone in slow motion, at 240 fps or faster. Click inside the dark box, which turns white on the click. In the video, count the frames from the moment the button goes down to the first frame where the box is white, and enter that count in the calculator. Repeat about 10 times and use the average.

Can a website measure input lag?

Not the whole delay. The mouse, USB polling and operating system act before the browser sees the click, and the graphics card and monitor act after the page draws it. A browser can only time its own part, which this page shows as browser side only. The full click to screen delay needs a camera or a hardware tester.

How do I test mouse click latency?

Use the camera method on this page with the mouse button in view. Use the same camera, frame rate and monitor for every mouse you compare, and average 10 or more clicks, since a single click can vary by a few milliseconds. The difference between two mice is their difference in click latency.

Is 240 fps slow motion good enough for an input lag test?

Yes for most uses. At 240 fps each video frame is 4.2 ms, so a single count is accurate to about 4 ms and an average of 10 counts is better. 960 fps gives about 1 ms steps. Normal 30 or 60 fps video is too coarse. Some phones record slow motion at a lower real rate, so check the frame rate in the video file details.

How do I test controller input lag on PC?

Connect the controller, press a button once so the browser can see it, then film the button and the screen together. The box flashes on any controller button. Browsers read controllers about once per frame, so the result includes up to one extra frame compared with a game that reads the controller more often.

How do I test monitor input lag?

The camera method measures the whole chain, so test the monitor by changing only the monitor: keep the same mouse, computer and browser, film both screens and compare the averages. Turn on game mode or low latency mode first, since picture processing on TVs and some monitors can add tens of milliseconds.

Does V-Sync add input lag?

Usually yes. Classic V-Sync makes the game wait for the screen, which can add one or more frames of delay, more when the frame rate is capped by the refresh rate. Turning it off, or using variable refresh rate with a frame cap a few fps below your refresh rate, keeps delay lower.

Is a Bluetooth mouse or keyboard slower than a cable?

Often, yes. Bluetooth links commonly poll less often than USB, which adds a few milliseconds and some variation. A cable or a 2.4 GHz receiver at a 1000 Hz polling rate is the low latency choice. You can see the difference with this test if you average enough clicks.

Why is the browser side number so much lower than my camera result?

The browser side number only covers the time from the browser stamping your click to the next frame starting. The mouse, the USB link, the compositor, the monitor and the pixels changing all come on top, and those parts are usually most of the total.

More tests