Functions vs mixins comparison in SASS - Performance Comparison

Performance: Functions vs mixins comparison

MEDIUM IMPACT

This affects CSS generation size and browser rendering speed by controlling how styles are reused and output.

Reusing style code for multiple selectors

SASS

$shadow: 0 4px 6px rgba(0,0,0,0.1);
.button { box-shadow: $shadow; }
.card { box-shadow: $shadow; }

Using variables or functions outputs CSS once, reducing duplication and file size.

📈 Performance GainSmaller CSS bundle, faster LCP due to less CSS to parse

Reusing style code for multiple selectors

SASS

@mixin box-shadow() { box-shadow: 0 4px 6px rgba(0,0,0,0.1); }
.button { @include box-shadow(); }
.card { @include box-shadow(); }

Mixins duplicate CSS code each time they are included, increasing CSS file size and load time.

📉 Performance CostAdds repeated CSS rules, increasing bundle size and blocking rendering longer

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Using mixins for repeated styles	No direct DOM impact	No direct reflows but larger CSS triggers slower style calculation	Higher paint cost due to larger CSS	[X] Bad
Using functions for value reuse	No direct DOM impact	No reflows triggered	Lower paint cost with smaller CSS	[OK] Good

Rendering Pipeline

Functions compute values at compile time, producing minimal CSS. Mixins inject full CSS blocks each use, increasing CSS size and parsing time.

→Style Calculation

→Layout

→Paint

⚠️ BottleneckStyle Calculation due to larger CSS from mixins

Core Web Vital Affected

LCP

This affects CSS generation size and browser rendering speed by controlling how styles are reused and output.

Optimization Tips

1Use Sass functions to compute and reuse values without duplicating CSS.

2Avoid overusing mixins to prevent bloated CSS and slower page load.

3Check CSS bundle size and style recalculation time to optimize Sass usage.

Performance Quiz - 3 Questions

Which Sass feature helps reduce CSS file size by returning values instead of duplicating styles?

A Mixins

B Functions

C Placeholders

D Variables

DevTools: Performance

How to check: Record page load and look at CSS parsing and style recalculation times; compare CSS file sizes in Network panel.

What to look for: Longer style recalculation or larger CSS files indicate inefficient mixin use; smaller CSS and faster style calculation indicate good function use.

Practice

1. What is the main difference between a function and a mixin in Sass?

easy

A. Functions output CSS rules, while mixins return values.

B. Functions return values, while mixins output CSS rules.

C. Functions and mixins both return values but in different formats.

D. Functions and mixins both output CSS rules but with different syntax.

Solution

1. Step 1: Understand what functions do in Sass

   Functions calculate and return values like colors, numbers, or strings.

2. Step 2: Understand what mixins do in Sass

   Mixins insert blocks of CSS rules where they are included.

3. Final Answer:

   Functions return values, while mixins output CSS rules. -> Option B

4. Quick Check:

   Functions = return values, Mixins = CSS rules [OK]

Hint: Functions return values; mixins add CSS blocks [OK]

Common Mistakes:

• Thinking mixins return values like functions
• Confusing output of CSS rules with returned values
• Assuming both do the same thing

2. Which of the following is the correct syntax to define a Sass function named double that returns twice the input number?

easy

A. @function double($n) { @return $n * 2; }

B. @mixin double($n) { @return $n * 2; }

C. @function double($n) { $n * 2; }

D. @mixin double($n) { @content; }

Solution

1. Step 1: Identify function syntax in Sass

   Functions use @function keyword and must include a @return statement.

2. Step 2: Check each option

   @function double($n) { @return $n * 2; } correctly defines a function with @return $n * 2;. Choices using @mixin are incorrect for functions. @function double($n) { $n * 2; } lacks @return.

3. Final Answer:

   @function double($n) { @return $n * 2; } -> Option A

4. Quick Check:

   Functions need @return [OK]

Hint: Functions use @function and must return a value [OK]

Common Mistakes:

• Using @mixin instead of @function for functions
• Forgetting the @return statement
• Confusing mixin syntax with function syntax

3. Given the Sass code below, what CSS will be generated?

@mixin border-radius($radius) {
  -webkit-border-radius: $radius;
  -moz-border-radius: $radius;
  border-radius: $radius;
}

.button {
  @include border-radius(10px);
}

medium

A. .button {
-webkit-border-radius: 10px;
-moz-border-radius: 10px;
border-radius: 10px;
}

B. .button {
border-radius: 10px;
}

C. Error: mixin border-radius not found

D. .button {
@include border-radius(10px);
}

Solution

1. Step 1: Understand what the mixin does

   The mixin adds three CSS properties for border-radius with vendor prefixes.

2. Step 2: Check how the mixin is included

   The mixin is included inside the .button selector with argument 10px, so all three properties will appear with that value.

3. Final Answer:

   .button { -webkit-border-radius: 10px; -moz-border-radius: 10px; border-radius: 10px; } -> Option A

4. Quick Check:

   Mixins output CSS rules where included [OK]

Hint: Mixins insert CSS blocks with given arguments [OK]

Common Mistakes:

• Expecting only the last property without prefixes
• Thinking mixins return values instead of CSS
• Confusing @include with outputting @include literally

4. What is wrong with this Sass code?

@function add($a, $b) {
  $sum: $a + $b;
}

.result {
  width: add(10px, 5px);
}

medium

A. Mixins cannot be called inside property values.

B. The function uses invalid variable names.

C. The function should use @mixin instead of @function.

D. The function does not have a @return statement.

Solution

1. Step 1: Check function definition

   The function calculates $sum but does not return it with @return.

2. Step 2: Understand function usage

   Functions must return a value to be used inside property values like width. Without @return, it returns nothing.

3. Final Answer:

   The function does not have a @return statement. -> Option D

4. Quick Check:

   Functions must return values to be used [OK]

Hint: Functions need @return to output values [OK]

Common Mistakes:

• Forgetting @return in functions
• Confusing mixins with functions
• Using mixins inside property values

5. You want to create a reusable Sass code that sets a color with 50% opacity. Which approach is best and why?

hard

A. Use a mixin that returns a value (mixins don't return values).

B. Use a mixin to output CSS rules setting color with 50% opacity.

C. Use a function to return the color with 50% opacity for flexible use.

D. Use a function that outputs CSS rules (invalid syntax).

Solution

1. Step 1: Understand the goal

   You want a reusable way to get a color with 50% opacity that can be used anywhere, like in variables or properties.

2. Step 2: Choose between function and mixin

   Functions return values, so they can be used inside any property or variable. Mixins output CSS rules directly and cannot return values.

3. Step 3: Evaluate choices

   The choice suggesting a mixin that returns a value is incorrect because mixins do not return values. The choice using a mixin to output CSS rules for the color property is less flexible. The choice using a function to output CSS rules has invalid syntax. The choice using a function to return the color value with opacity is best for flexibility.

4. Final Answer:

   Use a function to return the color with 50% opacity for flexible use. -> Option C

5. Quick Check:

   Functions return values for reuse; mixins output CSS [OK]

Hint: Use functions to return values; mixins to add CSS rules [OK]

Common Mistakes:

• Using mixins when a value return is needed
• Expecting mixins to return values
• Trying to output CSS from functions