Loading Issue in Storyline 03 output

Dear Team,

I have a course with around 50-60 slides. After publishing it in the LMS version using Storyline 03, the package size goes upto 157MB. Out of which 136MB's are consumed by ".js" files itself.

Due to the high package size, course is getting too long to load(locally as well).

Can anyone help me out with the solution to optimized ".js" files size?

Thanks in advance!

10 Replies
Katie Riggio

Hi there, Gouri! 

While this is outside of my expertise, this is a great question for our Support Engineers – I've relayed this over to our team in a case, so we can dive deeper into that loading issue for you. You should receive a confirmation email shortly, and I'll be following along as well!

In the meantime, can you share your .story file with us for testing?

gouri chaudhari

Dear Katie,

Thanks for your response!

I am extremely sorry Katie. But here, I will not be able to share my .story file with you guyz, as I will need permission from my project manager to do so and that process is quite lengthy. Do let me know if I can help in any other terms to sort it out. 

As I mentioned earlier, my .story file contains around 50-60 slides with heavy content and with some clickable elements. Each screen has around 5-6 layers and number of triggers. I hope this is not the reason behind the loading issue?

 

Katie Riggio

Thanks for keeping us posted, Gouri ☺️ You can learn more about our commitment to security as well as our privacy policy at our Trust Center here

Additionally, our Support Engineers are happy to sign a NDA, if you'd like! I see you're working with my colleague, Miker, so I let him know that may be of interest. Miker will take it from here, and I'll follow the case as well!

gouri chaudhari

Hi Articulate Team,

Your support engineer Miker has confirmed that the JavaScript files in the published Storyline output is large due to the intricate Slide Master that we were using for our project.

Miker's response was, "The JavaScript files generated correlates to the function for this specific slide master, and is generated for all slides using this slide master. If you remove all the layers in the slide master, the JavaScript in the output will be significantly lower."

I had included menu in the slide master which was getting called on every slide. Now as a work-around I have deleted the menu layers and its coding from slide master and added it as a different slide and accessed that slide as a lightbox on every slide. And my package size is turned to 35MB from 158MB. The difference is indeed huge.

I am confirming that the issue has been resolved now, you can close this case.

Thank you for all your help and support. Appreciated your promptness. :-)

 

Katie Riggio

Hi there, Vitaly. Happy to help!

I took a peek at Gouri's case and saw that our team determined that the Menu from a specific Slide Master was causing the JavaScript file size to increase. It looks like deleting the Menu from there and using the Menu from the Player should do the trick!

If that doesn't help, please let us know. If you're able to share the .story file with us, we can take a thorough look at your project to see what's happening with the size. If that works for you, please use this private upload link!