It seems to error on the call to resizeIt() in the onload event. I can't find a reference to that function, so that may explain the error.

If you look in the final HTML, you'll see the JavaScript I am talking about. Calls like MM_preloadImages to preload the images and so on.

One way to optimize a little is to move all the JavaScript functions to a separate file so they only need to be downloaded once. Search Google for "javascript external file" to get some ideas.

Other than that, I see a lot of HTML markup (e.g. a background attribute) that can be moved to external CSS files for easier (and faster) reuse across pages.

But again: if you don't want to do all of this then don't bother. It's not the most important thing in the world.... ;)

Imar
---------------------------------------
Imar Spaanjaars
http://Imar.Spaanjaars.Com
Everyone is unique, except for me.
Author of ASP.NET 2.0 Instant Results and Beginning Dreamweaver MX / MX 2004
Want to be my colleague? Then check out this post.

Well, I guess I need the resize command only in the index page, and then all the other pages will be loaded in the correctly sized browser window, right?

Personally, I don't like sites that resize my browser window. If you have a large screen with a high resolution, you can easily have two windows side by side. Then all of a sudden, you, the developer, determine that your site should be displayed full screen on my monitor. Hmmmm....

Resizing the window on the first page should be enough. That gives your user a chance to re-resize the window to something they like. If you keep resizing it on every page, you frustrate them even more.... ;)

Your call to resizeIt may not be necessary as you already have "self.resizeTo" in your code.

Cheers,

Imar
---------------------------------------
Imar Spaanjaars
http://Imar.Spaanjaars.Com
Everyone is unique, except for me.
Author of ASP.NET 2.0 Instant Results and Beginning Dreamweaver MX / MX 2004
Want to be my colleague? Then check out this post.