Controller Latency Database

How to use it

1. Find your controller in the table. Use the filters to choose USB, Bluetooth or wireless dongle.
2. Compare average latency and polling rate with other models.
3. To add your own result, run the Input Lag Test and Polling Rate Test, then press Submit to database and choose your controller model.

What your results mean

What the columns mean:

Column Meaning

Polling rate (Hz) How often the controller reports its state each second. Higher is better.

Average latency (ms) Average time between reports, measured in the browser. Lower is better.

Jitter (ms) How much that timing varies. Lower is more consistent.

Tests How many results the average is based on. Models need at least 20 to be listed.

How we keep the data reliable

Rule Why

A model appears only after 20+ submissions One unusual test can't skew the result

Extreme outliers are removed Filters out broken setups and mistaken submissions

Results split by connection type USB, Bluetooth and dongle behave very differently

No personal data is stored Only the controller model, connection and the measured numbers

Browser measurements show the timing your browser receives. They're best for comparing controllers with each other, not as lab-grade absolute numbers.

Why controller latency matters

Every controller adds a small delay between your press and the game seeing it. In casual games you'll never notice. In fighting games, rhythm games and competitive shooters, a few milliseconds can decide who reacts first.

Two things drive that delay: how often the controller reports (polling rate) and how it connects. A controller reporting 1,000 times a second can deliver a press up to several milliseconds sooner than one reporting 125 times, and cables are usually steadier than Bluetooth.

How results are measured

Every result in the table comes from our Polling Rate Test and Input Lag Test, run in the tester's own browser. The polling rate test counts how often the controller sends updates while you move a stick. The input lag test measures

the timing between those updates and how much it varies.

Because everyone uses the same tests, results can be compared fairly between models. The table shows the average for each controller and connection type, along with how many tests that average is based on.

Wired, wireless dongle and Bluetooth compared

How a controller connects has a big effect on its speed. A cable is usually the fastest and most consistent. A 2.4 GHz wireless dongle, the small USB receiver that comes with many gaming controllers, is often close to wired. Bluetooth is the slowest and least consistent for most controllers, because it shares the radio with other devices and runs at lower update rates.

That's why the database splits every model by connection. A controller can look slow over Bluetooth and fast over a cable, and both results are correct.

Connection Typical speed Consistency

USB cable Fastest Most consistent

2. 4 GHz dongle Close to wired on many controllers Good

Bluetooth Slowest on most controllers Varies more

How to submit a reliable result

Close other programs and browser tabs, plug the controller straight into the computer rather than a hub, and keep this browser tab in focus while the test runs. Choose the exact model and connection type when you submit.

If you have more than one connection option, test each one and submit them separately. Results from different connections are kept apart, so each one adds useful data.

Using the database to choose a controller

For competitive games, look at polling rate and jitter together. A high polling rate with low jitter means the controller reports often and steadily. For casual play, almost every controller in the table is fast enough, and comfort and features matter more.

Remember that your own setup adds delay too: your display, the game and your computer all play a part. The database is most useful for comparing controllers measured the same way, rather than predicting exact numbers on your system.

What the numbers mean

Each result shows how long the controller takes to report a press. Lower is better. The database shows an average and the range of results, because latency varies a little from one press to the next.

Consistency matters as much as the average. A controller with a slightly higher average but a narrow range can feel more predictable than one with a lower average and a wide range.

Column What it shows

Average latency Typical delay from press to report

Range How much the delay varies

Connection Wired, dongle or Bluetooth

Polling rate How often the controller reports

Submissions How many results the average is based on

Polling rate explained

Polling rate is how often a controller sends its state to the computer. At 125 Hz, that's every 8 milliseconds. At 1000 Hz, it's every millisecond. A higher polling rate means a press can be reported sooner.

Polling rate isn't everything. Some controllers have a high rate but extra processing delay inside. The database shows the overall result, which includes both.

Connection type matters

The same controller can perform very differently wired and wireless. Bluetooth usually adds the most delay and variation. Dedicated wireless dongles can be close to wired. Cables are usually the most consistent.

When comparing controllers, compare the same connection type. A controller tested wired will usually beat one tested over Bluetooth.

Your system affects results

Your computer, operating system, browser and USB ports all add small differences. That's why results from different people vary, and why the database shows averages from several submissions.

For the most reliable comparison, test controllers yourself on the same setup, using our Controller Reaction Test or the measuring tool on this page.

Does latency matter for you?

For most games, the difference between controllers is too small to notice. It matters more in fighting games, rhythm games and competitive shooters, where a few milliseconds can matter.

If you play casually, comfort and drift resistance are probably more important than latency. If you play competitively, latency is worth considering alongside them.

Lowering latency with your current controller

Before buying a new controller, try a cable instead of wireless, and check whether your controller has a higher polling rate option in its software. Turn on game mode on your TV and close background programs.

These changes often make a bigger difference than switching controllers.

Console versus PC latency

The database focuses on PC, because that's where browser testing is possible. On consoles, the console decides how often it reads the controller, so a controller's PC result may not match exactly.

Use the database as a general guide to which controllers are faster, not as an exact figure for consoles.

Submitting results from different setups

If you test the same controller with different connections, submit each one separately and choose the right connection type. That keeps the averages accurate and helps others see how connection affects each controller.

If you've updated the controller's firmware since your last test, submit a new result. Firmware updates can change latency.

Third-party controllers in the database

Many third-party controllers advertise high polling rates and low latency. The database lets you check how they perform in real tests rather than relying on the box. Results from several people give a clearer picture than any single test.

Common problems

Frequently asked questions

Related tools and guides

• Input Lag Test→
• Polling Rate Test→
• Average controller input lag→
• Dongle vs Bluetooth latency→