Poor Function

Poor function can be caused by a range of elements, but it consists of a site that performs poorly in a mechanical way - such as scripts which give errors, visible HTML code on the page instead of visual elements, broken links, missing graphics, buttons that don't work, etc.

Poor function is USUALLY the result of a coding error, but it can occur because of unexpected actions on the part of a user, or by the user choosing a browser that you did not anticipate.

  • Most users will not stop to question whether they should be using a different browser.
  • If they set their font size larger than you thought they would, and your page breaks and does unexpected things, they won't think that they should change the font size, they will think your design is bad.
  • If they view your site on a small monitor, they will just think you are rude if your site does not allow them to access necessary features.
  • If they are using an older browser and your new code does not function in it, they won't wonder if they need to update, they will just think your site does not work.
  • When they click a link and it gives them a 404 error because you mistyped the URL, they won't be able to correct it.
  • If an image is not where it should be, they will not get your message.
  • When code shows on the page instead of the feature you wanted there, the visitor will just go somewhere else to see if they can find what they want.

I have seen these issues with thousands of sites. I have seen them on some very major sites (eBay frequently has visible code on the page instead of elements at the top). Accidents happen. If you, like eBay, provide a world-renowned service that everyone wants anyway, and if your mistakes, like eBay's mistakes, do not interfere with that essential service, people will stick around anyway.

But if you are trying to compete with thousands of others offering the same thing, or if the malfunction is serious, then people won't keep trying. They'll go somewhere else to find what they want.

If you use Java on your site (not the same thing as JavaScript), it may appear to not work on older systems, because it takes a long time to load.

JavaScript frequently malfunctions, either because the script was corrupted, or because the site designer made changes that were not done accurately. Rollovers, buttons, and other interactive features which are supposed to be simple and transparent to the user often end up doing weird things instead of what you intended.

The more complicated a site is, the more of a chance there is for something to go wrong. Again, keep it as simple as possible, and make sure there is a good reason for any advanced features that you add. Simple is always more predictable. Complex always takes more testing to insure reliability.

Reliability is pretty necessary! I mean, nobody cares if your site boasts the only feature of its kind. It won't matter how cool it sounds, or how much it promises to do, if it fails to do it as promised, or if using it is so inconvenient that it is not worth the trouble.

When you decide that advanced features are necessary to the function, it is worth your time and money to insure that it is done right. An experienced developer or coder will know better how to adjust the code for reliability and predictability. And that experience can save you huge hassles and expenses later.

Written by Laura Wheeler