Crashing Customers? - have you tested your website?

08 Jul 2002

  • Tweet this item
  • share this item on Linkedin

How many times has your browser crashed? It may not be your fault, has the site been tested?

Problems that are on your site and at best are detracting from its efficiency, at worst are costing you money by devaluing your brands and losing you customers.

Question?
How would you proof read, 150 pages of technical data (say a technical manual) looking for around 60 potential problems, reading say 100 lines per page ? All within a minute………….

Answer
You wouldn’t it isn’t possible – that’s about 900,000 checks…. Sitemorse™ performs this on an average site every minute - manual testing with such accuracy & efficiency of your website isn't possible.

Until now it has not been possible to test every element on every page of your site for problems - some that are visible, some that are not (from simple missing images, to more serious faults eg corrupted cookies).

- Internal (self) Testing
Testing performed internally often fails to highlight problems obvious to external users, essentially because the site is relying upon some feature of the company internal network that is not available outside it.

This can include, for example, domain name search paths, access to resources blocked by the firewall, routes to private address space, etc. The only simple way to test that the web site works from outside the company network is to perform the testing from outside the company network.

There is problem for those who are directly involved with the development or deployment of the site – not being about to spot problems due to their reaped exposure to the site, in essence not being able ‘to see the wood for the trees’ effective and efficient QA / checking of any work is not handled by those who commissioned and carried it out the development.


We have made testing you own site simply - you only need to key in your website address.