Sometimes we the developers, up our site live and face some problems. this is very often happen when deadline comes nearer. if we maintain a pre-launch checklist before make our site live then we may not face such problems like:
1. Error Management: check whether your site has a 404 not found page that includes links to functional pages. this may happen when you port an existing site to some major changes. so include some pages links to this page so that user can easily find the working page.
2. Valid Markup: check whether every page validate as XHTML or at least HTML. otherwise you may find several problems in different browsers and may be a real mess if you browse from mobile phone.
3. Basic Browser Test: check your site’s pages in many browser as you can. specially FF3, IE6, IE7, IE8, Safari, Google Chrome.
4. Minimal Semantic: Check whether every page has unique and relevant title, meta description and meta keywords. without this your search engine rank will suffer.
5. Control Search Engine Indexing: Check if you created a robot.txt in your webroot or not. it’s better for search engine crawler.
6. Favicon: Check whether your site have a favicon file or not. if you omit the favicon icon then each visitor to your site will add an additional 404 ’favicon.ico’ not found error message to your log files.
9. Search Submission: Create a valid XML sitemap and submit your site for search engine indexing.
10. Compress Throughput: Enable gzip compression on your web server, it will greatly improve your network throughput at the cost of a negligible amount of CPU overhead. You can also make it happen using php code at top of the page.
11. Domain Distribution: Keep your external files accessed by your site like images, js, css distributed over several domains. Many browsers, by default, will not make more than two simultaneous connections to a single domain. But it will make many connections to different domains simultaneously. You can use sub-domains but it will cost a slight delay as each domain needs to be resolved before any requests can be sent to it.
12. Common URL Checks: Check if the passwords or back-end source code be accessed by simply navigating to a URL? Some common examples to check are: