Widget performance

This page explains how Cevoid UGC widgets load and how they affect your website and its speed. Share it with your developers if they ask about the performance of the Cevoid implementation.

When you implement Cevoid on your website, you add only one script: the widget script from Embed galleries and cards. It powers all Cevoid UGC widgets and renders them.

The script is code-split, so it loads only the parts a page needs. The code for each gallery layout, for cards and for the popup loads only when a widget on the page uses it.

All images and videos in the UGC widgets are lazy-loaded and load asynchronously, so they never hold up the initial load of a page. A video loads its file only when it is in view and starts playing.

Images in the UGC widgets and popups are scaled to fit the area where they are displayed. Each image comes in a range of sizes, from 160px thumbnails up to 1080px, and the browser loads the size that best matches the area. If a gallery post is 400px wide, the browser fetches the closest size instead of the original image. This saves bandwidth for your visitors and speeds up image loading on your website. See Image optimization for the image sizes the Cevoid CDN serves.

Images and videos are served from the Cevoid CDN, and gallery and card data is cached on a CDN as well, which speeds up the requests. When you change a gallery, a card, its posts or your markets, Cevoid clears the affected cached copies, so your changes show without waiting for the cache to expire.