Switching from tgs-player to dotLottie-wc #514
Replies: 2 comments 2 replies
-
|
Hi there. I've created a very simple (MWE) website that illustrates this issue. The homepage https://dotlottie-test.pages.dev just has two links for both tests:
I've run Yellow Lab Tools tests to show the increase in JS execution time:
It’s noteworthy too that, even though both components are loaded using the same style, the results are not the same. |
Beta Was this translation helpful? Give feedback.
-
|
Apologies for the delayed response — just saw this. You’re right that there’s a noticeable difference in JS execution time between tgs-player and dotlottie-wc. That’s somewhat expected due to the way the players are built:
That said, dotlottie-web isn’t just a player — it’s a full runtime for .lottie features like theming, state machines, expressions, and multi-animation support, which naturally adds some overhead. We’re currently working on a lighter Lottie player optimized for both size and performance, especially for simple use cases like yours. In the meantime, if you don’t need .lottie-specific features, lottie-player or tgs-player would be more efficient for TGS playback. Thanks again, and really appreciate you flagging this. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I'm trying to switch from the old
tgs-player(https://github.com/LottieFiles/lottie-player?tab=readme-ov-file#telegram-sticker-tgs-player) to the newdotLottie-wc(https://developers.lottiefiles.com/docs/dotlottie-player/dotlottie-wc/) since my website uses multiple animations (mostly TGS stickers) but, to my surprise, using the new web component almost doubles the JavaScript execution time (loading the script via CDN in both cases and using the same animation, converted from*.tgsto*.jsonand then to*.lottie). Is this expected? I can provide further details if needed. Thanks in advance!Beta Was this translation helpful? Give feedback.
All reactions