Console Messages

[Hemant Nandrajog]

Below are the list of console messages from few of my domains 

First suggestion will be to release more details/breakdowns about the messages in future version which will help with debugging of the issues.

Other is to have the configuration (like one in statistics) displayed in console too

http://icnd.info/

Notable issues (Click through for the links for info on how to fix these problems):

CSS combine opportunities missed: 100.00%

Cache lookups were expired: 44.40%

Resources not rewritten because domain wasn't authorized: 26.00%

Image rewrite failures: 4.69%

Resources not rewritten because of restrictive Cache-Control headers: 4.11%

Cache misses: 0%

Resources not loaded because of fetch failure: 0.00%

CSS files not rewritten because of parse errors: 0.00%

JavaScript minification failures: 0.00%

http://bollywoodfans.in/

Notable issues (Click through for the links for info on how to fix these problems):

Cache lookups were expired: 46.90%

CSS combine opportunities missed: 15.91%

Resources not rewritten because of restrictive Cache-Control headers: 11.30%

Cache misses: 2%

Resources not rewritten because domain wasn't authorized: 0.82%

Resources not loaded because of fetch failure: 0.00%

CSS files not rewritten because of parse errors: 0.00%

JavaScript minification failures: 0.00%

Image rewrite failures: 0.00%

http://mastposters.com/

Notable issues (Click through for the links for info on how to fix these problems):

CSS combine opportunities missed: 100.00%

Cache lookups were expired: 57.53%

Resources not rewritten because of restrictive Cache-Control headers: 14.97%

Resources not rewritten because domain wasn't authorized: 10.73%

Cache misses: 5%

Resources not loaded because of fetch failure: 0.00%

CSS files not rewritten because of parse errors: 0.00%

JavaScript minification failures: 0.00%

Image rewrite failures: 0.00%

Thanks 

Hemant

[Shawn Ligocki]

Hi Hemant,

Sorry about the delay. It looks like the main issue you are running into is high cache expiration. This means that about half of your resources are not being served rewritten because nobody is requesting them before they expire. We have a new documentation up about what you can do about this:

• Cache lookups that were expired: Although these resources were found in cache, they were not rewritten because they were older than their max-age. Remedy: (A) Enable LoadFromFile to tell the server to load the files straight from disk rather than through HTTP. (B) Reconfigure your server to serve resources with longer TTL. For example, Header set Cache-Control "max-age=3600" to set one hour TTL in Apache config.

Could you try either of these solutions and see if that improves your rates?

Cheers,

-Shawn