Real browser test
Does your phone delay click after a tap?
This page does not simulate anything. It measures the real time between finger release
(pointerup or touchend) and the browser's click event on elements
using touch-action: auto and touch-action: manipulation.
.fast-tap {
touch-action: manipulation;
}Tap the controls
Same elements, different touch-action
The left column keeps the browser default: touch-action: auto. The right column uses
touch-action: manipulation. If the browser delays click while checking for
double-tap zoom, it will show up in the "release -> click" measurement.
The image cards mirror the common app pattern where a whole preview tile opens a modal, so the test is not limited to native buttons.
Live results
Measurements from this browser
| Element | touch-action | Last release -> click | Last release -> visible | Average | Taps |
|---|
In the old tap-delay scenario, the gap is usually around 250-350ms. If everything reads 0-30ms,
this browser is already dispatching click immediately in this setup. That is a useful result too.
If release -> click is low but release -> visible is high, the lag is likely in
app work after the click: state updates, modal rendering, image decoding, layout, or main-thread JavaScript.
Recent events
Event log
How to read this
touch-action: manipulation does not make hardware or JavaScript faster.
It tells the browser up front that double-tap zoom is not needed on that element. If the browser
would otherwise wait for a second tap before generating click, that wait can disappear.