Deleting the plugin causes problems of performance & Pagespeed Warnings

Cache Enabler affects your web performance. Uninstalling it can reduce your performance as it’s no longer in use. Uninstalling Autoptimize can also do this as it handles quite a bit. However, there are very few grades actually affected by Cache Enabler that I’m aware of. When Cache Enabler is removed your website would return to the same performance levels when Cache Enabler wasn’t installed. There are no permanent changes.

The Lighthouse grades that would be affected by Cache Enabler that I’m aware on the top of my head is first reducing the initial server response time (because your page being tested could be cached by Cache Enabler). Additionally, Cache Enabler can deliver images in the next-gen format (WebP). Everything else is not applicable to Cache Enabler.

Cache Enabler does clean up files added by during the activation when the plugin is deactivated: https://www.keycdn.com/support/wordpress-cache-enabler-plugin#what-is-performed-when-cache-enabler-is-deactivated

Cache Enabler will clean up the database when the plugin is uninstalled (deleted): https://www.keycdn.com/support/wordpress-cache-enabler-plugin#what-is-performed-when-cache-enabler-is-uninstalled

If the plugin is manually removed then those disk and database cleaning procedures won’t take place.

Hi, is it possible there’s a bug? Scores are just too low (they used to be higher even without the plugin). For some reason it seems it didn’t clean up properly after deleting it normally… As I initially deactivated/deleted CacheEnabler in tomastestart.com in order to use a Cloudlfare plugin. Afterwards I deleted the CacheEnabler plugin in otzerling.com and casued the same issues. Tried reinstalling Cache enabler but it doesn’t help, I can’t get scores as they were before deleting/reinstalling it.

No, that wouldn’t be the case. This isn’t related to Cache Enabler. Even if the advanced-cache.php file is left behind that would not cause what you’re describing. The advanced-cache.php file is a simple drop-in PHP file that is included early by WordPress. It allows caching plugins, like Cache Enabler, to implement certain behavior at an earlier point than when the plugin itself would normally be instantiated. In the case of Cache Enabler the advanced-cache.php file requires Cache Enabler to be installed. Without it the advanced-cache.php drop-in file will not do anything.

Improving the Lighthouse score is rather straightforward. Follow the recommendations and a higher score can be achieved.

Improving the Lighthouse score is rather straightforward. Follow the recommendations and a higher score can be achieved.

I’m only referencing it as an indicator of something unwanted going on.

I’m afraid I only know how to replicate the issues, is there any way to verify everything is ok with Cache enabler? If yes maybe a conflict with another plugin? I don’t know, but I’m certain something is happening.

• This reply was modified 3 years, 6 months ago by snippet24.
• This reply was modified 3 years, 6 months ago by snippet24.

Usual scores used to be around 68 mobile for otzerling.com, and now is 50 average which started happening consistently after deactivating and deleting the plugin. This was the only change. And reinstalling it doesn’t generate the usual scores (which also doesn’t make sense).

• This reply was modified 3 years, 6 months ago by snippet24.
• This reply was modified 3 years, 6 months ago by snippet24.

Maybe I could try manually removing the plugin data to see if that fixes the issues?
If yes can you indicate what should I remove? otzerling.com’s seo is affected by bad mobile scores so is critical for me to fix it.

This will not affect anything. As mentioned a couple times now Cache Enabler will not cause what you’re describing. However, if you want to manually remove the plugin data all that exists is the following:

• Disk: wp-content/plugins/cache-enabler
• Disk: wp-content/settings/cache-enabler
• Disk: wp-content/cache/cache-enabler
• Disk: wp-content/advanced-cache.php
• Database: <prefix>_options table > option_name > cache_enabler
• Database: <prefix>_options table > option_name > _transient_cache_enabler_cache_size
• Database: <prefix>_options table > option_name > _transient_timeout_cache_enabler_cache_size

Just a reminder this is all handled automatically when the plugin is deactivated and uninstalled.

Thank you!! will check them to be sure.

Found so far these files after deleting the plugin in tomastestart.com:
1. wp-content/cache/cache-enabler/www.tomastestart.cl/https-index.html
2. wp-content/settings/cache-enabler/www.tomastestart.cl.php
Found nothing in the database at least but I did find this in wp-config so there may be more left overs after all.

/** Enables page caching for Cache Enabler. */
if ( ! defined( 'WP_CACHE' ) ) {
define( 'WP_CACHE', true );
}

Look no matter how good developed is a plugin chances are there are bugs.

• This reply was modified 3 years, 6 months ago by snippet24.
• This reply was modified 3 years, 6 months ago by snippet24.
• This reply was modified 3 years, 6 months ago by snippet24.
• This reply was modified 3 years, 6 months ago by snippet24.

In case is of any debug use, I created a new WordPress installation with a backup (from before deleting Cache Enabler): https://www.tomastestart.cl/test-back/wordpress/

while tomastestart.cl even despite having render blocking enabled is getting lower scores than https://www.tomastestart.cl/test-back/wordpress/ on average in Pagespeed.

Update: I can tell “reduce server response time ” is still not passed in PS
Please take a look at this:
https://drive.google.com/file/d/1vJ2j3sO4-U7bQHJIL0OHYESrs7wFGK75/view?usp=sharing

https://drive.google.com/file/d/1A0cL87JCY0kQdRX5thvWQJiwT4yi-qTT/view?usp=sharing

Oops, I did forget to mention another disk related operation in my previous reply, which was the WP_CACHE constant in the wp-config.php file. You’re really searching in the wrong place though. You’ve had this explained by myself as well as another developer in a different support thread. While having a static cached page delivered by your origin server can reduce the initial server response time, it doesn’t magically make your origin server fast. You will still need to optimize this as much as possible.

Okey, really aside from PS scores which sometimes is variable/debatable., the issue I had observed is that after deleting Cache enabler there were some leftovers which should had been deleted by the plugin. No idea why as you have stated those should be cleaned automatically.

Update: I may have found whats going on.. let me confirm it and I will post here. Thanks for the patience.

The only way those files above would not be removed automatically is either if a hidden file was somehow created, which would not come from Cache Enabler, or due to the server permissions.