dylanlee98

Currently using CentOS with mariaDB 10.1 and PHP 7.1 with FPM enabled. And yes, as mentioned before I have tried disabling both W3TC and mod_pagespeed. I have been extraordinarily careful with mod_pagespeed by restricting it to specific configurations for each site. Some don’t play well with MPS, so instead I just use MPS in IPRO mode so I don’t need to worry about minification.

I usually use W3TC with a copy/paste configuration that’s extremely general if the client doesn’t have the finances for me to dive in deep with optimization. I only really go deep into haggling with MPS if I have either extra time on my hands, if they pay for extra optimization, orif the client complains that their website isn’t achieving that ridiculous 100% PageSpeed score.

EDIT: Typo fix and MariaDB version number

• This reply was modified 6 years, 6 months ago by dylanlee98.

My php.ini is set to 512MB for memory_limit, completely overkill for what I am doing and how little traffic I get. There was nothing located in the drop-in section that wasn’t related to W3TC (Which I also cleared, just in case).

That isn’t what I am talking about. I am talking about mod_pagespeed, an Apache module that automatically optimizes website content and serves clients optimized website data. Not PageSpeed, the website analyzing service provided by Google.

It was a mistake on my part, didn’t restart the Apache service after installing all my packages.

But now I have encountered another issue, the moment I enable page caching (Disk), mod_pagespeed optimizations no longer appear when I load up any of my sites.

I really want to combine W3TC and mod_pagespeed to get the absolute best performance possible with my site, along with automating image compression supporting multiple formats depending on browser.

Solved, nvm. Didn’t see the <p> tags