Reducing compiled CSS size in SASS - Performance & Optimization

Performance: Reducing compiled CSS size

MEDIUM IMPACT

This affects page load speed by reducing CSS file size and parsing time, improving Largest Contentful Paint (LCP).

Writing CSS with Sass to style a website efficiently

SASS

$primary-color: #3498db;

.common-text {
  color: $primary-color;
}

.button, .card, .alert {
  @extend .common-text;
}

Using @extend shares common styles, reducing repeated CSS declarations and shrinking the compiled CSS size.

📈 Performance GainSaves kilobytes in CSS file size, reduces parsing time, and speeds up initial render.

Writing CSS with Sass to style a website efficiently

SASS

$primary-color: #3498db;

.button {
  color: $primary-color;
}

.card {
  color: $primary-color;
}

.alert {
  color: $primary-color;
}

Repeating the same property with the same value in multiple selectors generates redundant CSS rules, increasing file size.

📉 Performance CostAdds unnecessary kilobytes to CSS bundle, increasing load time and blocking rendering longer.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Repeated CSS properties	No extra DOM nodes	No extra reflows	Higher paint cost due to larger CSS	[X] Bad
Shared styles with @extend	No extra DOM nodes	No extra reflows	Lower paint cost due to smaller CSS	[OK] Good

Rendering Pipeline

Smaller CSS files reduce the time browser spends downloading, parsing, and applying styles, speeding up the critical rendering path.

→Network

→Style Calculation

→Layout

⚠️ BottleneckNetwork and Style Calculation stages are most impacted by large CSS files.

Core Web Vital Affected

LCP

This affects page load speed by reducing CSS file size and parsing time, improving Largest Contentful Paint (LCP).

Optimization Tips

1Avoid repeating identical CSS declarations across selectors.

2Use Sass @extend to share common styles and reduce duplication.

3Remove unused CSS to keep the compiled file small.

Performance Quiz - 3 Questions

How does reducing compiled CSS size affect page load?

A It increases the number of DOM nodes.

B It decreases CSS download and parsing time, improving load speed.

C It causes more layout reflows.

D It has no effect on performance.

DevTools: Network

How to check: Open DevTools, go to Network tab, reload page, filter by CSS files, and check file sizes and load times.

What to look for: Look for smaller CSS file sizes and faster load times indicating optimized compiled CSS.

Practice

1. Which of the following is the best way to reduce the size of compiled CSS when using Sass?

easy

A. Write very deep nesting of selectors for clarity

B. Use variables and mixins to avoid repeating the same styles

C. Add comments in Sass files to explain styles

D. Use many separate Sass files without combining them

Solution

1. Step 1: Understand Sass features for reuse

   Variables and mixins let you reuse style code instead of repeating it multiple times.

2. Step 2: Compare with other options

   Deep nesting creates many selectors increasing CSS size. Comments do not reduce CSS size. Many files without combining can increase HTTP requests.

3. Final Answer:

   Use variables and mixins to avoid repeating the same styles -> Option B

4. Quick Check:

   Reuse styles = smaller CSS [OK]

Hint: Reuse styles with variables and mixins to shrink CSS [OK]

Common Mistakes:

• Thinking deep nesting reduces CSS size
• Believing comments affect compiled CSS size
• Assuming splitting files always reduces size

2. Which Sass syntax correctly defines a mixin to reduce repeated styles?

easy

A. @function button-style() {\n padding: 1rem;\n border-radius: 0.5rem;\n}

B. @include button-style {\n padding: 1rem;\n border-radius: 0.5rem;\n}

C. @extend button-style {\n padding: 1rem;\n border-radius: 0.5rem;\n}

D. @mixin button-style {\n padding: 1rem;\n border-radius: 0.5rem;\n}

Solution

1. Step 1: Identify mixin syntax

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

2. Step 2: Differentiate from other directives

   @include is used to use a mixin, not define it. @function defines functions, not mixins. @extend is for inheritance, not mixin definition.

3. Final Answer:

   @mixin button-style { padding: 1rem; border-radius: 0.5rem; } -> Option D

4. Quick Check:

   Define mixin = @mixin [OK]

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

Common Mistakes:

• Confusing @include with @mixin for definition
• Using @function instead of @mixin
• Trying to define mixin with @extend

3. Given this Sass code, what will be the compiled CSS size impact?

$color: blue;

.button {
  color: $color;
  @include rounded-corners;
}

@mixin rounded-corners {
  border-radius: 0.5rem;
  border: 1px solid $color;
}

medium

A. The CSS will be larger because mixins duplicate code each use

B. The CSS will be smaller because styles are reused via mixin

C. The CSS will have syntax errors and not compile

D. The CSS will ignore the mixin and only use color

Solution

1. Step 1: Understand mixin behavior

   Mixins insert their styles wherever included, duplicating code each time.

2. Step 2: Analyze code impact

   Since @include rounded-corners adds border-radius and border styles inside .button, these styles are duplicated in CSS for each use.

3. Final Answer:

   The CSS will be larger because mixins duplicate code each use -> Option A

4. Quick Check:

   Mixins duplicate styles = larger CSS [OK]

Hint: Mixins duplicate styles; use carefully to reduce size [OK]

Common Mistakes:

• Assuming mixins always reduce CSS size
• Thinking variables reduce duplication inside mixins
• Believing mixins cause syntax errors here

4. This Sass code aims to reduce CSS size but causes unexpected large output. What is the error?

.card {
  .header {
    color: red;
    .title {
      font-weight: bold;
    }
  }
}

medium

A. Mixins are not included for repeated styles

B. Missing semicolons cause syntax errors

C. Nesting is too deep, creating many selectors increasing CSS size

D. Variables are not used for colors

Solution

1. Step 1: Examine nesting depth

   The code nests .header inside .card and .title inside .header, creating selectors like .card .header .title.

2. Step 2: Understand CSS size impact

   Deep nesting creates many combined selectors, increasing compiled CSS size and complexity.

3. Final Answer:

   Nesting is too deep, creating many selectors increasing CSS size -> Option C

4. Quick Check:

   Deep nesting = bigger CSS [OK]

Hint: Keep nesting shallow to avoid large CSS selectors [OK]

Common Mistakes:

• Ignoring nesting depth impact on CSS size
• Looking for syntax errors when none exist
• Thinking variables fix nesting issues

5. You want to reduce compiled CSS size by reusing button styles but avoid duplication from mixins. Which Sass feature helps achieve this best?

hard

A. Use @extend to share styles between selectors

B. Use deeply nested selectors for buttons

C. Use multiple mixins for each style property

D. Write all styles inline without variables

Solution

1. Step 1: Understand @extend behavior

   @extend shares selectors in compiled CSS, avoiding duplication by merging rules.

2. Step 2: Compare with mixins

   Mixins duplicate styles each use, increasing CSS size. @extend reuses styles without duplication.

3. Final Answer:

   Use @extend to share styles between selectors -> Option A

4. Quick Check:

   @extend shares styles, reduces CSS size [OK]

Hint: Use @extend to share styles without duplicating CSS [OK]

Common Mistakes:

• Using mixins expecting no duplication
• Nesting deeply to reuse styles
• Avoiding variables and mixins altogether