Pavel Dosev

Hello @generous,

We generate a handler for the style. However it isn’t a static one which you can use. It is dynamically assigned based on the content of the site. The way we generate it is as follows:

$style_hash = md5( implode( ‘’, $content ) );

As the handle will be different when regenerated, adding the data handler is not possible as once it’s regenerated the one you entered before that will no longer be the correct one.

Thus the option to preload the CSS is through our plugin and the option Daniela outlined in the previous reply.

Hello Fernando,

I see that your site is using a theme that has both mobile and desktop versions of the site. One of the menu divs has this class that makes indicates it is hidden by default on mobile:

class=”whb-row whb-top-bar whb-sticky-row whb-with-bg whb-without-border whb-color-light whb-flex-equal-sides whb-hidden-mobile”

This may be causing the problem. If this menu is cached in our dynamic cache and then requested from a desktop browser, the menu will not appear.

We have a setting in the WordPress admin >> SiteGround Optimizer >> Caching >>Browser-specific Caching. Toggling on this setting will create a separate cache for mobile and desktop users, and the problem should no longer occur. After toggling the feature, you must clear your website’s cache and Cloudflare’s cache.

Hello @meljoyl,

I checked the form and when I submit it I see the following error in the POST request response:

Please enable JavaScript in your browser to complete this form. 
The form was unable to submit. Please contact the site administrator

I also see that the form data is collected via Javascript (JS), which leads me to believe that one of the JS optimizations is responsible for this.

You can try disabling them one by one through SG-Optimiser >> Frontend >> Javascript and see which of the features there is causing this.

You can see the available functions here:

https://wordpress.org/plugins/sg-cachepress/

You can clear the cache per URL basis with the function below:

if (function_exists('sg_cachepress_purge_cache')) {
    sg_cachepress_purge_cache('https://yoursite.com/pluginpage');
    sg_cachepress_purge_cache('https://yoursite.com/postname');
}

However, if you update many products, clearing their cache like this and modifying the URL will likely require more adjustments each time you perform the operation. In addition, you may also need to remove other pages’ cache on which the old information is still cached.

Thus based on this, you can see if this is a feasible approach for you, or you can clear the cache for the whole website.

Hello @corytrevor,

Thank you for your feedback, we will pass it to our team responsible for the documentation. I just want to elaborate more about our documentation and why it is written that way.

I want to start by confirming that you are right. The plugin is not saving the page in the browser cache but on the server, in the wp-content/cache folder.

The documentation we wrote in the plugin and on the Siteground website is not meant to be technical documentation, though. Instead, its purpose is to briefly describe the plugin’s functionality and features in an easily understandable manner.

We aim for our descriptions to be less technical and more easily understandable by everyone. The goal is for more people to see and more easily understand the benefit of each feature and what improvement it brings to their website.

Hello @guidotg,

I checked the site, and you should be able to correct this by excluding the class of your slider. This way, however, the slider images won’t be lazy-loaded, but the plugin caches them.

You can go to your admin page >> SG Optimizer >> Media >> Exclude CSS Classes from Lazy Load.

You can add “rsImg” (without the quotes), which will exclude the slider images from our Lazy load, and they will load correctly.

Hello @deputt,

Thank you for your feedback, and I am sorry to hear you are facing issues with the plugin.

Could you please provide us with more detailed information on what the problem was on your end so that we can see if we can replicate it on our end?