Recursive mixins in SASS - Performance & Optimization

Performance: Recursive mixins

MEDIUM IMPACT

This affects CSS compilation time and the size of the generated CSS, impacting page load speed and rendering performance.

Generating nested styles with recursion in Sass

SASS

@mixin recursive-good($n) {
  @for $i from 1 through $n {
    .level-#{$i} {
      color: red;
    }
  }
}

@include recursive-good(10);

Using a loop instead of recursion reduces compiler overhead and generates flat CSS, improving compile time and output size.

📈 Performance GainSingle loop compile, smaller CSS output, faster page load.

Generating nested styles with recursion in Sass

SASS

@mixin recursive-bad($n) {
  @if $n > 0 {
    .level-#{$n} {
      color: red;
      @include recursive-bad($n - 1);
    }
  }
}

@include recursive-bad(10);

This recursive mixin generates deeply nested selectors and repeated styles, increasing CSS size and compile time.

📉 Performance CostTriggers multiple nested loops in compiler, increasing compile time linearly with $n; generates large CSS increasing page load.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Recursive mixin with deep nesting	N/A (CSS only)	N/A	High due to complex selectors	[X] Bad
Loop-based mixin generating flat CSS	N/A (CSS only)	N/A	Low due to simple selectors	[OK] Good

Rendering Pipeline

Recursive mixins affect the CSS compilation stage before the browser rendering pipeline. Large or deeply nested CSS increases CSS file size, which delays Style Calculation and Layout stages in the browser.

→Style Calculation

→Layout

→Paint

⚠️ BottleneckStyle Calculation due to large CSS and complex selectors

Core Web Vital Affected

LCP

This affects CSS compilation time and the size of the generated CSS, impacting page load speed and rendering performance.

Optimization Tips

1Avoid deep recursion in Sass mixins to prevent large CSS output.

2Prefer loops (@for, @each) over recursion for generating repetitive styles.

3Keep generated CSS selectors simple to reduce browser style calculation time.

Performance Quiz - 3 Questions

What is a main performance drawback of using recursive mixins in Sass?

A They reduce CSS specificity causing style conflicts.

B They can generate very large CSS files increasing page load time.

C They prevent CSS from being cached by browsers.

D They cause JavaScript to run slower on the page.

DevTools: Network and Performance panels

How to check: Use Network panel to check CSS file size and load time; use Performance panel to record page load and see Style Calculation duration.

What to look for: Large CSS files and long Style Calculation times indicate inefficient recursive mixins.

Practice

1. What is the main purpose of a recursive mixin in sass?

easy

A. To call itself repeatedly to apply styles multiple times

B. To import external CSS files

C. To define variables for colors

D. To create animations with keyframes

Solution

1. Step 1: Understand what recursion means in programming

   Recursion means a function or mixin calls itself to repeat an action.

2. Step 2: Apply this to sass mixins

   A recursive mixin calls itself to repeat styles multiple times, often with changes each time.

3. Final Answer:

   To call itself repeatedly to apply styles multiple times -> Option A

4. Quick Check:

   Recursive mixin = repeated self-call [OK]

Hint: Recursive mixins repeat styles by calling themselves [OK]

Common Mistakes:

• Confusing recursion with importing files
• Thinking mixins only define variables
• Mixing up animations with recursion

2. Which of the following is the correct syntax to define a recursive mixin in sass?

easy

A. @mixin repeat($n) { color: red; @include repeat($n + 1); }

B. @mixin repeat($n) { @if $n > 0 { color: red; @include repeat($n - 1); } }

C. @mixin repeat { @include repeat; }

D. @mixin repeat($n) { @if $n < 0 { @include repeat($n - 1); } }

Solution

1. Step 1: Check for stop condition in mixin

   @mixin repeat($n) { @if $n > 0 { color: red; @include repeat($n - 1); } } uses @if $n > 0 to stop recursion when $n reaches 0.

2. Step 2: Verify recursive call decreases $n

   @mixin repeat($n) { @if $n > 0 { color: red; @include repeat($n - 1); } } calls itself with $n - 1, moving towards stop condition.

3. Final Answer:

   @mixin repeat($n) { @if $n > 0 { color: red; @include repeat($n - 1); } } -> Option B

4. Quick Check:

   Stop condition + decrement = correct recursion [OK]

Hint: Look for stop condition and decrement in recursive mixin [OK]

Common Mistakes:

• Missing stop condition causing infinite loop
• Incrementing instead of decrementing parameter
• Calling mixin without parameters

3. Given the following recursive mixin, what will be the color of the text inside .box after compilation?

@mixin colorLayers($n) {
  @if $n > 0 {
    color: lighten(blue, $n * 10%);
    @include colorLayers($n - 1);
  }
}

.box {
  @include colorLayers(2);
}

medium

A. The text color will be pure blue

B. There will be a syntax error and no color applied

C. The text color will be dark blue

D. The text color will be a light blue shade (lightened twice)

Solution

1. Step 1: Understand the recursion steps

   The mixin calls itself twice: first with $n=2, then $n=1, then stops at 0.

2. Step 2: Analyze color changes

   Each call applies color: lighten(blue, $n * 10%). So first lighten by 20%, then by 10%.

3. Final Answer:

   The text color will be a light blue shade (lightened twice) -> Option D

4. Quick Check:

   Recursive lighten steps = light blue [OK]

Hint: Trace recursive calls and their style effects stepwise [OK]

Common Mistakes:

• Assuming only one color applied
• Ignoring recursive layering of styles
• Thinking recursion causes error here

4. Identify the error in this recursive mixin and choose the fix:

@mixin borderLayers($count) {
  border: 1px solid black;
  @include borderLayers($count - 1);
}

medium

A. Missing stop condition; add @if $count > 0 before recursive call

B. Wrong parameter name; change $count to $n

C. Use @extend instead of @include

D. No error; code is correct

Solution

1. Step 1: Check for stop condition

   The mixin calls itself without any condition, causing infinite recursion.

2. Step 2: Fix by adding stop condition

   Adding @if $count > 0 before recursive call stops recursion when count reaches 0.

3. Final Answer:

   Missing stop condition; add @if $count > 0 before recursive call -> Option A

4. Quick Check:

   Stop condition prevents infinite recursion [OK]

Hint: Always add stop condition to recursive mixins [OK]

Common Mistakes:

• Forgetting stop condition
• Confusing @include with @extend
• Changing parameter names unnecessarily

5. You want to create a recursive mixin that adds nested box shadows with increasing blur. Which of these mixins correctly applies 3 layers of shadows with blur increasing by 2px each time?

hard

A. @mixin shadowLayers($n, $blur: 2) { @if $n < 0 { box-shadow: 0 0 #{$blur}px rgba(0,0,0,0.3); @include shadowLayers($n + 1, $blur + 2); } }

B. @mixin shadowLayers($n) { box-shadow: 0 0 2px rgba(0,0,0,0.3); @include shadowLayers($n - 1); }

C. @mixin shadowLayers($n, $blur: 2) { @if $n > 0 { box-shadow: 0 0 #{$blur}px rgba(0,0,0,0.3); @include shadowLayers($n - 1, $blur + 2); } }

D. @mixin shadowLayers($n, $blur: 2) { box-shadow: 0 0 #{$blur}px rgba(0,0,0,0.3); }

Solution

1. Step 1: Check for stop condition and parameter updates

   @mixin shadowLayers($n, $blur: 2) { @if $n > 0 { box-shadow: 0 0 #{$blur}px rgba(0,0,0,0.3); @include shadowLayers($n - 1, $blur + 2); } } has @if $n > 0 to stop recursion and increments blur by 2 each call.

2. Step 2: Verify recursive call and shadow layering

   @mixin shadowLayers($n, $blur: 2) { @if $n > 0 { box-shadow: 0 0 #{$blur}px rgba(0,0,0,0.3); @include shadowLayers($n - 1, $blur + 2); } } calls itself with $n - 1 and increasing blur, layering shadows correctly 3 times.

3. Final Answer:

   @mixin shadowLayers($n, $blur: 2) { @if $n > 0 { box-shadow: 0 0 #{$blur}px rgba(0,0,0,0.3); @include shadowLayers($n - 1, $blur + 2); } } -> Option C

4. Quick Check:

   Stop condition + parameter increment = correct recursive layering [OK]

Hint: Use stop condition and increment parameters in recursion [OK]

Common Mistakes:

• No stop condition causing infinite recursion
• Wrong comparison operator in stop condition
• Not incrementing blur value each recursion