Are you a GenerateCustomer?

Do you have an active GP Premium or GenerateBlocks Pro license key?

Create a GenerateSupport account for GeneratePress and GenerateBlocks support in one dedicated place.

Create an account
Already have a GenerateSupport account? Login

Just browsing?

Feel free to browse the forums. Support for our free versions is provided on WordPress.org (GeneratePress, GenerateBlocks).

Want to become a premium user? Learn more below.

Primary navigation doubled

  • OK, I have excluded wp-content/themes/generatepress/assets/css/main.min.css from Ezoic’s CSS optimization and cleared the Ezoic cache. But I still see the problem with the navigation.

    The problem of the sticky nav could be, that Ezoic’s Core jQuery Feature Preload is active. I had to enable it to solve the LCP problem.

    The link is ok. In wordfence I found a country block list for login attemps and excluded Canada. Please let me know if it works now.

  • I can see the backend now.

    This is a typical issue of CSS being loaded too late.
    Is it really not possible for you to disable the cache?

  • Hi Ying,
    I can’t do without the Ezoic Cache at the moment. The problem has only been occurring since I started using primary navigation. Before I used secondary navigation, off canvas and a third menu, but I changed that for speed reasons because it involved a lot of additional CSS and LCP was bad.
    I could try to define critical css rules if you can tell me what is needed. Or can you suggest a script to preload the required CSS?

  • What I’m wondering is that it never happens on the first load but only when loading further pages. If the CSS would be loaded late, shouldn’t it happen on the first page? Shouldn’t it be in the browser cache afterwards?

  • Hi there,

    the issue stems from how Ezoic is “optimizing” your CSS.
    What it does is gather up all the sites CSS, splits it into what it believes is Critical and Non-Critical CSS. The former it loads as inline CSS in the <head> of your website, so its now part of the main document which will NOT be cached by the browser.

    Unfortunately we are no experts in the way Ezoic does this, its quite archaic and very prone to these kinds of issues. You will need to speak to Ezoic support on how to resolve this.

  • Hi David,
    ok, but the CSS to deal with is content/themes/generatepress/assets/css/main.min.css?

    I opened the topic because on desktop the mobile navigation was hidden late. Is this depending on the same CSS or is it another issue? In a first step I was asked to disable the mobile header and then I saw the other issue. I liked more the mobile header with the navigation logo and the hamburger on the right. When I could re-enable it, I would not need additional CSS.
    Would it be possible to trigger the mobile header with wp_is_mobile?

  • you can re-enable the mobile header, it should not have this issue if the cache isn’t enabled, anyway.

    please talk to your cache plugin’s support and see how to solve this issue.

  • Ok, I defined main.min.css as critical and it works now.
    Thank you 🙂

  • You are welcome!

    We’ve been telling you it’s a cache issue 🙂

  • That is a matter of definition. As far as I have observed, CSS runs through an optimization at Ezoic, but is not cached (in the classic sense that the cache must be purged after a CSS change). Perhaps we have misunderstood each other. But after you pointed out to me that main.min.css is involved, I was able to configure it accordingly.

Viewing 10 posts - 17 through 26 (of 26 total)
  • You must be logged in to reply to this topic.