Keyframe animations in CSS - Performance & Optimization

Performance: Keyframe animations

MEDIUM IMPACT

Keyframe animations affect the browser's paint and composite stages, impacting smoothness and visual stability during animations.

Animating an element smoothly without causing layout shifts or heavy repaints

CSS

@keyframes moveAndScale {
  0% { transform: translateX(0) scaleX(1); }
  100% { transform: translateX(200px) scaleX(3); }
}
.element {
  animation: moveAndScale 2s infinite;
  will-change: transform;
  position: absolute;
}

Animating 'transform' uses the compositor thread, avoiding layout and paint, resulting in smooth animations.

📈 Performance Gainsingle composite per frame, no reflows or repaints, smoother animation with less CPU

Animating an element smoothly without causing layout shifts or heavy repaints

CSS

@keyframes moveAndResize {
  0% { left: 0; width: 100px; }
  100% { left: 200px; width: 300px; }
}
.element {
  position: absolute;
  animation: moveAndResize 2s infinite;
}

Animating 'left' and 'width' triggers layout recalculations and repaints on every frame, causing jank and high CPU usage.

📉 Performance Costtriggers multiple reflows and repaints per frame, increasing CPU load and causing jank

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Animating 'left' and 'width'	High (style changes affect layout)	Multiple per frame	High (full paint)	[X] Bad
Animating 'transform' and 'opacity'	Low (no layout changes)	None	Low (composite only)	[OK] Good

Rendering Pipeline

Keyframe animations update styles each frame. Animating layout properties triggers Style Calculation, Layout, and Paint stages repeatedly. Animating transform or opacity bypasses Layout and Paint, going directly to Composite, which is faster.

→Style Calculation

→Layout

→Paint

→Composite

⚠️ BottleneckLayout and Paint stages are most expensive when animating layout properties.

Core Web Vital Affected

CLS

Keyframe animations affect the browser's paint and composite stages, impacting smoothness and visual stability during animations.

Optimization Tips

1Animate only transform and opacity properties for best performance.

2Avoid animating layout-affecting properties like width, height, margin, or position.

3Use 'will-change' to hint the browser about upcoming animations for smoother rendering.

Performance Quiz - 3 Questions

Which CSS property is best to animate for smooth performance?

A width

B left

C transform

D margin

DevTools: Performance

How to check: Record a performance profile while the animation runs. Look for Layout and Paint events during animation frames.

What to look for: High number of Layout and Paint events indicates poor animation performance; mostly Composite events indicate good performance.

Practice

1. What does the @keyframes rule do in CSS animations?

easy

A. Stops the animation immediately

B. Applies the animation to an HTML element

C. Sets the animation duration and delay

D. Defines the stages of an animation with style changes over time

Solution

1. Step 1: Understand the role of @keyframes

   The @keyframes rule defines how styles change at different points during the animation timeline.

2. Step 2: Differentiate from animation properties

   Properties like animation-duration or animation-name apply the animation, but @keyframes sets the actual style changes.

3. Final Answer:

   Defines the stages of an animation with style changes over time -> Option D

4. Quick Check:

   @keyframes defines animation steps [OK]

Hint: Remember: @keyframes sets animation steps [OK]

Common Mistakes:

• Confusing @keyframes with animation properties
• Thinking @keyframes applies animation to elements
• Mixing up animation duration with keyframe definitions

2. Which of the following is the correct syntax to define a simple keyframe animation named fade that changes opacity from 0 to 1?

easy

A. @keyframe fade { start { opacity: 0; } end { opacity: 1; } }

B. @keyframes fade { from { opacity: 0; } to { opacity: 1; } }

C. @animation fade { 0% { opacity: 0; } 100% { opacity: 1; } }

D. @keyframes fade { 0 { opacity: 0; } 1 { opacity: 1; } }

Solution

1. Step 1: Recall correct @keyframes syntax

   The correct rule is @keyframes followed by the animation name and curly braces containing percentage or keyword steps.

2. Step 2: Check the step keywords and values

   Valid steps are from and to or percentages like 0% and 100%. @keyframes fade { from { opacity: 0; } to { opacity: 1; } } uses from and to correctly.

3. Final Answer:

   @keyframes fade { from { opacity: 0; } to { opacity: 1; } } -> Option B

4. Quick Check:

   Correct @keyframes syntax uses from and to [OK]

Hint: Use @keyframes with from/to or 0%/100% [OK]

Common Mistakes:

• Using @animation instead of @keyframes
• Using invalid step names like start or end
• Omitting percentage signs or keywords in steps

3. Given the CSS below, what will happen to the <div> element when the page loads?

div {
  width: 100px;
  height: 100px;
  background-color: red;
  animation: slide 2s forwards;
}

@keyframes slide {
  0% { transform: translateX(0); }
  100% { transform: translateX(200px); }
}

medium

A. The div moves 200px to the right over 2 seconds and stays there

B. The div moves 200px to the right instantly with no animation

C. The div moves 200px to the left over 2 seconds and returns

D. The div does not move because animation is missing

Solution

1. Step 1: Analyze the animation properties

   The div has an animation named slide that lasts 2 seconds and uses forwards fill mode, meaning it keeps the final state.

2. Step 2: Understand the keyframe effect

   The slide animation moves the div from translateX(0) to translateX(200px), which moves it 200 pixels to the right.

3. Final Answer:

   The div moves 200px to the right over 2 seconds and stays there -> Option A

4. Quick Check:

   Animation moves right 200px and stays [OK]

Hint: Check animation duration and fill mode for final position [OK]

Common Mistakes:

• Confusing direction of translateX (right vs left)
• Ignoring the forwards fill mode effect
• Thinking animation happens instantly without duration

4. Identify the error in this CSS animation code:

@keyframes grow {
  0% { width: 100px; }
  100% { width: 200px }
}

.box {
  animation-name: grow;
  animation-duration: 3s;
  animation-iteration-count: infinite
}

medium

A. Missing semicolon after width: 200px in keyframes

B. Incorrect animation property name; should be animation

C. Animation duration must be in milliseconds, not seconds

D. Missing @keyframes keyword

Solution

1. Step 1: Check syntax inside @keyframes

   Each CSS declaration must end with a semicolon. The width: 200px line is missing a semicolon.

2. Step 2: Verify animation properties

   The properties animation-name, animation-duration, and animation-iteration-count are correct and properly used.

3. Final Answer:

   Missing semicolon after width: 200px in keyframes -> Option A

4. Quick Check:

   CSS declarations need semicolons [OK]

Hint: Always end CSS declarations with semicolons [OK]

Common Mistakes:

• Omitting semicolons inside keyframes
• Confusing animation property names
• Using wrong units for duration

5. You want to create a bouncing ball effect using keyframe animations. Which keyframe sequence best simulates a ball dropping and bouncing back up smoothly?

hard

A. @keyframes bounce {
0% { transform: translateX(0); }
50% { transform: translateX(100px); }
100% { transform: translateX(0); }
}

B. @keyframes bounce {
0% { transform: translateY(100px); }
50% { transform: translateY(0); }
100% { transform: translateY(100px); }
}

C. @keyframes bounce {
0%, 100% { transform: translateY(0); }
50% { transform: translateY(100px); }
}

D. @keyframes bounce {
0% { transform: translateY(0); }
50% { transform: translateY(-100px); }
100% { transform: translateY(0); }
}

Solution

1. Step 1: Understand bounce motion direction

   A bouncing ball moves down (positive Y) then back up (to zero). So translateY should go from 0 to positive value and back.

2. Step 2: Analyze each option's keyframes

   @keyframes bounce { 0%, 100% { transform: translateY(0); } 50% { transform: translateY(100px); } } moves from 0 to 100px down at 50% and back to 0 at 100%, simulating a bounce. @keyframes bounce { 0% { transform: translateY(100px); } 50% { transform: translateY(0); } 100% { transform: translateY(100px); } } starts at 100px down, which is unnatural. @keyframes bounce { 0% { transform: translateY(0); } 50% { transform: translateY(-100px); } 100% { transform: translateY(0); } } moves up (-100px), not down. @keyframes bounce { 0% { transform: translateX(0); } 50% { transform: translateX(100px); } 100% { transform: translateX(0); } } moves horizontally, not vertically.

3. Final Answer:

   @keyframes bounce { 0%, 100% { transform: translateY(0); } 50% { transform: translateY(100px); } } -> Option C

4. Quick Check:

   Bounce moves down then up vertically [OK]

Hint: Bounce means down (positive Y) then back up (zero) [OK]

Common Mistakes:

• Using negative translateY for bounce down
• Animating horizontal movement instead of vertical
• Starting animation at the bottom position