Console feedback

[Hardey]

Some day my  console feedback results are all "0%" and other day are like:

1. CSS combine opportunities missed: 100.00%
2. Resources not rewritten because of restrictive Cache-Control headers: 98.03%
3. Cache lookups were expired: 28.89%
4. Resources not rewritten because domain wasn't authorized: 7.82%
5. JavaScript minification failures: 3.18%
6. Cache misses: 2%
7. Resources not loaded because of fetch failure: 0.00%
8. CSS files not rewritten because of parse errors: 0.00%
9. Image rewrite failures: 0.00%

[Shawn Ligocki]

Thanks Hardey, 

Did you expect this result? Was it surprising to you? Do you know what your "Cache-Control" headers are set to? Can you send me a URL to your site?

Cheers,

-Shawn

[Hardey]

It's a multi-site server, i'm using cPanel and i don't know what 'Cache-Control' headers are set  to. 

[Shawn Ligocki]

How about any URL for any site? 98.03% is quite high, so probably all your sites are having this same problem.

[Hardey]

I think that is because my site has htaccess login, this evening l'm going to remove it. ( url: http://globoforum.com/ )

[Shawn Ligocki]

htaccess login could definitely cause problems when we try to fetch the resources!

That URL does not appear to be running mod_pagespeed, for example, it does not show an X-Mod-Pagespeed header.

[Hardey]

Ok, i removed htaccess login but it still does not combine css and javascript ( url: http://globoforum.com/ , check it now )
My mod pagespeed console says:

1. CSS combine opportunities missed: 67.47%
2. Cache lookups were expired: 36.86%
3. Resources not rewritten because domain wasn't authorized: 9.75%
4. CSS files not rewritten because of parse errors: 8.06%
5. JavaScript minification failures: 4.32%
6. Resources not rewritten because of restrictive Cache-Control headers: 3.59%
7. Cache misses: 1%

1. Resources not loaded because of fetch failure: 0.00%

1. Image rewrite failures: 0.00%

[Shawn Ligocki]

Ah, looks much better.

You are getting some combining and actually our metric "CSS combine opportunities missed" is not the best, so I wouldn't worry too much about it right now.

I think "Cache lookups were expired: 36.86%" is actually much more notable. I would usually expect that to be an issue of short TTL Cache-Control headers. But the URL you supplied has quite long TTL on Cache-Control headers, so I'm not sure what the problem is. Probably it would be more useful if the console could tell you which resources this was a problem for.

[Giulio Zaccaroni]

Certainly yes, thank you :)

2013/6/12 Shawn Ligocki <slig...@google.com>

[Giulio Zaccaroni]

1. CSS combine opportunities missed: 80.60%
2. Cache lookups were expired: 73.07%
3. Resources not rewritten because domain wasn't authorized: 28.76%
4. CSS files not rewritten because of parse errors: 19.23%
5. Resources not rewritten because of restrictive Cache-Control headers: 9.76%
6. JavaScript minification failures: 1.96%

1. Cache misses: 1%
2. Resources not loaded because of fetch failure: 0.00%
3. Image rewrite failures: 0.00%

Mmmm ...probably some problem in cache lookups and css combine? 

2013/6/12 Giulio Zaccaroni <zaccaro...@gmail.com>

[John Dever]

 I like the new look of the console in 1.6, with the graphs.

What do you think about somehow incorporating the beacon timings into a graph? I know the results would probably be fairly subjective as it likely wouldn't be feasible to separate page requests in a production environment, while still interesting to look at. It may be more useful during controlled QA an/or stress testing.

Again, cheers for all of the hard work.

[Giulio Zaccaroni]

I think that it would be really great!

2013/7/24 John Dever <deve...@gmail.com>

[Shawn Ligocki]

Thanks for the suggestion, John. Right now the console is a place to find out what is wrong with your installation, we're starting to think now about a version that shows what's right :) I think that beacon timings, bytes reduced, etc. would all be part of that dashboard. Stay tuned.

[John Dever]

Awesome. Thank you!