Skip to content

Black Friday 50% off your first year on all premium plugins and the Suite.

See the deals

Divi mobile menu needs two taps

Delaying JavaScript boosts Divi PageSpeed scores but can make the mobile menu need two taps. Why it happens and how to fix it without losing the gain.

3 min read · Updated 8 November 2026

“Delay JavaScript until user interaction” is the single biggest PageSpeed win on most Divi sites. It is also behind a familiar complaint: on a phone, the hamburger menu does nothing on the first tap, opens on the second, or opens after a pause. Toggles, tabs and sliders can behave the same way. Here is why, and how to fix it on any caching or optimisation plugin.

For what to delay, what never to delay and the full touch test, see Delay JavaScript on Divi safely.

Why the first tap is lost

Delaying means scripts are not downloaded until the visitor scrolls, moves the mouse or touches the screen. The menu’s click handler lives in one of those scripts. On a phone the visitor’s first touch is the tap on the menu — so that tap starts loading the scripts, and by the time the handler exists the tap is over. Divi makes this more likely because its menu, toggles and animations are driven by its main script and jQuery; if either is delayed, everything that depends on them waits.

The fix, step by step

  1. Keep jQuery and Divi’s own scripts out of the delay. They should be deferred (loaded without blocking the page) but not delayed. In most plugins this is an “exclude from delay” list; add jquery, /themes/Divi/ and et-core. If you use a child theme with its own menu script, add that too.
  2. Turn off Divi’s own script options. In Divi → Theme Options → Performance, switch off Defer jQuery And jQuery Migrate, Load jQuery In Body and Minify And Combine JavaScript Files when another plugin handles scripts. Two tools deferring and combining the same files is a classic cause of a dead menu.
  3. Use only one delay feature. If your host’s cache, a separate “flying scripts” plugin and your optimisation plugin all delay scripts, pick one.
  4. Replay the first tap. Better tools remember a tap made before scripts arrived and replay it afterwards, so the menu opens on the first tap after all.
  5. Keep the menu styled from the start. If critical CSS is generated automatically, make sure the mobile menu’s open-state classes (et_mobile_menu, mobile_nav) are kept in the critical part, or the menu opens unstyled.
  6. Test properly. Open the page fresh on a real phone (or a private window with device emulation) and tap the menu immediately, before scrolling. That is the case that breaks.

How TurboCache handles it

TurboCache is built around this problem, so its defaults already do most of the above:

  • jQuery, jQuery Migrate and Divi 4 and Divi 5 core scripts are built-in critical scripts: deferred, never delayed.
  • The first click or tap before scripts load is replayed afterwards (250 ms by default), and the Divi sticky / menus and Divi core shims re-initialise menus and modules once delayed scripts arrive.
  • Divi menu and mobile-menu classes are on the Always critical CSS list.
  • Self-diagnostics flags Divi’s conflicting performance options and turns them off in one click.

If a menu still needs two taps, it is usually a third-party menu or header plugin. Add part of its script file name to Critical scripts on Scripts and styles. If only one page has the problem, use a content group to switch off delay for that page alone. More symptoms and fixes: Layout or scripts broken after optimisation.

Frequently asked questions

Will excluding jQuery from delay hurt my PageSpeed score?

A little, but far less than you might expect when jQuery is still deferred. Most of the delay gain comes from third-party scripts such as analytics, chat and social widgets, which stay delayed.

Why does the Divi menu work on desktop but not on mobile?

On desktop the mouse moves before the visitor clicks, which triggers the delayed scripts early. On a phone the first touch is often the tap on the menu itself, so the scripts are not ready yet.

Should I use a timeout for delayed scripts?

A timeout of a few seconds loads delayed scripts even without interaction. It helps visitors who never touch the page, but it does not fix the first-tap problem; keeping menu scripts critical does.

Does this also affect Divi toggles, tabs and sliders?

Yes, the cause is the same. Keeping Divi’s core scripts critical and keeping their state classes in critical CSS fixes all of them.

Did this answer the question? No — open a support request