Question

Mod_pagespeed installed but filters not running on page. No pagespeed headers present

I’ve just started a standard LAMP DigitalOcean droplet and installed Google Pagespeed. The package is installed and listed in /etc/apache2/mods-enabled/

I have added the following items to the pagespeed.conf

ModPagespeedEnableFilters prioritize_critical_css                   
ModPagespeedEnableFilters lazyload_images,inline_preview_images,insert_image_dimensions
ModPagespeedEnableFilters resize_mobile_images,insert_image_dimensions

Which I have used on previous projects. For some reason none of these filters are being run. Inspecting the headers being passed from the server show no pagespeed headers.

I don’t seem to be running across any errors anywhere and I am stuck as to what to look for next.


Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Accepted Answer

It turns out it was the CMS I am using. It uses the register_shutdown_function from php which with a call back introduces no-pragma and breaks pagespeed

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

After enabling the mod with a2enmod pagespeed did you ensure that you restarted the apache process with service apache2 restart?

In some instances mod_expires is also required in order to use mod_pagespeed. It can be enabled with a2enmod expires; service apache2 restart