I am currently building a website, and I have it rigged so that the entire page is contained in one .html file, with a matching css file.
The site works pretty well for basic text.
Now I got into an argument with a fellow scripter. One of the pages should include images, an arbitrary amount. This page isn't the home page. but since all that a page is is a div tag that is switched between display:none and display:block this page loads at the same time as the home page, with the images loading at the same time (later technically since they are only called at the end of the .html file).
(I hope this makes sense)
Now what we were arguing about was bandwidth. He argued that the user might not browse to the images page, and thus loading it took up a lot of bandwidth (more as the number of images increases) that wasn't necessary. I argued that since the home page loads first (as well as all the other pages which don't have images), this shouldn't be an issue, because the user can still use the site while the images are loading in the back ground. If he then no longer needs the site he just closes, no harm done. If he then decides to view the images, they're there preloaded.
To this he responded that the loading of the images might slow down the loading of other (non associated) pages the user was viewing at the same time.
What he proposed to do was make the images load only once you click on the portfolio page (essentially making it a seperate page). I argued that then the whole benefit of the fast seeming page is gone.
What is the proper course of action here?