dan1 wrote:
Google suggests that the page's associated js file and the opus.js file are downloading before the page is rendered, plus there is also about 1mb of html.
Scripts can be downloaded before or after the HTML has been loaded. Don't mess with the Opus.js but custom scripts that are not needed until the publication is ready, can use the defer attribute:
http://www.w3schools.com/tags/att_script_defer.aspAjax may solve your problem, it's not a one size fits all though. The basic principle is that you create your index page and use XHR (XMLHTTPRequest) to load the data (your Opus publication) - this happens in the background, so a waiting page / indicator could be displayed.
After the data has loaded, an event is triggered and you need to process that data - in this case load it into the DOM (the HTML index page). Depending on the AJAX method employed you may need to process the JavaScript before or after the data loads into the DOM.
After the data and scripts have all load, you will probably need to initial the first page of the publication which can be done by using the start method on the first page object.
I would recommend starting with a simple clean publication to understand the process. Then when you move on to your actual project, ensure that you test all function and do this in the browsers you intend on supporting.
</mack>