http://www.webpagetest.org/result/120221_DV_3AHEB/
Leverage browser caching of static assets: 66/100
FAILED - (No max-age or expires) - https://
There ist no https in use.
I wonder if all of those embedded base64 data URIs in your page might be tripping an alarm in Chrome’s client-side phishing protection. The SSL request is to one of Google’s IP addresses (I repeated the test here). Testing from Montreal (Chrome), however, I see no SSL connections, but it reappears when testing from San Jose (a resource is loaded from ssl.gstatic.com).
It might be US-only, but I can’t say for sure as all other Chrome tests from various locations have been unresponsive, hanging at the front of the queue for at least the last 20 minutes.
Sorry, the visibility into SSL requests is pretty bad with the Chrome agent right now - I am working on a fix and hope to have it available soon (may be as long as 2 weeks though - I’ll be traveling next week).
I’m not sure what happened to the Chrome agents this morning but I think someone backed up the queues in several locations with the IE agents (the Chrome and IE agents alternate work) but it looks like it has cleared up now.
There’s probably a difference in the configuration of Chrome on the Dulles VA machine, seeing as that’s the only one showing the SSL request right now (phishing & malware filter turned on?). Wouldn’t worry about it, piratos, it’s not so much an error as a real-world example of how your site may actually be loaded for some users (who all tend to have different setups).
Hi - i’m not worry.
From NY the same http://www.webpagetest.org/result/120223_86_3BD5K/1/performance_optimization/