Neve Mobile Menu Not Working: Why the Hamburger Ignores the Tap

Four ways a Neve menu lets a thumb down

Write down exactly what the phone does before changing anything. Neve's menu fails in a few distinct patterns, and each one points at a different layer of the site. Test logged out, because caching and optimization plugins usually skip administrators, which is why the owner is often the last person to see the fault.

• The tap does nothing at all. No X, no panel, no dimmed overlay. The listener that waits for the tap never attached, or an error stopped the script first.
• The icon turns into an X and no panel appears. The script ran and marked the page as open, but the styles that slide the panel into view are missing or overridden.
• It works, eventually. Taps are ignored for several seconds after the page looks finished, then the menu behaves. Something is holding back the browser's load event.
• The panel opens and the links misbehave. Submenus will not expand, carets look wrong, or the panel shuts the moment a link is tapped.

One pattern belongs elsewhere: a panel that opens empty, or a phone header with no menu icon at all. Those are layout problems, and our Neve header builder repair notes cover placing the Menu Icon and filling the slide-out area. This page deals with the menu that is placed correctly and still refuses to work.

From tap to panel: Neve's menu, read from the 4.2.15 code

Neve does not ask what device a visitor holds. It measures the window. In the 4.2.15 stylesheet, the desktop header rows hide below 960 pixels and the mobile rows take over, so an upright tablet gets the same header as a phone. The mobile layout has its own rows in the Customizer header builder, plus a row named Mobile Sidebar, which is the slide-out panel itself. In Neve's built-in header presets, the Menu Icon sits in a mobile row and the Primary Menu sits in Mobile Sidebar.

The tap is handled by frontend.js, about 8 KB, loaded asynchronously in the footer with no jQuery dependency. When the icon is tapped, the script adds a class called is-menu-sidebar to the page body and marks the icon active. The CSS that actually moves the panel into view keys off that class, and Neve prints those rules inline, in the same style block as your Customizer settings. The Open Behavior setting picks the motion: Slide from Left (the default), Slide from Right, Pull from Left, Pull from Right, Full Canvas or Slide Down.

Suspects on a Neve site, ranked, with a test for each

Optimizers lead the list for a reason. In June 2026 a Neve owner reported a hamburger that ignored taps in iOS Safari. Themeisle support could not reproduce it on test sites, and the owner then traced it to the SiteGround speed-optimization plugin. The thread never says which switch did it. A neighboring case is better documented: in August 2026 OceanWP staff acknowledged that SiteGround Speed Optimizer's Combine JS setting breaks that theme's mobile menu. Different theme, same mechanism, so Combine is the first switch to test.

Combining hurts Neve in a second way. Loaded alone, Neve's script is isolated: an error in a slider plugin's file cannot stop it. Merged into one large file with a dozen other scripts, a single error earlier in that file halts everything after it, and the menu goes down with a plugin it has never met.

Menu repairs in Neve's 2026 changelog

Themeisle shipped several menu fixes this year, and two describe this page's symptoms closely. If your site runs an older release, updating on a staging copy may be most of the work. These entries come from the changelog bundled with Neve 4.2.15, released October 1, 2026.

• 4.2.9 (July 22): fixed an error that could stop the mobile menu from opening when certain optimization plugins delay script loading.
• 4.2.9: fixed menu items with quotes in their titles breaking the mobile submenu toggle button.
• 4.2.12 (September 14): fixed mobile off-canvas carts that did not open after adding products, and right-edge dropdowns opening beside their parent items.
• 4.2.13 (September 24): made menus keyboard-ready as part of an accessibility pass.
• 4.2.15 (October 1): fixed menu caret buttons showing a rounded background and shadow instead of a plain arrow.

An older entry still matters on neglected sites: version 4.1.0 fixed a mobile navigation sidebar that did not work when no navigation menu was added to the header. Update Neve and Neve Pro together, because Pro's header components expect a matching theme. If an update rearranges things, follow our steps for a Neve update that broke the layout, and the general advice on a theme that broke after an update covers the rollback.

Getting the Neve hamburger to respond again

1. 1

   Capture the failure honestly

   Open the page on an actual phone in a private tab, signed out, ideally on mobile data. Note which of the four patterns you see. Desktop device emulation keeps your login and cache state, so it often passes while customers fail.

2. 2

   Switch off script optimization

   In SiteGround Speed Optimizer, WP Rocket, LiteSpeed Cache or whatever you run, disable JavaScript combine, defer and delay. Purge every cache layer, including any separate mobile cache, and retest. If the menu returns, re-enable one option at a time and exclude Neve's frontend.js from the one that breaks it.

3. 3

   Test the CSS cleanup

   If the X appears without a panel, switch off remove-unused-CSS or critical-CSS generation and retest. If that fixes it, add is-menu-sidebar, header-menu-sidebar and the classes beginning menu_sidebar_ to the tool's safelist instead of leaving the feature off.

4. 4

   Read the console

   Connect the phone to a desktop browser's remote debugging, reload, and read the console. An error names its file. If the file belongs to another plugin, fix that plugin or exclude it from combining.

5. 5

   Check the panel settings

   In the header builder's mobile view, select Mobile Sidebar and confirm Open Behavior. Select the Primary Menu inside it and decide whether 'Expand first level of dropdowns when menu is in mobile menu content' suits your menu. Publish.

6. 6

   Update on staging

   Bring Neve to 4.2.15 and Neve Pro to its current matching release on a staging copy, purge, and repeat the phone test before touching the live site.

7. 7

   Retest the edges

   Check widths just under and over 960 pixels, rotate a tablet, and tap through a submenu and an anchor link. Neve closes the panel when a link to a section of the same page is tapped, which is intended.

Keeping the menu alive after the next speed tweak

Repeat failures usually trace back to one habit: somebody tunes speed on the live site, checks the homepage on a laptop, and calls it done. The menu breaks on phones that evening and nobody notices for a week. A short set of rules prevents most of it.

• Write down every exclusion you add to an optimizer, with the reason, somewhere the next person will see it.
• Run one optimization plugin. A host plugin and a second caching plugin both rewriting scripts doubles the odds of a collision.
• After any update to Neve, Neve Pro or an optimizer, tap the menu on a real phone, logged out.
• Keep third-party widgets few, so the load event, and with it the menu, arrives sooner.
• Use uptime and form monitoring, or our free website health check, so customers are not your alarm system.

If the menu opens but feels sluggish, that is a speed problem rather than a breakage. The Neve speed guide covers what competes with the menu on a phone's main thread, and WordPress mobile menu not working explains the same failure across other themes.

When the menu is the canary for the whole stack

Neve's menu script is small and depends on nothing. When it breaks, something else almost always rewrote, delayed or stripped it. That is a fair summary of many WordPress sites in 2026: a capable theme surrounded by tools that each change the page after the theme has finished with it. Our Neve review gives the theme its due. The fragility lives in the arrangement.

Neve's most fragile feature is whatever the speed plugin did to it last night.

On a Next.js site the menu is a component in one codebase, built and tested before deploy, with no plugin rewriting it afterward. That costs more up front and needs a developer for structural changes. Neve vs Next.js sets out the trade, and moving a Neve site to Next.js explains the process, with editing in Athena CMS. To keep Neve, our theme troubleshooting service finds the failing piece on a copy of your site, and the Neve repair hub and troubleshooting section cover neighboring faults such as Neve CSS not updating.