Skip to main content

Learn/Animations

Animated Backgrounds Without Killing Performance

A background runs all the time, covers the whole screen, and sits behind the content Google times. How to pick one, how many a page can carry, and what each family costs.

Daniel, founder of BricksfusionBy DanielAugust 3, 20268 min read

The short answer

An animated background is not like other animations: it covers the whole viewport, it runs continuously, and it sits behind the content Google is timing. Pick one per page, put it where it earns attention rather than everywhere, and check its weight before you commit. Cost varies enormously between effects: in our own library of 30 background animations, only 3 are light enough to use anywhere, and 18 are heavy enough that they should be the centerpiece of the page or not on it at all.

Animated backgrounds are the effect people want most and research least. They look extraordinary in a showcase and they are the single easiest way to make a fast site feel slow, because unlike a fade-in that happens once, a background keeps working for as long as the visitor is on the page.

This is the guide to using one without paying for it twice.

What counts as an animated background?

Three quite different things get the same name, and they do not cost the same:

  • A moving gradient or pattern. Color shifting slowly, a subtle grid, a soft glow that follows the cursor. Usually the cheapest family, and often the most tasteful.
  • A looping video. Footage behind your hero. The animation itself is cheap once it plays; the file is what costs you.
  • A drawn scene. Particles, flowing liquid, clouds, flocking shapes, anything generated frame by frame rather than replayed. These are the ones that look like nothing else and ask the most of the device.

Most advice about animated backgrounds fails because it treats these as one category. Deciding which family you are in is most of the decision.

Why is a background different from any other animation?

Three reasons, and they compound.

It is always on. An entrance animation costs you once and then stops. A background runs while your visitor reads, scrolls, and fills in your form, which means it is still consuming the device when they tap the button you want them to tap.

It is full size. Cost scales with pixels, so the same effect in a 300 pixel card and behind a full-screen hero are not the same effect. Backgrounds are always the expensive version of themselves.

It sits behind the thing being measured. Your hero headline or hero image is usually your Largest Contentful Paint, the metric Google wants under 2.5 seconds. Anything that delays that content or holds the page busy while it arrives is charged directly to the number that matters most. Our guide to whether animations slow down your site covers how those metrics work; the point here is that backgrounds are the animation family closest to them.

Which backgrounds are cheap and which are not?

Here is the honest version, using our own library as the sample, because it is the inventory we can actually count. Of the 30 background effects in Bricksfusion:

That ratio is the useful part, and it is not flattering to anyone selling background effects, us included. The majority of what exists in this category is heavy, because heavy is what looks impressive in a demo. The three that are light are the ones most sites should actually be using.

Good to know

Weight is not quality. A GPU-heavy effect is not better built than a light one, it is doing more work per frame. The label tells you where an effect belongs, not how good it is: light effects can sit anywhere, heavy ones need to be worth the page they take.

How many should one page have?

One. And frequently zero.

The technical argument is that everything on screen shares one graphics budget, so a second continuous effect does not cost twice as much, it competes. The design argument is stronger: a moving background works by drawing the eye, and two of them on one page draw the eye to nothing. Whatever you put in the hero stops being special the moment the section below it also moves.

The practical rule that survives client revisions: one animated background per page, in the section that has to make the first impression, and static everywhere else. If a second section feels flat by comparison, that is the first background doing its job.

What about video backgrounds specifically?

They deserve their own answer because the cost sits somewhere different. A video background is not usually a graphics problem; it is a bandwidth problem. Once it is decoding, the effect is cheap. Getting the file to the visitor is what hurts, and that cost lands on the same first impression the video was meant to improve.

What keeps one reasonable: short loop, muted, compressed hard, and a poster image so something correct is on screen before a single frame arrives. Serve a static image instead on phones unless the video is truly the message. A hero video that arrives after your visitor has already decided is decoration you paid for and nobody saw.

How do you choose one without guessing?

Four questions, in order:

  • Is this section worth a continuous effect? Heroes and landing pages, usually yes. A contact section, almost never.
  • Does the text on top stay readable? A moving background changes the contrast underneath your headline from second to second. If any frame makes the copy hard to read, the effect needs an overlay or a different effect.
  • What does it weigh? If the effect you are considering publishes a weight, believe it. If it does not, that absence is itself information.
  • How does it feel on a mid-range phone? Not your desktop, and not the newest phone in the house. This one check catches more problems than the other three together.

Every effect in the Bricksfusion library carries its weight on its own page, alongside a live preview you can watch before deciding, which is why the numbers in this article could be counted at all.

Bottom line

Animated backgrounds are worth it when one of them carries a page and not much else has to. Pick the family first, because a gradient, a video and a drawn scene are three different bills. Use one per page, in the section that earns it. Check the weight before you commit, and check it on a phone rather than on the machine you designed it on. Done that way, a background is the cheapest way to make a site feel expensive. Done the other way, it is the most expensive way to make it feel slow.

FAQ

Questions about this topic

How many animated backgrounds can one page have?

One, in almost every case. Not because a second would break the page, but because a background that runs continuously behind your content is competing for the same graphics budget as everything else on screen, and because two moving backgrounds on one page cancel each other out visually. If a page seems to need two, the better question is usually whether it needs one.

Are video backgrounds lighter than animated ones?

Not automatically. A video background trades graphics work for bandwidth: the effect plays cheaply once it is decoding, but the file has to arrive first, and on a phone connection that can hurt more than the animation would. A short, well-compressed, muted loop is fine. A 20 MB hero video is not, whatever else the page does right.

Will an animated background hurt my Core Web Vitals?

It can hurt two of the three. It hurts LCP if it delays or covers the main content the browser is timing, and it hurts INP if it keeps the main thread busy while a visitor taps. It rarely hurts CLS, because a background sits behind the layout rather than pushing it around, as long as its container has a reserved size.

Should an animated background run on mobile?

Judge it on a mid-range phone, not on your desktop. Some effects are fine everywhere and some are noticeably heavier on a small device with a weaker chip. If an effect is the reason a phone visitor waits, the right call is to serve a static image or a plain gradient there and keep the motion for larger screens.

Animated Backgrounds Without Killing Performance | Bricksfusion