Naming conventions in CSS - Performance & Optimization

Performance: Naming conventions

MEDIUM IMPACT

Naming conventions affect CSS selector performance and maintainability, impacting how quickly browsers match styles to elements.

Writing CSS selectors for styling elements

CSS

.nav-link:hover { color: red; }

Flat, single-class selectors reduce the number of elements the browser must check.

📈 Performance Gainsingle selector match per element, faster style application

Writing CSS selectors for styling elements

CSS

.header .nav ul li a:hover { color: red; }

Deep descendant selectors force the browser to check many elements, increasing selector matching time.

📉 Performance Costtriggers multiple selector matching steps per element, slowing rendering

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Deep descendant selectors (.header .nav ul li a:hover)	High (many elements checked)	0	Low	[X] Bad
Flat class selectors (.nav-link:hover)	Low (direct match)	0	Low	[OK] Good

Rendering Pipeline

CSS selectors are matched during Style Calculation. Complex selectors increase the time to find matching elements, delaying layout and paint.

→Style Calculation

→Layout

→Paint

⚠️ BottleneckStyle Calculation due to complex selector matching

Optimization Tips

1Use flat, single-class selectors instead of deep descendant selectors.

2Avoid universal (*) and attribute selectors when possible for performance.

3Adopt consistent naming conventions to keep selectors simple and predictable.

Performance Quiz - 3 Questions

Which CSS selector pattern is generally faster for browsers to match?

A Universal selectors like *

B Deep descendant selectors like .header nav ul li a

C Flat class selectors like .button

D Attribute selectors like [type='text']

DevTools: Performance

How to check: Record a performance profile while loading the page and inspect the Style Calculation phase to see selector matching times.

What to look for: Look for long Style Calculation times or high selector matching costs indicating complex selectors.

Practice

1. Which of the following is the best practice for naming CSS classes?

easy

A. Use camelCase, like mainHeader.

B. Use uppercase letters and underscores, like Main_Header.

C. Use lowercase letters and hyphens to separate words, like main-header.

D. Use spaces between words, like main header.

Solution

1. Step 1: Understand common CSS naming styles

   CSS classes should be easy to read and consistent. Lowercase with hyphens is widely accepted.

2. Step 2: Compare options

   Use lowercase letters and hyphens to separate words, like main-header. uses lowercase and hyphens, which is recommended. Options B and C use uppercase or camelCase, less common in CSS. Use spaces between words, like main header. uses spaces, which is invalid in class names.

3. Final Answer:

   Use lowercase letters and hyphens to separate words, like main-header. -> Option C

4. Quick Check:

   Lowercase + hyphens = best CSS naming [OK]

Hint: Use lowercase and hyphens for CSS classes [OK]

Common Mistakes:

• Using spaces in class names
• Using uppercase letters
• Using camelCase instead of hyphens

2. Which CSS class name follows the BEM naming convention?

easy

A. button--primary

B. button_primary

C. buttonPrimary

D. button primary

Solution

1. Step 1: Recall BEM naming rules

   BEM uses block__element--modifier format. Double hyphens separate modifiers.

2. Step 2: Identify correct format

   button--primary uses double hyphens for modifier --primary, matching BEM. Options A and B use camelCase or underscores, not BEM. button primary uses space, invalid in class names.

3. Final Answer:

   button--primary -> Option A

4. Quick Check:

   BEM modifier uses double hyphens [OK]

Hint: BEM modifiers use double hyphens (--modifier) [OK]

Common Mistakes:

• Using underscores instead of hyphens
• Using camelCase for BEM
• Using spaces in class names

3. Given this CSS class name: card__title--large, what does it represent in BEM?

medium

A. Block: card, Modifier: title, Element: large

B. Modifier: card, Block: title, Element: large

C. Element: card, Block: title, Modifier: large

D. Block: card, Element: title, Modifier: large

Solution

1. Step 1: Break down the BEM parts

   In card__title--large, card is the block, title is the element (after double underscore), and large is the modifier (after double hyphen).

2. Step 2: Match parts to options

   Block: card, Element: title, Modifier: large correctly identifies block, element, and modifier. Other options mix these parts incorrectly.

3. Final Answer:

   Block: card, Element: title, Modifier: large -> Option D

4. Quick Check:

   BEM = block__element--modifier [OK]

Hint: BEM: block__element--modifier order [OK]

Common Mistakes:

• Confusing element and modifier positions
• Mixing block and element names
• Ignoring double underscores and hyphens

4. Identify the error in this CSS class name: nav__item_active

medium

A. Class name is too long

B. Underscore used instead of double hyphen for modifier

C. Spaces are used instead of underscores

D. Double underscore missing between block and element

Solution

1. Step 1: Check BEM syntax

   BEM requires modifiers to be separated by double hyphens --, not underscores.

2. Step 2: Analyze the class name

   The class nav__item_active uses a single underscore for the modifier, which is incorrect. It should be nav__item--active.

3. Final Answer:

   Underscore used instead of double hyphen for modifier -> Option B

4. Quick Check:

   Modifier separator = double hyphen [OK]

Hint: Modifiers need double hyphens, not underscores [OK]

Common Mistakes:

• Using single underscore for modifiers
• Forgetting double underscore between block and element
• Using spaces in class names

5. You want to create CSS classes for a card component with a title and a highlighted state using BEM. Which naming set is correct?

hard

A. card, card__title, card--highlighted

B. card, card_title, card_highlighted

C. card, card-title, card-highlighted

D. card, card__title--highlighted, card__highlighted

Solution

1. Step 1: Understand BEM structure for blocks, elements, and modifiers

   Block is card. Element is card__title. Modifier on block is card--highlighted.

2. Step 2: Evaluate options

   card, card__title, card--highlighted correctly uses BEM naming. card, card_title, card_highlighted uses underscores, not BEM. card, card-title, card-highlighted uses hyphens but not BEM format. card, card__title--highlighted, card__highlighted incorrectly applies modifier to element and duplicates modifier.

3. Final Answer:

   card, card__title, card--highlighted -> Option A

4. Quick Check:

   BEM block, element, modifier naming [OK]

Hint: BEM: block, block__element, block--modifier [OK]

Common Mistakes:

• Using underscores instead of BEM separators
• Applying modifiers to elements incorrectly
• Mixing hyphen and underscore styles