Lottie performance problems usually come from the file, not the player. After Effects makes it easy to add features that are expensive to render frame by frame on a phone.
Start with the file. Masks and track mattes are often the biggest cost; replace them with simpler shapes where possible. Remove effects and blurs the player does not need. Merge shapes, reduce layer count and precompose carefully. Large embedded images add memory and decoding cost, so optimise or replace them with vectors. A Lottie inspector, such as our free Lottie JSON viewer, helps you see what is inside a file.
Then check how the app plays it. Animations that keep looping when off screen, inside a closed tab or in a list cell that scrolled away still use the CPU and battery. Pause them when they are not visible and stop loops that are not needed. Avoid playing dozens of animations at once.
Pick the right options for your platform. On the web, the SVG and canvas renderers perform differently depending on the animation, so test both. The compressed .lottie (dotLottie) format reduces download size. On Android, test with hardware acceleration where your player supports it.
Finally, measure on a low-end device. If an animation is still too heavy, it may be the wrong tool for the job: a simple CSS or native animation can replace a decorative loop, and interactive components may be better built in a state-based tool such as Rive or ExodeUI, which we make.