You could use a javascript image preloader like so (goes in the head of the page):
Code:
<script type="text/javascript">
function preload_page_images(){
//Enter your images (and paths, if any) in the preloads array:
var preloads=['image_1.jpg', 'image_2.jpg'];
/////////// Stop Editing ////////////
var loadem=function(im){
var pimg=new Image();
pimg.src=im;
}
for (var i_tem = 0; i_tem < preloads.length; i_tem++)
loadem(preloads[i_tem]);
}
preload_page_images();
</script>
If you are doing this, as you propose, on a previous page, use:
Code:
onload=preload_page_images;
in place of the red highlighted line. Preloading on the page itself will not save any time and is only good for preloading small rollover images.
You could also do as you propose with the iframe. This would have the advantage of working even for folks who have javascript disabled.
One thing that will help with or without preloading is optimizing your images. This is something that generally should be done for any page with significant image byte load.
And, don't be fooled into thinking that preloading the page (I like the idea of preloading the whole page) or images will speed things up beyond the available bandwidth. By this I mean - say, it takes 5 minutes for a dial up user to load the images for your page. If you preload them on another page, this will save the full loading time for the user only if they stay on the preload page for its loading time plus the 5 extra preload minutes. This is why it is also important to reduce the overall image byte load.
Preloading the next page?
Reply With Quote
Originally Posted by Sparaker
Bookmarks