Variable declaration with $ in SASS - Performance & Optimization

Performance: Variable declaration with $

LOW IMPACT

This affects CSS compilation speed and final CSS file size, impacting page load speed.

Defining and reusing colors in styles

SASS

$primary-color: #3498db;

.button {
  background-color: $primary-color;
  border: 1px solid $primary-color;
}

Using the variable reduces repetition and keeps CSS smaller and easier to update.

📈 Performance GainSmaller CSS file size reduces network load and speeds up LCP.

Defining and reusing colors in styles

SASS

$primary-color: #3498db;

.button {
  background-color: #3498db;
  border: 1px solid #3498db;
}

Repeating the same color value instead of using the variable causes harder maintenance and larger CSS output.

📉 Performance CostIncreases CSS file size slightly, which can delay LCP by a few milliseconds on slow networks.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Using repeated color literals	0	0	Slightly higher due to larger CSS	[X] Bad
Using $ variables for colors	0	0	Smaller CSS size, no runtime cost	[OK] Good

Rendering Pipeline

Sass variables are resolved during CSS compilation before the browser receives the CSS. This means no runtime cost in the browser rendering pipeline.

→CSS Compilation

⚠️ BottleneckNone in browser rendering; compilation time can increase slightly with many variables.

Core Web Vital Affected

LCP

This affects CSS compilation speed and final CSS file size, impacting page load speed.

Optimization Tips

1Sass variables with $ are replaced at compile time, so they don't affect runtime rendering.

2Using variables reduces CSS repetition and file size, improving load speed.

3Avoid redefining variables unnecessarily to keep compilation fast.

Performance Quiz - 3 Questions

How does using $ variables in Sass affect browser rendering performance?

A It increases paint cost because variables add extra CSS rules.

B It has no direct impact on browser rendering since variables are compiled away.

C It causes more reflows because variables change dynamically in the browser.

D It blocks rendering because variables delay CSS loading.

DevTools: Network

How to check: Open DevTools, go to Network tab, reload page, and check CSS file size and load time.

What to look for: Smaller CSS files load faster, improving LCP.

Practice

1. What symbol is used to declare a variable in Sass?

easy

A. $

B. #

C. @

D. %

Solution

1. Step 1: Recall Sass variable syntax

   In Sass, variables always start with the $ symbol to distinguish them from other values.

2. Step 2: Identify the correct symbol

   Among the options, only $ is used for variables in Sass.

3. Final Answer:

   $ -> Option A

4. Quick Check:

   Variables start with $ in Sass [OK]

Hint: Remember: Sass variables always begin with $ [OK]

Common Mistakes:

• Using # or @ instead of $ for variables
• Confusing CSS IDs (#) with Sass variables
• Omitting the $ symbol before variable names

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

easy

A. main-color: $3498db;

B. $main-color: #3498db;

C. $main-color = #3498db;

D. @main-color: #3498db;

Solution

1. Step 1: Check variable declaration syntax

   Sass variables start with $, followed by the name, a colon, then the value, ending with a semicolon.

2. Step 2: Compare options

   $main-color: #3498db; matches the correct syntax: $main-color: #3498db;. Others use wrong symbols or order.

3. Final Answer:

   $main-color: #3498db; -> Option B

4. Quick Check:

   Variable declaration uses $name: value; [OK]

Hint: Use $name: value; to declare variables in Sass [OK]

Common Mistakes:

• Using = instead of : to assign values
• Placing $ after the variable name
• Using @ instead of $ for variables

3. What will be the background color of the button in this Sass code?

$btn-bg: #ff0000;
button {
  background-color: $btn-bg;
}

medium

A. Blue

B. Green

C. Red

D. No color (default)

Solution

1. Step 1: Identify the variable value

   The variable $btn-bg is assigned the color #ff0000, which is red.

2. Step 2: Check usage in button style

   The button's background-color uses $btn-bg, so it will be red.

3. Final Answer:

   Red -> Option C

4. Quick Check:

   $btn-bg = #ff0000 (red) [OK]

Hint: Match variable value to color code to find output [OK]

Common Mistakes:

• Confusing hex color codes with color names
• Forgetting to use $ before variable name
• Assuming default color if variable is used

4. Identify the error in this Sass variable declaration:

$font-size 16px;

medium

A. Variable name should not start with $

B. Semicolon is missing at the end

C. Value should be in quotes

D. Missing colon between variable name and value

Solution

1. Step 1: Review correct variable syntax

   Sass variables require a colon : between the name and value, like $font-size: 16px;.

2. Step 2: Identify missing colon

   The code misses the colon, causing a syntax error.

3. Final Answer:

   Missing colon between variable name and value -> Option D

4. Quick Check:

   Variable declaration needs colon : [OK]

Hint: Check for colon : after variable name [OK]

Common Mistakes:

• Omitting colon between name and value
• Using = instead of :
• Forgetting semicolon at end (less critical)

5. You want to create a Sass variable for spacing that changes based on screen size. Which is the best way to declare and use it?

$spacing: 1rem;

@media (min-width: 600px) {
  $spacing: 2rem;
}

.container {
  padding: $spacing;
}

hard

A. Variables cannot be redefined inside media queries

B. This works; $spacing changes inside media query

C. Use !default to change variable inside media query

D. Declare two variables and use @if to switch

Solution

1. Step 1: Understand Sass variable scope

   Sass variables are static and cannot change inside media queries because media queries are CSS rules, not Sass logic blocks.

2. Step 2: Evaluate the code behavior

   Redefining $spacing inside @media does not work; Sass processes variables before CSS is generated.

3. Step 3: Correct approach

   To handle responsive spacing, declare separate variables or use mixins/functions with media queries.

4. Final Answer:

   Variables cannot be redefined inside media queries -> Option A

5. Quick Check:

   Sass variables are static, not dynamic in media queries [OK]

Hint: Sass variables are static; media queries can't change them [OK]

Common Mistakes:

• Trying to redefine variables inside media queries
• Assuming Sass variables behave like CSS custom properties
• Not using separate variables or mixins for responsiveness