hello and thanks for the new site.
I’ve added some links to automated testing. You might be purposefully triggering some warnings to support wierd browsers ofcourse
I hope the feedback in these tools can help further improve the site, and particularly improve the experience on mobile devices with small screens and limited data plans.
Take the advice of GTmetrix with a big grain of salt. Many of their recommendations are conflicting (“Remove query strings from static resources” vs “Use a CDN”) or difficult/expensive to implement (CSS sprites).
It looks like easy wins would be to enable compression and put script tags after CSS includes. Everything else, meh.
hello and thanks for the new site. I’ve added some links to automated testing. You might be purposefully triggering some warnings to support wierd browsers ofcourse
The pagespeed and yslow tests still show a lot of oppurtunity for improvement: http://gtmetrix.com/reports/lesswrong.com/MwBG3tEn
W3C has some conformance to standards advice http://validator.w3.org/unicorn/check?ucn_uri=lesswrong.com&ucn_task=conformance#
W3C says rss tests pass but compatibility could be further improved: http://validator.w3.org/unicorn/check?ucn_uri=lesswrong.com&ucn_lang=nl&ucn_task=feed#
W3C says the site completely fails mobile compatibility (this is big for me since i browse it mostly through mobile devices with small screens) http://validator.w3.org/unicorn/check?ucn_uri=lesswrong.com&ucn_task=mobileok#
I hope the feedback in these tools can help further improve the site, and particularly improve the experience on mobile devices with small screens and limited data plans.
Take the advice of GTmetrix with a big grain of salt. Many of their recommendations are conflicting (“Remove query strings from static resources” vs “Use a CDN”) or difficult/expensive to implement (CSS sprites).
It looks like easy wins would be to enable compression and put script tags after CSS includes. Everything else, meh.
Thanks for analysing the results!
This might be relevant too
http://googleonlinesecurity.blogspot.com/2011/06/introducing-dom-snitch-our-passive-in.html