In short
It is not bad; it is a trade-off that is often made by default. Hiding navigation behind an icon roughly halves how often it is used, and a site's most important paths should therefore not depend on it. On phones with more than four or five destinations a hamburger is usually the right container for the rest. On desktop, where there is room, it hides things for no reason. The better pattern on mobile is to show the two or three most important destinations and put the remainder behind the icon.
What the icon does
A hamburger menu is a container that hides navigation until tapped. That is the entire mechanism, and every argument about it is an argument about the cost of hiding things.
The cost is real and has been measured. Studies by the Nielsen Norman Group and others found that hidden navigation is used roughly half as often as visible navigation, that visitors take longer to find things and rate the experience worse, and that a noticeable share of people do not recognise the icon as a menu at all, although that share has fallen as the pattern has become ubiquitous. Hiding navigation also removes the orientation it provides: a visible menu tells you what a site contains and where you are in it before you tap anything.
None of that makes the icon bad. It makes it expensive, which means it should buy something.
When it is the right choice
Phones with more than a handful of destinations. A screen 390 pixels wide fits three or four labels. A site with nine sections has to put five of them somewhere, and a drawer behind an icon is a reasonable somewhere. The alternative, cramming nine tiny links across the top, is worse.
Secondary navigation. Account settings, legal pages, the less-visited sections. Nobody needs those visible; they need them findable. A hamburger is exactly right for the things that must exist without competing for attention.
Utility and content-first apps. Reading apps, tools with one primary screen, sites where the content is the point and the navigation is an occasional need. Hiding the menu gives the content the screen.
When it is the wrong choice
On desktop. There is room for a full navigation bar. Hiding it behind an icon on a 1,400-pixel screen is a stylistic choice that costs discoverability and buys whitespace. Designers like it because it is clean; visitors use the site less because of it.
For the primary action. If the site exists to get people to book, buy, or contact, that path should never be inside a menu. A visible button next to the icon costs nothing and is one of the most common navigation fixes a site can make.
For sites with three or four sections. If everything fits, show it. A hamburger containing four items is hiding navigation for no reason other than habit.
When visitors need orientation. E-commerce, large content sites, anything where knowing the categories helps someone decide what to do next. Hidden categories are categories that do not get browsed.
The pattern that usually wins
On mobile, show the two or three destinations that matter most as visible tabs or links, plus the primary call to action, and put everything else behind the icon. This is sometimes called a priority-plus or "hamburger plus" pattern and it recovers most of what hiding costs while keeping the screen usable.
Apps solved the same problem with a bottom tab bar: three to five icons with labels, always visible, reachable by thumb. It works on websites too and is under-used there. The thumb zone argument is straightforward: the top-left corner, where hamburgers traditionally sit, is the hardest place on a phone to reach one-handed.
On desktop: a full horizontal navigation, with a mega menu or dropdown only if the sections genuinely need sub-levels. Reserve the hamburger for whatever does not fit at the narrowest desktop width.
What to measure before deciding
Most sites already have the data to settle this. Look at how often the menu is opened on mobile sessions, which is usually a fraction of the desktop navigation's use, and compare mobile and desktop visits to the pages that matter most, such as booking or pricing. If a page is reachable only through the hamburger and its mobile share is far below its desktop share, the hidden navigation is costing you that page. Surface a direct link or button, wait a month, and compare again. The change is cheap enough to try and the effect is large enough to see without a formal test.
If you use one, do it properly
- Label it. The word "Menu" beside or beneath the icon raises use measurably, particularly among older visitors. It costs a few pixels.
- Make the drawer fast and obvious. It should open instantly, cover the screen or slide in clearly, and be dismissable by tapping outside, by a visible close button, and by the back button.
- Keep the tap target large. At least 44 by 44 pixels, and not jammed into the corner.
- Announce it to assistive technology. A
buttonelement witharia-expandedand a label, controlling a landmarknav, and focus moved into the drawer when it opens. This is the part most implementations skip and the part that makes the site accessible. - Order by use. The first three items should be the three most-visited destinations, not the organisation chart.
The question to ask instead
Not "hamburger or not" but "what are the three things most visitors need, and can they see them without tapping anything?" If yes, the hamburger is doing its proper job of holding the rest. If no, the site has a navigation problem, and the icon is just where it is hiding.
If you would like a second opinion on a specific site's navigation, book a call; it is usually a fifteen-minute diagnosis.
Common questions
Why do designers hate the hamburger menu?
Because it hides navigation, and hidden navigation is used about half as much as visible navigation, makes sites harder to orient in, and can conceal the primary action. The objection is to hiding by default, not to the icon. Used for secondary items on small screens, it is a sensible tool.
Should I use a hamburger menu on desktop?
Usually not. Desktop screens have room for a visible navigation bar, and hiding it costs discoverability for no practical gain. The exceptions are content-first or app-like interfaces where navigation is genuinely occasional. If the reason is that it looks cleaner, the visitors are paying for the aesthetics.
What is the alternative to a hamburger menu on mobile?
Show the two or three most important destinations and the main call to action visibly, and put the rest behind the icon. A bottom tab bar with three to five labelled icons, borrowed from apps, works well for sites with a few clear sections and is easier to reach with a thumb than a top-corner icon.
Do people know what the hamburger icon means?
Most do now; recognition has risen as the pattern became universal, but a minority, skewing older, still do not treat it as a menu. Adding the word "Menu" next to the icon measurably increases how often it is used and costs almost nothing.
Is a hamburger menu bad for SEO?
Not directly. Links inside a hidden menu are still in the page's HTML and are crawled. The indirect effect is that hidden navigation is used less, so pages reachable only through it get less internal traffic and engagement. Important pages should also be linked from visible content and footers.
