Well, the page really loads in three requests, minus the images. It lazy-loads the images and player afterward (and drops them into the page without reflowing).

Well, the page really loads in three requests, minus the images. It lazy-loads the images and player afterward (and drops them into the page without reflowing). It looks like the the images come in document order, too, so the visible part of the page is fully ready to view, images, included, before all the images load. Something is a little screwy with the page though -- the main HTML page, which is 27K, takes two seconds. Some infrastructure somewhere could be running/configured better.