Browser. 15 Essential Checks Before Launching Your Website. Advertisement 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. 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. Favicon A favicon brands the tab or window in which your website is open in the user’s browser.
And if you have an iPhone favicon: Titles And Meta Data Your page title is the most important element for SEO and is also important so that users know what’s on the page. Cross-Browser Checks Proofread Read everything. High Performance Web Sites. The article Use compression to make the web faster from the Google Code Blog contains some interesting information on why modern browsers that support compression don’t get compressed responses in daily usage.
The culprit? Anti-virus software, browser bugs, web proxies, and misconfigured web servers. The first three modify the web request so that the web server does not know that the browser can uncompress content. Specifically, they remove or mangle the Accept-Encoding header that is normally sent with every request. This is hard to believe, but it’s true. A large web site in the United States should expect roughly 15% of visitors don’t indicate gzip compression support. This blog post from Arvind Jain and Jason Glasgow contains additional information, including: Is there something about your browser, proxy, or anti-virus software that’s preventing you from getting compressed content and slowing you down 25%?
Database Normalization and Table structures. Unfortunately, this is not quite correct.
To give a quick summary, the normal forms are as follows: 1NF: Every row must be an identifiable relation. This means that, in a table, no row may be an exact duplicate of another row, and nor may the row be completely filled with NULL. 2NF All non-key attributes of the table must depend on the entire key. This means that, when a table has a compound key, attributes which depend only on a subset of the key columns should be moved out of the table. For example, take the comment above which mentions a compound primary key of OrderID and LineNo; if the application wants to use invoice_bgcolor to alternate the background color of rows on an invoice, it should go outside of this table, because it depends on LineNo but not on OrderID 3NF You have 3NF pretty much correct above. Finally, as stated above, a table must meet all previous normal forms, ie: 2NF implies 1NF, 5NF implies 4NF, 3NF, BCNF, 2NF, 1NF, etc.
A database is normalized if it is in 5NF. Performance tips for web applications « The Storyteller. I have recently came by the article “High performance websites” in yahoo developer network.