Is there any point in ispmanager caching and compression?

Question

CMS

If one of the caching plugins is WP-optimize or WP-Rocket or autooptimize . Should I enable server side caching and compression in ispmanager? And does this compression make sense or is it just a burden and extra weight? Or is it better to disable the plugin and leave it on the server?

Answer 1

Yes, enable these options in the ISP.
And set the caching time on the browser side to 365 days.
Then add commands to htaccess to cache certain types of files.
The site will work faster for those who visited it before (no need to load data - you can take it from the browser cache) and the most important thing for which they actually do it - gives about 10-20 (sometimes even more!) Parrots in Google Pages Speed with such simple manipulations.
Your caching plugins will also increase it a little, but on the other hand. And the most important thing that plugins do is reduce the load on hosting for new visitors (who do not have saved parts of the site in the browser) and speed it up by returning static hundreds of times.
Therefore, I recommend enabling the plugin and the settings in the isp panel too.
And check in Google PS, before and after.

Answer 2

Server-side caching and compression in ispmanager is static caching and gzip compression in nginx.
Caching in plugins is page-level caching based on files.
Conclusion for you:
Hire an admin on a quark (for a maximum of 2 hours), he will sort out your zoo and leave what is needed.