Re: How do I check which filter is actively running in mod_pagespeed?

299 views
Skip to first unread message

Joshua Marantz

unread,
Oct 10, 2012, 9:35:44 AM10/10/12
to mod-pagespeed-discuss
Hi,

There's not currently an easy way to see what filters are enabled, other than looking in the pagespeed.conf file.  However this would be a good enhancement, so I filed it as http://code.google.com/p/modpagespeed/issues/detail?id=515.

It does appear that mod_pagespeed is failing to rewrite your CSS files in any way.  I suspect something is not going well when mod_pagespeed tries to fetch these resources.  This might typically happen if the Apache server is running with a different DNS configuration to prevent outbound connections.  There will usually be evidence in the Apache error log file of mod_pagespeed's fetching failures.

If this is indeed the problem, it can usually be resolved by using ModPagespeedMapOriginDomain or ModPagespeedLoadFromFile.   See https://developers.google.com/speed/docs/mod_pagespeed/domains.


On Wed, Oct 10, 2012 at 8:26 AM, Didik Wicaksono <didik.w...@gmail.com> wrote:
I have "mod_pagespeed on" and "ModPagespeedRewriteLevel CoreFilters"
in my website: http://dapurmasak.com.

Even though its rewrite level was set to "CoreFilters", it seems that
"combine_css" filter is not active.

How do I check which filter is actively running in mod_pagespeed?

Regards,

Didik.

Matt Atterbury

unread,
Oct 11, 2012, 4:38:26 PM10/11/12
to mod-pagesp...@googlegroups.com
I looked at your site by copying the home page and running mod_pagespeed over it.

Regarding combine_css, I looked at recipe.css and welcome.css and they both reported that they could not be combined because of parse errors. This was reported in Apache's error log (I have debug log level turned on).

Our CSS parser handles much of CSS2.1 and only a little of CSS3, and apparently it can't handle yours.

I suspect you're using CSS3 constructs but you could check by running the files through an online CSS validator.

Regards, m.

Joshua Marantz

unread,
Oct 11, 2012, 6:28:03 PM10/11/12
to mod-pagespeed-discuss
One other note:  we have been actively working on parsing more of CSS3 and in our next Beta release (and the current trunk build, if you can build from source) you might have more luck.

-Josh

marstonstudio

unread,
Oct 12, 2012, 10:41:30 AM10/12/12
to mod-pagesp...@googlegroups.com
That's great news on the CSS3 improvements in trunk!

I see there has been work on the 'media' elements, has there been any work on supporting font-face? Seems like fonts could be good candidate for extended-cache as well.

jon marston

Shawn Ligocki

unread,
Oct 12, 2012, 1:45:19 PM10/12/12
to mod-pagesp...@googlegroups.com
We have been looking into possible optimizations for fonts, but do not yet do any, likewise we don't parse the @font-face directives in CSS yet either. I just added http://code.google.com/p/modpagespeed/issues/detail?id=524 to track that.
Reply all
Reply to author
Forward
0 new messages