Optimocha

We’re about to release a fix version (3.8.5.1), but don’t worry, these messages are “warnings” and not “errors” (meaning it won’t break your site but it needs to be fixed). We’re working on the fix and update you here as soon as possible.

@mistacup we’ve released a new version of Speed Booster Pack and we included a function that effectively disables all Speed Booster Pack features while the user is on a front-end page builder, including Divi! Can you test and confirm the issue you were having is resolved with the new version?

Hi @joshyhud,

Technically this isn’t a support-related question but a killer feature suggestion, so I actually marked this as “not a support question”; but I’ll definitely post to this topic once the feature is added. If you want to get a more “personal” notification, you can say hi to us over here and I’ll personally let you know when the feature goes live.

Hi @joshyhud,

Great idea! We’re about to release a new version but I’m adding this feature to the release after that. Thanks for reaching out! (I’d like to return the favor – if you ever need speed optimization services, I can give you a €100 discount code for our speed optimization services.)

@mistacup we found out that enabling the “Disable jQuery Migrate” option is responsible for breaking Divi Builder. If you have that option enabled, can you disable it and try again please?

Edit: We have multiple culprits! ?? Please disable the following options and try again:
– Remove jQuery Migrate
– Enable lazy loader
– Enable instant.page
– Move scripts to footer
– Defer parsing of JS files

Remember that we’ve written a function that disables Speed Booster Pack completely & temporarily while Divi Builder is active.

• This reply was modified 5 years, 1 month ago by Optimocha.

Hi @spikeycactus,

I’m marking this topic as resolved but remember to contact us from our website, like I said earlier:

https://optimocha.com/contact/

Hello @mistacup,

We tested and saw the issue ourselves, and we’re working on a fix. By the end of the month, we’ll release an update to the plugin with that issue fixed. Stay tuned!

@spikeycactus can you send us the link of the website you’re having issues with? If you don’t want to reveal it here, we can talk via email: https://optimocha.com/contact/

Hi @spikeycactus,

Is there any chance that you’re using another lazy loading plugin (or a theme/plugin feature of lazy loading) in your website?

I visited the WP installation on draky.net and it seems the Darkmode button is hidden behind the reCAPTCHA div on the bottom right. You can add the following custom CSS in your Customizer to change the position of the Darkmode button:

.darkmode-layer--button, .darkmode-toggle {
bottom: 64px;
}

• This reply was modified 5 years, 3 months ago by Optimocha.
• This reply was modified 5 years, 3 months ago by Optimocha.

Gotcha! Like I said earlier, you can always contact us so we can further investigate how WooCommerce disables instant.page (if it really does).

@filona hehe, always happy to see people who obsess over speed, even if they don’t use our products/services! ?? I’ll let you know when the beta version of SBP is out.

Hello @filona,

Thanks for using Speed Booster Pack! We’re actually about to release a new version of SBP and we kind of wrote the whole JavaScript optimization feature from scratch. What you said is a known bug (the buggiest part of SBP, to be honest) but things will get better when we release the new version.

We need real-life users to test this feature though; because it was a complete rewrite we expect minor issues with it. Would you be interested in testing the new (beta) version and sharing your experience with us?

@maaw deactivating the option would immediately remove the instant.page script from your front-end; but you need to make sure your caches are cleaned as well. And by cache, I mean caching plugins, plus your own browser’s cache, plus any server-level cache (some hosting companies have that), and any third-party service like CloudFlare or Sucuri.

Hi @maaw,

Since this is kind of a duplicate of the other thread, I’m going to close this one – let’s continue through the other thread.