Title: Security Optimizer + Speed ​​Optimizer problem with cache Last modified: May 21, 2025 --- # Security Optimizer + Speed ​​Optimizer problem with cache * Resolved [Dioni Sánchez](https://wordpress.org/support/users/dioni00/) * (@dioni00) * [1 year ago](https://wordpress.org/support/topic/security-optimizer-speed-optimizer-problem-with-cache/) * Hi team, * We’ve encountered a cache-related issue when both **Security Optimizer** and ** Speed Optimizer** are enabled on our site. * Specifically, URLs that we’ve excluded from caching in **Speed Optimizer** are being ignored, and those pages are still being cached. This is causing problems with dynamic content that should not be cached. * We’ve confirmed that the exclusions are correctly set in Speed Optimizer, and when we disable Security Optimizer, the exclusions work as expected. This leads us to believe there may be a conflict between the two plugins. * Best regards. Viewing 5 replies - 1 through 5 (of 5 total) * Plugin Support [Plamen M](https://wordpress.org/support/users/plamenm/) * (@plamenm) * [1 year ago](https://wordpress.org/support/topic/security-optimizer-speed-optimizer-problem-with-cache/#post-18476681) * Hello [@dioni00](https://wordpress.org/support/users/dioni00/) , * I tested the reported issue on a new instance of WordPress with our Speed Optimizer enabled with all levels of caching, as well as the Security Optimizer plugin enabled. Then, I excluded the /privacy-policy/ page of my test site from being cached. Then I flushed the cache. When testing the results, all other pages of my test site were cached, except for the /privacy-policy/ cache. It was properly excluded from caching. * Here is my test: * `$ curl -I -X GET https://test.****.eu/privacy-policy/ | grep x-proxy-cache x- proxy-cache: **MISS**x-proxy-cache-info: W NC:000000 UP: * but * `$ curl -I -X GET https://test.****.eu/sample-page/ | grep x-proxy-cache x-proxy- cache: **HIT** * I would advise you to temporarily disable the other plugins in your site and then test the URL exclusion again. Remember to purge the cache before your tests. * _[ Please do not spam ]_ * [Renato Gelforte](https://wordpress.org/support/users/spolaorso/) * (@spolaorso) * [1 year ago](https://wordpress.org/support/topic/security-optimizer-speed-optimizer-problem-with-cache/#post-18480943) * I have the same problem. I am using Siteground plugins: Security Optimizer and Speed ​​Optimizer and I am forced to disable Speed ​​Optimizer because it gives me problems with cache. * When enabled, it causes broken CSS menus and other problems. Probably (I think) there is some conflict with Elementor. * Plugin Support [Plamen M](https://wordpress.org/support/users/plamenm/) * (@plamenm) * [1 year ago](https://wordpress.org/support/topic/security-optimizer-speed-optimizer-problem-with-cache/#post-18481257) * Hello [@spolaorso](https://wordpress.org/support/users/spolaorso/), * We have thousands of WordPress clients hosting sites with Elementor and SiteGround’s Performance and Security Optimizer plugins enabled. In most cases, reports related to broken CSS styles are related to third party plugin conflicts. These usually occur with plugins which would not follow the strict coding standards for CSS Styles. * For such cases, instead of disabling a plugin, you may consider excluding the style related to the menu. You can read more at: * [https://eu.siteground.com/tutorials/wordpress/speed-optimizer/frontend-optimization/#Combine_CSS_and_JS_files](https://eu.siteground.com/tutorials/wordpress/speed-optimizer/frontend-optimization/#Combine_CSS_and_JS_files) * Each one of the front en d optimization options allows exclusion of styles. Please, give it a try, as well as trying my suggestion in the previous thread – to temporarily disable the other plugins and enable them one by one. * _[ Please do not spam ]_ * [Renato Gelforte](https://wordpress.org/support/users/spolaorso/) * (@spolaorso) * [1 year ago](https://wordpress.org/support/topic/security-optimizer-speed-optimizer-problem-with-cache/#post-18484709) * Thanks a lot Plamen I managed to fix the problem by disabling “Defer render-blocking JavaScript”.If I disable minification and CSS/JavaScript combinations, nothing changes.After disabling all minifications and combinations, I disabled “Defer render-blocking JavaScript” and the dropdown menus works.The strange thing is that the problem does not occur when I visit the site as a logged-in administrator. * Plugin Support [Preslav Kenanov](https://wordpress.org/support/users/preslavkenanov/) * (@preslavkenanov) * [1 year ago](https://wordpress.org/support/topic/security-optimizer-speed-optimizer-problem-with-cache/#post-18484797) * Hello [@spolaorso](https://wordpress.org/support/users/spolaorso/), * I am happy to hear that you found a way to resolve the issue you have encountered. * As for the absence of the issue while navigating the administrative dashboard of your website, it is actually anticipated. Most caching plugins and solutions are designed to bypass or minimize caching for the admin dashboard. This ensures that administrators always see the most up-to-date information and changes as they are made. * Kind Regards, Preslav Kenanov Viewing 5 replies - 1 through 5 (of 5 total) The topic ‘Security Optimizer + Speed ​​Optimizer problem with cache’ is closed to new replies. * ![](https://ps.w.org/sg-security/assets/icon-256x256.gif?rev=2971855) * [Security Optimizer - The All-In-One Protection Plugin](https://wordpress.org/plugins/sg-security/) * [Support Threads](https://wordpress.org/support/plugin/sg-security/) * [Active Topics](https://wordpress.org/support/plugin/sg-security/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/sg-security/unresolved/) * [Reviews](https://wordpress.org/support/plugin/sg-security/reviews/) ## Tags * [cache](https://wordpress.org/support/topic-tag/cache/) * 5 replies * 4 participants * Last reply from: [Preslav Kenanov](https://wordpress.org/support/users/preslavkenanov/) * Last activity: [1 year ago](https://wordpress.org/support/topic/security-optimizer-speed-optimizer-problem-with-cache/#post-18484797) * Status: resolved