ControllerTest.io

Controller Latency Test

Not connected
Press a button to connect
Last 10 presses 0 / 20
Press Measured
— Press any button to add a row —
— —
— —
— —
— —
— —
— —
— —
— —
— —
Browser gets the input
Possible wait Page read To screen Not measured One tick = —

Latency breakdown

Not tested
Browser-side latency0 / 20 presses
≈—ms
Median of 20. Excludes controller and display
Report waitUp to one intervalNeeds WebHID
Browser readAbout every 4 ms≤4 ms
Page readUntil the next frame—
To screenOne frame—
Refresh rate—
Interval—
Stalls—
Start with the longest stage

How to test

About 30 s
01
ConnectUse a cable, Bluetooth or a 2.4 GHz receiver.
02
Time reportsOptional. Adds the report wait with WebHID.
03
Press 20 timesPress and release, one button at a time.
04
Check resultsStart with the highlighted stage.

TipRelease each button before the next press. Holding a button counts as one press.

Where a press spends its time

6 stages

This controller input lag test splits a press into six stages, from button to screen. The page measures the middle two, estimates the two before them from their longest possible time, and can't see inside the controller or the display. The bars share one 0–20 ms scale.

StageTypicalDepends onThis page
In controller Varies Scan and debounce, set by firmware Not measured
Report wait 0–8 ms Polling rate: up to 1 ms at 1000 Hz, 8 ms at 125 Hz WebHID estimate
Browser read 0–4 ms Chrome and Edge read about every 4 ms Estimated
Page read 0–1 frame Until the next frame; longer when busy Measured
To screen 1 frame Refresh rate: 16.7 ms at 60 Hz, 6.9 ms at 144 Hz Measured
Display Varies Lower in game mode Not measured
RangeMeasuredOne frameNot measuredTicks: a 144 Hz frame, a 1000 Hz report

Refresh rate vs polling rate

Average wait

To reduce controller input lag, raise the screen's refresh rate before the polling rate. On average a press waits half a report interval for the controller but about 1.5 frames for the screen, so the screen costs more.

Polling rateHalf a report interval on average
125 Hz4 ms
250 Hz2 ms
500 Hz1 ms
1000 Hz0.5 ms
Refresh rateAbout 1.5 frames: half a frame to be read, one to show
60 Hz25 ms
120 Hz12.5 ms
144 Hz10.4 ms
240 Hz6.3 ms
Saved by 60 → 144 Hz≈ 14.7 ms
Saved by 125 → 1000 Hz≈ 3.5 ms
Games addA few queued frames

When the result looks wrong

5 cases
ProblemIn the testLikely causeFix
Many stallsBusy programs, power saving or a background tabClose programs and plug in the laptop
Slow page readOther tabs, video or animationClose other tabs and videos
Low refresh rateLower rate selected, a cable or port limit, or another screenSelect the highest rate; use DisplayPort or HDMI 2.0+
No report waitFirefox, Safari, or an Xbox controller on WindowsIn Chrome or Edge, press Time reports
Long report waitBluetooth, or a low polling rate settingUse a cable or raise the rate in the appPolling rate test
The line marks when the browser gets the inputTest again after each change

Measure full input lag

Slow motion

A page can't see inside the controller or display, so the full delay takes slow motion. At 240 fps a frame is 4.17 ms: if the button goes down in frame 1 and the screen changes in frame 4, that's 3 frames, or about 12.5 ms.

Record

Film the controller and screen together at 240 fps

Find two frames

Where the button goes down and where the screen changes

Count

Multiply the frames by 4.17 ms. Repeat and take the median

Watch for a new row in the test above: that's the screen change

Frequently asked questions

11 questions

What is normal controller input lag?

Depends on refresh rate

This controller latency test measures the browser side, from report to screen, and most of that is waiting for the next frame and showing it. It usually comes to about 25–30 ms at 60 Hz and 12–15 ms at 144 Hz. If yours is higher, start with the highlighted stage in the breakdown.

How accurate is a web gamepad latency test?

Partly measured

Page read and To screen are measured directly. For Report wait and Browser read, the page knows the maximum and uses the average. Time inside the controller and the display isn't included; for the full delay, film in slow motion.

Why is the report wait missing for an Xbox controller?

No WebHID

On Windows, Microsoft's Xbox controllers use their own driver and aren't HID devices, so they don't appear in the WebHID list. The page can't time their reports, so the report wait is hatched and left out of the result.

Is Bluetooth slower than wired?

Compare the interval

The connection matters mostly through the report interval: on average a press waits half of it. With WebHID, run one round wired and one over Bluetooth, then compare the Interval cell. WebHID works with PS5 and PS4 controllers. Compare connections in the polling rate test →

Does a higher refresh rate reduce input lag?

Yes, more than polling rate

Going from 60 Hz to 144 Hz cuts a frame from 16.7 ms to 6.9 ms. At about 1.5 frames on average, that saves about 14.7 ms. Raising the polling rate from 125 Hz to 1000 Hz saves about 3.5 ms.

What is the difference between polling rate and latency?

How often vs how long

Polling rate is how often the controller sends a report, in Hz. Latency is how long a press takes to reach the screen, in ms. Polling rate sets only one part of it: a press waits up to 1 ms at 1000 Hz and up to 8 ms at 125 Hz.

Is a higher polling rate always better?

Gains shrink

On average a press waits half a report interval: 4 ms at 125 Hz, 0.5 ms at 1000 Hz. Above 1000 Hz each step saves a fraction of a millisecond, which is small next to one frame.

Is this the same as input delay in games?

Games add more

Games add their own render queue, V-Sync and frame generation, which can add several frames. This page draws one simple frame, so it shows the lowest input delay on the browser side. Use it to compare controllers, connections and screen settings.

Why 20 presses?

For a steady median

Each press lands at a different point between two frames, so a single reading jumps between zero and one frame. The median of 20 is steadier. A press during a page stall over 100 ms still gets a row, marked Stall, but isn't counted.

How do I measure the full input lag?

Film in slow motion

Film the controller and screen at 240 fps. Count the frames from the button going down to the screen changing, and multiply by 4.17 ms. A new row appearing in the test is an easy screen change to spot.

Is any data uploaded?

No

Press times are worked out in the browser. Each round is kept on this page only and cleared when you refresh or close it. Privacy policy →