To increase the loading performance try to inline all includes and to compress (encrypt) the xml files. On large xml files the compression ratio can be also way above 50%.
Klaus, what do you mean by "inline"
I need to have all text divided into a textfile for each pano. It will be impossible to handle it in one file,
There will be from my current calculation 1200 to 1500 hotspots.
Apparently I need to have them included in each scenes unless I rename them all with new names for each scene.
By the way I did a test with encryption. It does not make any difference at all.
The folder with the textfile went from 440 to 209 kb but the standard browser still takes 32 sec to read before it shows panos.
Firefox does it in just 12 sec
My iPad 3 with IOS 6 takes also 12 sec. I will update to see if that helps.
My solution is to make a frontend currently. I has an onloaded loadpano event so that it starts opening the tour behind the startpage.
I just would like the loading text to be visible on the frontpage as clicking START gives you a delayed reaction.
http://360-foto.dk/nationalhistorisk-museum/start.html