Avoiding selector bloat from @extend in SASS - Performance & Optimization

Performance: Avoiding selector bloat from @extend

MEDIUM IMPACT

This affects CSS file size and browser rendering speed by controlling how many selectors are generated and matched.

Reusing styles without creating large, complex selectors

SASS

@mixin button-style {
  padding: 1rem;
  border-radius: 0.5rem;
}

.button {
  @include button-style;
}
.alert {
  @include button-style;
}
.card {
  @include button-style;
}

Using mixins duplicates styles but keeps selectors simple and separate, reducing selector bloat and improving browser style matching speed.

📈 Performance GainReduces CSS size growth and improves style recalculation speed by avoiding large combined selectors.

Reusing styles without creating large, complex selectors

SASS

@extend .button;
@extend .alert;
@extend .card;

Using multiple @extend directives on different selectors causes Sass to combine selectors, creating very long selector lists that increase CSS size and slow browser matching.

📉 Performance CostIncreases CSS file size by 30-50% and triggers slower style recalculation in browsers.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Multiple @extend on different selectors	No direct DOM changes	0	High due to complex selector matching	[X] Bad
Using mixins for style reuse	No direct DOM changes	0	Low due to simple selectors	[OK] Good

Rendering Pipeline

Large combined selectors from @extend increase the complexity of the Style Calculation stage, making the browser spend more time matching elements to styles.

→Style Calculation

⚠️ BottleneckStyle Calculation due to complex selector matching

Core Web Vital Affected

LCP

This affects CSS file size and browser rendering speed by controlling how many selectors are generated and matched.

Optimization Tips

1Avoid using @extend on many different selectors to prevent large combined selectors.

2Prefer mixins or utility classes to reuse styles without selector bloat.

3Keep CSS selectors simple to speed up browser style matching and improve LCP.

Performance Quiz - 3 Questions

What is a main performance problem caused by excessive use of @extend in Sass?

A It blocks JavaScript execution during page load.

B It creates very long combined selectors that slow down browser style matching.

C It increases the number of DOM nodes on the page.

D It causes images to load slower.

DevTools: Performance

How to check: Record a performance profile while loading the page and look at the 'Style Recalculation' time in the summary.

What to look for: Long style recalculation times indicate complex selectors; shorter times mean simpler CSS selectors and better performance.

Practice

1. What is the main problem with using @extend in Sass without placeholders?

easy

A. It creates long combined selectors causing selector bloat.

B. It duplicates all CSS properties in the output.

C. It prevents styles from being reused.

D. It only works inside mixins.

Solution

1. Step 1: Understand what @extend does

   @extend shares styles by combining selectors in the output CSS.

2. Step 2: Identify the problem with combining selectors

   When many selectors are combined, the CSS file grows longer and harder to maintain, called selector bloat.

3. Final Answer:

   It creates long combined selectors causing selector bloat. -> Option A

4. Quick Check:

   @extend causes selector bloat = A [OK]

Hint: Remember: @extend merges selectors, causing long combined lists [OK]

Common Mistakes:

• Thinking @extend duplicates properties instead of combining selectors
• Confusing @extend with mixins
• Believing @extend only works inside mixins

2. Which of the following is the correct way to define a placeholder selector in Sass?

easy

A. %button { color: blue; }

B. .button { color: blue; }

C. #button { color: blue; }

D. &button { color: blue; }

Solution

1. Step 1: Recall placeholder selector syntax

   Placeholder selectors start with a percent sign (%) in Sass.

2. Step 2: Match the syntax to the options

   Only %button { color: blue; } uses %button, which is the correct placeholder syntax.

3. Final Answer:

   %button { color: blue; } -> Option A

4. Quick Check:

   Placeholder selector syntax = %name [OK]

Hint: Placeholders start with % in Sass [OK]

Common Mistakes:

• Using class selector syntax (.) instead of %
• Using ID selector (#) for placeholders
• Confusing & with placeholder syntax

3. Given the Sass code:

%btn { color: red; }
.primary { @extend %btn; }
.secondary { @extend %btn; }

What will the compiled CSS look like?

medium

A. .primary, .secondary, %btn { color: red; }

B. .primary, .secondary { color: red; }

C. %btn { color: red; } .primary, .secondary { color: red; }

D. .primary { color: red; } .secondary { color: red; }

Solution

1. Step 1: Understand placeholder selectors output

   Placeholder selectors do not appear in the compiled CSS; only selectors that extend them appear combined.

2. Step 2: Combine selectors that extend the placeholder

   .primary and .secondary both extend %btn, so they are combined into one selector with the shared styles.

3. Final Answer:

   .primary, .secondary { color: red; } -> Option B

4. Quick Check:

   Placeholder selectors disappear, extended selectors combine [OK]

Hint: Placeholder selectors don't output; extended selectors combine [OK]

Common Mistakes:

• Expecting %btn to appear in CSS
• Thinking styles duplicate for each selector
• Confusing combined selectors with separate blocks

4. What is wrong with this Sass code that uses @extend without placeholders?

.btn { color: green; }
.primary { @extend .btn; }
.secondary { @extend .btn; }

medium

A. It duplicates the .btn styles instead of combining selectors.

B. It causes a syntax error because @extend needs placeholders.

C. It causes selector bloat by combining all selectors including .btn.

D. It does not apply styles to .primary and .secondary.

Solution

1. Step 1: Understand @extend with normal selectors

   Extending a normal class merges selectors including the original class, creating longer combined selectors.

2. Step 2: Identify the problem caused

   This merging causes selector bloat because the original selector (.btn) stays in output and combines with all extending selectors.

3. Final Answer:

   It causes selector bloat by combining all selectors including .btn. -> Option C

4. Quick Check:

   @extend without placeholders causes selector bloat [OK]

Hint: Extending normal selectors merges all selectors, causing bloat [OK]

Common Mistakes:

• Thinking @extend requires placeholders
• Expecting duplicated styles instead of combined selectors
• Believing styles won't apply to extending selectors

5. You want to share button styles in Sass but avoid selector bloat from @extend. Which approach is best?

hard

A. Use a placeholder selector with @extend in button classes.

B. Use @extend directly on a normal class selector.

C. Copy and paste the styles into each button class.

D. Use a mixin to include styles in each button class.

Solution

1. Step 1: Understand selector bloat causes

   @extend merges selectors, which can cause long combined selectors and bloat.

2. Step 2: Compare placeholders and mixins

   Placeholders reduce bloat but still combine selectors. Mixins copy styles without merging selectors, avoiding bloat.

3. Step 3: Choose the best approach to avoid bloat

   Using mixins copies styles directly, preventing selector bloat while sharing styles.

4. Final Answer:

   Use a mixin to include styles in each button class. -> Option D

5. Quick Check:

   Mixins avoid selector bloat better than @extend [OK]

Hint: Mixins copy styles, avoiding selector bloat from @extend [OK]

Common Mistakes:

• Thinking placeholders fully prevent bloat
• Using @extend on normal selectors causing bloat
• Copy-pasting styles manually instead of using mixins