No 300ms tap delay
Why it matters
Legacy mobile browsers inserted a 300ms delay on tap events to distinguish between a single tap and a double-tap-to-zoom gesture. That delay makes buttons feel sluggish and unresponsive compared to native apps. Modern browsers eliminate the delay when a correct viewport meta tag is present, but older WebViews and some embedded browsers still apply it. touch-action: manipulation disables the double-tap-zoom gesture on interactive elements, removing the delay explicitly.
Severity rationale
Low because the primary mitigation (viewport meta tag) is already required by another check, and modern browsers no longer impose the delay.
Remediation
If the viewport meta check already passes, no further action is required for modern browsers. For extra coverage on older mobile WebViews, add touch-action: manipulation to buttons, links, and anything with role="button" in your global CSS.
button, a, [role="button"] { touch-action: manipulation; }
DetectionPro
The detection method for this pattern is part of AuditBuffet Pro.
The full method (what to look for, pass and fail conditions, and how results get reported) ships inside the Mobile Responsiveness Audit. The pattern definition, severity rationale, and remediation remain openly licensed under CC-BY-4.0.
Taxons
History
- 2026-04-18·v1.0.0·Initial import from mobile-responsiveness·automated