^C^Usability
^R^Global site understandability
The website should have a consistent theme.
Navigation tools should make sense to the user.
^R^On-line feedback and help features
The site should offer an introduction or tutorial for first time visitors to your site.
A FAQ (Frequently Asked Questions) page is often useful in assisting users.
If your site uses any special plugins, you should offer a link, or directions to find and install the plugin.
Searchable help databases give more specific help to the user.
A "Glossary of Terms" page is useful for acronyms or tech words.
^R^Interface and aesthetic features
A toolbar or menu common to all pages should provide navigation.
A reasonable amount of graphics should be present on each page.
The graphics on each page should complement the theme of the website.
Screen resolutions from 800x600 to 1280x1024 should be accommodated.
Browser differences should be minimized as much as possible.
^R^Special features
Special features of a website should be explained to the user in order to be taken advantage of.
^C^Functionality
^R^Searching and retrieving capability
If your website contains large amounts of data, or several unrelated topics, a searchable database is recommended.
^R^Navigation and browsing features
If possible, the option to search your specific site is helpful.
An understandable map of your site helps users keep track of where they are.
If your site uses graphical links, alternate text links should exist for non-graphical browsers.
General information on your site should be included at the bottom of your page.
^R^Application domain-related features
If applicable, your site should offer links to more detailed information on general topics.
Sub pages should be provided with more detailed information when the general topic is frequently used in the site.
^C^Reliablility
^R^Correct link processing
All hyperlinks should be tested and operational.
If frames are used, links must be tested to ensure the right page opens in the right frame.
If Java/JavaScript is used, the right java window should appear when requested.
^R^Error recovery
You should backup your website regularly to an offsite computer.
The web server the site resides on should incorporate reliable backup.
All scripts/applets/etc must have the ability to recover from errors or missing files.
^R^User input validation and recovery
Any FORM fields should be validated after the SUBMIT call.  Any errors found should be reported to the user and prompted for correction.
^C^Efficiency
^R^Response time performance
Server side processing should take no longer than 1.5 seconds.  If this time is exceeded, an indication to the user should be displayed indicating the estimated time to completion.
The site should not reside on an over-utilized or heavily accessed server.
^R^Page generation speed
The site should not involve excessive page formatting.
Modules should be loaded independently, with as little reliance on other modules as possible.  This helps speed load time and reduces browser hangs.
^R^Graphics generation speed 
There should be no more than 70K of graphics on any given page.
Sub-pages should be used as much as possible.  This avoids long load times.
^C^Maintainability
^R^Ease of correction
HTML pages should be scripted in tabular format to create a more friendly code for future updates.
Applets should be well commented and documented.
^R^Adaptability
Relative links (../graphic.jpg) are preferred to absolute links (http://graphics.jpg) as they are more portable.
Graphics, HTML files, and applet files should be stored in separate sub-directories.
^R^Extensibility
The website should reside on a server that supports CGI and other database enhanced features for future expansion.