Max,
Google’s PageSpeed Insights gets specific about CSS and JS files that block rendering:
https://developers.google.com/speed/pagespeed/insights/
In the case of my “https://visionsecurity.jp” site, it complains about the following CSS because I am using external CSS files in Freeway and for whatever reason Freeway breaks the CSS into 3 separate files:
https://visionsecurity.jp/bodypages950pxne.css
https://visionsecurity.jp/index.css
https://visionsecurity.jp/sheet1.css
So it would seem the only way to consolidate that mess would be to disable use of external CSS altogether. But doing that dumps all that CSS inline, inside my main *.html file, which is pretty ridiculous.
PageSpeed Tools also complains about all of Walter’s actions on my page:
https://ajax.googleapis.com/ajax/libs/prototype/1.7/prototype.js
https://ajax.googleapis.com/…culous/1.9/scriptaculous.js?load=effects
https://ajax.googleapis.com/ajax/libs/scriptaculous/1.9/effects.js
https://dnk2vbhoq39rr.cloudfront.net/carousel2/0.1.11/carousel2.js
And the only way for me to fix all those would be to rewrite the code without Prototype or Scriptaculous and then figure out what to do with carousel2.js.
As if all that wasn’t bad enough…
Google’s “Optimize CSS Delivery” page says “Don’t inline CSS attributes”:
But Freeway adds inline STYLE attributes for _clear.gif.
Here’s what Freeway puts inside the “body” tag on my “visionsecurity.jp” site:
'<img src="_clear.gif" border="0" width="1" height="1" alt="" STYLE="vertical-align:baseline">'And using Rollovers causes Freeway to add the following inside the
style="visibility:hidden"Pleasing Google is a mess of trouble.
–James W.
freewaytalk mailing list
email@hidden
Update your subscriptions at: