Stacking context in CSS - Performance & Optimization

Performance: Stacking context

MEDIUM IMPACT

Stacking context affects how elements are layered visually and can impact paint and composite performance during rendering.

Managing element layering without unnecessary stacking contexts

CSS

/* CSS */
.element {
  position: relative;
  z-index: 1;
  /* No opacity or transform here */
}

Avoids creating extra stacking contexts, reducing paint and composite layers.

📈 Performance GainSingle paint and composite layer, reducing GPU load and improving rendering speed.

Managing element layering without unnecessary stacking contexts

CSS

/* CSS */
.element {
  position: relative;
  z-index: 1;
  opacity: 0.99;
  transform: translateZ(0);
}

This creates multiple stacking contexts unnecessarily due to opacity and transform, increasing paint and composite layers.

📉 Performance CostTriggers multiple paint and composite layers, increasing GPU work and memory usage.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Many stacking contexts (opacity, transform)	No extra DOM nodes	0	High paint and composite cost due to multiple layers	[X] Bad
Minimal stacking contexts (only needed z-index)	No extra DOM nodes	0	Lower paint and composite cost with fewer layers	[OK] Good

Rendering Pipeline

When stacking contexts are created, the browser separates elements into layers. Each layer requires paint and composite steps. Excessive stacking contexts increase the number of layers, causing more paint and composite work.

→Paint

→Composite

⚠️ BottleneckComposite stage is most expensive due to multiple layers needing GPU compositing.

Core Web Vital Affected

CLS

Stacking context affects how elements are layered visually and can impact paint and composite performance during rendering.

Optimization Tips

1Avoid CSS properties that create stacking contexts unless needed (opacity < 1, transform, filter).

2Minimize the number of elements with z-index to reduce stacking contexts.

3Use browser DevTools to monitor paint and composite layers for performance bottlenecks.

Performance Quiz - 3 Questions

Which CSS property can create a new stacking context and increase paint cost?

A color

B font-size

C opacity less than 1

D margin

DevTools: Performance

How to check: Record a performance profile while interacting with the page. Look for high paint and composite times and many layers in the Layers panel.

What to look for: High composite layer count and long paint durations indicate excessive stacking contexts.

Practice

1. What creates a new stacking context in CSS?

easy

A. An element with color property set

B. An element with position: relative and z-index set

C. Any element with display: block

D. An element with margin applied

Solution

1. Step 1: Understand stacking context creation

   A stacking context is created by elements with position other than static and a z-index value set.

2. Step 2: Analyze options

   Only An element with position: relative and z-index set mentions position: relative with z-index, which creates a stacking context. Other options do not create stacking contexts.

3. Final Answer:

   An element with position: relative and z-index set -> Option B

4. Quick Check:

   Stacking context = position + z-index [OK]

Hint: Look for position plus z-index to spot stacking contexts [OK]

Common Mistakes:

• Thinking any positioned element creates stacking context without z-index
• Confusing display or color properties with stacking context
• Assuming margin affects stacking order

2. Which CSS snippet correctly creates a stacking context?

easy

A. position: static; z-index: 10;

B. display: inline; z-index: 3;

C. position: relative; z-index: 5;

D. color: red; z-index: 1;

Solution

1. Step 1: Check position and z-index combination

   Only elements with position other than static and a z-index value create stacking contexts.

2. Step 2: Evaluate each option

   position: relative; z-index: 5; uses position: relative and z-index: 5, which correctly creates a stacking context. Others either have static position or irrelevant properties.

3. Final Answer:

   position: relative; z-index: 5; -> Option C

4. Quick Check:

   Position relative + z-index creates stacking context [OK]

Hint: Position must not be static to create stacking context [OK]

Common Mistakes:

• Using position static with z-index expecting stacking context
• Assuming display or color create stacking contexts
• Ignoring that inline elements don't create stacking contexts with z-index

3. Given this HTML and CSS, which element appears on top visually?

<div class='parent'>
  <div class='child1'>Child 1</div>
  <div class='child2'>Child 2</div>
</div>

.parent { position: relative; z-index: 1; }
.child1 { position: absolute; z-index: 2; }
.child2 { position: absolute; z-index: 1; }

medium

A. Parent appears on top of children

B. Child 2 appears on top

C. Both overlap equally, no stacking order

D. Child 1 appears on top

Solution

1. Step 1: Identify stacking contexts

   The parent has position: relative and z-index: 1, creating a stacking context. Children stack inside this context.

2. Step 2: Compare children's z-index inside stacking context

   Child 1 has z-index: 2, child 2 has z-index: 1. Higher z-index means it appears on top.

3. Final Answer:

   Child 1 appears on top -> Option D

4. Quick Check:

   Higher z-index inside stacking context = on top [OK]

Hint: Higher z-index inside same stacking context is on top [OK]

Common Mistakes:

• Ignoring stacking context created by parent
• Assuming parent overlays children
• Confusing absolute positioning with stacking order

4. Why does this CSS not create a stacking context as expected?

.box { position: absolute; }

What is missing?

medium

A. Missing z-index property

B. Position should be static

C. Need display: block

D. Color property must be set

Solution

1. Step 1: Understand stacking context requirements

   Positioned elements create stacking contexts only if z-index is set.

2. Step 2: Analyze given CSS

   The element has position: absolute but no z-index, so no stacking context is created.

3. Final Answer:

   Missing z-index property -> Option A

4. Quick Check:

   Position alone doesn't create stacking context without z-index [OK]

Hint: Position plus z-index needed for stacking context [OK]

Common Mistakes:

• Assuming position absolute alone creates stacking context
• Thinking display or color affect stacking context
• Confusing static position with stacking context creation

5. You have nested elements:

<div class='outer'>
  <div class='inner'>Content</div>
</div>

CSS:

.outer { position: relative; z-index: 1; }
.inner { position: relative; z-index: 10; }

Which statement is true about their stacking order?

hard

A. Inner's z-index 10 stacks only inside outer's stacking context

B. Inner's z-index 10 places it above all elements outside outer

C. Outer and inner share the same stacking context ignoring z-index

D. Inner's z-index is ignored because outer has lower z-index

Solution

1. Step 1: Identify stacking contexts

   The outer element creates a stacking context with position: relative and z-index: 1. The inner element creates a new stacking context inside outer with position: relative and z-index: 10.

2. Step 2: Understand stacking context isolation

   Inner's stacking order is only relative to siblings inside outer's stacking context. It cannot escape outer's stacking context to appear above elements outside it.

3. Final Answer:

   Inner's z-index 10 stacks only inside outer's stacking context -> Option A

4. Quick Check:

   Nested stacking contexts isolate z-index scope [OK]

Hint: Nested stacking contexts isolate z-index effects [OK]

Common Mistakes:

• Thinking inner z-index affects outside elements
• Assuming stacking contexts merge ignoring nesting
• Believing outer's lower z-index cancels inner's stacking