How's your website, then?

I'm not asking whether it's a good site or not, but what its performance is like. Is it slow to load? Does it have problems with certain web browsers? Occasionally you'll find that code working perfectly on, say Internet Explorer, doesn't work with Firefox. And vice-versa. Any coding problems?

How should I know? Who... who cares? I hear you ask.

Because it's important. You only have seconds -- tenths of seconds, even -- to make an impression on people who come to your site. If the site isn't working, has dead links or some old code that doesn't work and leaves the site with blank areas, you can bet your life those lovely, potential customers will click away at the drop of a pixel. And more than likely they'll be clicking away to the welcoming site of one of your competitors.

Wake up and smell the Mugicha! After reading this post you no longer have any excuses for not knowing. There's a website I often turn to when I want to see how my own site is doing, performance-wise. It makes for uncomfortable reading sometimes, because it doesn't hesitate to tell me stuff I don't particular want to hear -- the site's too heavy, too many images, too many elements, you've failed at life, you're a bad, bad person... et depressing cetera. But it's well worth it.

I have no connection whatsoever with the owners of the site and this isn't an affiliate link, so click in confidence. Here it is:

http://www.websiteoptimization.com/services/analyze/

Put in the full address of your website and have a look at what it says. Pretty eye-opening stuff, eh? You didn't realise it was that bad, did you?!

I'm not particularly interested in contacting the owners of the site to ask for their optimization services, but the results I get when I check my site are very interesting. Useful, too. Oh, and completely free. Check it out.

Let's begin with a little history. Many years ago, when the web was up and coming and you needed to be on it, I paid someone to build a site for me. Afterwards, I could say, "Yeah, I have a site, go to -" and then I would name my site a feel a hit of pride. I'd also get satisfaction when my webmaster (if you could call him that; I don't know that I would in retrospect, but that's another story) occasionally forwarded me an email of an interested visitor. My satisfaction was short-lived, as you might imagine. I soon began to understand the power of the web and found the sad reality that my "webmaster" was getting all my emails from my website visitors to be annoying. I had him change this so that the emails came to me. He charged me a one-time fee for getting him to do this.

Okay, so these days it is not quite that bad, is it? Your webmaster or whoever is doing the "web thing" for you isn't charging you for every little service? Excuse me. I'll reserve my rant for another article, or possibly a blog entry.

So anyway, I fired my webmaster. I built my own webpage. I did this - of all things - with Microsoft Publisher. Yeah, well, it worked - in that I was able to build a site and, with some effort, get it on the web. I won't go into why you shouldn't try this, kids, at home. I was at home when I tried it, sure. But I don't suggest building a site with Publisher. It can be done, but don't do it.

One thing that happens - talk about annoying: The site crams all against the left side of the page. There's nothing you can do to change that. You might as well type out onto the web page "Look, Ma, I can create a website using Publisher." Don't do it.

Well, I knew at the time I shouldn't be messing around with Publisher. It's great for putting together a book or something for print. It's not good for websites. I had just been so excited because I had created a downloadable book for lulu.com. Publisher was great for laying out a book. I had so much momentum...

I put the Publisher site up, and thought I had done a pretty good job, considering that everything was crammed up to the left of the screen. I had yet to become a blogger, and I had yet to realize the importance of tagging and so on. All that important "extra" stuff. I'm joking. Writing tags is not extra. It's essential. So is the blog - on the website.

Then I bought FrontPage and a book and... That's all she wrote. I learned FrontPage and I haven't tried anything else out since. Why not? So far I don't need to use the fantastic Dreamweaver that everyone talks about. Oh, I can't do Flash on FrontPage? Uh - yes you can. Easily.

I continue to believe that content is all-important. Not bells. Not whistles. Content. I don't care what kind of a site you are putting up. Well, okay, I wouldn't necessarily use FrontPage for every circumstance. But for you and me, the individual or small company that wants to be up and shining on the web, FrontPage is the clear answer. At least it was for me. As I say, I haven't looked back since.

One needn't learn the bells and whistles. One certainly needn't incorporate dhtml or whatever that code is that will make letters pop and fly about. Old browsers can't see it, and new browsers - mine, at least - don't want to see it.

I have affiliated with companies. That is, I've tried to turn a dollar by putting them up on my site, a link or banner or what have you. Let me say that what I don't like are the banners that flicker and blink and all that junk. If I want the Las Vegas experience, I'll go there.

Just give me content. FrontPage can handle that and handle it well. You want to be able to upload Flash, for sure. FrontPage can do it. You want to be able to get as much information on your website with as few bytes as possible. FrontPage can do this as well as any program. So, I'm happy. Are you happy - yet?

Like a lot of web developers, I'm not always that disciplined when it comes to the file naming convention I use and I sometimes end up with a situation whereby I have some files that are in lowercase, some that begin with a capital, and some that are a bit of a mixture.

One web site I maintain contains about 2000 web pages and has about 20,000 hyperlinks. As you can imagine, I had one of those sinking feelings when I was told that in order to migrate the web site to a new content management system, all the file names and hyperlinks would need to be changed to lowercase.

Whenever I am presented with a problem like this, my instinct is always to write a Perl script using one or more regular expressions to solve the problem. This particular situation was no exception.

Change a string to lowercase

The following regular expression changes all the characters in a string to lowercase. The first part of the regular expression finds a hyperlink, and the second part converts the string. (Just in case this article is not displayed correctly, there should be a single backslash in front of the 'L$1').

Change a filename to lowercase

Likewise, changing a filename itself is very simple. The following two lines perform the task quite nicely:

(Again, there should be a single backslash in front of the 'L$name'.)

If you need more information on how to incorporate the above code snippets into a complete script, feel free to contact me directly.