There should always be a good reason why to make a web site. "But everybody else is doing it" is not a particularly good reason. The reason should be thought about whether the pages are for a large company or an individual person. A web site without information is needless and only a waste of time and bytes. It should also be taken into consideration what kind of information the users expect to find, what they are looking for.
However my report is not considering what a web site should contain. There is not a single answer
to this question. This is not a HTML-guide either, dozens of these can be found in Internet or in
the libraries. I am writing about the site design, page design and content design in general and
how web site can be made userfriendly and also attractive. I will only deal with the basic elements
like navigation, graphics, text and page layout and the structure of the site.
1. Site design
The structure of the site is not as clearly seen as is the page design and content. That is the reason why the design of the site structure is often forgotten in the design process. If the site contains vast amount of documents, the structural design of site becomes more and more important, or the user gets easily lost. A small site (less than 20 documents) does not need very careful structure design.
1.1 Structure models
The site structure can be described with 3 different models: linear model, tree model or net model. In most cases none of these models are purely used. Usually a site is a combination of all models mentioned before and the result is somehow net-like.
1.1.1 Structure model
The linear model is like a book: the user is forced to move on from one page to another in the same order as the author has designed. In most cases, this is not a recommendable model. The model does not utilize the opportunities of hypertext at all and the user is not capable to look for the information he or she is interested in.
The good aspect in the linear model is simplicity. The user is not given a possibility to get lost. [Metsämäki 1996]
However, there should not be many sub-levels in the tree model, 2 or 3 or in some cases 4 is an appropriate number. [Metsämäki 1996]
The main purpose of the main page is to give user an idea of the site and what it contains. Based on the main page the user can evaluate whether the site is useful and if it is worth to spend more time looking around.
There should also be the links to the sub-page in the main page, of course. The main page is the central point of the navigation. But when designing navigation the designer should remember, that all users do not see the main page first, because if the user arrives to the site via search engines and links they can be lead straight to some sub-page. Every sub-page should contain a link to the main page. [Nielsen 2000]
The following information is supposed to be found from main page in addition to the links and the description of the content:
When designing the navigation, the following things should be taken into consideration:
The search-function is ought to be in every big site (more than 100 documents). Jacob Nielsen’s usability studies show that about a half of all users are search-oriented, they usually go straight to Search-button and they are not interested in looking around. [Nielsen 2000]
1.4 URL
The URL (Uniform Resource Locator) needs to be designed, too. It is not indifferent what kind of
string of characters it is. The URL should be short; it decreases the possibility for errors. The
usage of special characters and uppercase characters is not recommended. The URL is supposed to be
in common language and descriptive, so that users can expect what they are going to find behind an
unfamiliar URL. And the last thing: URL should look good in e-mail addresses. [Nielsen 2000]
2. Page design
2.1 Using screen space
The screen space is always limited and the navigation takes some part of the screen space. The web page is ought to be dominated by the content, not by navigation. It is just a necessary evil that is not a goal itself. However, this does not mean, that the page is supposed to be overly compact with no white space. White space is not wasted when it is part of content or navigation design. There is said in chapter 3 “Content design” that the texts are ought to be easy to scan through, easy to read, and the paragraphs ought to be clearly separated from each other. White space helps with these goals. The easiest and fastest way to separate paragraphs is two blank rows. And it is not easy to read screen-wide text but the text is better in a narrower table and the side or sides are white.
Sometimes one can see some very trendy layouts with extremely complex frame schemes, it is called sometimes an inline frame. The empty frames surround the little window in the middle of them. The window is maybe 20% of the screen space and all the information is introduced in it, the rest is empty or for navigation. This kind of website is a total disaster, most of the screen space is just wasted. [Nielsen 2000]
2.2 Different browsers
One page can look very different when viewed by different browser or by the different version of the browser. Sometimes the page may not be working at all. This problem often can be avoided by using only standard HTML -language but even when used standard HTML page can look different though it is working properly. [Nielsen 2000]
Yet, the page is supposed to be working well with both leading browsers: Internet Explorer (IE) and Netscape Navigator (NN). If it works somehow with less known browsers, like Mozilla, Opera etc. it is fine, but there is no need to configure the site especially for Opera or another not widely used browser. It can cause some not wanted effects when viewed by IE or NN. Usually there are enough problems to make the pages work with NN and IE, in my experience when pages are fine with IE, they work with Opera and Mozilla, too but optimising for Navigator results most of the problems.
2.3 Different displays
The designer does not know what kind of display the user has, what is the size of display, what is the resolution or the colour quality. Despite of that the page should work with different kind of displays. In most cases it is enough if the page looks tolerable in 14-inch monitor with 800*600 resolution and in 21-inch monitor with 1152*864 resolution. Most users still use traditional table CRT’s (cathode ray tube) or LCD (liquid crystal display) with laptops though different kind of PDA’s (personal digital assistant) are becoming more common.
The first way to take into consideration the different displays is not to use exact size attributes with tables, pictures, fonts or frames. It is recommendable to use proportional attributes. When using frames they are ought to be resizable.
Not recommendable: FRAMESET COLS="200,*"
Recommendable: FRAMESET COLS="20%,80%"
Some web authors have solved the display problem by creating two separate sites: one for smaller resolution and another for bigger resolution. Sometimes it is a good and working solution but it doubles the updating work. [Nielsen 2000]
2.4 Response time
The users hate waiting. Pages should be made so, that the download is as fast as possible. The HTML-code is very quick to download, but the graphics take most of the bandwidth. That is the reason why pages with heavy graphics should be avoided.
There are some tricks to make page download faster:
There are listed some meanings and associations of different colours in the table 2.1
Table 2.1 Colours and associations [Sinkkonen & Kuoppala 2002] [Peltonen 2000]
| COLOUR | ASSOCIATION | Red | Love, fire, danger, warmth, stimulating | Orange | Warmth, fire, stimulating, joyfulness | Yellow | Sun, dynamic, attention | Green | Nature, calmness | Blue | Cold, water, sky, calmness | Purple | Royalty, mystery, dignity | Violet | Festivity, coolness | White | Cleanliness, innocence, modesty, emptiness | Grey | Conservative, ordinariness | Black | Death, night, darkness, mystery |
How the pages are made easier to scan?
The font should be clear and big enough with any resolution. It seems to be highly fashionable to use extremely small font, but it certainly is not recommendable. Luckily, the user can change the font size in his browser when using Internet Explorer.
The Sans Serif fonts (Arial, Verdana etc.) are better for web page than Serif fonts (Times New Roman etc.). The Sans Serifs do not have finishing strokes, thus they are clearer than Serif fonts. Times New Roman is often the default font of the browsers and if some other font is used, it is recommendable to specify more than one font, for example: [Nielsen 2000] [Nielsen 2002] [Fontmenu.com 2002]
Example: font face="Arial, Verdana, Helvetica"
3.2 Graphics
As it is said in 2.4, all pictures, photos and other graphical elements are ought to be quite small and quick to download. But graphics always take more time to download than text and that is why they should be used sparingly. It is true that one picture is worth of thousand words, but the web author should think whether these thousand words are important or not. If not, the photo should not be used. There are not supposed to be any needless graphics on the web site. Photos and pictures should always strengthen the text content; any decorations are not needed. [Nielsen 2000]
3.3 Animations
Animations catch user’s eye very effectively. For that reason using the animations should be minimized. In some cases it can be useful when it is illustrating change or visualizing three-dimensional structures, but in most cases animations are needless, even annoying. Moving texts should be used very sparingly though they are very effective to catch attention. The moving text should be short enough to see at one glance. According to Jacob Nielsen’s usability studies, users seldom read a long, moving text. [Nielsen 2000]
References
Fontmenu.com 2002: Sans Serif, http://www.fontmenu.com/site/sans-serif.html, 2002
Iiskola 2003: Antti Iiskola, Viritä kotisivusi tiukkaan kuntoon. MikroBitti 3/2003. Sanoma Magazines 2003.
Metsämäki 1996: Markku Metsämäki, Elektronisen julkaisun suunnittelu. Edita, Helsinki 1996
Nielsen 2000: Jacob Nielsen, Designing Web Usability. New Riders, USA 2000
Nielsen 2002: Jacob Nielsen, Let Users Control Font Size, http://www.useit.com/alertbox/20020819.html. UseIt.com, 2002.
Peltonen 2000: Teija Peltonen, Värisymboliikka, http://sinuhe.jypoly.fi/~tpeltone/mater/varit.htm, 2000
Sinkkonen & Kuoppala 2002: Irmeli Sinkkonen, Hannu Kuoppala, Jarmo Parkkinen, Raino Vastamäki: Käytettävyyden psykologia. IT Press, Finland 2002