Why mixins eliminate duplication in SASS - Performance Evidence

Performance: Why mixins eliminate duplication

MEDIUM IMPACT

This affects CSS file size and browser style recalculation by reducing repeated code blocks.

Applying the same style rules repeatedly in CSS

SASS

@mixin common-padding { padding: 1rem 2rem; border-radius: 0.5rem; } @media (min-width: 600px) { .btn { @include common-padding; } } .card { @include common-padding; }

Mixins reuse style code, reducing duplication and CSS file size.

📈 Performance GainSaves kilobytes in CSS and reduces style recalculations.

Applying the same style rules repeatedly in CSS

SASS

@media (min-width: 600px) { .btn { padding: 1rem 2rem; border-radius: 0.5rem; } } .card { padding: 1rem 2rem; border-radius: 0.5rem; }

Repeating identical style blocks increases CSS size and parsing time.

📉 Performance CostAdds extra kilobytes to CSS file and triggers multiple style recalculations.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Repeated CSS blocks	No extra DOM nodes	Multiple style recalculations	Higher paint cost due to slower style calculation	[X] Bad
Using mixins for reuse	No extra DOM nodes	Single style recalculation per unique rule	Lower paint cost due to efficient style calculation	[OK] Good

Rendering Pipeline

Mixins reduce CSS file size, which speeds up CSS parsing and style calculation stages in the browser.

→Style Calculation

→Layout

⚠️ BottleneckStyle Calculation due to repeated CSS rules

Core Web Vital Affected

LCP

This affects CSS file size and browser style recalculation by reducing repeated code blocks.

Optimization Tips

1Use mixins to write reusable CSS blocks and avoid repeating code.

2Reducing CSS duplication lowers file size and speeds up style calculation.

3Smaller CSS files improve Largest Contentful Paint (LCP) by loading styles faster.

Performance Quiz - 3 Questions

How do mixins improve CSS performance?

A By increasing the number of DOM nodes

B By adding more CSS rules for each element

C By reducing repeated CSS code and lowering file size

D By delaying CSS parsing until user interaction

DevTools: Performance

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

What to look for: Fewer and shorter style recalculation events indicate better CSS reuse and less duplication.

Practice

1. Why do Sass mixins help reduce duplication in your stylesheets?

easy

A. Because they generate random colors for your styles

B. Because they let you write a style once and reuse it multiple times

C. Because they replace all CSS selectors with shorter names

D. Because they automatically compress your CSS files

Solution

1. Step 1: Understand what duplication means in CSS

   Duplication means writing the same style code multiple times in different places.

2. Step 2: See how mixins solve duplication

   Mixins let you write a style block once and reuse it by calling the mixin wherever needed.

3. Final Answer:

   Because they let you write a style once and reuse it multiple times -> Option B

4. Quick Check:

   Mixins reduce duplication = reuse styles [OK]

Hint: Mixins = write once, use many times [OK]

Common Mistakes:

• Thinking mixins compress CSS files
• Confusing mixins with CSS selectors
• Believing mixins generate random styles

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

easy

A. @mixin example { color: red; }

B. @define example { color: red; }

C. @include example { color: red; }

D. @style example { color: red; }

Solution

1. Step 1: Recall the keyword to define a mixin

   The correct keyword to define a mixin is @mixin.

2. Step 2: Check the syntax format

   The mixin is defined with @mixin name { ... }. Other options use incorrect keywords.

3. Final Answer:

   @mixin example { color: red; } -> Option A

4. Quick Check:

   Define mixin with @mixin [OK]

Hint: Define mixins with @mixin keyword [OK]

Common Mistakes:

• Using @include to define instead of call
• Using @define which is invalid
• Confusing @style with mixin syntax

3. What will be the output CSS of this Sass code?

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

.box {
  @include border-radius(10px);
  background: blue;
}

medium

A. Syntax error: missing semicolon

B. .box { border-radius: $radius; background: blue; }

C. .box { background: blue; }

D. .box { border-radius: 10px; background: blue; }

Solution

1. Step 1: Understand mixin with parameter

   The mixin border-radius takes a parameter $radius and sets border-radius property.

2. Step 2: See how mixin is included

   The class .box includes the mixin with argument 10px, so border-radius: 10px; is added.

3. Final Answer:

   .box { border-radius: 10px; background: blue; } -> Option D

4. Quick Check:

   Mixin parameter replaced correctly [OK]

Hint: Mixin parameters replace variables inside [OK]

Common Mistakes:

• Expecting variable names in output CSS
• Ignoring mixin parameters
• Thinking mixin causes syntax errors

4. Identify the error in this Sass code that tries to use a mixin:

@mixin text-style {
  font-size: 16px;
  color: black;
}

.title {
  text-style;
  font-weight: bold;
}

medium

A. Mixin is not called with @include keyword

B. Mixin is missing parameters

C. Mixin name is invalid

D. Mixin should be inside a selector

Solution

1. Step 1: Check how mixins are called

   Mixins must be called with @include mixin-name; inside selectors.

2. Step 2: Identify the error in usage

   The code uses text-style; without @include, so it won't apply the mixin styles.

3. Final Answer:

   Mixin is not called with @include keyword -> Option A

4. Quick Check:

   Call mixins with @include [OK]

Hint: Always use @include to call mixins [OK]

Common Mistakes:

• Forgetting @include before mixin name
• Adding parameters when none needed
• Placing mixin inside selector definition

5. You want to create a button style that can have different background colors but share the same padding and border radius. How can mixins help you avoid duplication?

@mixin button-style($bg-color) {
  background-color: $bg-color;
  padding: 1rem 2rem;
  border-radius: 0.5rem;
}

.primary-btn {
  @include button-style(blue);
}

.secondary-btn {
  @include button-style(gray);
}

hard

A. Mixins force you to write all styles separately for each button

B. Mixins only work without parameters, so colors must be hardcoded

C. Mixins let you write padding and border-radius once and reuse with different colors

D. Mixins duplicate styles for each button, increasing CSS size

Solution

1. Step 1: Analyze the mixin with parameter

   The mixin button-style defines padding and border-radius once and accepts a background color parameter.

2. Step 2: See how different buttons reuse the mixin

   Both .primary-btn and .secondary-btn include the mixin with different colors, reusing common styles without duplication.

3. Final Answer:

   Mixins let you write padding and border-radius once and reuse with different colors -> Option C

4. Quick Check:

   Mixins reuse common styles with custom inputs [OK]

Hint: Use parameters in mixins for flexible reuse [OK]

Common Mistakes:

• Thinking mixins require rewriting all styles
• Believing mixins can't take parameters
• Assuming mixins increase CSS size unnecessarily