IWeb Pages Load Slowly in Browser

Question

Even since the 1.0 version of iWeb, I noticed that the content rich themes resulted in very slow page loads. So, I decided to choose the most minimalist theme possible -- Modern. Even with the latest version, I still notice that the pages created load quite slowly. Here's a simple page with just a few elements on it:
http://web.mac.com/resourcesforlife/journal/
The various layers load at different times, so rather than text appearing on a page, the text appears without a page and then the image layer of the paper shows up later -- kind of ruining the effect of text on a paper.
Previously, the blog directory (main page) would load at an average speed. Now it seems even slower. There are some kind of white borders being placed around the images and this takes a while to apply. I didn't notice these prior to the 2.0 version of iWeb.
So, in general, the density of coding on the pages and inefficient design of the pages, seems to cause them to load slowly. This is a similar problem to what I've heard about with people using Microsoft Word to create HTML pages. The code ends up being very complicated and takes a long time for the browser to interpret. So, many people use programs like Dreamweaver to create the cleanest and simplest code possible for their pages allowing them to load quickly.
Another example of an unnecessarily slow page is my blog archive. It's just text. When it generates, it almost seems like the server is creating the page using a MySQL engine or something like that. One would think that the archive page might be generated into clean HTML at the time of publishing. I looked at the source code, and it isn't pre-generated using basic HTML. It's calling up Java Script routines to generate the page:
http://web.mac.com/resourcesforlife/journal/writings/Archive.html
Any thoughts on this topic?

Answer 1

How weird, but cool! It's too bad iWeb isn't as smart as you are. Since the site generates much of the coding on the fly at the time of publishing to the web, you would think it could think of a smarter way (like the one you've presented) to generate the page image. For example, the text I typed in on the little notepad begins as me typing text. It ultimately ends up as a graphic image created by iWeb when publishing. So, why not just make the entire page a relatively compact JPG image?
Your suggestion would work great if I wasn't planning on changing the content of my main opening page.
I noticed if I used the fun handwriting font along with others in the same text box, that the entire text box became hundreds (like 300) different images representing the separate text and links on the page -- super inefficient. So, I ended up using the fun handwriting font in a separate text box that gets converted to an image and then another text box of Arial font text:
http://web.mac.com/resourcesforlife/journal/topics.html
So, that works on those pages. But I wanted the main page to look nice. Oh, also, some of the elements on the page are links. The movie tickets link to a certain page, for example. So, I'd need to create hotspots in the jpg image to accommodate for that.
In any event, I'm still going back to mark this question as solved because I think for most people's situations it would be with the suggestion you made -- use iWeb to design the graphics of a page, and then save it as a JPG.
I suppose I could also use Pages or Keynote to do the same. Once an entire web page is a JPG image, it doesn't matter how it was created.