[tmohans]

I am thinking on pre-loading the website pages of my site and have couple of doubts regarding that.

1. I would be achieving a better user exp but How usable would it be?
2. Is pre loading couple of images(mostly Bg's) a better option?
3. Can u suggest any java/ajax scripts for pre loading html page!
4. Can u suggest a better way of building a high quality graphic site with PNG images?

[d*d]

I have never heard of, or seen the need to preload a html page - why?

[NicolaFred]

If your code is clean and accessible, you definitely wont need to pre-load anything....
ps. dont use png's..... ie cant see them!!

[haku]

IE sees them. IE6 doesn't work well with png transparency. But they will appear just fine.

---------------------------------------------

Yahoo says this about preloading:

Preload Components

tag: content

Preload may look like the opposite of post-load, but it actually has a different goal. By preloading components you can take advantage of the time the browser is idle and request components (like images, styles and scripts) you'll need in the future. This way when the user visits the next page, you could have most of the components already in the cache and your page will load much faster for the user.

There are actually several types of preloading:

* Unconditional preload - as soon as onload fires, you go ahead and fetch some extra components. Check google.com for an example of how a sprite image is requested onload. This sprite image is not needed on the google.com homepage, but it is needed on the consecutive search result page.
* Conditional preload - based on a user action you make an educated guess where the user is headed next and preload accordingly. On search.yahoo.com you can see how some extra components are requested after you start typing in the input box.
* Anticipated preload - preload in advance before launching a redesign. It often happens after a redesign that you hear: "The new site is cool, but it's slower than before". Part of the problem could be that the users were visiting your old site with a full cache, but the new one is always an empty cache experience. You can mitigate this side effect by preloading some components before you even launched the redesign. Your old site can use the time the browser is idle and request images and scripts that will be used by the new site

Best Practices for Speeding Up Your Web Site