Stackla's out of the box widgets have been optimized for the shortest possible load times. The manner in which Stackla is designed is that it will load in isolation to the rest of the site, meaning that elements on the parent page will not be held up by the Stackla Widget rendering (and in some cases, Stackla will wait until these elements load before loading itself). This design also means that Stackla won't cause any conflicts with any Javascript, CSS or other elements that exist on the parent page, nor will it prevent more important elements on the page from loading.

Widgets generally bootstrap within 100ms globally, and load all images completely within 4 seconds. Note that there can be a large variance in load times, depending on the content itself.

Additionally, Widgets have been designed with a mobile-first approach in order to minimise load times and content bandwidth requirements. When serving social media content, Stackla will utilise similar technologies as the social networks themselves to optimise delivery to mobile devices.

What kinds of things can slow down a widget loading?

Widgets are built using the same technologies as web pages and as such face the same challenges as the page they are embedded on itself (i.e. "parent page"). Loading too many assets on the parent page (e.g. images, JavaScript and CSS files), slow client connectivity, using assets from many domains, unoptimized image or video content delivery and slow parent page scripts are some of the common reasons why a widget may load less than optimally.

If you plan to use two or more widgets on a single page, then we recommend only using one JavaScript script vs. two full embed codes.

When it comes to building any page, less is more, and the same applies to Widgets.

Want to try improving these load times?

Naturally there are options which can be taken to further optimize the load of UGC on your website. These include:

  • Reducing the quality or quantity of Media Files that load in a Widget

  • Increasing the cache time

  • Build a Custom Display using Blank Canvas which is optimized for the clients requirements

  • Rendering via the REST API and caching locally on the server

The latter two options provide much more control over the exact loading experience, allowing you to implement any content handling requirements you may have.

For any further questions or queries, please send an email to support@stackla.com or submit a request and our support team will get back to you.

Did this answer your question?