Thread

I’ve just enabled the mod_pagespeed option on my site at Dreamhost, but it has made no difference at all to the site on the frontend. I know this because when I run a speedtest, nothing has changed and when I viewsource nothing has changed. Whereas the sourcecode on my own blog hosted at linode has quite clearly changed.

I logged a support call with Dreamhost and they have come back with”

mod_pagespeed is definitely enabled for your domain; an extract from the httpd.conf follows:

<IfModule pagespeed_module>
    ModPagespeed on
    SetOutputFilter MOD_PAGESPEED_OUTPUT_FILTER
    ModPagespeedDomain <a href="http://www.gilt-edge.com">http://www.gilt-edge.com</a>
    ModPagespeedDomain gilt-edge.com
    ModPagespeedUrlPrefix <a href="http://www.gilt-edge.com/_cache/">http://www.gilt-edge.com/_cache/</a>
    ModPagespeedFileCachePath         "/var/mod_pagespeed/cache/"
    ModPagespeedGeneratedFilePrefix      "/var/mod_pagespeed/files/"
    ModPagespeedEnableFilters collapse_whitespace,remove_quotes </IfModule>

I’m not sure why it’s not appearing to do anything for your page, though; it’s possible that something on your page is making mod_pagespeed give up prematurely.

Any ideas as to what could be making my site ‘give up prematurely’?

PS - we do have template caching and query caching enabled

Welcome to the forums, martinduys -

Server-side, environmental changes like this are outside of what we can offer for supporting ExpressionEngine itself. I’ll move this down to the CodeShare Corner in case other community members have tackled this.

Thank you.

martinduys, here’s a FAQ page from the project which may suggest an idea.

http://code.google.com/p/modpagespeed/wiki/FAQ

It occurs to me that you might be running with Gzip Enabled in EE Output and Debugging preferences. Apparently mod_pagespeed works only with html, css, etc. that hasn’t already been compressed.

Just an idea - this is not something I’ve worked with, but will offer.

Regards,
Clive