Mixin definition with @mixin in SASS - Performance & Optimization

Performance: Mixin definition with @mixin

MEDIUM IMPACT

This affects CSS generation size and browser rendering by reusing style blocks efficiently.

Reusing common style blocks across multiple selectors

SASS

@mixin blue-box {
  background-color: blue;
  border-radius: 0.5rem;
  padding: 1rem;
}

button {
  @include blue-box;
}
.card {
  @include blue-box;
}

Reuses styles via mixin, reducing CSS duplication and file size.

📈 Performance GainSaves CSS bytes, improves LCP by faster CSS download and parse.

Reusing common style blocks across multiple selectors

SASS

button {
  background-color: blue;
  border-radius: 0.5rem;
  padding: 1rem;
}
.card {
  background-color: blue;
  border-radius: 0.5rem;
  padding: 1rem;
}

Repeating the same styles increases CSS file size and parsing time.

📉 Performance CostAdds unnecessary CSS bytes, increasing download and parse time.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Repeated styles without mixin	No change	No change	Higher due to larger CSS	[X] Bad
Styles reused with @mixin	No change	No change	Lower due to smaller CSS	[OK] Good

Rendering Pipeline

The browser downloads the CSS file generated from Sass. Smaller CSS files from mixin reuse reduce download and parsing time. Once parsed, styles are applied during Style Calculation and Layout stages.

→CSS Download

→Style Calculation

→Layout

⚠️ BottleneckCSS Download and Parsing

Core Web Vital Affected

LCP

This affects CSS generation size and browser rendering by reusing style blocks efficiently.

Optimization Tips

1Use @mixin to avoid repeating CSS code and reduce file size.

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

3Avoid duplicating styles to keep CSS parsing efficient.

Performance Quiz - 3 Questions

How does using @mixin in Sass affect CSS file size?

A It reduces CSS file size by reusing style blocks.

B It increases CSS file size by duplicating styles.

C It has no effect on CSS file size.

D It removes all CSS styles.

DevTools: Network

How to check: Open DevTools > Network tab > Reload page > Filter by CSS files > Check file size of CSS output.

What to look for: Smaller CSS file size indicates efficient reuse with mixins; large files suggest duplication.

Practice

1. What is the main purpose of using @mixin in Sass?

easy

A. To create reusable blocks of CSS code

B. To define variables for colors

C. To import external CSS files

D. To write JavaScript inside Sass

Solution

1. Step 1: Understand what @mixin does

   @mixin is used to write reusable CSS blocks that can be included multiple times.

2. Step 2: Compare options

   Only 'To create reusable blocks of CSS code' correctly describes this purpose. Variables, imports, and JavaScript are unrelated to @mixin.

3. Final Answer:

   To create reusable blocks of CSS code -> Option A

4. Quick Check:

   Mixin = reusable CSS block [OK]

Hint: Mixins bundle CSS to reuse easily [OK]

Common Mistakes:

• Confusing mixins with variables
• Thinking mixins import files
• Assuming mixins run JavaScript

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

easy

A. @include button-style { color: blue; }

B. @mixin button-style { color: blue; }

C. @mixin: button-style { color: blue; }

D. mixin button-style() { color: blue; }

Solution

1. Step 1: Recall mixin definition syntax

   The correct way to define a mixin is using @mixin name { ... }.

2. Step 2: Check each option

   @mixin button-style { color: blue; } uses @mixin button-style { ... }, which is correct. @include button-style { color: blue; } uses @include which is for using mixins, not defining. Options C and D have invalid syntax.

3. Final Answer:

   @mixin button-style { color: blue; } -> Option B

4. Quick Check:

   Define mixin with @mixin [OK]

Hint: Define mixins with @mixin, use with @include [OK]

Common Mistakes:

• Using @include instead of @mixin to define
• Adding colon after @mixin
• Omitting @ symbol

3. Given the Sass code:

@mixin box-shadow($x, $y, $blur, $color) {
  box-shadow: $x $y $blur $color;
}

.button {
  @include box-shadow(2px, 4px, 6px, rgba(0,0,0,0.3));
}

What CSS will be generated for the .button class?

medium

A. .button { box-shadow: 2px 4px 6px rgba(0,0,0,0.3); }

B. .button { box-shadow: $x $y $blur $color; }

C. .button { box-shadow: 2px, 4px, 6px, rgba(0,0,0,0.3); }

D. Syntax error, no CSS generated

Solution

1. Step 1: Understand mixin parameters and usage

   The mixin box-shadow takes four parameters and sets the CSS box-shadow property using them.

2. Step 2: Substitute parameters in the mixin call

   The call @include box-shadow(2px, 4px, 6px, rgba(0,0,0,0.3)) replaces variables with these values, producing box-shadow: 2px 4px 6px rgba(0,0,0,0.3);.

3. Final Answer:

   .button { box-shadow: 2px 4px 6px rgba(0,0,0,0.3); } -> Option A

4. Quick Check:

   Mixin parameters replaced correctly [OK]

Hint: Parameters replace variables inside mixins [OK]

Common Mistakes:

• Leaving variables as $x, $y in output
• Using commas instead of spaces in CSS property
• Confusing @mixin and @include usage

4. Identify the error in this Sass code:

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

.box {
  @mixin border-radius(10px);
}

medium

A. Mixin name should be borderRadius without hyphen

B. Missing semicolon after border-radius property

C. Using @mixin instead of @include to apply the mixin

D. Parameters cannot be passed to mixins

Solution

1. Step 1: Check mixin application syntax

   Mixins are defined with @mixin but applied with @include.

2. Step 2: Identify the incorrect usage

   The code uses @mixin border-radius(10px); inside .box, which is wrong. It should be @include border-radius(10px);.

3. Final Answer:

   Using @mixin instead of @include to apply the mixin -> Option C

4. Quick Check:

   Apply mixins with @include [OK]

Hint: Use @include to apply mixins, not @mixin [OK]

Common Mistakes:

• Confusing @mixin and @include
• Thinking parameters are not allowed
• Assuming hyphens are invalid in names

5. You want to create a mixin responsive-text that sets font size differently for small and large screens. Which of these mixin definitions correctly uses parameters and media queries?

hard

A. @mixin responsive-text($size) {
font-size: $size;
@media (min-width: 600px) {
font-size: calc($size * 2);
}
}

B. @mixin responsive-text {
font-size: 12px;
@media (min-width: 600px) {
font-size: 18px;
}
}

C. @mixin responsive-text($small, $large) {
font-size: $small;
@media (max-width: 600px) {
font-size: $large;
}
}

D. @mixin responsive-text($small-size, $large-size) {
font-size: $small-size;
@media (min-width: 600px) {
font-size: $large-size;
}
}

Solution

1. Step 1: Understand the goal

   The mixin should accept two sizes: one for small screens and one for large screens using a media query with min-width 600px.

2. Step 2: Analyze each option

   @mixin responsive-text($small-size, $large-size) { font-size: $small-size; @media (min-width: 600px) { font-size: $large-size; } } correctly defines two parameters and applies font sizes with a media query for screens wider than 600px. @mixin responsive-text { font-size: 12px; @media (min-width: 600px) { font-size: 18px; } } has no parameters, so not flexible. @mixin responsive-text($size) { font-size: $size; @media (min-width: 600px) { font-size: $size * 2; } } tries to multiply a variable inside CSS, which Sass does not support directly without interpolation or calculation. @mixin responsive-text($small, $large) { font-size: $small; @media (max-width: 600px) { font-size: $large; } } uses max-width media query incorrectly for large screens.

3. Final Answer:

   @mixin responsive-text($small-size, $large-size) { font-size: $small-size; @media (min-width: 600px) { font-size: $large-size; } } -> Option D

4. Quick Check:

   Parameters + correct media query = @mixin responsive-text($small-size, $large-size) { font-size: $small-size; @media (min-width: 600px) { font-size: $large-size; } } [OK]

Hint: Use parameters and min-width media query for responsive mixins [OK]

Common Mistakes:

• Not using parameters for flexibility
• Using max-width instead of min-width for large screens
• Trying to do math directly in CSS without Sass functions