Menu Search
Jump to the content X X
SmashingConf London Avatar

We use ad-blockers as well, you know. We gotta keep those servers running though. Did you know that we publish useful books and run friendly conferences — crafted for pros like yourself? E.g. our upcoming SmashingConf London, dedicated to all things web performance.

The Website Launch Checklist – 15 Essential Checks Before You Go Live

Your website is designed, the CMS works, content has been added and the client is happy. It’s time to take the website live. Or is it? When launching a website, you can often forget a number of things in your eagerness to make it live, so it’s useful to have a checklist to look through as you make your final touches and before you announce your website to the world. [Content Care Dec/15/2016]

This article reviews some important and necessary checks that web-sites should be checked against before the official launch — little details are often forgotten or ignored, but – if done in time – may sum up to an overall greater user experience and avoid unnecessary costs after the official site release. Here is your website launch checklist:

Further Reading on SmashingMag: Link

Favicon Link

A favicon brands the tab or window in which your website is open in the user’s browser. It is also saved with the bookmark so that users can easily identify pages from your website. Some browsers pick up the favicon if you save it in your root directory as favicon.ico, but to be sure it’s picked up all the time, include the following in your head.

<link rel="icon" type="image/x-icon" href="/favicon.ico" />

And if you have an iPhone favicon:

<link rel="apple-touch-icon" href="/favicon.png" />
website launch checklist

Titles And Meta Data Link

Your page title is the most important element for SEO and is also important so that users know what’s on the page. Make sure it changes on every page and relates to that page’s content.

<title>10 Things To Consider When Choosing The Perfect CMS | How-To | Smashing Magazine</title>

Meta description and keyword tags aren’t as important for SEO (at least for the major search engines anyway), but it’s still a good idea to include them. Change the description on each page to make it relate to that page’s content, because this is often what Google displays in its search result description.

<meta name="description" content="By Paul Boag Choosing a content management system can be tricky. Without a clearly defined set of requirements, you will be seduced by fancy functionality that you will never use. What then should you look" />

Cross-Browser Checks Link

Just when you think your design looks great, pixel perfect, you check it in IE and see that everything is broken. It’s important that your website works across browsers. It doesn’t have to be pixel perfect, but everything should work, and the user shouldn’t see any problems. The most popular browsers to check are Internet Explorer 6, 7 and 8, Firefox 3, Safari 3, Chrome, Opera and the iPhone.

website launch checklist

Proofread Link

Read everything. Even if you’ve already read it, read it again. Get someone else to read it. There’s always something you’ll pick up on and have to change. See if you can reduce the amount of text by keeping it specific. Break up large text blocks into shorter paragraphs. Add clear headings throughout, and use lists so that users can scan easily. Don’t forget about dynamic text too, such as alert boxes.

Don’t just assume all your links work. Click on them. You may often forget to add “http://” to links to external websites. Make sure your logo links to the home page, a common convention.

Also, think about how your links work. Is it obvious to new users that they are links? They should stand out from the other text on the page. Don’t underline text that isn’t a link because it will confuse users. And what happens to visited links?


Functionality Check Link

Test everything thoroughly. If you have a contact form, test it and copy yourself so that you can see what comes through. Get others to test your website, and not just family and friends but the website’s target market. Sit back and watch how a user uses the website. It’s amazing what you’ll pick up on when others use your website differently than how you assume they’d use it. Common things to check for are contact forms, search functions, shopping baskets and log-in areas.

Graceful Degradation Link

Your website should work with JavaScript turned off. Users often have JavaScript turned off for security, so you should be prepared for this. You can easily turn off JavaScript in Firefox. Test your forms to make sure they still perform server-side validation checks, and test any cool AJAX stuff you have going on.


Validation Link

You should aim for a 100% valid website. That said, it isn’t the end of the world if your website doesn’t validate8, but it’s important to know the reasons why it doesn’t so that you can fix any nasty errors. Common gotchas include no “alt” tags, no closing tags and using “&” instead of “&amp;” for ampersands.


If your website has a blog or newsreel, you should have an RSS feed that users can subscribe to. Users should be able to easily find your RSS feed: the common convention is to put a small RSS icon in the browser’s address bar.

Put this code between your <head> tags.

<link rel="alternate" type="application/rss+xml" title="Site or RSS title" href="link-to-feed" />

Analytics Link

Installing some sort of analytics tool is important for measuring statistics to see how your website performs and how successful your conversion rates are. Track daily unique hits, monthly page views and browser statistics, all useful data to start tracking from day 1. Google Analytics12 is a free favorite among website owners. Others to consider are Clicky13, Kissmetrics14, Mint15 and StatCounter16.


Sitemap Link

Adding a sitemap.xml file to your root directory allows the major search engines to easily index your website. The file points crawlers to all the pages on your website. XML-Sitemaps18 automatically creates a sitemap.xml file for you. After creating the file, upload it to your root directory so that its location is

If you use WordPress, install the Google XML Sitemaps plug-in19, which automatically updates the sitemap when you write new posts. Also, add your website and sitemap to Google Search Console20. This tells Google that you have a sitemap, and the service provides useful statistics on how and when your website was last indexed.


Defensive Design Link

The most commonly overlooked defensive design element is the 404 page. If a user requests a page that doesn’t exist, your 404 page is displayed. This may happen for a variety of reasons, including another website linking to a page that doesn’t exist. Get your users back on track by providing a useful 404 page that directs them to the home page or suggests other pages they may be interested in.

Another defensive design technique is checking your forms for validation. Try submitting unusual information in your form fields (e.g. lots of characters, letters in number fields, etc.) and make sure that if there is an error, the user is provided with enough feedback to be able to fix it.


Optimize Link

You’ll want to configure your website for optimal performance. You should do this on an ongoing basis after launch, but you can take a few simple steps before launch, too. Reducing HTTP requests, using CSS sprites wherever possible, optimizing images for the Web, compressing JavaScript and CSS files and so on can all help load your pages more quickly and use less server resources.

Besides, depending on the publishing engine that you are using, you may need to consider taking more specific measures – for instance, if you are using WordPress, you may need to consider useful caching techniques to speed up the performance23.

Yahoo Best Practices24

Back Up Link

If your website runs off a database, you need a back-up strategy. Or else, the day will come when you regret not having one. If you use WordPress, install WordPress Database Backup27, which you can set up to automatically email you backups.

If a user wants to print a page from your website, chances are she or he wants only the main content and not the navigation or extra design elements. That’s why it is a good idea to create a print-specific style sheet. Also, certain CSS elements, such as floats, don’t come out well when printed.

To point to a special CSS style sheet that computers automatically use when users print a page, simply include the following code between your <head> tags.

<link rel="stylesheet" type="text/css" href="print.css" media="print" />

Download the Ultimate Website Launch Checklist! Link

Just recently Dan Zambonini has published a very detailed checklist that covers both the pre-launch and the post-launch phase of the web site life cycle. Among other things his Ultimate Launch Checklist30 contains checks related to content and style, standards and validation, search engine visibility, functional testing, security/risk, performance and marketing.

Ultimate Check List

The checklist is a very useful reference that may help you in your daily projects and will help you to prevent errors and mistake once the site is released.

You may also want to consider the Quick Usability Check List31 by David Leggett that highlight some of the more common problems designers should address on their own sites in a Usability checklist of sorts. Not all of these items will apply to every website, these are just suggested things to look for in your own site design.

Quick Usability Check List32

What other checks would you list? Link

Make yourself a to-do list and keep it handy to check over before making any website live. Are there any other points you would add? Share them in the comments!


Footnotes Link

  1. 1
  2. 2
  3. 3
  4. 4
  5. 5
  6. 6
  7. 7
  8. 8
  9. 9
  10. 10
  11. 11
  12. 12
  13. 13
  14. 14
  15. 15
  16. 16
  17. 17
  18. 18
  19. 19
  20. 20
  21. 21
  22. 22
  23. 23
  24. 24
  25. 25
  26. 26
  27. 27
  28. 28
  29. 29
  30. 30
  31. 31
  32. 32

↑ Back to top Tweet itShare on Facebook

Lee Munroe is a web developer and creator of based in San Francisco.

  1. 1

    Great ;-)

  2. 2

    thanks so much that

  3. 3

    Mike Rundle

    April 7, 2009 1:53 pm

    Thanks for the 9rules screenshot! When it first popped up in my RSS reader I thought you were showing 9rules as an example of a site that didn’t do something right and I got real nervous, then I clicked over to read the article and I saw that wasn’t the case. Good thing!

  4. 4

    This is an excellent list. If every site did these things first, the Internet would be a much happier place.

    One comment: Progressive enhancement might be a better approach than graceful degradation. The two are really the same thing (making pages look good in trimmed-down browsers), but take different approaches. Graceful degradation designs an insanely awesome site for the latest browsers, then hacks the stylesheets to not look awful on older browsers. Progressive enhancement designs a tasteful site for basic browsers, then hacks the stylesheets to look insanely awesome in the latest browsers. This way, backward compatibility is a step along the way rather than an afterthought.

  5. 5

    Josh Cooper

    April 7, 2009 1:56 pm

    This is a fantastic post! I strongly feel that there needs to be a post specifically on the speed optimization section of this checklist. There are so many loose resources out on the net, and to pull that all together would be great. Otherwise, this is a great complilation, Thanks!

  6. 6

    Thank you, this is very useful.

  7. 7

    I agree with most of these, but I disagree with #7. Users do not “often” have javascript turned off. Most don’t turn it off since it is on by default. Only among the comp savy is this even slightly the case.

  8. 8

    Elijah Grey

    April 7, 2009 2:08 pm

    Shouldn’t the iPhone apple-touch-image be a png file? I’ve never seen an ico file working on an iPhone before.

  9. 9

    Great idea for a post! This is very useful and informative.
    Thanks Lee

  10. 10

    SmashingMag, you never cease to amaze! Thanks for the awesome post!

  11. 11

    Very useful! Thanks!

  12. 12

    Nice article, maybe you could have included something about Robots.txt

  13. 13

    great article and great timing… thank you very much!

  14. 14

    Martin Jensen

    April 7, 2009 2:51 pm

    Nice with a usable post instead of all those “inspiration” posts :) Nice work SM!

  15. 15

    Thanx – great post, helpful stuff here as I’d usually leave this for a developer to sort out ‘cos it seems too technical for a designer – you’ve just added some great tools to my web arsenal!

  16. 16

    How can this awesome site not give users the ability to share these blog posts on facebook or send by email? Seems kind of ironic given the natures the posts, no?

  17. 17

    Nice and useful! Thanks!

  18. 18

    I love articles like this.

    SM you’ve been on fire lately !!

  19. 19

    Nice article, thank you.

  20. 20

    John Faulds

    April 7, 2009 5:08 pm

    Other items on my list include:

    – Checking the layout on small screens
    – Testing Microformats if used
    – Minifying CSS/js
    – Testing accessibility with Total Validator, aDesigner, WebAIM etc.
    – Checking colour contrast
    – Checking for unused selectors with Dust Me Selectors (FF extension)
    – Checking robots.txt
    – As well as Google Analytics, also signing up for Google Webmaster tools, Yahoo Site Explorer, and Live Webmaster Center

  21. 21

    Great post.

    Just a question… Did you have some sponsorship from Silverback?

  22. 22

    The only thing I disagree with is the Javascript item. In this day and age, Javascript is absolutely essential, as are cookies. Don’t believe me? Fine. Go ahead and turn either of those off, and start surfing and using many sites you normally go to. You’ll be dead in the water.

    Now, Javascript often breaks, so that’s why we have jQuery — it gives us pretty much cross-browser functionality no matter what browser someone is using. And about 50% of the sites out there use cookies instead of session variables because they realized that session vars are either configured to use enormous amounts of server RAM, especially when you get slashdotted, or are slow because they are configured to go to the database. For me, encrypted, compressed cookies let you scale affordably unless you have invested a lot of cash in your backend — a suitable thing when you’re just starting your website out with one to three servers in the first couple years.

  23. 23

    That’s very useful set of guiding final buttons to close tightly.
    Thank you very much!


  24. 24

    Great. I wish I had advice like this years and years ago when I was first starting web design. :D

  25. 25

    From this checklist it seems that the most important thing to check… your favicon. LOL I wonder whether someone important has left SM. Posts are getting worse every day…

  26. 26

    Very rubbish!
    IE6 is NOT one of the most commonly used browser, iPhone doesn’t worth mentioning at all (iphone? dude, really iphone???)
    Validation has NO LINK WHAT SO EVER with your site success and google indexing.
    Making site without JS because 0.1% of the users may turned it off??? Come one, we are 2009, it’s a ridiculous idea!
    Favicon as number one to check? Are you serious?

    Seems like the quality of the articles here is declining each day, so sad:-(

  27. 27

    Man, screw this… these days are over. SEO is BS and all of this stuff is a waste of time. A smoke screen on top of that. A lot of this is stuff designed to stall the competition and bog them down with details.

    The reality is nobody really gives a crap about most web sites. Short attention span is at an all time high. The internet is dead. Too many thieves stealing content and even if you do make a killer site with a billion hits a day advertising is pretty much dead so you’ll probably lose money on it.

    Best thing to do is turn off your computer and quit dicking around with this shit. Buy a guitar, take lessons and start a band. Or… play the lottery. Your odds of success at either of those will be much higher than wasting your life away on the Internet.

    P.S. Global warming is a scam

    • 28

      So why are you online now, reading a web design post? Hmmm… be quiet fool.

  28. 29

    Smashing Editorial

    April 8, 2009 12:27 am

    @Pandjarov (#33) and Johny (#37): why would you think that checking favicon is the most important thing? Why would you suggest that the items in this article are ranked according to their importance? And maybe you are not concerned about Gracefule Degradation of your web-site, but you certainly should be.

  29. 30

    You can detect if a user has JS turned off and serve them alternate content, and this is exactly what I do for a website that relys heavily on JS.

    For pages that absolutely won’t function without JS, the user gets a nicely designed and worded error message and not simply a broken page.

  30. 31

    Dear Smashing Editorial,

    In many of the posts in this website you have spoken about the usability of a website and the way users scan/read through a page.

    Although experienced web designer, I read this article/post as a normal visitor. It has left me with the impression that the points in this check list are ordered. Maybe because they were numbered.

    I believe you will agree with me that the favicon is not the first thing you should check when publishing your website.

    If you don’t want users to think that the items in this article “are ranked according to their importance” you should not place numbers in front of them :) Just a common sense.

    Personally, I would advise the usage of the website. I have nothing to do with it, haven’t even added it as a link here but it is a fantastic way to check how your website looks in different browsers.

    As for the “Graceful Degradation” I agree with you. Never said anything bout that, I suppose you are quoting John.

    I would argue about the validation of your website. Although a good thing (having a new Porsche is good too but not all of us can afford it unfortunately) it is not “Essential”. You can try validating and I believe they rank pretty hight in the SERPS :)

    In conclusion I think this article was written more in terms of SEO rather than web design. After all, visitors don’t read meta description, do they :)


  31. 32

    “Your website should work with JavaScript turned off ” – please!!!
    how many users have turned it off or browsing web from linux console? none?

  32. 33

    Vishnuvardhan Reddy

    April 8, 2009 1:59 am

    Nice article, thank you.

  33. 34

    gareth hunt

    April 8, 2009 3:03 am

    Over 30 million people have downloaded the NoScript extension for Firefox, people working in government buildings or secure corporate offices often have javascript disabled by default, most search engine spiders are analogous to users browsing without javascript, etc.

    You can’t simply say something as baseless as “it’s 2009! who doesn’t have javascript enabled” if you are serious about making your site accessible to as many people as possible using different technologies.

  34. 35

    I don’t know whether to start with the article or the proceeding comments.
    I guess starting with the article makes more sense.

    1. Many of the things mentioned here, while important tasks, are not the kind of things you should be doing pre-launch – they should be occuring much earlier in your development cycle than that. In some cases (how to handle no-script issues) should be handled all the way back in the wireframing stage. Defensive design and validation is certainly something you don’t want to be first thinking about towards the end of a project.

    2. The article lacks a lot of advice on what you should have checked during this crucial time. Things like
    i) Making sure you have a the required details needed to go live: does your client allow ftp to their server or only sftp? Do you have the details to login? Do you know how their file structure is configured?
    ii) Does their server/scripting language/database have all the appropriate addons/configurations you might have used in development? For that matter are you developing and hosting on indentical environments? (You should be, and you should have a definitive answer to that question before you even start a project).
    iii) Do you know when the client wants the go-live to happen? Have you cleared enough time from your schedule to do the job properly? (If in doubt or the project is remotely complex, schedule a full day).
    iv) Have you backed up the live site and data? (This is mentioned in the article but you can never remind people to backup enough)
    v) Are all your internal links appropriate? No linking a sneaky css file from the testing server? No including that debugging javascript file by accident? No hardcoded links to the development or client display server? No forgotten # in the footer that should link to a privacy policy?
    vi) No lorem ipsum content anywhere? This includes making sure that previous placeholders like ads or blockquotes have been replaced with the correct content.
    vii) SQL files created for making the appropriate databases and also for adding any required data? Do you know how those sql files are going to get run? Does the client have a user panel for doing this or do you have to ssh into their server and run it by command line or do you have to send it to a third party system admin to execute? (If it’s an external System Admin, have you scheduled enough time to get the job done? Have you? Really? I don’t think you’ve dealt with enough Sys Admins, triple that timeframe).
    viii) Is your data clean? No test data lurking in the database that might result in ‘test user’, ‘testuser1’ being seen on the live site?
    ix) Did you re-clean the database after running the tests you should have run when the site is live for testing that signup form?

    3. Graceful degradation is dead, killed by progressive enhancement. Please don’t publish articles promoting the use of a dead methodology.

    As for the comments.
    1. Yes, you design and build with the possibility of javascript being turned off in mind. No, shut up, don’t argue, don’t even open your mouth. The fact you’re even opening your mouth to say something tells me you’re utterly clueless and you shouldn’t be entering the conversation. Be quiet and let the adults talk.
    You design and build with no-script in mind because that’s the whole point of progressive enhancement. Make sure that everyone can make use of or at the very least comprehend the service you are offering. If you’re using the canvas tag, you provide a fall back notification for browsers that don’t support it. Every other javascript interaction should be detailed/wireframed/documented in terms of progressive enhancement. This is a bigger issue than you thinking ‘Oh man, this is just bullshit.’ This is an accessibility issue and if you don’t understand it you should just shutup, walk quietly away and go and study until you’re capable of holding a conversation about it.

    Ok, apparently this got a bit long. I’ll stop now.

    • 36

      You are talking about Lee’s idea in more detail. It’s not your idea. It’s not your initiative. If you are clever enough, why not start writing your own article?

      Lee has written it for a general audience, like me and everything makes total sense.

      To me, Graceful Degradatoin is simpler to understand and easy to start from as compared to your PROGRESSIVE ENHANCEMENT.

      What a pity to people like you who have no respect for other people’s work and spotting a few arguable points to make yourself look smarter.

  35. 37

    Christopher Mena

    April 7, 2009 7:27 pm

    I love you Smashing, I really do. Thank you for being so awesome…

  36. 38


  37. 39

    Tom Isaacson

    April 7, 2009 8:32 pm

    The number one annoying oversight on websites – forgetting to include an easy-to-find contact email (preferably at the bottom of every page)! If I find a problem with a website I usually try to let the owner know, but some of them don’t want to be found…

  38. 40

    saurabh shah

    April 7, 2009 9:04 pm

    nice post.. very useful for me as m going to live my site soon.. thnx for sharing …

  39. 41

    mangesh jog

    April 7, 2009 9:15 pm

    fantastic post! i think all are covered point are impotent thankful for this this post

  40. 42

    Arthur Brown

    April 8, 2009 6:38 am

    Great check list. As a web designer / developer the lines of distinction are constantly blurred so a check list like this is essential before a site goes live. Thanks!

  41. 43

    Nice stuff. Going to print it out and paste it over my desk now =)

  42. 44

    Thanks… great post!

  43. 45

    Cross browser checks and title tags are hardly things one ‘checks’ at the end. how can you develop a site without checking IE constantly!?

    Otherwise, good post. Checking IE is like our company mantra… for the many times we forget. …stupid IE.

  44. 46


    April 7, 2009 11:12 pm

    Thaks a lot…………and its very useful guidence for every web designer and web developer for creating great web site or web applications.

    Thanks a million again…………………….

  45. 47

    Waouw ! Great Post ! Thank you… As a web content strategist, I appreciate, of course, you integrated content (Tip 4) in your check-list ;-)

  46. 48

    thanks for useful post,.. I missed some of really important steps before launch my website

  47. 49

    Alpesh darji

    April 7, 2009 11:39 pm

    .htaccess file with directory listing disabled for the inner folders. I guess this is most important from security point of view.

  48. 50

    Another smashing magazine post to pass on to my bosses to show how we should be doing things!

  49. 51

    12: checking your form for validation.
    I used to have “helpful” diagnostics but the spammers used them to try to circumvent my anti-spam measures. I use javascript validation so those with JS enabled get on-the-fly error prompts and follow that with PHP validation. Spammers disable JS but 99.9% of “real” users” don’t so they get the helpful prompts. The PHP validation gives a less helpful error response that says something like “the message appears to have some characteristics in common with junk mail, please review your input and try again”.
    I also put a “JS disabled” alert on form pages because I agree with Volomike and others – Web without JS is like a kiss without a moustache (to paraphrase J P Sartre?).

  50. 52

    Jamiel Sharief

    April 8, 2009 3:32 am

    Brilliant. Thanks for putting this together.

  51. 53

    I wonder why my reply is awaiting administration approval all day…

  52. 54

    Just to clarify, this isn’t a list in order of importance, it’s simply a quick checklist as a reminder.

    Agreed all of these things should be checked throughout the process (along with a lot of other checks) and not left to ‘5min before going live’. This is just a useful final reminder checklist to make sure everything has been covered in case there is something you overlooked.

    To back up gareth hunt’s point, unfortunately there are users who do have JS turned off even in this day and age. Usually coming from government buildings where they have it turned off to stop pop-ups and the likes. Other platforms, e.g. some mobile phone browsers, may not support JS also so it’s important to make sure you have these scenarios covered.

    @Elijah: You’re right, well spotted. The favicon for iPhone should be favicon.png

    Thanks for all the comments.

  53. 55

    All this talk about functions disabled in the browser. How about checks for human users with disabilities? Color blind testing, vision impaired users?

  54. 56

    Just a small thing, but if you are spending time and money launching and promoting the site/URL, it helps to set yourself up to catch the inevitable mistakes people make, so:
    – set up DNS so that,, etc work as well, preferably using 302s to correct them gently.
    -If you have a server that is case sensitive, be consistent in how you use case, and work out what happens when people type things in the ‘wrong case’.
    – On larger sites, if the budget allows, register similar or common typo domains and use 302s as well. This not only helps get users who mistyped, but forestalls competitors or unrelated sites from getting your traffic by accident.

  55. 57

    Great article! Will be sure to refer back to this when I finish the redesign of my site.

  56. 58

    Andrew Turnbull

    April 8, 2009 4:36 am

    great stuff, im currently on 2 web projects one for work and 1 for client. I not sure what the person way above was talking about in his essay, its just a guide mate. Love the check list link will be using it soon.

  57. 59

    spectecular. thanks!

  58. 60

    Matt Pramschufer

    April 8, 2009 5:03 am

    This is a pretty good list. I wrote an article a month or so ago titled 13 Steps to a Successful Website Launch (Link). We had a couple items in common, but it seems like your list concentrates more on SEO and non critical items of a launch.

  59. 61

    Smashing Editorial

    April 8, 2009 5:34 am

    Thank you for your feedback, the numbers in the headings of the article sections were removed.

  60. 62

    Very Useful. Thanks. I am not sure I agree with the RSS Feed suggestion, regardless, this checklist has great suggestions for those who don’t have a solidified checklist.

  61. 63

    Very informative! Thank you!! :-)

  62. 64

    Incredible how some people cannot see past their ignorance.

    Sites should work without Javascript. Maybe not every little feature, but main content of the site should be accessible without Javascript. Main menu that relies on JS is fail. Search that relies on JS is fail. Etc.


    Because most mobile phones today do not support JS, or at least complex JS. There are TONS of users, at least in Europe, that check some small info on website via mobile phone. I book tickets for cinema via mobile phone. I do not BROWSE that website, because it is impossible, but i just manage somehow to click through to book tickets. If at any point JS is required, i would not be able to do so.

    Also, on multiple occasions, i used mobile phone to visit website of some company to check their contact phone number / call center. I did not BROWSE website with mobile phone, rather i just checked something really fast.

    So stop that nonsense complaining about good point SmashMag made, and realize that if you can reach 3% more of people with your website – that’s 3% more of potential revenue for site’s owner at the end of the year.

  63. 65

    Does anyone know why some feeds have a favicon and some don’t? Smashing Magazine’s feed for instance has a favicon so all the visited pages have a favicon and the new ones don’t which makes it really easy to find updates. Other feeds on the other hand only have the default icon. I’m using Firefox’s built-in feed service.

  64. 66

    nice article!

  65. 67

    I agree – graceful degradation is dead. I use the mighty noscript addon myself but when something doesn’t work – I turn it on. 95% are using JS by default, the 5% that doesn’t are most likely doing that in a similar aware fashion. Still.. Basic stuff like registration and navigation should be working anyway but not because of the end-user, but because of the site’s best interest, that’s correct. It’s the same rule we apply to the IE6-compatibility right now – “let them know it’s not worth using it”. And of course Steerpike is right: that’s an early development stage, not final. Same with optimization, etc. I agree with you t in most cases except using lorem-ipsum (not the idea behind it), which should rather be replaced with some real text likely to appear in particular areas (which – yeah – is a must-do).

    Daemon: should we really care about the mobile phone users? NO – UNLESS they’re an important part of your target. In most cases they are not. In addition, soon all mobile phones will have webkit-based browsers or some IE and then what? You’ll be rewriting your sites, adding tons of new stuff you suddenly realized could or should be there from the beginning? Creating mobile versions, if you really care, is way better. You make them download much lighter, faster, minimalistic version with the most important stuff while not limiting the whole projects because of your naive idealism. “Equal to everyone” – we’ve seen countries falling because of this idea. It’s impossible to make everyone comfortable and usually it’s not best to. There is no general rule like that – it’s about every project individual needs. Will you throw out all your graphics because I’m gonna watch your site in some text-based phone? You get the point. Everything progresses. If you watched the mobile phones market closely, you’d see soon it won’t really matter. 0,5ghz cpus are standard for PDAs now, next year it’s gonna be 1ghz. And as for normal phones – again, mobile versions are best the solution. And if you wanna use your phone for web most often, you’re more likely to have an iPhone, HTC, or whatever PDA already. If not, then you’re an idiot. You don’t buy acoustic guitar to play heavy metal.

  66. 68

    love the ultimate website checklist, awesome

  67. 69

    Awesome list! I was doing pretty good, but some of these I was missing, they will be in place for my next launch. Thanks.

  68. 70

    If you don’t want to find yourself in court, ensure that you properly cited copyrighted and trademarked products! And if you think that you can use the little icon–that really well-known icon–to indicate the flavor of the document that the user is about to open, you’d better read the fine print on the owner’s website. If you can’t find it on their site, shame on them, but CALL their legal department to get a very clear directive.

    And you’d better be darn sure that your company either created their own images or appropriately paid for images from a stock shop…. Or be prepared to receive a bill from them–and yes, they do that.

    Keep all of this documented so that if anyone from your legal department comes knocking on your door, you’ll have that CYA you deserve.

  69. 71

    I agree with most things in this article. I wont mention the issue of javascript since plenty of others have posted about how silly it is to worry about the 1 or 2 people in the world who have javascript disabled.

    The only other thing worth mentioning is regarding the browser compliance. As a general rule, I test in IE6, IE7, IE8 and Firefox. Sorry Safari and Opera but for a combined 5% of users, its just not worth it unless the client absolutely demands compliance in these browsers (but that should be a little extra for the time needed). IE8 is the exception. Currently, according to browser stats, IE8 only commands around 1.4% but this is IE we are talking about and its use will dramatically increase as IE5 and IE6 get closer to the exit. In an ideal world, every website works in every browser, with or without javascript but the reality for many web designers and developers is that time is of the essence. Clients are more and more demanding for shorter turnarounds and we have to pick our battles.

    • 72

      Hey Xavier: Safari represents the webkit rendering engine, which is also used in Google Chrome and Konqueror (the second most popular browser on Linux after Firefox). So adding one of these three browsers to your test suite can help you cover more user base than you might think!

      Browsers I test with upon every layout change:
      IE6, Firefox 3.5, Safari or Chrome depending on what OS I’m on.

    • 73

      Aww. I use Chrome. I may be tech-savvy, but so are many. One site I happen to use lately is David’s Bridal ( ;-) ) and it doesn’t work well from Chrome (in several important ways). It’s annoying; I HAVE to open Firefox most of the time on that site in order to perform certain actions, like saving an item to favorites.

      It’s a good example, though, because perhaps one wouldn’t think of geeky people using such a site (at least the people within the business, for some reason), but there are geeky fashionable girls, but far more importantly than that: most people get married (and girls are web-savvy too!), and techy people aren’t priced above that store, haha.

      Anyway, yes, occasionally things don’t work in Chrome that work in Firefox; so it’s quite different even though display-wise it’s similar.

      I’d like to add that I think a lot of Facebook gamers use it because it is much faster, and often works better with the games (sometimes it doesn’t). Facebook “gamers” are common!!!

      Just some things to think about.

  70. 74

    Why your site should work with javascript turned off:
    Because javascript is the bas-relief of a website – there’s nothing wrong with adding beautiful carvings into the side of a building, but if it’s been build on a crumbling foundation then all your hard work wont survive.
    The fact that functionality fails without javascript is an indication that the developer doesn’t understand functionality. AJAX enhancements require the server side functionality exists anyway so why are you not first creating the functional version before enhancing the experience with a smooth javascript UI? What exactly are you doing with your website that’s more complex than what google maps does? Yet they can provide a functional experience when the user turns off javascript.

    They can do that because the system has been written properly from the foundations upwards. Not slapped together and had a glossy layer of paint thrown over it to make it look exciting.

    Do your job properly, it’s embarassing listening to you arguing against it.

  71. 75

    Great list! But I really don’t think validation is necessary. If it works in all the browsers (IE6 – 8, FF, Chrome, Safari, Opera, etc) then you’re fine. Using Strict doctype has its quirks, like you can use _target in links. What’s the deal with that? Screw validation. And, I’d add a focus on security. Preventing XSS, injection, overflows, etc.

  72. 77

    Ilya Bodner

    April 8, 2009 7:30 am

    This is a great list for small business owners. Simple yet equally important to do everything on this list.

    Great work!


    Ilya Bodner
    Small Business Owner
    Initial Underwriting Group

  73. 78

    excelent article, added to my favorites

  74. 79

    Nice article. I already have a check list to check all the things before the launch of a website.
    I do xhtml validation, but no css! I am already much into css3 and I use hacks as well!
    W3C doesn’t seems to be liking my habit.
    and one more thing ~~Screw IE6~~ I never waste time to fix things for IE6. If clients insist, I usually handover that part to my colleagues :P

  75. 80


    April 8, 2009 7:55 am

    1. According to my company’s last web stats check, the number of people who use IE6 is about the same as the people who use Firefox. Would you consider Firefox one of the most popular browsers? Also more and more people are using iPhones or similar devices, so if you want to make sure your market is as wide as possible, its probably a good idea to check it.

    2. I don’t remember the article saying that validation had to do with Google indexing. With that said, even if it has nothing to do with SEO, it is related to success of your site, because if you don’t have things coded correctly, they often don’t show up correctly when people view the site. Bad site = less success.

    3. I agree with the JS thing….sort of. I think I saw another comment on here about how the main content of your site should be accessible without JS, but that doesn’t mean your entire site needs to be JS-free.

    4. Yes, the favicon is *one* of the points to check. Just because it was listed first doesn’t mean it’s the most important.

    It seems these days people just want to complain about everything, no matter how useful. I always find it hilarious when you see a string of 20-30 people saying “nice post!” etc… then you have 1 guy saying “This article is horrible!” or something similar, as if it was a personal attack against them. If you don’t like the article, leave it for the rest of us that aren’t on a personal mission to hate everything posted on this site.

  76. 81

    Great article

    Honestly though, people dont browse the web with Javascript disabled unless they manually disable it.
    If you use javascript for things like form validation make sure you have server-side validation too.

  77. 82

    bruce bielawski

    April 8, 2009 8:05 am

    I would love the job of reviewing web sites before launch. It would seem that a ‘web site’ company would have a review person, or even group. I’m hereby starting a new service for anybody with a web design that’s about to go to launch, contact me to review, and see if it’s ready. twitter me @brucebski and we’ll get the source that connects us in on the new company too. I just have to thing of a name. Anyways, this is a wonderful checklist that comes from the school of hard knocks. College education material, seriously, Let’s print it and I’ll sell this to some University…

  78. 83

    This is one of the best “tips” posting I have seen in a long time. Very practical. I know I am guilty sometimes of rushing to get a site or an update up and running and forget some of the basics…….. they always come back to haunt you……. thanks for the info

  79. 84


    This should be included:
    Check if your website works with Adblock Plus (firefox extension) with all filter lists enabled.

  80. 85

    Wow–I have just learned so much by reading this article and the posts and by following the links.

    I am not a developer, but I am responsible for our site. My web developer is just getting started on building a new site from the ground up. This information helps me to understand how to monitor the process.

    Thanks to everyone!

  81. 86

    Great article. Though I have already launched my site, I can still benefit from this list.

  82. 87

    These things are very essential. I also loved the “Ultimate Website Launch Checklist”…

  83. 88

    great great list! thank you! (to Lee Munroe)

  84. 89

    Marcus Nelson

    April 8, 2009 10:58 am

    One part is missing from this article —
    Create an easy way to get feedback from users & thrive off that feedback. Nothing will build your reputation faster then showing users that you’re listening and building for them!

  85. 90

    Great article! I will recommend this to anyone who is starting their first site or blog.

  86. 91

    Patricia Davidson

    April 8, 2009 12:04 pm

    Nice checklist – thanks so much!

  87. 92

    George Munroe

    April 8, 2009 12:13 pm

    Masterclass stuff Lee, well done! Great resource.

  88. 93

    In regards to browser compatibility, I believe Chrome has more market share than Opera now…

  89. 94

    You guys keep knocking out these great articles!

  90. 95

    Erik Wallace

    April 8, 2009 12:59 pm

    Excellent article, a great list indeed. One thing that I feel might be overlooked is using Delicious to tag important pages on a website or blog. I’ve noticed that some of the savvy people I follow tag their articles, blog posts and pages. Seems like it might be a good way to help people find and save your work.

  91. 96

    swetha ganjipally

    April 8, 2009 1:30 pm

    This is an excellent list. If every site did these things first, the Internet would be a much happier place.

  92. 97

    Dude (or gal),
    First of all comments like “nice” and “cool” are completely useless. Second, I’m working on that field for 11 years now and this is the reason why I find 90% of the articles here shallow and too general, telling nothing but bla bla which you can find in any other site. That’s ok, obviously most of the users here are not so long into the web design and they like it, that’s fine. But I DON”T have to agree and I CAN express whatever I feel about certain article, just the same way other people say “fantastic”. You are not the one to judge me, so please in the future keep your advises to yourself unless you have to say something on the topic.

    And on the topic – they missed even to say about testing different resolutions! But lol, the favicon is there! Nothign about choosing hosting provider, nothing about testing dbase queries, nothing about trying to access the site through various continents (I bet you never heard you can do that, try to find that service for yourself, I won’t do your homework for you mean little person:-)

  93. 98

    Excellent Post. Thank you for the insite.

  94. 99

    Great post! Nice info.

  95. 100


    This was a great article like almost every article on this page :)

    Im building a webpage for a hotel and followed this checklist which was great, I have one qustion though about adThis (share with facebook, delicious etc.) that wasn’t on the list:

    What do you guys think is it an important thing and accepted or will it on a hotel page be seen as unserious because the target auidance is mostly older people and companies?

  96. 101

    Wonderful addition to the Ultimate Website Launch Checklist!. This is more in a simplistic way of things.

  97. 102

    I have done some of these…thanks..

  98. 103

    you might wanna check your js code on debugger and console.log statements and at least outcomment them

  99. 104

    Thanx! This is a perfect checklist, which we gladly used for checking.
    It’s a start to set up your own checklist. Quality & content are essential we like to think!

  100. 105

    o and check your outcommented try catch statements in your js code… for debugging these are often outcommented to be able to see where errors occur. But on live they should be capturing your js errors and report them in a userfriendly way to the visitor.
    Hmmm there might be a list of 15 things to check when you put your js code live…

  101. 106

    I think that all listed here is absolutely obvious and It’s really surprising that so many people found it useful :) nice post in any case

  102. 107

    Setting the write permissions for files and directories is also a thing I forget.

  103. 108

    Good, very much helpful for testing, Thanks

  104. 109

    Deepak Gupta

    April 9, 2009 3:15 am

    Many thanks to provide this checklist.

  105. 110

    Great checklist, I second Icepick about Opuast (english and french): it’s a great tool for improving the quality of your websites!

  106. 111

    great stuff!!

  107. 112

    Vitaly/Sven – any chance of a post on JS degradation/enhancement best practices? Seems like it’s a bit of a ‘hot potato’…

  108. 113

    nice post :)

  109. 114

    Cross browser checks with IE are a waste of time. If my site looks good in Firefox, Opera, Chrome and Safari, I’m done. I don’t code for browsers that are not standards compliant. :)

  110. 115

    Thank you, very well done!

  111. 116

    wendy de Haan

    April 9, 2009 9:29 am

    I now have a favicon! Yeah!

  112. 117

    @Pandjarov (#33) and Johny (#37) : I quite agree.

    Surely one of the things that should be done before releasing a blog post is to check that the title is accurate – this stuff is general advice, not a pre-release checklist.
    Most of this stuff should be done as part of the initial site setup, and only needs to be done once.

  113. 118

    I personally believe this is a GREAT list, but checking this everytime MANUALLY is waste of time. I think there needs to be someway to Automating the Unit Testing, so that the validation is run everytime there is any chance.

    Automation Baby Automation….

  114. 119

    @Brian #123
    It is necessary to cross browse/ test/ check within IE (6,7 and 8) because mostly in the East used IE as their browser including Asian or any web developers out there.

    So take a shot with IE first before you consider that your site was checked properly.


  115. 120

    Thanks very much! This really helps (again)!

  116. 121

    Hi. Also accessibility. this is a great list, but you need to make sure it is useable for disabled populations.

  117. 122

    Excelent post!!! I am using some of them right now and I will include the ones that not.

  118. 123

    i don’t know why i thought this could be useful i get here and you guys are are talking about double checking to see if you’ve created a favicon.. .wow! see-L an amature mistake at best :(

  119. 124

    Yofie Setiawan

    April 11, 2009 6:15 pm

    nice article, thanks for sharing :D

  120. 125

    Jeffrey Friend

    April 12, 2009 5:47 am

    Excellent info we should all adhere to. Just missed one very important thing … robots.txt with a sitemap link.

  121. 126

    Very nice&helpful. I’ll try everything. Thanks!

  122. 127

    great information!

  123. 128

    wow ! Simply excellent !

  124. 129

    I believe you meant to say that you should use & instead of just &. I think you have it backwards. Great article, but I agree with most here that using JS is silly.

  125. 130

    good :)

  126. 131

    Jack Bremer - 3B Digital, London

    April 15, 2009 8:31 am

    FANTASTIC – am using some of these points as the central force in my new company-wide Best Practice Manual!

  127. 132

    Aaron Peters

    April 16, 2009 5:45 am

    Having a favicon in place for your site is important. Not *the* most important thing, but definitely something you don’t want to overlook. Not having a favicon in place will cause a 404 error in many browsers. And the 404 error has a negative impact on load time. Browsers handle favicons in different ways.
    IE7 will usually (but not always, for reasons unknown) follow the link in the head and download the image as specified. It’s best to actually include a second link in the head for IE: . If IE7 finds not link(s) in the head, it will try to fetch /favicon.ico.

    IE6 will ignore the link(s) in the head and always try to download /favicon.ico, but only actually show the icon after the website has been added to the Favorites of the browser. Weird stuff, but fits the profile…

    Firefox is a good boy: look for link in head and download the .ico file in the link. If no link is present, try to fetch /favicon.ico.

    IE browsers will not show .png files as a favicon. Only .ico files.
    So this for example will not work in IE:

    Last note: webservices such as Delicious and Google Toolbar will always look for /favicon.ico and ignore the link in the head.

    Conclusion: put the favicon.ico file in the root folder of your site and place two link tags in the head.

  128. 133

    Good article for those final checks. What I’d like to see added would be a check that the design is really maximising the value of the content and getting the desired message across – doing all it can to get a response. Sort of ‘Content functionality’ I’d say – that there’s focus on the right elements, no distractions in the design, there’s flow through the content, calls-to-action are reinforced etc.
    Oh, and proofreading is the checking of typographical/ ‘type-setting’ errors – what you described under this heading is copy-editing… a proofreader would’ve picked that up!

  129. 134

    Great Comprehensive List. Keep it up.

  130. 135

    Brilliant compilation. I always forget favicons and feed meta. Bookmarked.

  131. 136

    Great list!
    I was suprised that so many people are defensive of javascript. I guess I’m one of the “1 or 2” people that leave JS turned off. This stops new window pop-ups, and some annoying windows that ask if you’re sure you want to leave the site. Sometimes I’ll turn JS on if a site needs it to function, but I can’t stand sites that don’t work without JS or Flash enabled and don’t provide alternatives.

  132. 137

    David Radovanovic

    May 26, 2009 4:15 pm

    SEOMOZ and Hubspot offer a membership fee for a suite of useful (up to date) SEO tools. It would be great if there were more like these two, especially with more emphasis on self serve SEO. Just a thought. Thanks for your very useful post!

  133. 138

    Aravind Babu

    May 29, 2009 11:02 am

    Great!…Very useful post

  134. 139

    haha i love bobs comment … this really is a lot of hullabaloo. throw your stupid PCs and Macs out the window and grab a surfboard and head out to some lonely mexican beach to get back in touch with real life.

  135. 140

    I am looking for checklist that lets a small bank check each of its web pages for FDIC compliance. Things such as is there as pop up indicating you are leaving a secure site for an open one.

  136. 141

    Perfect timing, I was about to do one of these but this is just what I was looking for, thanks

  137. 142

    Great list, I am a newbie and would like to learn more about caching will someone please guide me ( a url, an ebook) please.

  138. 143

    CMI Web Studio

    July 3, 2009 12:20 pm

    this article is right on the money. so many web developers don’t even validate their code against w3c standards, or some of the others mentioned, and it’s the difference between professionals and novice amateurs in this business.

  139. 144

    h-a-r-v wrote: ‘You don’t buy acoustic guitar to play heavy metal.”

    Why not? Jimmy Page did. I think he was pretty successful.

  140. 145

    Here is a good one – make sure you have some way for prospective customers (etc) to contact you. If you are offering products for sale, make sure people who might want to buy them can see how much they cost. Perhaps make sure that if you are offering them for sale directly, you give them a way to actually purchase them. If you only sell via resellers, then include links to reseller websites. You should also inlude things like detailed specs and information on your products, perhaps online (pdf) user manuals if applicable. Note you should not only do this for “current” products but also for any products you’ve sold within the last few years – it greatly increases the resale value of your brand, which might increase how much someone buying new product from you might consider worth paying. (New BMWs and Hondas sell for more than new Chevys and Fords because they know when they are ready to upgrade, they will get more for their used BMW or Honda than a Chevy or Ford)

    Don’t forget to include some way for people to contact you – a phone # (that someone answers during business hours), an email address, and maybe an online form. (Note: an online form by itself is not sufficient, nor is any method that forces a potential customer to give you *their* contact info and wait around for you to get back to them)

  141. 146

    Richard Pelletier

    September 1, 2009 10:22 am

    I am completely amazed at how many “newly launched” sites have title tags like “home” or just the name of the business. Thanks, Smashing, for a smashing article.

  142. 147

    Thank you for an informative and interesting read.

  143. 148


    November 2, 2009 2:29 am

    great advice,, makes me inspirated. thanks for this article

  144. 149

    Thanks….. to developer and post.
    Really great!!!!!!

  145. 150

    I am continually astounded by this website’s ability to know exactly what I need to know just when I need it.
    Whatever you guys are on, keep taking it.
    Now, next week’s lottery number please….

  146. 151

    nice blog keep up the good work I will comeback soon to read more articles
    thanks and regards

  147. 152

    Thanks for providing a good information.

  148. 153

    great article.
    keep on rolling!!

  149. 154

    Great article :)

  150. 155

    sorry i left few things and now i had already launched Technical Quest website .. but i will try to improve in future and apply these tips to my new website..
    thanks a lot for this precious information

  151. 156

    Thanks for this post. Great information for me.

  152. 157

    Thanks for this post. Great information for me.


  153. 158

    This is a decent list, a Favicon is nice to have but would be near to the bottom of my list.

    One of the biggest areas is the functionality check, depending on how big and complicated your site is. For bigger sites, having a proper testing plan where you think about the functionality that you need to test, what outcomes you need to test for and what you expect to happen before going straight into it is a good idea.

    Overall though it is a good checklist.

  154. 159

    Another smashing magazine post to pass on to my bosses to show how we should be doing things!

    vinyl letters

  155. 160

    Hey I landed on your site by accident on bing while hunting for something really irrelevant but I am truly glad that I did, You have just caught yourself another subscriber. :)

  156. 161

    Nice post, some great things to think about..

  157. 162

    Great article, thanks very much! I have to print this list and check it every time I finish a website.

  158. 163

    This may as well be the most useful,brilliant advice I have read online.Can you tell me where and if I can find someone to do all that for me?Something like outsourcing but trustworthy?

  159. 164

    very complete!

  160. 165

    I will definitely make an instruction board for my employees. Nice one, thanks.

  161. 166

    Hey, thanks alot for such an informative post…definitely gotta bookmark this one.

  162. 167

    Handy checklist.. If there are pdf’s or articles to be downloaded it is also better to check once.

  163. 168

    Thanks for the check list, it will be very useful to every one.

  164. 169

    Nice article. Some other nice wordpress plugins I use are slimstat, pagemash and all in one SEO. Yahoo analytics is also a good option if you don’t want to use Google Analytics.



  165. 170

    Sergio Carabetta

    October 17, 2010 7:41 am

    It’s great to see that there are more people who enjoyed and appreciated the effort put in this article, than the trolls that “already knew all this stuff yet” and try to show everybody else that they should be writing the absolute best articles… if they wanted to.

    Thanks and keep doing a good job!

  166. 171

    great article with some very good resources. I found several of the checklists very helpful Thanks

  167. 172

    A great compilation of checklists. I’m attempting to put all this information together in just one place/book. These checklists have been an invaluable resource. Thank you!

  168. 173

    One of the best programs for checking broken links, both internal and external ones, is (Xenu, freeware developped by Tilman Hausherr. We use is for our translation company web site, Übersetzungen, and for our language training company homepage, Sprachschule Berlin.

  169. 174

    Good article for those final checks. What I’d like to see added would be a check that the design is really maximising the value of the content and getting the desired message across – doing all it can to get a response. Sort of ‘Content functionality’ I’d say – that there’s focus on the right elements, no distractions in the design, there’s flow through the content, calls-to-action are reinforced etc.
    Oh, and proofreading is the checking of typographical/ ‘type-setting’ errors – what you described under this heading is copy-editing… a proofreader would’ve picked that up!

  170. 175


  171. 176

    Manuel BAGO COBO

    March 30, 2011 12:53 am

    Great post!!! congratulations.
    Also I look as necesary yet “Google Website Optimizer”

  172. 177

    thanks for this valuable information

  173. 178

    Elijah Nitcher

    May 19, 2011 1:46 am

    My developer is trying to persuade me to move to .net from PHP. I have always disliked the idea because of the costs. But he’s tryiong none the less. I’ve been using WordPress on numerous websites for about a year and am worried about switching to another platform. I have heard great things about Is there a way I can import all my wordpress posts into it? Any help would be really appreciated!

  174. 179

    Abhishek Singh

    May 31, 2011 3:44 am

    Nice Article.. Thanks :-)

  175. 180

    I think this is one of the most significant information for me. And i’m glad reading your article. But wanna remark on some general things, The web site style is great, the articles is really nice : D. Good job, cheers

  176. 181

    Very helpful post.Thanks

  177. 182

    I’m looking for a internet marketing forum that has no spam on it and that has an active community. I’ve tried several in the past such as DP and they just have to much spam. Can anyone suggest an internet marketing forum that has no to very little spam and helpful insightful internet marketers on it? Thanks!

    • 183

      Catherine Anderson (@SparkySparkler)

      May 7, 2012 6:05 am

      I would try the marketing groups on LinkedIn – I find those very useful and full of professionals who are all there for the same reason – to learn and contribute.

  178. 184

    Nice post, I guess it covers most of the technical and usability problems. But there’s one more thing to plan maybe : you should have a marketing plan before even thinking about putting your website online.

  179. 185

    You forgot server load test… need to emulate traffic…

  180. 186

    Still accurate! + cross platform + cross resolution check!

  181. 187

    Thanks for the great checklist. I’m getting ready to launch my first website sometime this month. I’m a novice, so this is very helpful.

  182. 188

    Very informative…. Great job.

  183. 189

    Dave Macdonald

    August 14, 2012 10:27 pm

    I like how you mention Favicon first. We recently started adding iPhone favicons and it always seems to get forgotten on the first roll out!

  184. 190

    Very nice! Thank you!

  185. 191

    Thanks! Wasn’t sure where to start but this has been really helpful!

  186. 192

    There are too many “Launch Checklists” posted on the internet that are really list of QA Tests that should be done LONG before the actual launch.

    What’s missing is a good list of the things that need to be done on the day of the launch cutover.

    Two very different things.

    But this is a decent enough QA checklist…

  187. 193

    Youssef ilouafi

    September 25, 2013 11:46 am

    Great article,
    it gives the right advices to enhance the web.

  188. 194

    It’s a great article and easy to understand :) well done

  189. 195

    Checking the site after a cache clear, or on a new machine, is imperative – as you may see all the bits still from your cache, but the live site could be empty!

  190. 196

    It’s a great article and easy to understand :) well done


↑ Back to top