forcing HTML5 and Optimizilla
Aug 13, 2016
Recent usability testing of our program shows Storyline file load time is too long for our participants. It has been recommended by our developer that we change iframe code from /story.html to /story_html5.html to force HTML5 and to use http://optimizilla.com as a lossless png compression tool to make images download faster before embedding them in Storyline. Has anyone used this combination with success? I understand that Articulate does not support forcing HTML5 so I am concerned about implementing this procedure. I am not familiar with Optimizilla, and would love to hear how it has worked for others.
Can anyone recommend other solutions that resulted in shorter Storyline file load times?
2 Replies
I believe SL (re) compresses all images during publishing time so chances are any optimization by optimizilla or other tools would be undone. And I'd suggest you time the story.html and story_html5.html files yourself in a browser before altering the code. Your viewer's browsers may not work if you essentially copy html5.html to story.html
If you're looking to speed up Storyline, look at graphic object and multimedia reuse; that also can shrink the overall file size too
Hi Michelle,
I'm not familiar with the Optimizilla either - but Storyline does preload content to make playback easier, so you may want to keep that in mind as you're designing the course and we do compress the output upon publish to ensure the smallest file size at the best possible playback. As far as the HTML5, we support the browsers detailed here so you may want to confirm that you're testing in one of those as well.
This discussion is closed. You can start a new discussion or contact Articulate Support.