Tina said:
therapy if
I appreciate you taking the time to peek at the site. I was actually just
asking about the load time and general layout.
Then here's more.
- Many words are colored with the same color for links: so, as a
visitor, I can not quickly and visually figure out what are the links.
Not a big thing but if you are sensitive to small details with usability
consequences, then that's one.
- No margin on the page. So, the left side of the content starts at left
pixel 0. There is no printed document anywhere (newspaper, book,
magazines, etc..) in all cultures, in all societies, throughout history
which used no margin at all on a printed document. And removing margin
and padding on the body element was intentional, deliberate not an
accidental oversight or something
- Like someone else said, your title is spam-like. What's wrong with the
simple straightforward "Affordable Host, inc" as a title?
- Use pictures for real pictures; don't use pictures for text... unless
you want to reduce the accesibility of your site and to increase
download time deliberately
- use map and areas when it is justified and proper to do so
I came to your website for the first time yesterday. The word CPanel is
used at 6 spots. I have no idea what CPanel means or what it refers to
exactly. And I'm visiting the topmost page of your site.
I'm aware that it doesn't
completely validate - and I'm willing to live with that (which is why I only
asked about load time and layout only).
The top nr 1 and very first reason to validate is speed (webpage
rendering performance): I've said so before in this newsgroup. Right
now, above 70% of all users out there are using W3C web standards
compliant browsers which are geared and tuned to support W3C web
standards. As soon as you deliberately and intentionally use code that
will trigger backward compatible rendering mode in these browsers, then
you are choosing an inferior rendering mode which brings all kinds of
difficulties for users as well as webpage designers:
- inconsistent layout by browsers: If you can't test your documents in
all browsers (browser versions and other web-aware applications)
available out there, then validating your HTML is the best mean to make
sure that your document has the best chance of being rendered without
problems, by making sure your HTML doesn't have mistakes. Even MSDN
recommends that!
- longer parsing time due to malformed document tree or other problems
- error-correcting mechanisms involved during parsing time; these
mechanisms vary a lot from browser to browser, even from browser version
to browser version
- reduced accessibility
- reduced interoperability in several areas
- etc.
A wide majority of valid HTML documents will be considerably smaller in
size (by as much as 25% to 50%) because valid HTML documents often
assume CSS implementation where style formatting and code reusability
are best and optimal. Therefore download time should be smaller.
Choosing table design (and nested tables) to structure a document is
choosing an inferior design which is not best for parsing and rendering
and I'm talking about speed and browser rendering performance here. It
not only slows down the rendering, it makes the webpage more complex to
figure out, to update, to modify. The webpage is not easy to maintain
since its design was not based on code reusability, code evolutivity in
the first place.
Choosing table design for non-tabular data is as logical as using
MS-Excel to write a document, to write an email.
Choosing to ignore validation, choosing to put up with invalid documents
is as much professional as writing without concerns for badly formed
syntax, grammar errors, obvious spell-checking errors.
The rest of your comments were a bit mean spirited. Off to therapy I go, I
guess! ;-)
--Tina
What irritated me the most with your webpage is that you pompuously
pretended that 2 companies worked on the html and layout when I really
think they did a LOUSY job. You want to give your company a
respectability and reputation regarding the quality and excellence of
its work, services, employees, etc...? Then start with your website
coding practices. One day, you might be able to calmly and confidently
claim in your own company website that your whole business is focused on
quality, excellence, accessibility, usability, wise and optimal use of
technology and then people who know their own art will start to believe
your own words by verifying that by themselves.
DU
--
Javascript and Browser bugs:
http://www10.brinkster.com/doctorunclear/
- Resources, help and tips for Netscape 7.x users and Composer
- Interactive demos on Popup windows, music (audio/midi) in Netscape 7.x
http://www10.brinkster.com/doctorunclear/Netscape7/Netscape7Section.html
