If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

Code is usually not as much of an issue as images, but ultimately it's a factor of how many total bytes split across how many different http requests (i.e. different files), as each http request adds overhead to the process. Just for fun, check out: http://10k.aneventapart.com/

"Please give us a simple answer, so that we don't have to think, because if we think, we might find answers that don't fit the way we want the world to be."
~ Terry Pratchett in Nation

If you enable compression, the text probably isn't any issue. I might look into whether or not you could use CSS sprites, where you combine separate images into one image file, then only use the part you need in a given usage (often done for things like corners and borders).

"Please give us a simple answer, so that we don't have to think, because if we think, we might find answers that don't fit the way we want the world to be."
~ Terry Pratchett in Nation

The answer to the question in the OP is: whatever is fit for purpose. E.g. A landing page needs to load almost instantly, or the user may navigate away. Whereas a page containing technical information which will only be accessed infrequently may take significantly longer to load.