wpmansour

@iscomputerman, high PHP-FPM usage could be caused by excessive caching or database operations. You might want to try reducing the cache lifespan or disabling certain features like minification to ease the server load.

@jakezehn, your approach of manually clearing the cache directory and setting a smaller cache window is a solid solution. Reducing the cache lifespan to ensure regular purges is key for avoiding the cache growing too large.

For both of you, if the issues persist, consider adjusting the cache settings or disabling unnecessary features temporarily to balance server load. Feel free to start a new thread if you need more specific guidance!

Hey @jennygw,

Thanks for sharing those PageSpeed results! I see the desktop performance is solid, but mobile needs a little tweaks. No worries, though—since you’re already using WP-Optimize, we can fine-tune a few things to boost that mobile speed!

One of the first things I noticed is the large image slowing things down. You can use WP-Optimize’s WebP image conversion option under the “Images” tab. This will help compress the image without losing quality, making it load faster. Also, try using the Preload Largest Contentful Paint image option, which will tell the browser to load that key image earlier.

Since JavaScript is blocking the page from loading quickly, head over to the Minify tab in WP-Optimize. Here, you can enable JavaScript and CSS minification and merging, which reduces the file size and the number of requests your site makes. You can also enable asynchronous loading of scripts, which ensures that essential content shows up before the non-essential JavaScript files.

Also, don’t forget to check the Caching tab to make sure page caching is enabled and set up properly. WP-Optimize offers advanced caching features that will keep your pages loading fast, especially for mobile. You can enable it and even fine-tune it by excluding specific URLs from being cached, if needed.

Lastly, if you haven’t already enabled lazy loading under the “Images” tab, I recommend turning that on. This will make sure images only load when they’re about to appear on the screen, which can be a big help for mobile users with slower connections.

Let me know how it goes or if you need any help adjusting these options.

Thanks!

It appears there may be some server-related issues causing the 403 Forbidden error when trying to access your website. I recommend reaching out to your hosting provider or checking your server logs for further insights.

If the issue isn’t server-related or you suspect WP-Optimize might be contributing, please feel free to contact our dedicated support team. As a premium user, you have access to priority support. You can submit a request here: WP-Optimize Premium Support, and our team will assist you promptly.

Yes, you’re absolutely correct. Once you press the “Mark all images as uncompressed” button with the “Create WebP version of image” option enabled, WP-Optimize will treat those previously compressed images as new and will re-compress them, and create the WebP versions at the same time.

So by pressing that button, the previously compressed images will indeed be re-processed with both compression and WebP creation!

Sure, Let me break it down for you:

1. Auto Compression and WebP: Yes, you can enable both the auto-compress and Create WebP version of images options at the same time. When you upload new images, WP-Optimize will first compress them and then create a WebP version, giving you even smaller file sizes without sacrificing much quality. So, ticking both boxes is a good idea if you’re looking to save more space!
2. Batch Conversion of Existing JPGs: To batch convert your previously compressed images to WebP, you don’t need to worry about re-optimizing all the images. Simply selecting the “Create WebP version of image” will convert all the images that have already been optimized to WebP format.

However, if you want to re-optimize all your images (and also create WebP versions for them again), you can go to WP-Optimize → Images and click “Mark all images as uncompressed”. This will let you re-optimize the images, and the plugin will handle the compression and WebP conversion as needed.

Hope that helps : )

Glad to hear that. You’re welcome : )

Thank you for reaching out and providing detailed information about the issue you’re encountering with WP-Optimize and Wordfence. It’s great that you’ve already done some research and server checks!

From what you’ve described, this seems to be a case of a false positive from Wordfence, especially since the flagged files are minified JavaScript files generated by WP-Optimize and not PHP scripts or actual malware. Wordfence may have detected the “alexusmailer” string because WP-Optimize caches or minifies files that may have had URLs containing suspicious terms in them. It’s important to note that caching tools like WP-Optimize can include the URLs in cached files, and these might trigger certain security plugins as you observed.

Here are a few steps to consider:

1. Exclude the WP-Optimize cache folder: Since Wordfence is flagging files in the /wp-content/cache/wpo-minify/ folder, you could configure Wordfence to exclude this folder from its scans. This should prevent further false positives without affecting your site’s security.
2. Check the cache setup: WP-Optimize does indeed cache and minify static files, and depending on how the URLs are formed (e.g., via bots requesting unusual URLs), these might get cached and minified, leading to the inclusion of those strings. It’s not unusual for bots to scan for vulnerable paths, but as long as those scripts don’t exist on your server (which it sounds like they don’t), there’s no active threat.
3. Cloudflare and external bot requests: Given your finding of bot requests in Cloudflare logs, it’s likely a case where external bots are hitting your site, but since Wordfence didn’t log any malicious activity beyond the flagged files, your site’s core security seems intact.

As a precaution, you might also want to clear the cache from WP-Optimize and ensure the minification process doesn’t include unwanted elements from external bot requests.

Let me know if excluding the folder resolves the issue or if you need further assistance!

Best regards,

Hi @webprom,

Thank you for bringing this issue to our attention. I was able to replicate the problem you described: the “Compress” button in the image library popup from the block editor is unresponsive, but it works fine when accessed through the Media Library directly.

I’ve escalated this to our development team for immediate resolution. I’ll keep you posted with any updates as we progress. I truly appreciate you for taking the time to report this!

Thanks again!

Yes, WP-Optimize is designed to clear and rebuild the cache when certain changes are made to your site, including URL or slug changes, particularly with multilingual plugins like WPML. When a product URL is modified, the cache is invalidated to ensure that the newly updated pages are correctly cached, which can sometimes trigger the behavior you described — the cache clearing and rebuilding from scratch.

It seems like the manual changes to product URLs were indeed the cause of the cache reset loop. I believe that now the URLs have stabilized, the caching should function normally without further interruptions. However, if the issue persists, please let us know, and we can assist you with further troubleshooting.

It appears that the render-blocking error you’re experiencing could potentially be caused by a security plugin or firewall, which may be restricting certain resources from loading as expected.

Could you please try temporarily disabling any security plugins or firewalls you have in place and then check your site again?

Hello,

Let’s go through your concerns:

1. Deactivating WP-Optimize: Deactivating WP-Optimize should not break your website or cause errors, but you may notice some performance impacts:
   • Caching: If you’ve enabled caching through WP-Optimize, deactivating the plugin will stop it, which could lead to slower page loads until the cache is rebuilt.
   • Database Cleanup: Any database cleanup or optimizations made will remain intact, so no need to revert any changes. Deactivation will simply stop any automatic cleanups you’ve scheduled.
   • Image Compression: Image compressions are permanent, so those changes won’t be lost.
   • Minification: If you’ve enabled CSS/JS minification, deactivating WP-Optimize will stop this, which could result in minor layout changes. You can easily reactivate the plugin if needed to restore these optimizations.
   Overall, you can safely deactivate WP-Optimize for troubleshooting without needing to revert anything, though you might experience some temporary performance differences.
2. Impact on CRON Jobs: WP-Optimize generally doesn’t interfere with CRON jobs, but certain database cleanups could potentially affect scheduled events if there’s a conflict with another plugin. The error you mentioned (action_scheduler_run_queue) seems to be related to a plugin like WooCommerce that uses the Action Scheduler library. Deactivating WP-Optimize temporarily might help you determine if it’s contributing to the issue.
   • If the error persists after deactivation, check other plugins that manage scheduled tasks (like WooCommerce or UpdraftPlus) to pinpoint the source. You can also use a plugin like WP Crontrol to manage and debug CRON events.

Feel free to reach out if you need further assistance. Good luck with troubleshooting!

WP-Optimize has a cache lifespan setting that determines how long cached pages are stored before being refreshed. If this lifespan is too short, the cache might be clearing out and starting over repeatedly, which could explain the looping behavior you’re seeing (caching 50 files, then the cache resets to 0).

Here’s what to do:

1. Go to WP-Optimize > Cache settings.
2. Adjust the Cache lifespan to a longer period (e.g., 24 hours or more).
3. Make sure that the Schedule preloader is set to Same as cache lifespan. This ensures that the cache preloading process is in sync with the cache lifespan and doesn’t start clearing and rebuilding the cache prematurely.

This combination should help resolve the issue and allow the cache to build up and function properly.

Looks like there might be a typo in the path. Can you try using this corrected path:
/wp-content/plugins/borlabs-cookie/assets/javascript/borlabs-cookie.min.js
After that, please clear all caches, including any CDN cache if you have one, and see if that resolves the issue.

Hi there! It sounds like you’re running into an issue with saving the cache configuration file due to permissions. Don’t worry, there’s a solution! You can actually change the location where WP-Optimize stores this configuration file to a folder that’s writable for your setup.

To do this, you’ll need to add a small tweak to your wp-config.php file. Simply define a new path for the cache config like this:

define('WPO_CACHE_CONFIG_DIR', '/wp-content/uploads-shared/plugins/xxxx/');

Just replace that path with the directory you’d like to use—make sure it’s a location that has the proper write permissions. Typically, folders should be set to 755 and files to 644 to ensure everything runs smoothly.

After making this change, you can test it out by saving the cache settings again in WP-Optimize, and it should now write to your chosen directory. Hopefully, that helps resolve the issue!

Noted! To investigate further and identify what’s triggering the cache purge, I’d appreciate it if you could provide the site’s error log. This will help us pinpoint the exact issue. Please update your wp-config.php file by adding or modifying the following lines:

define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);
define('WP_DEBUG_DISPLAY', false);

This will create a debug.log file in your wp-content directory, where any errors or notices will be logged. Afterward, you can access this file and open it with any text editor to review the recorded events. If you could share the relevant portions of the log here via a service like Pastebin, it would be extremely helpful for us to pinpoint the issue and assist you further.