The PageSpeed module requires a relatively large amount of power. With our BOXES, this can lead to the module eating up more performance than it can gain through optimization. This is because the website content is compressed, but the compression in turn requires computing power. Thus, the overall loading time of site can suffer from the optimization. This is exactly what happened to us in some cases, especially when the sites was tested under load.
Thank you @eris since that post was written 5 years ago, maybe the PageSpeed Module has got better. I am going to try with a client that has a lot of traffic the small and low risk stuff and I’ll tell you how it went.
Hi guys, thanks for sharing this and i agree that is very interesting. I am testing it now on a test server. My first try with a test website not optimized (a dummy GRAV site) is very promising (perfomance score on lighthouse raise from 70 to 89).
Installation for pagespeed module for apache ran smoothly (just a little issue with google pagespeed repo GPG)
I didn’t touch Nginx nor any other setting on hestia.
Let’s see if someone else has positive tests to share about this.
I did some tests and my conclusion is that enabling mod_pagespeed for Apache on my Hestia setup is pointless.
I tried with 5 websites on producttion env and enabling/disabling the module has a neutral impact on lighthouse score. We don’t use wordpress or joomla or drupal or other mainstream CMS (we do web applications but time to time clients ask to revamp or redo their websites and we use GRAV as CMS) and we achieve the same perfomance score (90 to 100) on lighthouse without pagespeed module enable, just by setting up best practices for website itself.
On Hestia side, for websites, I am using default settings, just some little mods for PHP backend template like openbasedir or timeouts, no special tricks.
So, because I like to keep things simple and standard, I will remove the module and I forget about that.
Just to confirm that this is a team decission. Hestia is, as written multiple times, a tool for sysadmins which want to automate their hostings a bit and make their life easier. There is zero interrests in building a cpanel clone out of hestia or overload it with a lot of mods by default, which can be installed or configured within seconds.
And that’s the reason it works almost flawlessly. Mod Pagespeed and similar modules are easy and fast fix but I wouldn’t recommend it for prolonged period of time.
@jlguerrero I found a way to upgrade nginx to another apt source that bundles ngx_pagespeed as a dynamic module that can be activated easily.
I posted a tutorial here: