Quote:
|
Originally Posted by coldclimber
proud to say that it is number one with google.
|
Theory: there is no Google-indexed website in the world that contains any original content that is
not "number one with google" -- for
some search query. OTOH, your site appeared nowhere (what I like to call being "# infinity with Google" :-) in the Google serps for the possibly relevant terms "ice climbers" and "ice climbs", so some portions of that "hype about
PR" may yet prove of interest to you in the future if increasing relevant search engine traffic is one of your goals.
But on with the review:
Load Speed
wget says: 16 seconds (DSL connection) to download 293,392 bytes in 48 files. This is the slowest-loading home page I've looked at in a while. If you want anyone using a non-broadband connection to use this site, consider abandoning the idea of using little jpegs everywhere. Ironically, the slow-speed people are probably hitting the Back button before all those little jpegs arrive, while the high-speed people are more likely to be using a high enough screen resolution that the little boogers are nearly illegible anyway (try viewing at 1600x1200).
If you simply cannot give up the platoon of little jpegs, you might want to consider consulting an IIS expert to fix up your configuration so that client browsers can cache those images for some reasonable period of time. Right now, clients can cache the images upon first arrival, but every time they return to the home page, they must issue dozens of request to ask your server whether any of the images have changed (even if they were locally cached mere seconds ago). In geek-speek, your server is not tranmitting an HTTP
Expires: header for any of your images. That will not improve the horrible download speed of anyone's initial visit, but will at least slightly speed up subsequent views of the home page by the same visitor.
Bugs
I'm guessing that "Google Adds" was intended to be "Google Ads", assuming you want to refer to
advertising rather than the ability to
add something to Google.
"feelings that immerge" should be "feelings that emerge".
When you mean to say "it is", the correct contraction is "it's", not "its".
Various missing/inconsistent punctuation, capitalization and spacing problems. Could generally benefit from a thorough pass by a copyeditor.
Strange centered text that seems to be a half-aborted ad for Panasonic cameras. The text is so far from the actual link as to be confusing.
There is non-standard JavaScript cruft after your closing </html> that contains what wget mistook for a img reference to a non-existent URL. Personally, I try not to assume that search engine robots are smarter than wget. This may have been generated without your knowledge by your WYSIWYG HTML editor. Caveat emptor.
Your HTML contains no DOCTYPE declaration to tell clients which of the many versions of HTML you might be claiming to feed them. This lowers the odds that you can actually get the page to display roughly the same on more than one browser (or even widely different versions of the same browser!). It also means you can't use automated tools to detect errors in your HTML coding.
The value of such automated tools is that they could immediately inform you of such errors as (and these are actual examples from your home page HTML) wildly illegal uses of the <head> and <body> tags. Such errors matter because: they may mean your page displays horribly for people not using the exact same browser configuration as you, and they may mean that search engine robots can't understand your page well enough to index all of its text correctly.
However, if DreamWeaver has generated this illegal state of affairs for you, then you're sort of at the mercy of that tool and whatever support its vendor/users can offer you for getting it to generate legal HTML. Sadly, getting legal and safe HTML ought to be one of the benefits of using a high-level tool instead of hand-coding your own HTML. Doesn't always work out that way, though.