Lectora on Netg

What is the load time in comparison with other non-Lectora generated content? Have you compared the load time of the content between NetG and the ADL test Suite? In SCORM ... any major load delays is due to the LMS instantiating the API Adapter ... unlike AICC where the content has to issue the GetParam and parse the results before the content can load ... in SCORM, the content just finds the API Adapter and then issues any LMSGetValue/LMSSetValue requests based on what you have on the page.So ... the delay could be the load time for the adapter ... the load time for the content (do you have huge graphics, flash, etc. on the startup page?) ... or the communication between the two based on what you want the content to do (for instance do you access like 10 different SCORM variables that cause the adapter to make multiple requests of the LMS).I would create a stripped down title (no graphics just an exit hyperlink) and compare the load times between the LMS and the ADL Test suite - that gives you the overhead of the API Adapter Load. Then compare the stripped down title's load with your published content's load in the Test Suite (that shows overhead of content specific loading). From there you have enough data to determine where the delay may be ... with that, we can look at course structure and see if the content is doing something it shouldn't (repeated loads of data it doesn't need) or whether the API Adapter is the bottleneck.Tim