# Scroll animation performance

> Why Awesome Reveal animations stay smooth: compositor animations, no scroll listeners and a core of less than 2 kB gzipped, plus advice on will-change.

Awesome Reveal gives the work to the browser. The browser runs the viewport check and the animation, so the library runs no code on each scroll or on each frame.

## Animations on the compositor

Without `blur`, the generated entrance animates only `opacity`, `translate`, `scale` and `rotate`. These are [the properties that the compositor runs](/guides/keyframes/#animate-the-properties-that-the-compositor-runs). For the cases that run on the main thread, see [a start state with `blur`](/guides/entrances/#things-to-know) and [an additive keyframe](/guides/keyframes/#keep-the-elements-own-values).

## No scroll listeners

Core adds no `scroll` event listener. The browser runs the viewport check, and the [Intersection Observer API](https://developer.mozilla.org/en-US/docs/Web/API/Intersection_Observer_API) calls core only when the visible fraction of an element crosses a threshold.

## Do not add `will-change`

Do not add [`will-change`](https://developer.mozilla.org/en-US/docs/Web/CSS/Reference/Properties/will-change) for a reveal. The browser treats an animated property as if `will-change` already names it.

## Bundle size

`@awesome-reveal/core` has no dependencies. With `reveal()` and `cascade()`, it adds less than 2 kB gzipped to your bundle.

A [test in the packages repo](https://github.com/awesome-reveal/awesome-reveal/blob/next/packages/core/test/package/tree-shaking.test.ts) checks this size on each change. The test bundles an import of `reveal()` and `cascade()` with a Vite production build, which minifies the code. Then it compresses the bundle with gzip. The size applies only to `@awesome-reveal/core`. The React, Vue and Astro packages use another entry of core, `@awesome-reveal/core/adapter`.
