Test your L1 and R1, or LB and RB, bumpers for reliable presses, sticking, and double press accuracy, right here in the browser.
Checking for a controller…
No controller detected
Connect a controller by USB or Bluetooth, then press any button. Most browsers will not notice it until you do.
Tap either bumper twice as fast as you can. A clean double tap means the bumper registered both a press and a full release in between, with no missed or merged input. This is the fastest way to catch a bumper that feels fine for slow, deliberate presses but starts dropping inputs the moment you need it to fire quickly.
Each mark shows when a press happened. Evenly spaced marks matching your own rhythm mean a healthy bumper. Marks that look bunched together with odd gaps, when you were pressing at a steady pace, point to inconsistent registration.
Unlike triggers, which are analog and report a smooth range of pull depth, bumpers are simple digital switches under the hood, they are either pressed or they are not, with no in between value to inspect. That means the usual approach of watching a resting value for drift does not apply here at all, since there is no meaningful resting reading beyond zero and one. What actually fails on a worn or damaged bumper is different in character: a press that does not register at all, a press that registers but the switch sticks and does not cleanly release, or a fast repeated press where the second tap gets lost because the switch has not fully reset in time.
This test is built around that failure pattern specifically, tracking how reliably each individual press both starts and ends cleanly, rather than measuring a value that bumpers do not really have.
The pad fills solid the instant a press is detected and clears the instant it releases, with the press counter ticking up by one for each completed press. Watch the pad directly while pressing at different speeds, a bumper that visually lags behind your own finger, filling a noticeable beat after you actually pressed, is worth paying closer attention to even if the counter still increments correctly.
This is how long your most recent press lasted from the moment it registered to the moment it released. There is no universally correct hold time since that depends entirely on how you are pressing, but watch for holds that read unexpectedly long on what felt like a quick tap, which can indicate the switch is sticking slightly before releasing rather than snapping back cleanly.
This tracks the shortest time between the end of one press and the start of the next, across all your presses this session. A smaller number here generally means the bumper is keeping up well with rapid input. If this number seems to have a floor that never goes below a certain point no matter how fast you physically tap, that floor may be the switch's actual mechanical reset limit rather than a limit on your own tapping speed.
This counts presses that appear to have been attempted, based on timing and rhythm, but where the controller never reported a press event at all. This number is inherently an estimate, since a tap that produces nothing is by definition invisible to the controller, but a missed tap count that climbs noticeably during fast repeated presses is a meaningful warning sign worth taking seriously.
This isolates your single best attempt at two fast, clean presses in a row, with a genuine release in between rather than one long press being misread as two. A healthy bumper should comfortably manage a double tap somewhere under 150 to 200 milliseconds. If your best result sits well above that no matter how many attempts you make, and you are confident the slow result is not just your own finger speed, that points toward the bumper struggling with rapid reset.
This gives you a visual rhythm strip of exactly when each bumper fired over the last ten seconds. Press at a steady, even pace and look at the spacing between marks. Evenly spaced marks that match the rhythm you were actually pressing in indicate healthy, consistent registration. Marks that cluster unevenly, with some gaps far larger or smaller than your own pressing rhythm would explain, suggest the bumper is not responding consistently to identical input.
Bumpers carry a disproportionate amount of responsibility in a lot of genres relative to how little attention they usually get. Racing games map gear shifting directly to L1 and R1, where a single missed shift at the wrong moment can cost a race. Shooters frequently bind grenade throws, melee, or tactical sprint to a bumper, actions that matter most in exactly the high pressure moments where a missed input is most costly. Fighting games and platformers often use bumpers for blocking or dashing, where timing reliability is the entire point of the input existing at all.
Because bumpers are simple switches rather than the more closely watched analog sticks or triggers, a developing fault often goes unnoticed for longer, since there is no obvious drift or visible imprecision to catch your eye, it just quietly starts dropping the occasional press until it becomes a pattern you can no longer ignore in game.
Plug in over USB, or pair over Bluetooth in your system settings first. Chrome, Edge, and Firefox all support the controller out of the box once it is paired.
Pair the controller in your device's Bluetooth settings, then open this page in Chrome. Other Android browsers vary in their support.
Pair an MFi or Bluetooth controller in Settings, then open this page in Safari. iOS has supported the same Gamepad API since version 14.5.
Plug in over USB or pair over Bluetooth, then use Chrome or Firefox. Some distributions need a one time udev rule for certain Bluetooth controllers to be recognised by the operating system at all. If the controller is not visible at the system level, it will not be visible here either.
Try pressing in a slightly different spot along the bumper's length, since some bumpers respond less reliably near one edge than the centre, particularly once worn. If the missed taps counter climbs specifically during fast repeated presses but rarely during slow deliberate ones, that points toward a reset speed issue rather than a dead switch.
Watch the last hold reading on a press you know was short and quick. If it reads noticeably longer than the press actually felt, the switch may be sticking slightly on release rather than snapping back immediately, which is worth keeping an eye on even if it has not caused an obvious problem in game yet.
Compare it against the other bumper using the exact same tapping motion and speed. If one side consistently and clearly underperforms the other despite identical effort, that is a more reliable signal of an actual hardware difference than the absolute number alone.
Press a button first. Many browsers will not register a controller until they see its first input.
If your results look unusual, your controller will not stay detected during testing, or you want a second opinion on whether a bumper reading points to a real hardware issue, reach out directly. A short description of what you are seeing, along with your controller model and device, is normally enough to help track down what is going on.
info.gpadviewer@gmail.comSign in to your account