How to Make Website Navigation Work on Small Mobile Screens

On a small phone screen, a website menu has less room to work with, but visitors still need to find the same important information. They may be checking opening hours, comparing services or trying to contact you while standing in a queue. If the menu is hard to open, understand or use, they can lose their way before reaching the page they need.

Good mobile website navigation best practices are not about squeezing a desktop menu into a narrow header. They start with deciding what visitors need to find, then choosing a simple way to present those options. This guide explains how to make those decisions, avoid common mobile-menu problems and test the result without specialised equipment.

Start with what visitors need to find

Before choosing a menu style, make a short list of the pages and tasks that matter most. A small business site might need to help people understand what the business does, check prices or services, see examples of work and get in touch. A shop may need product categories, delivery information, returns and account access.

That list is not necessarily the same as your full sitemap. Some pages are useful to have but do not need a prominent place in the main navigation. A privacy notice, for example, may be linked in the footer. A detailed case study could be reached from a portfolio page rather than taking up a top-level menu position.

If you are still deciding which pages belong on the site, planning a small-business website sitemap can help you organise them before you design the menu.

Prioritise tasks, not internal departments

Use labels and groupings that make sense to a visitor, not the names your team uses internally. A menu item called “Solutions” may be clear inside your business but vague to someone who has just arrived. “Bookkeeping for freelancers” or “Website maintenance” gives people a better clue about what they will find.

Write down the main questions a visitor has and map each one to a page. For example:

  • What do you offer? Services
  • How much might it cost? Pricing or Get a quote
  • Can I trust your work? Projects or Reviews
  • How do I speak to you? Contact

Then compare that list with your existing navigation. If two items lead to similar information, consider combining them. If an important visitor task has no clear destination, the problem may be the site structure rather than the menu itself.

Choose a mobile menu pattern that fits the site

There is no single menu pattern that suits every website. The right choice depends on how many destinations people need, how often they use them and how important quick access is to the business.

A compact list in the page header

If the site has only a few destinations, you may be able to show them directly in the header on a phone. This avoids hiding the menu behind an extra tap. It can work for a one-person business with pages such as Services, About and Contact, but it becomes awkward when labels wrap or crowd the logo.

Try the actual longest labels on a narrow screen before committing to this approach. A row that fits in a design mock-up may wrap on a phone with larger text settings. Do not solve that by shrinking text until it becomes difficult to read.

A menu button that opens a panel

A menu button, often shown as a hamburger icon, can reveal a vertical list in a panel or drawer. This is a practical option when you have several destinations that will not fit in the header. It keeps the initial page uncluttered, but visitors must know the control opens the navigation and be able to use the panel comfortably.

Include a visible word such as “Menu” if the icon might not be familiar to your audience. When the panel is open, show a clear way to close it. The close control should be easy to reach, and tapping a link should take visitors to the page and close the panel rather than leaving an unexpected overlay behind.

A small set of persistent shortcuts

Some sites benefit from a few navigation controls that remain visible near the bottom of the screen, such as Home, Search, Basket or Account. This can suit a service where visitors repeatedly check a small number of sections, or a shop where the basket is a frequent destination.

Persistent controls use screen space even when the visitor does not need them. On a small device, they can obscure content, cover form buttons or compete with the browser controls. Use them only when those shortcuts are genuinely more useful than the space they occupy.

Keep the menu short, but do not hide essential pages

A shorter menu is often easier to scan, but a low item count is not a goal in itself. Removing a useful destination can force people to guess where information lives or search through several pages. Instead, organise items into clear groups and make the most important choices easy to spot.

For a local repair business, a sensible menu might be Services, Areas covered, Prices, About and Contact. If there are many service types, “Services” could open a second level with a short list. It is usually less helpful to place every service as a separate item in a long first-level menu.

Keep menu labels concise and specific. “Contact” is familiar; “Start your journey” is less predictable. If your main action is to request an estimate, “Request a quote” may be clearer than a generic “Get started”. A useful label tells visitors what will happen next without making them interpret a slogan.

Use submenus sparingly

Nested menus can be useful when a site has real categories, but each extra level adds a decision. On mobile, make the parent item and its submenu control behave predictably. If the parent page is useful, do not make the entire row expand the submenu with no way to visit the parent. A separate chevron or button can provide the expand action while the text remains a link.

Show whether a submenu is open, for example by changing the chevron direction and keeping the child links visible. Avoid hover-only interactions: touchscreens do not have a reliable hover state. Also ensure keyboard users can open, move through and close the menu.

Make every control comfortable to use

Small touch controls are easy to miss, especially when several links sit close together. Give menu rows enough height and spacing for a thumb, and avoid placing a tiny close icon against the edge of the screen. The visible icon may be small, but its clickable or tappable area can be larger.

The W3C explanation of WCAG 2.2 target size describes a minimum target size criterion of 24 by 24 CSS pixels, subject to stated exceptions and spacing rules. Treat that as an accessibility baseline to understand, not as a comfortable design target for every control. A larger touch area is often more forgiving, particularly for primary actions and controls people use while moving.

Make sure text remains readable when someone increases the browser’s text size. Avoid fixed-height menu rows that cut off enlarged labels. Check that focus indicators are visible for people navigating with a keyboard, and that the menu button has an accessible name such as “Open menu” rather than a decorative icon with no announced purpose.

Design the open state as carefully as the closed state

A menu that looks tidy when closed can still be frustrating after someone opens it. Decide how it behaves with the page behind it, with long content and with smaller viewports.

  • Show a clear state: Make it obvious whether the menu is open or closed, and use a visible close control.
  • Keep it in view: If the menu is taller than the screen, allow the list to scroll. Do not let the final link become unreachable behind a fixed footer or browser bar.
  • Prevent accidental page movement: If the menu overlays the page, consider whether the background should scroll while the panel is open. Whichever behaviour you choose, make it easy to reach every menu item.
  • Handle the keyboard: A keyboard user should be able to move through the links and controls in a logical order. If the panel behaves like a modal overlay, focus should not wander behind it while it is open.
  • Respect the current page: Indicate the visitor’s location in a restrained, understandable way, such as a different text weight or a “current page” label.

These details matter because navigation is part of the page experience, not a separate decoration. A visitor should not have to guess whether a tap registered or how to get back to the content.

Give key actions a clear place

Some actions deserve more emphasis than ordinary navigation links. A booking business may want people to reserve a time; a consultant may want visitors to request a proposal. You can distinguish that action with a button-like treatment, but avoid giving every menu item the same visual emphasis.

Make sure the action label matches the destination. “Book an appointment” should open a booking route, not a general contact page where visitors must work out what to do. If the next step involves several questions, explain what is needed and why. For advice on keeping an enquiry process focused, see our guide to qualifying leads without adding friction to a contact form.

Do not rely on colour alone to distinguish the main action. Use clear wording, sufficient contrast and a shape or border that helps it stand out. The action should remain obvious in the open menu and at larger text sizes.

Test the navigation on real phones

Responsive previews are useful, but they cannot tell you everything about using a menu with a thumb or with enlarged text. Test on at least one iPhone and one Android device if you can borrow them. If that is not possible, use your browser’s responsive mode, then ask someone with a real phone to try the key tasks.

Try realistic visitor tasks

Give a tester a specific task rather than asking whether they like the design. For example: “Find out whether you cover Bristol”, “Check how to book a consultation” or “Find the return policy”. Watch where they tap and whether they hesitate. Do not immediately explain the menu; confusion is useful evidence.

Test these conditions as well:

  • Open and close the menu one-handed.
  • Use the longest menu label and the smallest supported screen.
  • Increase text size or zoom the page.
  • Open a submenu, visit a page and use the browser’s Back control.
  • Use the keyboard to reach the menu button and navigate its links.
  • Check whether a sticky header or bottom shortcut covers content or form controls.

After testing, fix the points that block a task before polishing small visual details. If several people look for the same page under different labels, that is a sign to reconsider the wording or site structure. For guidance on the page flow beyond the menu, our article on laying out a small-business homepage explores how to make the next step clear.

A practical checklist for mobile website navigation best practices

  • List the visitor tasks the menu needs to support.
  • Use plain, specific labels that describe the destination.
  • Choose a menu pattern that suits the number and importance of your links.
  • Keep first-level choices manageable without burying essential pages.
  • Make buttons and links large enough to tap comfortably.
  • Provide clear open, close and submenu states.
  • Check keyboard access, focus visibility and enlarged text.
  • Test common tasks on real devices and revise based on where people hesitate.

Mobile navigation works when people can predict where a link leads, reach it without precision tapping and return to the page without losing their place. A few deliberate choices about structure, labels and testing will usually do more than adding another layer of animation or a more elaborate menu pattern.

Frequently asked questions

Should every mobile website use a hamburger menu?

No. A hamburger menu is useful when several links will not fit in the header, but a small site may be clearer with a few visible links. Choose the pattern that makes important destinations easiest to find on your actual pages and devices.

How many links should a mobile menu have?

There is no universal ideal number. Include the destinations visitors need, group related pages where that helps, and move lower-priority links to an appropriate secondary location. Test whether people can find common tasks rather than judging the menu by its item count.

Should the menu cover the whole screen?

It can, but it does not have to. A full-screen panel gives links room and reduces distractions behind the menu; a smaller drawer can keep some page context visible. Either way, make the close control clear and ensure every link remains reachable on a short screen.

Is a hamburger icon enough to identify the menu button?

It may be recognised by many visitors, but a visible “Menu” label can make the control clearer. The button also needs an accessible name for assistive technology, and its open or closed state should be communicated in a way users can understand.

How can I tell whether my mobile navigation is working?

Ask someone unfamiliar with the site to complete realistic tasks on a phone. Notice where they pause, tap the wrong control or fail to find a page. Also test keyboard access, larger text and the smallest screens your design supports.