Generally, interactive HTML5 assets will use one or more Javascript libraries to provide the desired functionality. These libraries may be packaged with the asset or loaded remotely. The asset may also have other required media objects such as images, video files, CSS files, other html and xml files, etc etc. Finally, all of these elements will be (usually) collected within a single directory/folder and called by an index.htm file or similar.
A single Author-it course may contain multiple assets from a range of vendors who all use a range of development tools. Unfortunately, each HTML5 development tool uses different javascript libraries, or even different versions of the same library, and packages the asset differently. The Author-it publishing process collects each of the assets used in the course and consolidates them into a single published output folder as part of the automatic publishing process. Therefore, if development guidelines are not set and adhered to, the range of javascript libraries required by a single course could be quite large, which increases the possibility of conflicts and performance issues.
Additionally, some interactive assets may use animation techniques and browser controls that can conflict or cause performance issues, such as svg animations, CSS animations, canvas animations.
Therefore in a single course or presentation there is the opportunity for: