WoodMart Mobile Menu Not Working: Start With the Header Nobody Checked

Six ways a WoodMart store loses its phone menu

Shoppers rarely report a broken menu. They leave. The owner finds out weeks later from a sales dip on mobile, or from a nephew who tried to buy a lamp. On WoodMart the failure takes a handful of recognizable shapes, and each one points at a different part of the theme.

• No hamburger at all. The phone header shows a logo and a cart, but nothing to open.
• The icon is there and does nothing. It may animate, but no drawer slides in.
• The drawer opens with the wrong links. Every page on the site appears, or last season's menu.
• Mega menu content is missing. The image columns and promo blocks from the desktop dropdown never appear on the phone.
• The first tap is ignored. A second or third tap finally opens it, usually after a pause.
• It works on a phone but not on a tablet. Or it works held upright and fails turned sideways.

If your theme is not WoodMart, or you want the mechanism across themes, the general mobile menu guide covers it. Everything below is specific to WoodMart's Header Builder, its menu locations and its bottom navbar.

Two layouts per header, and a 1,024 pixel line between them

The Header Builder lives under WoodMart > Header builder. Open any saved header and the editor toolbar has Desktop and Mobile controls. WoodMart's docs put the line at 1,024 pixels: the desktop layout appears at 1,025 pixels and wider, the mobile layout at 1,024 and below. That means many tablets get the phone header, which surprises owners who only tested on an iPhone.

The two layouts do not share elements. The docs say plainly that adding something to one layout does not add it to the other. The phone version needs its own Mobile menu element, and each row has Hide on desktop and Hide on mobile switches that can remove a whole row from one device range. Row heights are set separately per device too, so a mobile row squeezed to a sliver can hide an icon that is technically there.

The links inside the drawer come from WordPress, not from the builder. Under Appearance > Menus > Manage Locations, the menu assigned to Mobile Side Menu is the one the drawer shows. Leave that location empty and WoodMart falls back to the main menu, which on a big store means every category, subcategory and landing page in one long scroll. The Mobile menu element can also show a second tab through Show categories menu, with Choose menu to pick it and Swap menus to change their order.

Suspects in the order they turn up on WoodMart stores

Check the first three in the Header Builder before touching any plugin. They cost nothing to rule out, and a drawer that never existed in the mobile layout looks exactly like a broken one. For anything that shows red in the console, the JavaScript errors guide explains how to read it.

Script optimizers and the tap that waits its turn

Speed plugins that delay JavaScript until the visitor interacts are popular because they make test scores look better. They also hold back the code that opens WoodMart's drawer. In a September 2025 reply on the vendor's support forum, xtemos staff described exactly this: with WP Rocket's Delay JavaScript Execution on, the first tap starts loading all the delayed scripts at once, and that load is the lag. They added that excluding a few files does not cure it, because there are still many files to load.

So the honest choice is a trade. Let the theme's scripts load normally and the menu answers on the first tap, at some cost to the lab score. Keep the delay and accept that impatient shoppers tap twice. What you should not do is run two optimizers that both rewrite scripts, or combine WoodMart's per-page files into one bundle, which can change the order the menu's code depends on. The vendor already loads assets per page, by its own account, so a second layer mostly adds risk.

Interaction delay is also what Google's INP metric measures, so a menu that waits is a score problem as well as a sales problem. The WoodMart speed guide covers the Performance settings, and WordPress vs Next.js on INP explains the metric.

Restoring the WoodMart phone menu, step by step

1. 1

   Find out which header the broken page uses

   Open the page's settings and look for Custom header for this page, then check Theme Settings presets for conditions that match it. Fix the header that actually prints, not the default.

2. 2

   Open that header in Mobile view

   In WoodMart > Header builder, edit the header and press Mobile in the toolbar. Confirm a Mobile menu element sits in a row without Hide on mobile, with a row height that leaves room for the icon.

3. 3

   Assign a menu built for thumbs

   Create a short menu of top categories and key pages and assign it to Mobile Side Menu under Appearance > Menus > Manage Locations. Add a categories tab with Show categories menu only if it helps shoppers.

4. 4

   Decide what mega menu content phones get

   HTML Block submenus are off in the mobile menu by default. Turn on Show HTML Blocks only for content you have tested on a small screen; plain links usually serve better.

5. 5

   Save and purge

   Press Save header, then clear the caching plugin, the host cache and the CDN, in that order.

6. 6

   Test without the optimizer's script features

   Pause delay, defer and combine options, load the page on a real phone and tap once. If it now works, bring the options back one at a time.

7. 7

   Check the console and plugins last

   If it still fails, connect the phone to desktop developer tools or use a staging copy, read the first error, and disable plugins one by one until it clears.

Keeping the drawer working after the next update

• Edit menus in two places on purpose. A new category added to the desktop menu is not automatically in the Mobile Side Menu. Put both on the same checklist.
• Test at the breakpoint, not just on your phone. Try 1,024 pixels and a tablet held both ways, since that is where WoodMart swaps layouts.
• Retest after every theme, WoodMart Core or optimizer update. Menu scripts are exactly what optimizers rewrite. WoodMart update problems covers version mismatches between the theme and Core.
• Keep one owner for scripts. Either the theme's per-page loading or a plugin's rewriting, configured once and written down.
• Keep the phone header lean. Every icon and dropdown in the mobile layout is code that runs on the slowest devices your customers own.

A heavy mobile header is also a speed problem. WoodMart slow website looks at mega menus and mobile layouts as page weight, and the WoodMart repair hub collects the store-side faults. If the header itself vanishes rather than its menu, go to WoodMart header not showing.

A menu with four owners and no referee

Look at who is involved in one tap. The theme draws the icon. WoodMart Core, the required companion plugin, has to match the theme's version. WordPress holds the menu. A speed plugin decides when the script runs, a cache decides which copy of the page arrives, and any other plugin can throw an error that stops everything after it. Each vendor tests its own part. Nobody tests your combination except your customers.

That is the case for a built site. In Next.js the menu is a component in one codebase, tested in a build before it goes live, with no plugin rewriting its script afterward. It costs more up front and needs a developer for structural changes. WoodMart vs Next.js weighs it for store owners, and moving a WoodMart store to Next.js explains what has to be rebuilt. If you would rather keep WoodMart and hand the menu to someone, our theme troubleshooting service fixes it on staging first. The WoodMart review has the wider picture, and every theme's fixes are listed in the troubleshooting section.