I’ve been releasing a bunch of different websites recently. And when I do each release, I usually check a few things. Sometimes, I forget to check a thing or two. This is an attempt at transferring that mental checklist into something written (and hence, organized) —
- Validate HTML
- Validate CSS
- Remove all inline Javascript and CSS
- Semantic and accessible HTML?
- Works across browsers and platforms? (Are IE users banned?)
- Is all user input sanitized?
- Does it have a favicon? Does it have a page title?
- Analytics (Choon Keat)
- Add <meta> tags (Davide Casali)
- Are the number of HTTP requests as low as possible? (Alexander Limi)
- Robots.txt (especially important if you have a dev and a live site {which you might not always be a good idea}; Wim)
Any other suggestions for what should be on this checklist?
Eventually, all this should become automatic and constant rather than forced and climactic.
January 14th, 2010
by Davide 'Folletto' Casali
Is it an “unordered” checklist right? :)
I wouldn’t put “remove inline” and “semantic” because I strictly avoid the first one and I build the semantic part before anything, but yes, they could be “checked”, I agree.
I wouldn’t put the crossbrowser check because I think it’s “inherent” to the CSS development, but that’s something I agree it’s needed, because I’ve seen it often forgotten in many situations.
Maybe, I’ll add: . check feed / feedburner . check meta tags
January 14th, 2010
by Wim
Don’t forget the robots.txt in the sites rootfolder. Indeed metatags are important, though not visible.
January 14th, 2010
by Alexander Limi
“Check that number of HTTP requests is as low as possible”. This is the #1 thing you can do for performance. :)
January 14th, 2010
by Art
When I build websites, I usually have a “test” domain and a “live” domain. As expected, everything on your list is checked on the “test” domain prior to pushing the content to “live”.
That being said, things like analytic code (e.g. Google Analytics) need to be on the “live” website so make sure you check that it’s working.
The suggestion about robots.txt is also very important, as this will be different between the “test” and “live” domains.
Otherwise you have a great list!
January 16th, 2010
by eleg
accessibility… thx B-)
January 17th, 2010
by Choon Keat
Analytics.
Unless you’re the kind who don’t show up in your new restaurant, observing & waiting on customers. But instead, stays home refining recipes and thinking up new dishes.
January 23rd, 2010
by Abi Raja
The Author
Thanks for the suggestions everyone. Updated the checklist.
January 24th, 2010
by karl
There would be benefit to plug this with a wrapper like LogValidator. The principle being to validate the most popular pages every week using Apache Logs.
http://www.w3.org/QA/Tools/LogValidator/
January 24th, 2010
by karl
For dev sites, instead of robots.txt (which makes visible your hiding strategy), I would use .htaccess. So something to check the ACL for the Web site.
Weight/Speed of pages: total weight of each pages with the distribution in html/css/images/medias
Is gzip activated?
Are ETAGS, HTTP cache policies set correctly?
April 30th, 2010
by Website Project Planning 101.2 at the Online Business Success Center
[...] Website Release Checklist (abi.sh) [...]