Most paid traffic is mobile traffic. If a phone field pulls up the full alphabet keyboard instead of a number pad, that's friction on every single mobile visitor who reaches your form — not a one-off.
Mobile browsers decide which keyboard layout to show based on the form field's type and autocomplete attributes — not on the label text next to it. A field labelled "Phone Number" that's still coded as a generic text input shows the default full keyboard, forcing visitors to hunt for numbers among letters and manually switch keyboard modes themselves.
This is invisible on desktop, which is exactly why it survives so many launches — whoever tested the form was almost certainly testing it with a mouse and a physical keyboard.
Every extra tap between a visitor deciding to convert and actually submitting the form is a point where they can get distracted, frustrated, or simply give up — especially on a landing page they arrived at from a paid ad, where intent is high but patience is low. Autofill compounds this: without the right autocomplete value, browsers and password managers can't confidently pre-fill the field either, so visitors end up typing everything manually.
type="tel"type="email"inputmode="numeric" (the exact right type varies by country, so this is the safer default)autocomplete values (autocomplete="tel", autocomplete="email", autocomplete="postal-code") so autofill works correctly too, not just the keyboardForm field types are one of the checks we run automatically against every page.
Run a free check on your own site →