Here are a couple quick observations.
First, all the missing div contents do load when you click the link above. To test, empty your Temp Internet cache and click link above. All .swf eventually load, but one is HUGE...5.8MB!
With an empty cache, appending index.html does NOT make any difference. Reloading either address, once the .swfs are downloaded into the cache, page will display correctly. So problem is not the diference in addresses but whether or not the .swfs are in the Temp Internet folder or not.
So that seems to indicate that the first time through, the code is expecting to display something that is not yet available, as a variable or whatever. When the page reloads, since that resource or variable(the .swf) is now available in the cache, it will display. Not exactly sure what or how this is happening but I would be very suspicious of leftcollumn.swf. This is a 5.8MB file....that's HUGH and takes a heck of a long time to download even on my 6Mb connection.
Perhaps in the time it takes to complete downloading that file, the browser has parsed it's way down the code, past the display or show part and finished the page. It could not display because the resource was not available as that part of the code was being parsed.
A simple test could verify. Create a simple .swf with the same dimensions as the .swfs but just a few frames, so the file size is tiny (20kb). Give them the same names as the current .swf and replace the large files with the small files to see if the file size/loading order is an issue.
Regardless, I'd say that loading 6+MB on page loading is really way too much. The worst offender is leftcollumn.swf. You could use a loadMovie only onRelease to start the video download, don't put the whole video in the timeline. The file size would be much, much smaller if you only displayed the Television set on loading and used the controls to download the video
Eye for Video