Media query mixin patterns in SASS - Performance & Optimization

Performance: Media query mixin patterns

MEDIUM IMPACT

This affects how CSS is loaded and applied, impacting page load speed and rendering efficiency.

Applying responsive styles using media queries in Sass

SASS

@mixin respond($breakpoint) {
  $queries: (
    small: '(max-width: 600px)',
    medium: '(max-width: 900px)',
    large: '(max-width: 1200px)'
  );
  @media #{map-get($queries, $breakpoint)} {
    @content;
  }
}

.element {
  @include respond(small) {
    font-size: 1rem;
  }
  @include respond(medium) {
    font-size: 1.2rem;
  }
  @include respond(large) {
    font-size: 1.5rem;
  }
}

Uses a map to centralize media queries, reducing duplication and CSS size.

📈 Performance GainSmaller CSS bundle and fewer style recalculations, improving load and render speed.

Applying responsive styles using media queries in Sass

SASS

@mixin respond-bad($breakpoint) {
  @if $breakpoint == small {
    @media (max-width: 600px) {
      @content;
    }
  }
  @if $breakpoint == medium {
    @media (max-width: 900px) {
      @content;
    }
  }
  @if $breakpoint == large {
    @media (max-width: 1200px) {
      @content;
    }
  }
}

.element {
  @include respond-bad(small) {
    font-size: 1rem;
  }
  @include respond-bad(medium) {
    font-size: 1.2rem;
  }
  @include respond-bad(large) {
    font-size: 1.5rem;
  }
}

This pattern repeats multiple @media rules separately, causing duplicated CSS and larger file size.

📉 Performance CostAdds unnecessary CSS bytes and triggers multiple style recalculations during load.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Repeated media queries in mixins	No extra DOM nodes	Multiple reflows due to duplicated styles	Higher paint cost from redundant styles	[X] Bad
Centralized media query map in mixin	No extra DOM nodes	Single reflow per breakpoint	Lower paint cost with minimal CSS	[OK] Good

Rendering Pipeline

Media queries are parsed during CSS loading. Efficient mixins reduce CSS size and complexity, speeding up style calculation and layout.

→Style Calculation

→Layout

→Paint

⚠️ BottleneckStyle Calculation due to large or duplicated CSS rules

Core Web Vital Affected

LCP

This affects how CSS is loaded and applied, impacting page load speed and rendering efficiency.

Optimization Tips

1Use a single map to store all media query strings in Sass.

2Avoid repeating the same media query multiple times in your CSS.

3Keep media queries organized to reduce CSS file size and speed up style calculation.

Performance Quiz - 3 Questions

What is a main performance benefit of using a centralized media query map in Sass mixins?

A Increases the number of media queries

B Reduces duplicated CSS and file size

C Adds more DOM elements

D Blocks JavaScript execution

DevTools: Performance

How to check: Record a page load and look at the 'Style Recalculation' and 'Layout' events to see if multiple reflows occur due to CSS.

What to look for: Fewer style recalculation events and shorter layout times indicate better media query usage.

Practice

1. What is the main benefit of using a media query mixin in Sass?

easy

A. You write the media query once and reuse it multiple times

B. It automatically fixes all layout bugs

C. It converts Sass to JavaScript

D. It removes the need for CSS altogether

Solution

1. Step 1: Understand what a mixin does

   A mixin lets you write reusable code blocks in Sass.

2. Step 2: Apply this to media queries

   Using a media query mixin means you write the query once and reuse it for different styles.

3. Final Answer:

   You write the media query once and reuse it multiple times -> Option A

4. Quick Check:

   Reusable media queries = A [OK]

Hint: Mixins save repeating code by reusing media queries [OK]

Common Mistakes:

• Thinking mixins fix layout bugs automatically
• Confusing Sass with JavaScript
• Believing mixins remove CSS need

2. Which of the following is the correct syntax to define a media query mixin for max-width 600px in Sass?

easy

A. @mixin respond { @media (max-width: 600px) { @content; } }

B. @media respond { max-width: 600px; } @mixin { content; }

C. @mixin respond(max-width: 600px) { content; }

D. @media (max-width: 600px) { @mixin respond { content; } }

Solution

1. Step 1: Recall Sass mixin syntax

   A mixin is defined with @mixin name { ... } and uses @content to insert styles.

2. Step 2: Check media query inside mixin

   The media query should wrap @content inside the mixin block.

3. Final Answer:

   @mixin respond { @media (max-width: 600px) { @content; } } -> Option A

4. Quick Check:

   Mixin with media and @content = B [OK]

Hint: Use @mixin name { @media (...) { @content; } } for media queries [OK]

Common Mistakes:

• Placing @media outside the mixin
• Wrong order of @mixin and @media
• Missing @content inside media query

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

@mixin phone { @media (max-width: 480px) { @content; } }
.box {
  width: 100%;
  @include phone {
    width: 50%;
  }
}

medium

A. .box { width: 100%; width: 50%; }

B. .box { width: 50%; } @media (max-width: 480px) { .box { width: 100%; } }

C. @media (max-width: 480px) { .box { width: 100%; } } .box { width: 50%; }

D. .box { width: 100%; } @media (max-width: 480px) { .box { width: 50%; } }

Solution

1. Step 1: Understand mixin usage

   The mixin wraps included styles inside the media query for max-width 480px.

2. Step 2: Translate Sass to CSS

   .box has width 100% normally, and inside the media query it changes to width 50%.

3. Final Answer:

   .box { width: 100%; } @media (max-width: 480px) { .box { width: 50%; } } -> Option D

4. Quick Check:

   Normal style + media query override = D [OK]

Hint: Mixin wraps included styles inside media query block [OK]

Common Mistakes:

• Swapping widths inside and outside media query
• Putting media query styles outside the block
• Combining widths without media query

4. Identify the error in this Sass mixin and how to fix it:

@mixin tablet {
  @media max-width: 768px {
    @content;
  }
}

medium

A. Mixin name 'tablet' is invalid; must start with a capital letter

B. @content should be outside @media block

C. Missing parentheses around max-width value in @media; fix with @media (max-width: 768px)

D. @media cannot be used inside mixins

Solution

1. Step 1: Check @media syntax

   The media query must have parentheses around conditions, like (max-width: 768px).

2. Step 2: Correct the syntax

   Change @media max-width: 768px to @media (max-width: 768px) to fix the error.

3. Final Answer:

   Missing parentheses around max-width value in @media; fix with @media (max-width: 768px) -> Option C

4. Quick Check:

   @media needs parentheses = A [OK]

Hint: Always wrap media conditions in parentheses [OK]

Common Mistakes:

• Omitting parentheses in @media
• Placing @content outside media block
• Thinking mixin names must be capitalized

5. You want to create a Sass mixin that accepts a max-width value as a parameter and applies styles inside that media query. Which of these mixins correctly implements this pattern?

hard

A. @mixin respond($max) { @media max-width: $max { @content; } }

B. @mixin respond($max) { @media (max-width: $max) { @content; } }

C. @mixin respond { @media (max-width: $max) { @content; } }

D. @mixin respond($max) { @media (min-width: $max) { @content; } }

Solution

1. Step 1: Check parameter usage in mixin

   The mixin must accept a parameter $max and use it inside parentheses in the media query.

2. Step 2: Verify correct media query syntax

   @media (max-width: $max) is correct; missing parentheses or wrong media feature cause errors.

3. Final Answer:

   @mixin respond($max) { @media (max-width: $max) { @content; } } -> Option B

4. Quick Check:

   Parameterized media query with parentheses = C [OK]

Hint: Use parameters with parentheses in media queries [OK]

Common Mistakes:

• Missing parentheses around media condition
• Using min-width instead of max-width by mistake
• Not passing parameter to mixin