How to Fix Small Mobile Tap Targets and Tight Spacing

This warning means some rendered pages have more than five links, buttons or form controls under 32px wide or tall on a mobile viewport, which makes them easy to mis-tap. By the end of this guide you will have listed every undersized target, enlarged their hit areas to about 48×48px with 8px spacing, and confirmed that each page has five or fewer small targets.

By Updated ⏱ 45–90 minutes🎯 Intermediate● Medium impactOn-Page
Illustration: Mobile tap target spacing fix guide
ON-PAGE · FIX GUIDE Mobile tap target spacing IMPACTEFFORT TIME45–90 minutes LEVELIntermediate

Why it matters

On a phone, a 20px footer link or a 16px close icon causes mis-taps, accidental navigation and abandoned forms. These problems show up as weaker engagement and lower conversion rates. Google retired the Search Console Mobile Usability report and the Lighthouse tap-targets audit, so small targets are no longer flagged as a standalone ranking issue.

8 requires targets of at least 24×24 CSS px or enough spacing around them. Fixing them helps mobile users and keyboard or switch users, and reduces accessibility complaint risk.

✕Beforehttps://example.com/ on a 375pxviewport has 14 targets under 32px:18px-tall footer links, 20×20px social✓AfterEvery button, icon and nav link onhttps://example.com/ has at least a48×48px hit area with 8px gaps, and

What you need

Desktop Chrome or Edge with DevTools
Access to your theme CSS or site builder style settings
A list of the pages flagged by the audit
A real phone for a final tap test (optional but recommended)

Step-by-step fix

1

Open a flagged page in a mobile viewport

Open one of the pages listed by the audit in Chrome. Press F12, then Ctrl+Shift+M (Cmd+Shift+M on Mac) to toggle Device Toolbar. Choose a common phone size such as 375×667 or 412×915, then reload the page so mobile CSS and menus render correctly.

Pro tip: Start with templates rather than individual URLs. The header, footer, product card and blog post templates usually account for most flagged pages.
2

List every target smaller than 32px

Paste this snippet into the DevTools Console. It outlines every visible link, button and form control that is under 32px in either dimension, and prints a table with each element's size. The audit warns when a page has more than 5 of these, so note which elements repeat across templates.

javascript
const sel='a[href],button,input:not([type=hidden]),select,textarea,summary,[role=button],[role=link],[tabindex]:not([tabindex="-1"])';const small=[...document.querySelectorAll(sel)].filter(e=>{const r=e.getBoundingClientRect();const s=getComputedStyle(e);return r.width>0&&r.height>0&&s.visibility!=='hidden'&&(r.width<32||r.height<32);});small.forEach(e=>e.style.outline='2px solid red');console.log(small.length+' small targets');console.table(small.map(e=>{const r=e.getBoundingClientRect();return{tag:e.tagName,text:(e.innerText||e.getAttribute('aria-label')||e.value||'').trim().slice(0,40),w:Math.round(r.width),h:Math.round(r.height),cls:e.className.toString().slice(0,40)};}));
Pro tip: Scroll the whole page and open the mobile menu before running the snippet. Elements that are hidden or collapsed have zero size and are skipped.
3

Enlarge icon buttons without enlarging the icon

Social icons, cart, search, hamburger and close buttons are the most common failures. Set min-width and min-height to 48px on the clickable element and center the icon inside it. The visible icon can stay at 20–24px.

Only the hit area grows.

html
<style>
.icon-btn, .social-links a, .header__icon, .menu-toggle {
  display: inline-flex;
  align-items: center;
  justify-content: center;
  min-width: 48px;
  min-height: 48px;
}
.icon-btn svg, .social-links svg { width: 24px; height: 24px; }
</style>
Pro tip: Put the padding or min-size on the <a> or <button>, not on the <svg> or <img>. Padding on a child element does not enlarge the tappable area.
4

Pad navigation, footer and breadcrumb links

Text links in menus and footers are often only as tall as their line of text, around 16–20px. Make them block or inline-block and add vertical padding so each one reaches at least 48px tall. Then use gap on the parent so adjacent links have 8px between hit areas.

html
<style>
@media (max-width: 768px) {
  .site-footer ul, .main-nav ul, .breadcrumbs ol {
    display: flex;
    flex-wrap: wrap;
    gap: 8px;
  }
  .site-footer a, .main-nav a, .breadcrumbs a {
    display: inline-block;
    min-height: 48px;
    padding: 12px 8px;
    line-height: 24px;
  }
}
</style>
Pro tip: Use a pointer query such as @media (pointer: coarse) instead of a width query if you want larger targets on touch tablets too.
5

Fix form controls, pagination and small CTAs

Native checkboxes and radio buttons render at about 13–16px, so they count as small targets.

  • Wrap each control in its <label> and give the label padding, so the whole row becomes tappable.
  • Make pagination numbers, "Read more" links, quantity steppers and carousel dots at least 48px square.
  • Set inputs to font-size: 16px so iOS does not zoom in on focus.
html
<style>
.form-check label { display: flex; align-items: center; gap: 8px; min-height: 48px; }
.form-check input[type=checkbox], .form-check input[type=radio] { width: 24px; height: 24px; }
input, select, textarea { font-size: 16px; min-height: 48px; }
.pagination a, .qty-btn, .carousel-dot { min-width: 48px; min-height: 48px; display: inline-flex; align-items: center; justify-content: center; }
.carousel-dot::before { content: ''; width: 10px; height: 10px; border-radius: 50%; background: currentColor; }
</style>
Pro tip: For carousel dots, keep the small visual dot as a pseudo-element inside a 48px button. The design looks the same and the tap area becomes much larger.
6

Handle inline links inside body text

Links inside paragraphs are exempt under WCAG, but they can still appear in the small-target count if a page has many of them. Raise line-height to about 1.6 so the link boxes grow and the lines are easier to tap. If a paragraph contains a long string of short links, such as tag lists or "related" lists, convert it into a spaced list.

html
<style>
.entry-content p, .entry-content li { line-height: 1.6; }
.tag-list { display: flex; flex-wrap: wrap; gap: 8px; list-style: none; padding: 0; }
.tag-list a { display: inline-block; padding: 12px 14px; border-radius: 24px; }
</style>
7

Re-check each template and re-run the audit

Clear your page cache and CDN cache, then reload the flagged page in Device Toolbar. Run the Step 2 snippet again: the count should be 5 or fewer, and ideally 0. Repeat for each template, then re-run the site audit so the rendered pages are re-measured.

Pro tip: Check that the larger targets did not break the layout. A 48px footer link list can wrap awkwardly at 320px width, so test the smallest viewport too.

Platform-specific notes

WordPress

For classic themes, add the CSS in **Appearance > Customize > Additional CSS**. For block themes, use **Appearance > Editor > Styles > (pencil icon) > Additional CSS**, or set padding per block in the Navigation and Social Icons block settings. Social Icons blocks have a Size option: choose Large or add padding. Clear caching plugins such as WP Rocket or LiteSpeed Cache afterwards.

Shopify

In **Online Store > Themes > Customize > Theme settings > Custom CSS**, add the rules. Theme-wide Custom CSS has a character limit and does not accept every selector, so for larger changes use **… > Edit code** and edit assets/base.css (Dawn and most Online Store 2.0 themes). Header icons use classes such as .header__icon, and footer links use .footer-block__details-content a.

Wix

Classic Wix Editor has no global CSS. Switch to the **mobile editor** (phone icon at the top), select each button or menu, and increase its height and padding in the Design panel. Wix Studio supports custom CSS through the **global.css** file in the Code panel, so you can apply the min-height rules there.

Webflow

In the Designer, switch to the **Mobile Portrait** breakpoint, select the link or button class, and set **Min W/Min H** to 48px in the Style panel's Size section. Use Flex with a **Gap** of 8px on the parent. Styles set at this breakpoint cascade down only, so desktop stays unchanged. Republish to apply.

Next.js / Tailwind

Add `min-h-12 min-w-12 inline-flex items-center justify-center` to icon buttons and `gap-2` to link containers. Tailwind's `pointer-coarse:` variant (v4) limits the larger sizes to touch devices. If you use a component library, set the size prop on IconButton, such as `size="lg"`, instead of overriding it with CSS.

Check that it worked

✅ How to verify

  • Run the Step 2 Console snippet on each fixed template at a 375px viewport and confirm it reports 5 or fewer small targets, ideally 0.
  • In DevTools, select an icon button and hover it in the Elements panel. The highlighted box should be at least 48×48px, even if the icon inside is 24px.
  • Open the pages on a real phone and tap every footer link, social icon, checkbox and menu item with your thumb. You should not hit a neighbouring element by mistake.
  • Re-run the site audit and confirm the tap target spacing warning no longer lists the fixed pages.

⚠️ Common mistakes

  • Scaling up the icon itself instead of the clickable element. This makes the design heavier, and the parent <a> stays small if the padding sits on the wrong element.
  • Using transform: scale() or negative margins to enlarge targets. Transforms change the visual box unpredictably, and overlapping hit areas cause mis-taps.
  • Applying the fixes only at a desktop width or inside the wrong media query, so the mobile render the audit measures is unchanged.
  • Forgetting cached CSS. Page caches, CDNs and theme minification can serve the old stylesheet, so the audit still sees small targets.

Is this still an issue on your site? Run a free audit — ZORO checks this and 294 other SEO, AI-visibility, accessibility and security signals, with fixes for your platform.

Check my site free

FAQ

What is the minimum tap target size for mobile?

Google's Android guidelines recommend 48×48dp, and Apple recommends 44×44pt. WCAG 2.2 sets 24×24 CSS px as the AA minimum (2.5.8) and 44×44px as the AAA target (2.5.5). Our audit flags targets under 32px, and we recommend 48px with 8px spacing for comfortable tapping.

Do small tap targets hurt Google rankings?

Not directly anymore. Google retired the Search Console Mobile Usability report in December 2023, and Lighthouse removed its tap-targets audit. Small targets still hurt engagement, conversions and accessibility compliance, which affect the overall value of the page.

Does the visible button have to be 48px?

No. Only the tappable area needs to be that size. Keep a 24px icon or a compact text link visually, and add padding or min-width/min-height to the link or button element so the hit area reaches 48px.

Do links inside paragraphs need to be 48px tall?

No. WCAG exempts inline links in sentences, and making them 48px tall would break the text layout. Use a line-height of about 1.6 so they are easier to tap, and move long runs of short links into spaced lists.