OceanWP fix
OceanWP Mobile Menu Not Working? Why It Won't Open, Close or Show
The menu icon is there. You tap it and nothing happens, or the menu opens and refuses to leave. OceanWP's mobile menu is drawn by the theme's own JavaScript and governed by a handful of Customizer settings, so the cause is nearly always a script that did not run or a setting pointed the wrong way. It is a small icon to lose a customer over.
571 taps on the menu icon did nothing. The theme's script was delayed for logged-out visitors.
What you are seeing
- Tapping the menu icon does nothing
- The menu opens, then will not close or scroll
- No menu icon appears on phones or tablets at all
- The desktop menu wraps onto two lines on a tablet
- Submenus will not expand, or parent links cannot be tapped
Why it happens on OceanWP
Most common first.
- 1
A cache plugin delayed or combined the theme's script
The mobile menu opens when OceanWP's JavaScript hears the tap. Plugins that delay, defer or combine JavaScript can hold that script back or load it out of order, so the icon sits on the page with nothing listening. It still works for you, because most caches skip logged-in users, which is why owners so often cannot reproduce the fault.
- 2
A script was switched off in the Theme Panel
Ocean Extra's script and style switches let you stop loading pieces of the theme. Someone chasing a speed score can turn off a piece the chosen menu style depends on. The saving is a few kilobytes and the menu is the price.
- 3
The breakpoint does not suit the menu
OceanWP swaps the desktop menu for the mobile one at a set width, 959 pixels by default, adjustable in the mobile menu settings. A long menu wraps on tablets before the swap happens. A custom breakpoint set too low hides the icon on the very devices that need it.
- 4
A custom header replaced the theme's menu
When the header style is a custom template built in Elementor, OceanWP's own mobile menu and its Customizer settings may not be in play at all. The menu inside that template is a widget with its own mobile behavior, and it has to be fixed in the template.
- 5
The menu opens behind something
A sticky header, an Elementor section with a high stacking order or a cookie bar can sit above the menu panel. The menu did open. You cannot see it, and the page behind it will not scroll.
How to fix it, in order
Least invasive first. Stop at the step that fixes it.
- 1
Test logged out, on a real phone
Open the site in a private window on a phone, not in a narrowed desktop browser while logged in. If the menu fails only when logged out, a caching or optimization plugin is involved and the next step will find it.
- 2
Turn off JavaScript delay and combine
In your caching plugin, switch off the options that delay, defer or combine JavaScript, purge the cache and test again. If the menu returns, turn the options back on one at a time and exclude the scripts in the OceanWP theme folder from the one that broke it.
- 3
Check the mobile menu settings
Go to Appearance, Customize, Header, Mobile Menu. Confirm the style (sidebar, dropdown or full screen) and the breakpoint. If the desktop menu wraps on tablets, raise the breakpoint so the mobile menu takes over sooner.
- 4
Confirm which menu is assigned
Under Appearance, Menus, Manage Locations, the Main location needs a menu. OceanWP also has an optional Mobile location. If an old or empty menu is assigned there, phones show that one in place of your main menu.
- 5
Restore the theme's scripts
Open the script and style switches in the Theme Panel and turn back on anything that was disabled, then retest. Disable items again one at a time only if the menu still works after each.
- 6
Inspect the header itself
If the header is a custom template, edit that template and check its menu widget's mobile options. If the menu opens but hides behind the header or a section, the browser's inspector will show which element is on top, and a z-index rule in Additional CSS settles it.
Keep it from coming back
- After any change to caching settings, test the menu logged out on a phone
- Keep the theme's scripts on the exclusion list of whatever delays JavaScript
- Change script switches in the Theme Panel one at a time, testing after each
- Look at the menu on a tablet whenever you add a menu item
The permanent fix
A faster Next.js build, with a CMS made for your business
A menu that breaks whenever a cache setting changes shows how the site is assembled: the theme draws the menu, a plugin rearranges the theme's scripts to win back speed and the two disagree. On a Next.js build with a custom CMS the navigation is part of the site's own code and ships with the page, so there is no optimization plugin to reorder it. If the mobile menu has failed more than twice, weigh that against another patch.
| On OceanWP today | On Next.js with a custom CMS | |
|---|---|---|
| What you keep updated | WordPress, the theme, its builder and every bundled plugin, all in step | Nothing on a schedule. There is no theme or plugin stack to fall out of step |
| How a page is served | Built from the database on each visit, through the theme and its builder | Built ahead of time and served as finished files from servers near the visitor |
| How you edit it | A general-purpose builder with every option the theme ships | A CMS built around what your business actually changes: services, prices, photos, posts |
| What can break it | An update to any one of those parts, or a license that lapses | A change someone makes on purpose, tested before it goes live |
Your content, your addresses and your rankings come with you: every page is moved, every old address is redirected, and you get a login to an editor that only shows what you need. A repair is still the right call for many sites, and we will say so when it is.
Want this fixed on your OceanWP site?
Tell us what you are seeing. We look at the site, tell you plainly what is wrong and what it takes, and quote a fixed price before any work starts.
Which of these sounds like you? (pick any)
Frequently asked
Because you are logged in. Most caching plugins serve logged-in users an unoptimized page, so the theme's scripts load normally for you. Visitors get the cached version with JavaScript delayed or combined, and that is where the menu's script fails. Always test in a private window.
Under Appearance, Customize, Header, Mobile Menu there is a breakpoint setting. By default the switch happens at 959 pixels wide. Choose a larger custom value if your desktop menu is long and wraps on tablets or small laptops.
This shows up on one-page sites where menu items are anchor links to sections of the same page. No new page loads, so nothing resets the open menu. Update the theme first and test with JavaScript optimization off, then look for a smooth-scroll plugin or snippet that intercepts the same tap.
OceanWP lets you choose what a tap on a parent item does: open its submenu or follow its link. If only the small arrow is set to open the submenu, a tap on the text follows the link. Look for the dropdown target option in the mobile menu settings and set it to suit how your menu is organized.
Keep reading
- ServiceMobile Responsiveness FixesMost of your traffic is on a phone, and that is where most sites fall apart. We fix the layouts, tap targets, and overflow that cost you the sale.
- ServiceFixing WordPress PluginsOne bad plugin can take your whole site down. We fix plugin conflicts, fatal errors, and security holes fast — and build custom plugins when the off-the-shelf ones fall short.
- ServiceWordPress Speed & OptimizationA slow site loses customers before they read a word. We tune WordPress for speed, stability, and search — measured, not guessed.