Is mod_pagespeed working

[habeeb sk]

ModPagespeed on
ModPagespeedRewriteLevel CoreFilters
ModPagespeedEnableFilters collapse_whitespace
ModPagespeedEnableFilters combine_heads
ModPagespeedEnableFilters elide_attributes
ModPagespeedEnableFilters rewrite_javascript
ModPagespeedEnableFilters move_css_to_head
ModPagespeedEnableFilters outline_css
ModPagespeedEnableFilters outline_javascript
ModPagespeedEnableFilters remove_comments
ModPagespeedEnableFilters remove_quotes
ModPagespeedEnableFilters rewrite_css

Response Headers:-

Date Mon, 28 Feb 2011 15:33:17 GMT
Server Apache
Cache-Control max-age=0, no-cache, no-store
Pragma no-cache
X-Mod-Pagespeed 0.9.15.3-404
Vary Accept-Encoding
Content-Encoding gzip
Content-Length 25398
Keep-Alive timeout=20, max=98
Connection Keep-Alive
Content-Type text/html; charset=UTF-8

I have the above settings in pagespeed.conf file and the related
Response Headers for a webpage run . Even though all the filters are
enabled , the pagespeed analysis gives the suggestions as to :-
1.Leverage Browser Caching
2.Minify CSS


Can anyone help. Thanks in advance.

[Shawn Ligocki]

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

I installed mod_pagespeed; why isn't it rewriting any of my pages?

1. Check the HTTP response headers from your page (e.g., run curl -D - http://example.com). Look for a header like X-Mod-Pagespeed: 0.9.0.0-215. If you don't see one, this means that Apache is not adding mod_pagespeed to the filter chain, meaning the problem is probably in your Apache .conf files. One possible cause for this is multiple references to SetOutputFilter: only one of those will win. Seehttp://httpd.apache.org/docs/current/mod/core.html#addoutputfilterbytype
2. It's possible that none of the active mod_pagepspeed rewriters found anything useful to rewrite in your page. Try enabling more aggressive ones!
3. mod_pagespeed cannot optimize resources (css, js, or images) that are marked as cache-control:nocache or cache-control:private. If your default caching headers are marked as such, mod-pagespeed will not rewrite the resources.
4. mod_pagespeed cannot minify CSS files that it cannot parse, specifically it will fail on certain proprietary and CSS3 syntaxes (See issue 108).
5. We intentionally don't allow fetching and rewriting HTTPS resources (so we don't open up security holes in your server).

Looks like #1 is working. If you send us a link to your pages (if it is net-accessible) we could tell you more.

-Shawn

[habeeb sk]

'PageSpeed' firebug extension analysis , asks to Specify an expiration
at least one week in the future for some of the resources.And the
reponse headers of those resources do not contain "Cache Control" and
contain "Etag". But I have tried applying cache control to all the
resources using
<FilesMatch "\.(jpg|jpeg|png)$">
Header unset Etag
Header set Cache-control "max-age 1048500"
</FilesMatch>

But the above setting works only for some of the resources (which are
optimized infact) but not for the others.Waiting for your reply. Thank
You.


On Feb 28, 7:14 pm, Shawn Ligocki <sligo...@google.com> wrote:
> Fromhttp://code.google.com/p/modpagespeed/wiki/FAQ

>
> I installed mod_pagespeed; why isn't it rewriting any of my pages?
>

>    1. Check the HTTP response headers from your page (e.g., run curl -D -

>    http://example.com). Look for a header like X-Mod-Pagespeed: 0.9.0.0-215.
>    If you don't see one, this means that Apache is not adding mod_pagespeed to
>    the filter chain, meaning the problem is probably in your Apache
> .conf files.
>    One possible cause for this is multiple references to SetOutputFilter:
>    only one of those will win. See
>    http://httpd.apache.org/docs/current/mod/core.html#addoutputfilterbytype

>    2. It's possible that none of the active mod_pagepspeed rewriters found

>    anything useful to rewrite in your page. Try enabling more aggressive ones!

>    3. mod_pagespeed cannot optimize resources (css, js, or images) that are

>    marked as cache-control:nocache or cache-control:private. If your default
>    caching headers are marked as such, mod-pagespeed will not rewrite the
>    resources.

>    4. mod_pagespeed cannotminifyCSS files that it cannot parse,

>    specifically it will fail on certain proprietary and CSS3 syntaxes
> (See issue

>    108 <http://code.google.com/p/modpagespeed/issues/detail?id=108>).
>    5. We intentionally don't allow fetching and rewriting HTTPS resources

>    (so we don't open up security holes in your server).
>
> Looks like #1 is working. If you send us a link to your pages (if it is
> net-accessible) we could tell you more.

>  <http://code.google.com/p/modpagespeed/wiki/FAQ>
> -Shawn