Why design systems need SASS - Performance Evidence

Performance: Why design systems need SASS

MEDIUM IMPACT

Using SASS in design systems affects CSS bundle size and rendering speed by enabling reusable styles and reducing duplication.

Managing consistent colors and spacing in a design system

SASS

$primary-color: #0055ff;
$spacing: 0.625rem 1.25rem;

.button {
  background-color: $primary-color;
  padding: $spacing;
}
.card {
  border-color: $primary-color;
  margin: $spacing;
}

Using variables reduces repeated values, shrinking CSS size and speeding up style calculation.

📈 Performance GainSaves several KB in CSS size and reduces style recalculation time.

Managing consistent colors and spacing in a design system

SASS

.button {
  background-color: #0055ff;
  padding: 10px 20px;
}
.card {
  border-color: #0055ff;
  margin: 10px 20px;
}

Repeating the same color and spacing values everywhere causes large CSS files and makes updates slow and error-prone.

📉 Performance CostAdds unnecessary CSS size, increasing bundle by several KB and slowing LCP.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Repeated raw CSS values	Low	Low	Medium (due to larger CSS)	[X] Bad
SASS variables and mixins	Low	Low	Low (smaller CSS)	[OK] Good

Rendering Pipeline

SASS compiles to CSS before the browser loads the page, so it reduces CSS file size and complexity, which speeds up style calculation and layout.

→Style Calculation

→Layout

⚠️ BottleneckStyle Calculation due to large or repetitive CSS

Core Web Vital Affected

LCP

Using SASS in design systems affects CSS bundle size and rendering speed by enabling reusable styles and reducing duplication.

Optimization Tips

1Use SASS variables to avoid repeating CSS values.

2Leverage mixins and nesting to keep CSS concise.

3Smaller CSS files improve Largest Contentful Paint (LCP).

Performance Quiz - 3 Questions

How does using SASS variables in a design system improve performance?

A By reducing CSS file size through reuse of values

B By increasing the number of CSS files loaded

C By adding more JavaScript to the page

D By delaying CSS loading until user interaction

DevTools: Network

How to check: Open DevTools, go to Network tab, filter by CSS files, and check the size of your CSS bundle before and after using SASS.

What to look for: Look for smaller CSS file size and faster CSS load time indicating better performance.

Practice

1. Why do design systems benefit from using SASS?

easy

A. Because SASS allows reuse of styles with variables and mixins

B. Because SASS automatically creates images for design systems

C. Because SASS replaces HTML in design systems

D. Because SASS is a programming language for backend servers

Solution

1. Step 1: Understand SASS features

   SASS provides variables, mixins, and extends to reuse styles easily.

2. Step 2: Connect features to design systems

   Design systems need consistent styles and easy updates, which SASS helps with.

3. Final Answer:

   Because SASS allows reuse of styles with variables and mixins -> Option A

4. Quick Check:

   Reuse and consistency = A [OK]

Hint: Think about style reuse and consistency in design systems [OK]

Common Mistakes:

• Confusing SASS with image or backend tools
• Thinking SASS replaces HTML
• Ignoring the role of variables and mixins

2. Which of the following is the correct way to declare a variable in SASS?

easy

A. $primary-color: #3498db;

B. var primary-color = #3498db;

C. primary-color: #3498db;

D. #primary-color = #3498db;

Solution

1. Step 1: Recall SASS variable syntax

   SASS variables start with a dollar sign ($) followed by the name and value.

2. Step 2: Check each option

   Only $primary-color: #3498db; uses the correct syntax: $primary-color: #3498db;.

3. Final Answer:

   $primary-color: #3498db; -> Option A

4. Quick Check:

   SASS variables start with $ = A [OK]

Hint: Remember SASS variables always start with $ [OK]

Common Mistakes:

• Using JavaScript or CSS variable syntax
• Omitting the $ sign
• Using incorrect assignment symbols

3. Given the SASS code:

$base-color: #333;
@mixin button-style {
  background-color: $base-color;
  border-radius: 0.5rem;
}
.button {
  @include button-style;
  color: white;
}

What will be the background color of the .button class in the compiled CSS?

medium

A. transparent

B. white

C. #333

D. 0.5rem

Solution

1. Step 1: Understand the mixin usage

   The mixin button-style sets background-color to $base-color, which is #333.

2. Step 2: Check the included styles in .button

   The .button class includes the mixin, so its background color is #333.

3. Final Answer:

   #333 -> Option C

4. Quick Check:

   Mixin sets background-color = #333 [OK]

Hint: Look where variables are used inside mixins [OK]

Common Mistakes:

• Confusing text color with background color
• Ignoring mixin inclusion
• Thinking border-radius affects color

4. Identify the error in this SASS code snippet used in a design system:

$font-size: 1.2rem
.title {
  font-size: $font-size;
}

medium

A. Incorrect variable name syntax

B. Mixin not included

C. Wrong property name font-size

D. Missing semicolon after variable declaration

Solution

1. Step 1: Check variable declaration syntax

   SASS variables must end with a semicolon (;). The code misses it after $font-size: 1.2rem.

2. Step 2: Verify other parts

   Variable name and property are correct; no mixin is needed here.

3. Final Answer:

   Missing semicolon after variable declaration -> Option D

4. Quick Check:

   Semicolon missing = B [OK]

Hint: Always end SASS variable lines with a semicolon [OK]

Common Mistakes:

• Forgetting semicolons after variables
• Confusing variable syntax with CSS
• Assuming mixins are always required

5. In a large design system, how does using SASS variables and mixins help when the primary brand color changes?

hard

A. You need to rewrite all mixins to reflect the new color

B. You only update the color in one place, and all styles update automatically

C. SASS automatically detects brand changes without code updates

D. You must manually change the color in every CSS file

Solution

1. Step 1: Understand variable role in design systems

   SASS variables store values like colors in one place for easy updates.

2. Step 2: Apply to brand color change scenario

   Changing the variable updates all styles using it, avoiding manual edits everywhere.

3. Final Answer:

   You only update the color in one place, and all styles update automatically -> Option B

4. Quick Check:

   Single source update = D [OK]

Hint: Change variables once to update all related styles [OK]

Common Mistakes:

• Thinking manual changes are needed everywhere
• Believing SASS auto-detects brand changes
• Assuming mixins must be rewritten