Hi everyone,
I’ve noticed that the Bricksforge Lottie element loads the same Lottie JSON file twice on page load.
This happens even when caching is enabled and there’s only one <lottie-player> element in the DOM.
What I found
- The bundled player script is located at
/wp-content/plugins/bricksforge/assets/vendor/lottie-player.min.js?ver=1760007205 - Inside that file it defines
LOTTIE_PLAYER_VERSION = “2.0.2” and LOTTIE_WEB_VERSION = “^5.10.0”
So Bricksforge already uses @lottiefiles/lottie-player v2.0.2, which means this is not the old v1.5.x issue where the player itself triggered duplicate loads. - Both network requests originate from within
lottie-player.min.js, even though there’s only one<lottie-player>instance in the DOM.
This suggests the issue comes from Bricksforge’s integration logic (possibly an extra load() or update() call), not from the player itself.
Comparison
For reference, BricksExtras uses lottielight.min.js, and that version only makes one request for the same JSON file under identical conditions.
Suggestion
It would be great if the Bricksforge team could check how the Lottie component initializes the player.
Preventing the duplicate fetch would reduce network load and improve performance on pages with multiple animations.
Thanks!