Connecting you with Australian culture online
There are a lot of things that can go wrong with a website, and it's those little things that can annoy users and drive them away. So it's essential that you test your website thoroughly.
If possible:
Testing should be carried out by as many people within your organisation as possible, preferably by those who have not designed the site.
Bring in testers from elsewhere. Get people outside the organisation on old computers and slow modems to test it.
If you have a computer network, your site should be made available internally for testing.
Ask these questions when you test:
This testing should not stop when you go online. Log onto your site frequently to make sure that it still does what it should.
You might like to try
Dr Watson (1) to tune up your site for free.
There is a great temptation to change a site while it is online, which means the changes become public before being properly tested.
It's not unusual for your development and modification process to cause the server to crash, stopping access to your site, and to any others held on that server! Such crashing is not an uncommon occurrence during development. Although it may not worry you that much, it will certainly worry your users and those responsible for any other sites or data hosted by your server.
Notify users in advance if a server will be out of action for testing, and try to test during times of lowest use.
Develop and test your website rigorously, by all means, but refrain from jeopardising access to other sites in doing so.
There are several ways that the use of your site can be evaluated automatically.
For example, if you have surfed the Net you may have noticed on some Web screens a counter that states that you are visitor number 1,234,567 to that site. This software is not so much for your benefit as to provide important information for the Web manager. Of course, if you have very few visitors, a counter that indicates this could be counterproductive (if you'll pardon the pun).
Similar software, called a cookie, can tell which screens users visit. You can discover what links they used to get to and leave your site. You can even obtain information about the user's computer and operating system. In fact, this information is obtained about you almost every time you go to a site.
Numerous statistics packages are available to help you monitor your site usage. It is well worth analysing several packages before deciding which one to go with.
You need to know what sort of information you require and to look for a package to meet those needs.
If you're looking for something very simple and which is free, have a look at
StatCounter (2).
|
15 of 17 |
If you can see this message, you are probably not seeing this site in the way it was designed. This site uses cascading style sheets (CSS2) to control the way in which elements are displayed on the page.
You will still be able to access everything in this site, but we do recommend you upgrade your browser to a more recent, standards compliant, browser.