Millions of websites being launched year after year can only signify two important things. One, the importance of being on the net, regardless of whether yours is a small business website, a home page, an ecommerce or even a portal, and two, easy availability of variety of free templates which make website building a child's play.

In this article, let us try to explore whether templates, free or paid, offer suitability and ease of working and why they are taking the newbie web owners and builders as well as professionals by storm.

Website templates are pre made web designs into which you can start filling in your information straight after downloading. Easily, this eliminates the cumbersome task of having to design an appealing layout and more than that, it does not want you to have any knowledge of HTML at all.

At this point in time, you might be tempted to ask, if this is all, how good it is over HTML editors which don't require a template to be downloaded for every time you are building a website? True, they don't require you to possess knowledge of HTML but they still rest the task of creating an appealing layout upon you, juggling with color schemes, and placement of different sections on your page etc which are really not your job. It is precisely here that the website templates fill the void- import web templates into your favorite HTML editor and get-set-go with site building.

Conventional method of web designing is out of date as it takes a lot of manual labor a web entrepreneur can hardly afford to waste. When web presence matters to you for reasons beyond passion, you would never want to waste time and efforts on designing your own templates or even purchase them in bulk.

Free templates are in no way inferior to paid templates but you have to be choosey about your source. They do not limit your aspirations; instead you can have a variety of them such as free CSS templates, PSD templates, besides the plain HTML types. The very reason these templates are a matter of big business today is their aesthetics, functionality, easy of use and of course, the huge demand.

Free templates also make business sense considering the number of websites the ordinary people launch every month. To get your business off by launching hundreds of websites you know what makes sense and what not. Choose your templates without compromising on your needs and let the cost be condoned by the world.

Don't be fooled by seeming simplicity. A lot of developers get comfortable with a certain way of designing a database for their web applications that they miss out on techniques they should rather employ to make things run faster and more efficiently. A lot of developers don't bear in mnd that the small site they are creating now might grow into something incredibly large and complex, and the database they designed has become bloated and doesn't scale well to meet the demands of the increased traffic.

This article hopes to provide web developers with a few techniques to help make their database and queries faster and more efficient.

1. Avoid Character Types

When you are designing a database, it is so easy to set all data types to the VARCHAR type as it can then contain any data you want; numbers or text. But character data is amongst the most inefficient data type you can get. If a field is only going to contain numbers, then make it one of the appropriate types (INT, DOUBLE, etc).

Also, wherever possible in your web development code, try to use numeric data types as opposed to characters. One of the most common things a script has to store are flags like whether someone answered yes or no to a question, etc. You could of course store it as 'Y' or 'N' but why not store it as 0 and 1?

The reason this makes a difference is when you have a database, for example, with over 500 000 entries, and are running a SELECT on that field, comparisons are processed a lot faster for numeric data types than character types. Also, if you need to return data to the calling script, numeric data is less memory intensive than character data. In addition, your web development language (PHP, ASP, etc) would also be able to process and perform functions on numeric data better than character data.

I am not trying to convince you never to use character data types. Sometimes it is a necessity, but if you can find ways to reduce the amount of character data processed by your SQL database, the better your server will cope.

2. Normalization

Normalizing a database is really quite a complex process. It is a process that describes a way to design a database structure to avoid repetition of data in your database and can lead to significant performance benefits if employed correctly. However, the entire process of normalisation is a bit beyond the scope of this article as it can fill books on its own, but any developer designing a database should seriously consider becoming knowledgable about normalisation and employing it in their own designs.

For a good tutorial on this process: http://www.keithjbrown.co.uk/vworks/mysql/mysql_p7.php

3. DateTime vs Timestamp fields

This actually relates to 1. a bit. The big difference to bear in mind here is that a field of type DATETIME is actually stored as a series of characters. A field of type TIMESTAMP is actually stored as an integer. So therefore, a more efficient way of storing dates is using the timestamp method. The timestamp has its drawbacks however. For one, you cannot store a date early than 1 January, 1970. Also, timestamps in your script will need recalculating to get to the character format. Because of this recalculation, it may not be better to store as timestamp. It really is a case of testing which format works better for your needs.

4. Use LIMIT where possible

In your queries, if you are doing a SELECT to a database and you only expect a certain number of results, using the LIMIT statement can speed your query up incredibly.

For example, if you have a table of users and you need to run a query to search for one users record, you can use a query like:

SELECT user_name FROM users WHERE user_id = 453;

This query is perfectly valid and will return the right result. But you also know there will only be ONE result. The query above will search the database, find what you want, but then still continue searching after that. It would run a lot faster if you could tell the query that once it has found what you are looking for to stop searching. LIMIT can do this, as this query shows:

SELECT user_name FROM users WHERE user_id = 453 LIMIT 1;

Imagine this scenario. You have a table called logins, that records every login from a user. It currently contains over 2 000 000 records, and you want to find the first time a user logged in. Now bear in mind that because this table inserts data over time, it is already sorted for by date. You could do the following query:

SELECT MIN(login_date) FROM logins WHERE user_id = 4876;

This will return the record you want, but SQL will now have to get all dates for that user, sort them and then return the lowest value to you. Our table is already date sorted simply because of the way it records data for us. So using LIMIT can be more effective:

SELECT login_date FROM logins WHERE user_id = 4876 LIMIT 1;

Because it is sorted, the first one will always be a users first login.

5. Avoid using LIKE

If you have tried to employ 1. above, then hopefully you will be in a scenario where you do not need to use LIKE all that much. LIKE is one of the most inefficient ways of searching a table. LIKE performs a text comparison search in a field and with no wildcards is as efficient as a direct comparison; i.e. WHERE name = 'Jane' is equivalent to WHERE name LIKE 'Jane'. It is when you start introducing the wildcard characters like '%' that things get really hairy.

If you do have to use LIKE, then at least try and make efficient use of the wildcards. These are '_' (underscore) and '%'. Let me explain all this with a real world example.

In a project I was involved in, we had a SQL database storing logs generated automatically from a mail server. Unfortunately, the mail server pretty much just dumped a very long string of text data into a field that contained the data we wanted. A script had to be written to find all logs that referred to a login by a user into the POP server. The only way we could do this was to search every record for a string in the msg field that had the text "User logged in" in it. The first query developed was something like this:

SELECT msg FROM logs WHERE msg LIKE '%User logged in%';

This query took on average of about 35 minutes to process. Obviously not an ideal situation. The way the LIKE worked here was that it had to parse through every single portion of each and every record in the msg field looking for text that matched "User logged in" anywhere in the text. We were able to determine eventually that the text "User logged in" occured at the end of that text in the msg field and so we altered the query:

SELECT msg FROM logs WHERE msg LIKE '%User logged in';

The '%' at the end was removed as we do not want to worry about text after because there is none. The query now only compares text to our string in the msg field at the end of the field and no longer parses through the entire piece of text stored in msg. The query now ran in under 2 minutes. (This was actually still too long, but how we optimised from there is a little beyond the scope of this article.)

Hopefully with all these elements put into practice on your next web development project, you can have a database that runs quickly, efficiently, uses as little resources as possible and wont grind to a halt when the load suddenly increases.

Here's an analogy for you. Yesterday, I was working my butt off in the gym on the cardio machines, panting wildly with sweat dripping off me and my face as red as a beet. Not the most attractive sight, but I figure, you're at the gym to work out right? I might as well "go hard" or "go home", as they say.

As I looked around me, I could see all these people simply going through the motions. There they were, minus perspiration in their shiny new lycra and expensive gym shoes, casually walking on the treadmill or lazily turning the wheels on a bike while reading a book or glued to the TV screens in front of them. Only a few seemed to be there for the actual purpose of working out. The rest seemed to be there to check out the talent or to simply keep up the appearance of fitness, while doing the bare minimum.

Huh? I don't get it. Why have these gym bimbos paid so much money for a gym membership and all the related gear if they aren't going to take full advantage of their investment?

Then it struck me - these gymbos were just like those companies who spend thousands of dollars on a shiny new website with all the bells and whistles like graphic design, blogs, shopping carts, web analytics, the lot and then fail to take advantage of it. I see it so often, regardless of company size. Web sites that could easily be bringing in loads of traffic and revenue simply wasting away because nobody can be bothered tracking visitor activity, analyzing trends or checking for search engine compatibility and usability.

These companies are simply keeping up appearances, investing heavily in Internet technology because their competitors are doing the same. But no thought has gone into the search engine compatibility of the site, how usable it is for visitors or whether it meets accessibility guidelines. They don't look at their site statistics, they don't check for broken links and they sure as heck don't investigate why their sites aren't converting traffic into customers. What a waste!

Is your web site working hard enough for you? Run it through the following 20 point fitness assessment to find out:

- Is your site fully search engine compatible? Are all your pages being indexed by the major search engines?

- Do you track your visitor statistics on a regular basis? Do you use the information provided by your visitor statistics to improve your site?

- Is your web site accessible to visually-impaired visitors? Does it meet the international standards set down by the Web Accessibility Initiative (WAI)?

- Do you know which sites and search engines provide you with the most traffic? Do you use this information to increase your traffic further?

- Do you track the source of all reported errors in your site statistics and fix them promptly?

- Do you know which keywords your site was found for in the search engines? Have you conducted keyword research to determine what search terms your target markets are looking for so you can optimize for them?

- Does your web site HTML code validate to W3 standards? Do you check for validation regularly?

- Does your site contain zero broken links? Do you check for and fix broken links regularly?

- Has your site been fully search engine optimized to integrate your target search terms into your Page Titles, META Tags and visible page text?

- Have you created and submitted an XML sitemap to Google Sitemaps?

- Have you created and submitted a sitemap to Yahoo Site Explorer?

- Have you checked to see if your site meets Google's Webmaster Guidelines?

- Do you measure your visitor sign-ups and conversions on a regular basis? Do you tweak your landing page copy to increase the conversion rates?

- Is your site navigation intuitive and are your visitors following the navigation paths you intended?

- Do you encourage feedback from your site visitors and provide an obvious way for them to provide such feedback?

- Are there at least 250 words of text on your home page to satisfy search engines?

- Does your site contain a visible, text-based site map to aid user navigation?

- Do you have an ongoing link building campaign running to secure more incoming links to your site and improve your site's link popularity score?

- Does your site have a high percentage of repeat visitors? Are the majority of your visitors staying on your site for more than a minute?

- Do your search engine referrals and site traffic figures grow each month?

Unless you can answer yes to all the questions in the above checklist, your web site is not working hard enough for you and needs a workout. Get to it!