WP Rocket works fine with SiteGround hosting
How can I use Google Core Web Vitals to optimize my WordPress
Divi increases the speed of your visual layout
How to collapse and expand text at will within content in Wordpress
How to modify Astra theme settings for pages and posts in batch instead of one by one
How to organize meetings with Zoom video calls from a WordPress website
How to set a minimum and maximum order in your WooCommerce store
How to change the order of Divi submenu items
How to remove all Divi shortcodes when changing themes
How to auto link to WooCommerce product tabs from short description
How to add a custom message when paying in WooCommerce according to the selected country
How to fix critical WordPress error
How to turn off the default animation on Divi image galleries
SiteGround has been incorporating improvements in its services, such as the migration from cPanel to Site Tools or the use of the Google Cloud CDN network, all accompanied by 3 levels of cache (static, dynamic, Memcached).
For its part, WP Rocket, being a plugin independent of the hosting, performs cache based on the file system, as it cannot access the memory systems of the hosting.
With both systems active, if someone visits the web first it will load the server cache, from NGINX, and if it is not available then it will load the file cache from WP Rocket.
But the reality is that if you have the WP Rocket cache active, neither the dynamic cache nor the SiteGround Memcached will work, only the direct delivery of static from NGNIX.
This is because only a plugin can add its code to the advanced-cache.php and object-cache.php files to manage Memcached and dynamic cache.
In fact, if you activate the file cache of WP Rocket or any other plugin (WP Super Cache, Cache Enabler, etc.) the SiteGround SG Optimizer plugin automatically deactivates its dynamic cache and Memcached, even if you insist on activating it in the settings plugin or Site Tools panel of the hosting.
Are WP Rocket and SiteGround optimizations compatible?
Another big problem when using WP Rocket in conjunction with SG Optimizer, SiteGround's optimization plugin, is that both offer similar optimizations, which overlap, and can ruin your website.
These matching features are:
- GZIP compression (automatic in both plugins)
- Browser cache (automatic in both plugins)
- Minimized HTML, CSS and JS (manual)
- Remove query strings from static resources (manual)
- Disable emojis (manual)
- Optimize Google fonts (manual)
- Lazy loading of media (manual)
- Heartbeat control (manual)
- External DNS Preload (Manual)
- Scheduled database optimization
Now, one and the other have characteristics that the other does not have.
- PHP version change
- Force HTTPS
- Automatic image optimization
- Free CloudFlare integration
- Free WebP Image Creation
- Integrated PageSpeed test
- Critical CSS creation
- Cache expiration
- Cache for mobile
- Cache for connected users
- Disable WP Embeds
- Cached link preload
- Optimizations for Facebook, Varnish and CloudFlare pixel
- Show YouTube image on lazy loading
Can WP Rocket be used on SiteGround?
Of course, yes, I myself have WP Rocket active on several client sites hosted on SiteGround, and SG Optimizer and WP Rocket functionalities coexist.
What you have to keep in mind when both coexist is that ...
- Each website is different, and in one only SG Optimizer and its 3 cache levels will work better and in others the combination with WP Rocket, it depends on the type of content and needs.
- You should never have overlapping optimizations active.
- WP Rocket's minimized works best with lightweight themes like GeneratePress or GeneratePress, SG Optimizer's minimized is more effective with themes like Divi or layout designers like Elementor.
- Always use SG Optimizer database optimization, not WP Rocket. Remember, you are on SiteGround.
- Disable the cache of mobile devices and connected users in WP Rocket, because they can cause problems with SiteGround caches.
Date update on 2021-02-17. Date published on 2021-02-17. Category: Computer class Author: Oscar olg Fuente: ayudawp