Flexbox utility class generation in SASS - Performance & Optimization

Performance: Flexbox utility class generation

MEDIUM IMPACT

This affects page load speed and rendering performance by controlling how flexbox utility classes are generated and applied, impacting CSS size and browser layout calculations.

Creating reusable flexbox utility classes for layout

SASS

$flex-utilities: (
  justify-content: (center, flex-start, flex-end),
  align-items: (center, flex-start),
  flex-direction: (row, column)
);

@each $prop, $values in $flex-utilities {
  @each $value in $values {
    .#{$prop}-#{$value} {
      #{$prop}: #{$value};
    }
  }
}

Generates only needed utility classes, reducing CSS size and improving load and parse times.

📈 Performance GainSaves 10-30kb in CSS bundle, reducing LCP by 100-200ms on slow connections

Creating reusable flexbox utility classes for layout

SASS

@each $prop in (justify-content, align-items, flex-direction) {
  @each $value in (center, flex-start, flex-end, row, column) {
    .#{$prop}-#{$value} {
      #{$prop}: #{$value};
    }
  }
}

Generates many classes including unused ones, increasing CSS file size and causing longer CSS parsing and slower initial rendering.

📉 Performance CostAdds 20-50kb to CSS bundle depending on number of properties and values

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Generating all possible flexbox utilities	No extra DOM nodes	No direct reflows but large CSS slows style calculation	Medium paint cost due to slower layout	[X] Bad
Generating only needed flexbox utilities	No extra DOM nodes	No direct reflows, smaller CSS speeds style calculation	Lower paint cost due to faster layout	[OK] Good

Rendering Pipeline

Flexbox utility classes affect the Style Calculation and Layout stages by adding CSS rules that the browser must parse and apply. Larger CSS files increase Style Calculation time, and more layout changes can trigger reflows.

→Style Calculation

→Layout

→Paint

⚠️ BottleneckStyle Calculation due to large CSS size

Core Web Vital Affected

LCP

This affects page load speed and rendering performance by controlling how flexbox utility classes are generated and applied, impacting CSS size and browser layout calculations.

Optimization Tips

1Only generate flexbox utility classes you actually use to keep CSS small.

2Use Sass maps and loops to control which classes are created.

3Minify CSS to reduce file size and speed up style calculation.

Performance Quiz - 3 Questions

What is a main performance drawback of generating all possible flexbox utility classes in CSS?

A Adds extra DOM nodes to the page

B Triggers JavaScript re-execution on load

C Increases CSS file size and slows style calculation

D Causes images to load slower

DevTools: Performance

How to check: Record a performance profile while loading the page, then inspect the 'Style Recalculation' and 'Layout' sections to see time spent parsing CSS and calculating layout.

What to look for: Look for long style recalculation times and layout durations indicating large CSS or complex layout calculations.

Practice

1. What is the main purpose of generating Flexbox utility classes using SASS?

easy

A. To disable Flexbox features in the browser

B. To write long CSS rules for each Flexbox property manually

C. To convert Flexbox layouts into grid layouts automatically

D. To create small reusable classes that quickly arrange items with Flexbox

Solution

1. Step 1: Understand Flexbox utility classes

   Flexbox utility classes are small CSS classes that help arrange items quickly using Flexbox properties.

2. Step 2: Role of SASS in generating these classes

   SASS mixins automate creating these reusable classes, saving time and keeping code neat.

3. Final Answer:

   To create small reusable classes that quickly arrange items with Flexbox -> Option D

4. Quick Check:

   Flexbox utility classes = reusable small classes [OK]

Hint: Think: reusable small classes for layout with Flexbox [OK]

Common Mistakes:

• Confusing utility classes with full component styles
• Thinking SASS disables Flexbox
• Assuming SASS converts Flexbox to grid automatically

2. Which SASS syntax correctly defines a mixin to generate a flex container with customizable direction?

easy

A. @mixin flex-container($direction) { display: flex; flex-direction: $direction; }

B. @function flex-container($direction) { display: flex; flex-direction: $direction; }

C. @include flex-container($direction) { display: flex; flex-direction: $direction; }

D. @extend flex-container($direction) { display: flex; flex-direction: $direction; }

Solution

1. Step 1: Identify correct SASS mixin syntax

   A mixin is defined with '@mixin name(parameters) { ... }'.

2. Step 2: Check options for correct usage

   @mixin flex-container($direction) { display: flex; flex-direction: $direction; } uses '@mixin' correctly; others use '@function', '@include', or '@extend' incorrectly for definition.

3. Final Answer:

   @mixin flex-container($direction) { display: flex; flex-direction: $direction; } -> Option A

4. Quick Check:

   Mixin definition uses '@mixin' [OK]

Hint: Define mixins with '@mixin', not '@function' or '@include' [OK]

Common Mistakes:

• Using '@function' instead of '@mixin' to define mixins
• Confusing '@include' (for using mixins) with defining them
• Trying to use '@extend' to create mixins

3. Given this SASS code, what CSS class will be generated for .flex-row-center?

@mixin flex-utility($direction, $justify) {
  display: flex;
  flex-direction: $direction;
  justify-content: $justify;
}

.flex-row-center {
  @include flex-utility(row, center);
}

medium

A. .flex-row-center { display: flex; flex-direction: row; justify-content: flex-start; }

B. .flex-row-center { display: block; flex-direction: row; justify-content: center; }

C. .flex-row-center { display: flex; flex-direction: row; justify-content: center; }

D. .flex-row-center { display: flex; flex-direction: column; justify-content: center; }

Solution

1. Step 1: Understand mixin parameters and usage

   The mixin sets display: flex, flex-direction, and justify-content from parameters.

2. Step 2: Substitute parameters for .flex-row-center

   Parameters are row and center, so flex-direction: row; justify-content: center.

3. Final Answer:

   .flex-row-center { display: flex; flex-direction: row; justify-content: center; } -> Option C

4. Quick Check:

   Parameters match CSS properties exactly [OK]

Hint: Match mixin parameters to CSS properties directly [OK]

Common Mistakes:

• Mixing up flex-direction values
• Forgetting display: flex
• Using wrong justify-content values

4. Identify the error in this SASS code for generating flex utility classes:

@mixin flex-align($align) {
  display: flex;
  align-items: $align
}

.flex-align-center {
  @include flex-align(center);
}

medium

A. Missing semicolon after 'align-items: $align' property

B. Incorrect mixin name 'flex-align' instead of 'flex-align-items'

C. Wrong property 'align-items' should be 'justify-content'

D. Mixin call '@include flex-align(center)' is invalid syntax

Solution

1. Step 1: Check CSS property syntax inside mixin

   CSS properties must end with a semicolon; here 'align-items: $align' misses it.

2. Step 2: Verify mixin usage and names

   Mixin name and call are correct; property name is valid for alignment.

3. Final Answer:

   Missing semicolon after 'align-items: $align' property -> Option A

4. Quick Check:

   CSS properties need semicolons [OK]

Hint: Always end CSS declarations with semicolons [OK]

Common Mistakes:

• Omitting semicolons after CSS properties
• Confusing align-items with justify-content
• Incorrect mixin call syntax

5. You want to generate utility classes for flex direction (row, column) and justify-content (start, center, end) using SASS loops. Which SASS code correctly creates classes like .flex-row-start and .flex-column-center?

hard

A. @mixin flex-utility($direction, $justify) { display: flex; flex-direction: $direction; justify-content: $justify; }

@for $i from 1 through 2 {
@for $j from 1 through 3 {
.flex-#{$i}-#{$j} {
@include flex-utility($i, $j);
}
}
}

B. @mixin flex-utility($direction, $justify) { display: flex; flex-direction: $direction; justify-content: $justify; }

@each $dir in (row, column) {
@each $just in (start, center, end) {
.flex-#{$dir}-#{$just} {
@include flex-utility($dir, $just);
}
}
}

C. @mixin flex-utility($direction, $justify) { display: flex; flex-direction: $direction; justify-content: $justify; }

@each $dir in (row, column) {
.flex-#{$dir} {
@include flex-utility($dir, center);
}
}

D. @mixin flex-utility($direction, $justify) { display: flex; flex-direction: $direction; justify-content: $justify; }

@each $just in (start, center, end) {
.flex-#{$just} {
@include flex-utility(row, $just);
}
}

Solution

1. Step 1: Understand the goal of generating combined classes

   We want classes combining direction and justify-content, e.g., .flex-row-start.

2. Step 2: Check each option for correct nested loops and class naming

   @mixin flex-utility($direction, $justify) { display: flex; flex-direction: $direction; justify-content: $justify; } @each $dir in (row, column) { @each $just in (start, center, end) { .flex-#{$dir}-#{$just} { @include flex-utility($dir, $just); } } } uses nested @each loops over directions and justifications, correctly generating combined class names and including the mixin with proper parameters.

3. Step 3: Identify why other options fail

   @mixin flex-utility($direction, $justify) { display: flex; flex-direction: $direction; justify-content: $justify; } @for $i from 1 through 2 { @for $j from 1 through 3 { .flex-#{$i}-#{$j} { @include flex-utility($i, $j); } } } uses numeric loops without mapping to direction names; C and D generate only partial combinations.

4. Final Answer:

   Nested @each loops generating .flex-#{$dir}-#{$just} classes -> Option B

5. Quick Check:

   Nested @each loops + interpolation = combined classes [OK]

Hint: Use nested @each loops with interpolation for combined classes [OK]

Common Mistakes:

• Using numeric loops without mapping to names
• Generating only partial class combinations
• Incorrect class name interpolation syntax