Nosto's UGC out-of-the-box widgets have been optimized for the shortest possible load times. How Nosto is designed is that it will load in isolation from the rest of the site, meaning that elements on the parent page will not be held up by the UGC Widget rendering (and in some cases, UGC will wait until these elements load before loading itself). This design also means that Nosto 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 to minimize load times and content bandwidth requirements. When serving social media content, Nosto will utilize similar technologies as the social networks themselves to optimize delivery to mobile devices.
How are widgets optimized for loading?
To ensure we can optimize onsite widgets for loading but still be able to provide our customer with the original assets, we compress videos and images for onsite widgets but also keep a copy of the original asset in the Asset Manager.
On initial loads, a smaller web version of tiles' images at 400px will be displayed in the widgets. When a tile is expanded, the full web version of the image will be shown instead of the original one.
Here in more detail the types of compressions we do:
Images ingested via Direct Uploader: Yes
Compressed thumbnail image URL: https://upload-cdn.stackla.com/[image]?format=webp&d=400
Compressed full image URL: https://upload-cdn.stackla.com/[image]?format=webp
Videos Ingested via Direct Uploader: Yes
Videos uploaded via Direct Uploader will be compressed to mp4 format and H.264 video codec
Images ingested via Manual Create Tile: Yes
These images are processed similarly to images ingested via Direct Uploader.
Thumbnail image URL: https://upload-cdn.stackla.com/[image]?format=webp&d=400
Full image URL: https://upload-cdn.stackla.com/[image]?format=webp
Images ingested via a Search Term (Instagram, Youtube, Facebook, etc.):
Rights Approved Images: Yes
Thumbnail image URL: https://media-library.stackla.com/[image]?format=webp&d=400
Full image URL: https://media-library.stackla.com/[image]?format=webp&d=400
Non-Rights Approved Images: No
We do not have full control of the images loaded from external sites. No optimizations are applied to those images.
Videos / Reels ingested via a Search Term (Instagram, Youtube, Facebook, etc.):
Rights Approved Videos: No
Videos coming from these sites are typically already optimized before being ingested into Nosto. We do not perform any additional optimization to these videos.
Non-Rights Approved Videos: No
Same as rights-approved videos. No additional optimizations are performed.
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 (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, some options 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 (this is only possible if you have manually deployed your widget using the Embed Code, not if deployed via Nosto Placements)
Build a Custom Display using Blank Canvas which is optimized for the client's 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@nosto.com or submit a request and our support team will get back to you.