Design

Designing Mobile Navigation for WordPress Sites That People Can Actually Use

Designing Mobile Navigation for WordPress Sites That People Can Actually Use

On most business websites I look at, more than half of visitors are on a phone, often much more. Yet the mobile menu is usually designed last. The desktop navigation is planned carefully, with dropdowns and mega menus, and then everything is crammed behind a hamburger icon for smaller screens. The result is a long, nested list that’s hard to scan and harder to use with a thumb. Good mobile navigation starts with a different question.

Good mobile navigation isn’t a shrunken desktop menu. It’s designed for how people use phones: one hand, short attention, specific goals and a small screen. This article covers the principles and patterns that work, and how to implement them in WordPress.

Start with what people need

Before designing anything, look at your analytics, filtered to mobile visitors. Which pages do they visit most? What do they do? For many local businesses, mobile visitors overwhelmingly want a few things: the phone number, directions, opening hours, services and prices, and a way to book or enquire.

Your mobile navigation should make those things quick to reach. Everything else can be one level deeper.

Also check internal site search queries, if you have search. They show what people couldn’t find easily.

Simplify the structure

Desktop menus often grow over time until they contain twenty or thirty links. On mobile, that becomes an endless scroll inside a menu panel.

Reduce the top level to the essentials, ideally five to seven items. Group related pages logically, and use clear, familiar labels. “Services”, “Pricing”, “About” and “Contact” are better than creative labels like “What We Do Best” or “Say Hello”.

You don’t necessarily need the same menu on mobile and desktop. WordPress lets you show different menus at different breakpoints, and the Navigation block can use separate menus for overlay and desktop views with a little configuration or custom CSS. Many sites benefit from a shorter mobile menu.

Hamburger menus: pros and cons

The hamburger icon, three horizontal lines, is widely recognised. It saves space and keeps the header clean. But hiding navigation behind an icon has a cost: people use what they can see. Research over many years has shown that hidden navigation is used less than visible navigation.

That doesn’t mean hamburgers are bad. It means you should:

  • Keep the most important actions visible outside the menu, such as a call button or “Book now”
  • Label the icon “Menu” alongside the three lines, which improves recognition, especially for less tech-savvy users
  • Consider showing two or three key links directly in the header if there’s room

Visible primary actions

For most business sites, one or two actions matter more than everything else. Make them visible at all times on mobile:

  • A “Call” button with a tel: link for service businesses
  • A “Book” or “Get a quote” button
  • A cart icon with item count for stores
  • A WhatsApp link where customers prefer it

Put these in the header, next to the menu button. Many visitors never open the menu at all; they tap the call button and they’re done.

Bottom navigation

Phones have grown taller, and the top of the screen is the hardest place to reach with a thumb. Many apps put navigation at the bottom for this reason. Some websites, especially stores and web apps, now do the same: a fixed bar at the bottom with four or five key links, such as Home, Shop, Search, Cart and Account.

Bottom navigation works well for sites where people browse many pages in one visit. It’s less common on brochure sites, where a top header with a visible call-to-action button is usually enough.

If you add bottom navigation, make sure it doesn’t cover content or form buttons, works with the browser’s own interface and respects the safe area on phones with notches and gesture bars.

Sticky headers, carefully

A header that stays fixed at the top while scrolling keeps navigation and key actions available. But on a small screen, it also takes up space permanently.

Good sticky headers on mobile:

  • Are compact, roughly 56 to 64 pixels high
  • Contain only the logo, menu button and one key action
  • May hide on scroll down and reappear on scroll up, which gives space while reading and access when needed

Avoid tall sticky headers with announcement bars, full logos and multiple rows. They can consume a quarter of the screen.

Tap targets

Fingers are much less precise than mouse pointers. WCAG 2.2 includes a minimum target size of 24 by 24 CSS pixels at level AA, and platform guidelines from Apple and Google recommend 44 to 48 pixels for comfortable tapping.

In practice:

  • Make menu items at least 44 pixels tall
  • Add enough space between links that people don’t tap the wrong one
  • Make the whole row tappable, not just the text
  • Make the menu button and close button large enough to hit easily

Small, tightly packed links are one of the most common mobile usability complaints.

Submenus on mobile

Nested menus are where mobile navigation most often breaks down. Hover doesn’t exist on touch screens, so submenus must open on tap.

Common patterns:

  • Accordion: tapping a parent item, or an arrow beside it, expands its children below. Simple and widely used.
  • Drill-down: tapping a parent slides in a new panel with the children and a back button. Works well for deep menus but adds steps.
  • Flattened: no submenus at all on mobile, with parent pages linking to their children instead.

If the parent item is also a page, provide a separate toggle for the submenu, so tapping the label goes to the page and tapping the arrow expands the children. Otherwise, users can’t reach the parent page at all.

The Navigation block in WordPress

For block themes, the core Navigation block handles responsive menus. Its settings include:

  • Overlay menu: show the hamburger always, on mobile only or never
  • Open submenus on click: important for touch and keyboard users
  • Show arrow icons for submenus
  • Overlay colours, and in recent versions, the ability to design the overlay as a template part

The block outputs reasonably accessible markup, with a button for opening the overlay, focus management and Escape to close. Customising its appearance is done with block styles, theme.json and CSS.

Classic themes use their own menu code, which varies widely in quality. Test yours with a phone and with a keyboard.

Accessibility of mobile menus

An accessible mobile menu:

  • Uses a button element for the menu toggle, with aria-expanded showing whether it’s open
  • Has a visible label, or at least an accessible name like “Menu”
  • Moves focus into the menu when opened and returns it to the button when closed
  • Closes with Escape
  • Traps focus within a full-screen overlay while it’s open
  • Has submenu toggles that are buttons with aria-expanded

Many of these also improve the experience for everyone, not just users with disabilities.

Search on mobile

For sites with a lot of content or products, search is often faster than navigating menus on a phone. Make search easy to reach: a search icon in the header or a search field at the top of the menu panel. For stores, search is frequently the most-used navigation tool on mobile.

Test on real phones

Browser developer tools simulate mobile screens, but they don’t reproduce the experience of holding a phone. Test on real devices, ideally several, including a smaller older phone. Try:

  • Opening and closing the menu with one hand
  • Finding three common pages
  • Tapping the call button
  • Using submenus
  • Navigating while scrolled halfway down a long page

Better still, ask a few people unfamiliar with the site to find something specific and watch where they struggle.

Measuring whether it works

After changing mobile navigation, check whether it helped. Compare mobile bounce rates, pages per visit and conversion rates for a few weeks before and after. Track clicks on the menu button, the call button and other header actions as analytics events. If almost nobody opens the menu but the call button gets plenty of taps, your header is doing its job. If people open the menu repeatedly in one visit, they may be struggling to find something, which is worth investigating with session recordings.

Frequently asked questions

Should mobile and desktop menus be the same?

Not necessarily. The structure should be consistent so people aren’t confused, but the mobile menu can be shorter and prioritise different items.

Is the hamburger icon still recognised?

Yes, by most users. Adding the word “Menu” next to it improves recognition and costs very little space.

Do mega menus work on mobile?

Not as they are. Convert them into an accordion or drill-down structure, or simplify them for small screens.

Should the logo link to the homepage?

Yes. People expect it, on mobile as much as desktop. A separate “Home” link in the menu is optional.