why do you want to do this? displaying pages lazily is a feature, not a bug; give your images the correct width/height so they don't change the page layout on load and you should be fine; preloading only makes sense for images which are not part of the default page structure because they are added later via scripting or hover effects
–
ChristophSep 30 '10 at 16:41

All I can say is that my client is an idiot and will not understand arguements...
–
FranciscSep 30 '10 at 16:42

And if the user has javascript disabled they don't see anything. Btw, I don't know if it's true, but I've heard that Google tests if a pages text and background color are the same.. shouldn't surprise me if the also test for hidden content. Maybe you could tell your client that this is how the web works. You are making something that will not work in all browsers...
–
someSep 30 '10 at 17:08

Well if I would implement a solution I would make it Progressive Enhancement so that anyone with or without JS can visit the page. And yeah, Googles does that as well as looking for display:none or invisible elements.
–
FranciscSep 30 '10 at 20:07

Thank you Christoph and thanks everyone for all your very helpful input.
–
FranciscSep 30 '10 at 20:10

I have decided NOT to do this after reading all that was said and seeing that such a solution would imply hiding and showing the body, I was hoping there was a more elegant way which there isn't. Again, thank you, much appreciated.
–
FranciscSep 30 '10 at 20:11

I prefer Christoph's solution since it wouldn't 'destroy' anything if JavaScript isn't available. Here we should use something like <body id='body' onload="..."><script ...>document.getElementById('body').style.visibility='none';</script> ... That would be a mess. And we still might have that problem that onload is never called, as some mentioned.
–
JanSep 30 '10 at 17:19