Optimocha

@ertott this is an interesting case, for sure.

May I ask you to edit one line of code to see if it fixes things? If you can, I need you to deactivate SBP and then open the following file:

/wp-content/plugins/speed-booster-pack/includes/classes/class-sbp-lazy-loader.php

And go to line 37:

wp_enqueue_script( 'sbp-lazy-load', SBP_URL . 'public/js/lazyload.js', false, '17.7.0' );

And change the line with the following:

wp_enqueue_script( 'sbp-lazy-load', SBP_URL . 'public/js/lazyload.js', false, '17.7.0', true );

After saving the file, clear the cache and try again, see if Firefox handles lazy-loading better this time.

Alternatively, you can try disabling every SBP option except for lazy loading and see if it’s fixed. If it helps, then we can deduce that another feature of SBP is conflicting with the lazy loading feature.

@mgilbertson thank you so much! Just released version 4.5.4 for everyone.

Hi @mgilbertson,

Thank you for the thorough explanation! We actually fixed this in v4.5.4 which will be released soon. You can give it a test by downloading the ZIP file here: https://github.com/optimocha/speed-booster-pack/archive/refs/heads/development.zip

If you don’t want to upload the development version, you can test if the fix works by adding the following line:

if( ! get_option( 'sbp_activation_redirect' ) ) { return; }

…right under line 148 in the speed-booster-pack/admin/class-speed-booster-pack-admin.php file. After doing so, it will look like this:

View post on imgur.com

In our tests, this fixed all AJAX-related redirect issues. I hope it fixes your issues as well, and we’ll release the fix as soon as this weekend!

@sassie we released v4.5.2 yesterday, hope you update and it fixes the issue! 🙂

Thank you for your kind words, @spiralofhope2 🙂 If you have any comments on how to improve Speed Booster Pack, don’t hesitate to let us know!

Thank you for your kind words, @yozell 🙂 If you have any comments on how to improve Speed Booster Pack, don’t hesitate to let us know!

Hey @zabavljaev, tested it myself and can confirm the issue. Like the video lazy-load issue, we will fix this on v4.5.0 which will be released by the end of this month.