Web solution without mission
It is strange but true that some web solutions do not have a mission. They were built purely to be counted, no focus, no baselines, no nothing. The most interesting thing about such solution is that there is no documentation to show what the intentions were, let alone of what was achieved. All that is available is just hyperlinked pages and that is it. If you are building a web solution, it is important you insist on knowing what the minimum expectation is, when and how the solution is to attain it.

Solution hosted in the wrong domain
Another major design flaw is hosting a solution in the wrong domain. It is interesting to notice that even some government and educational institutions are hosted in .org instead of .gov and .edu. Naturally, users will be looking for your solution in the appropriate domain, instead of the incorrect one.

Solution without integrated business processes
Solutions are built mainly to enforce complaint, fast track and complement business rules. Where a solution fail to integrate established business rules, it ends up creating parallel processes, competing for attention, human and material resources. Take for example, content management systems (CMS) of most newspapers in the country that are always out of sync with their daily publications tell one that their news gathering, and editorial processes were never built into their solutions. A CMS typically has many capabilities - private sections, various levels of authorisation and approvals, auto inform, auto reminder, auto approve, who is active, discussion boards, chat, etc. When a CMS is properly implemented, reporters gathering news in the field can feed what they think is newsworthy into the solution and appropriate editor will be notified immediately. Such editor can start working on the content once the reporter releases it by granting permission to the editor. If such an editor is not available, within the allowable number of hours, the request escalates and the editor's supervisor gets notified. This way, the editor's supervisor can intervene directly through a telephone or engage the reporter through an online chat if the reporter is active on the site. To cut the long story short, once a decision to publish is made, the editors can then approve their sections subsequently to be available on the life server for public use. There is no need to have additional staff that will start another round of cut and paste, typing, etc, the solution is suppose to work seamlessly.

The use of unpaid public emails
This is another important issue most unsuccessful web solution owners choose to ignore. Most corporate bodies often filter out emails emanating from unpaid public emails and the chance that yours (if you use unpaid public email to write corporate mails) will be filtered is very high. Further, emails emanating from public domains can not be verified easily and often create credibility problem. We assume "419", once someone writes using an email from a public email domain and claim to be working in a reputable establishment that we can ascertain that has a web solution. Many do not know that emails help a lot in promoting businesses, as people end up visiting the domain that they received an email from, especially when the person writing is new to them. It does not make any technical sense to own a web solution and yet use unpaid public email. It may cost a little more to ensure that anything@yourdomain emails are captured. If the company hosting your solution does not offer email hosting services, it is possible to have your email hosted elsewhere.

Content quality and presentation
Many web solution owners often neglect this most important aspect of a web solution and spend more time on graphics and animations. No matter how beautiful a web solution is, if the content is not concise, direct to the point and above all, presented in a manner that it will be inviting to read, it may not encourage users to revisit or consider the solution as a source of valuable information. Web solutions should be considered as a front desk, which should be given maximum attention, ensuring that the content is of high quality. Some of the factors to consider when preparing materials for a web solution include:

1. Page layout and partitioning - there is no harm in having more pages on a web solution. The idea of having fewer pages portrays the establishment as one that does not having many ongoing activities.
2. Positioning of statements and or phrases - It is always elegant to position eye catching statements in locations where it will be visible to anyone visiting the solution for the first time.
3. Grammar and spelling mistakes - Always check for grammar and spelling errors.
4. The use of contrasting colours - Avoid the use of text and background colours that contrast each other. This applies to links - hover, mouse over, visited etc
5. Use only legible fonts - Even though some fonts could be very stylish, once it is not readable the content is of no value. The use of such stylish font should be avoided.
6. Accessibility - Ensure that your solution is inclusive and can be accessed by people that use assistive technology.

Insufficient, hidden or no contact information
One unpardonable issue is to provide only a contact form on a web solution and assume that visitors will complete the form and wait for a response. The recommended practice is to give as much contact options - phone, email and or online form to users as possible and encourage them to use the most cost-effective and convenient option.

Effects without purpose
The use of flash and other animating tools that does not deliver any specific message and unnecessary background music that does not relate to the subject matter is highly discouraged. Note that flash and animation tools are great tools but should be used in proper perspective. For example, flash and other animation could be used to demonstrate the transmission of HIV virus from one individual to another. It does not help when lights, thunders, etc are flashing across the screen unnecessarily, creating distractions.

Compatibility issues
Many unsuccessful solutions display well in some browsers and awful in others, making it difficult for users of such browsers to access some of the features if not the entire site content.

Unnecessary pop ups
While the use of pop ups for marketing purposes is helpful, the use of pop ups unnecessarily is discouraged. Pop ups are major source of distraction to anyone reading a content on the screen. It always remind one of virus, hijack, etc

Speed of response
For a particular web solution to deliver the goods, it must respond to users request within a reasonable time. This is the only way to guarantee revisits. Heavy images and scripts (un - optimised) are usually responsible for slow response.

Navigational issues
The use of lots of frames, menu options that can only work in certain situation (JavaScript enabled browsers for example) are highly discouraged. Improper classification and partitioning of contents can also make navigation difficult.

Solution optimisation for search engines
This is one factor that has the tendency to impact positively on the potentials of a web solution. It is important to ensure that appropriate data dictionary is defined for a solution. Once the solution is optimised and submitted to search engines, it has the tendency of boosting the visibility of such web solution. There are certain meta tags when embedded, using the defined data dictionary at the appropriate header section of solution pages that will help optimise the pages for search engines, and to enable search engines to index them. When this is not done, the solution can only be accessed by those who know the domain name but can not be found among solutions within a search engine.