Paths.js file is huge
I've been investigating very long (sometimes fatal) load times in my HTML5 only published version of a course and think I've tracked the culprit down to the paths.js file - it's over 5MB for me. While the browser is downloading the file it holds up other parts of the preload. In one test it took over 40s which was apparently enough to cause a timeout which blocked anything else from loading, apart from the player frame.
Anyone got any bright ideas?