Hidden and visibility control in Tailwind - Performance & Optimization

Performance: Hidden and visibility control

MEDIUM IMPACT

Controls how elements appear or disappear on the page, affecting rendering and layout stability.

Hiding elements without causing layout shifts

Tailwind

<div class="invisible">Content</div>

Keeps element in layout but hides it visually, preventing layout shifts.

📈 Performance GainNo reflow triggered, reduces CLS impact

Hiding elements without causing layout shifts

Tailwind

<div class="hidden">Content</div>

Using 'hidden' removes the element from layout, causing reflow and layout shifts.

📉 Performance CostTriggers 1 reflow and can cause CLS if layout changes visibly

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
hidden (display:none)	Element removed from layout	Triggers 1 reflow	Paint cost reduced (not painted)	[X] Bad
invisible (visibility:hidden)	Element remains in layout	No reflow	Paint cost for invisible element	[OK] Good

Rendering Pipeline

Visibility control affects the Layout and Paint stages by changing element presence or visibility, impacting reflows and repaints.

→Layout

→Paint

→Composite

⚠️ BottleneckLayout (reflow) when elements are removed or added

Core Web Vital Affected

CLS

Controls how elements appear or disappear on the page, affecting rendering and layout stability.

Optimization Tips

1Avoid using 'hidden' if you want to prevent layout shifts.

2Use 'invisible' to hide elements while preserving layout space.

3Use 'sr-only' for accessibility without visual impact or layout changes.

Performance Quiz - 3 Questions

Which Tailwind class hides an element without causing layout shifts?

A hidden

B invisible

C opacity-0

D sr-only

DevTools: Performance

How to check: Record a performance profile while toggling visibility classes; look for layout shifts and reflows in the summary.

What to look for: Check for Layout events and CLS score spikes indicating layout shifts caused by hiding/showing elements.

Practice

1. What does the Tailwind CSS class hidden do to an element?

easy

A. It changes the element's color to transparent.

B. It hides the element and removes its space from the layout.

C. It makes the element semi-transparent.

D. It hides the element but keeps its space in the layout.

Solution

1. Step 1: Understand the hidden class effect

   The hidden class in Tailwind CSS sets display: none;, which hides the element completely.

2. Step 2: Effect on layout space

   Because the element is removed from the layout flow, its space is also removed, so no empty gap remains.

3. Final Answer:

   It hides the element and removes its space from the layout. -> Option B

4. Quick Check:

   hidden = hides + removes space [OK]

Hint: Hidden removes element and space; invisible hides but keeps space [OK]

Common Mistakes:

• Thinking hidden keeps space like invisible
• Confusing hidden with opacity or visibility
• Assuming hidden only makes element transparent

2. Which Tailwind CSS class hides an element but keeps its space reserved in the layout?

easy

A. hidden

B. opacity-0

C. sr-only

D. invisible

Solution

1. Step 1: Identify the class that hides but keeps space

   The invisible class sets visibility: hidden;, which hides the element but keeps its space.

2. Step 2: Compare with other options

   hidden removes element and space, opacity-0 makes element transparent but still interactive, sr-only hides visually but accessible to screen readers.

3. Final Answer:

   invisible -> Option D

4. Quick Check:

   invisible = hide but keep space [OK]

Hint: Invisible hides but reserves space; hidden removes space [OK]

Common Mistakes:

• Choosing hidden instead of invisible
• Confusing opacity-0 with invisible
• Thinking sr-only hides visually and removes space

3. What will be the visible result of this HTML snippet with Tailwind classes?

<div class="w-24 h-24 bg-blue-500 hidden">Box</div>
<div class="w-24 h-24 bg-red-500 invisible">Box</div>

medium

A. Only the red box space is reserved but not visible; blue box is hidden and removed.

B. No boxes visible; both hidden and invisible hide elements.

C. Only the red box is visible but transparent.

D. Both boxes visible but blue is hidden behind red.

Solution

1. Step 1: Analyze the blue box with hidden

   The blue box has hidden, so it is not visible and its space is removed from layout.

2. Step 2: Analyze the red box with invisible

   The red box is invisible, so it is hidden but its space remains reserved in the layout, leaving an empty gap.

3. Final Answer:

   Only the red box space is reserved but not visible; blue box is hidden and removed. -> Option A

4. Quick Check:

   hidden removes element; invisible hides but keeps space [OK]

Hint: Hidden removes element; invisible keeps space but hides content [OK]

Common Mistakes:

• Thinking invisible shows a transparent box
• Assuming hidden keeps space
• Believing both boxes are visible

4. You want to hide a button visually but keep it accessible for screen readers. Which Tailwind class should you use?

medium

A. sr-only

B. invisible

C. hidden

D. opacity-0

Solution

1. Step 1: Understand accessibility needs

   To hide visually but keep accessible, the element must be off-screen but still in the accessibility tree.

2. Step 2: Identify the correct Tailwind class

   sr-only hides the element visually but keeps it readable by screen readers, unlike hidden or invisible.

3. Final Answer:

   sr-only -> Option A

4. Quick Check:

   sr-only = hide visually, keep screen reader access [OK]

Hint: Use sr-only to hide visually but keep screen reader access [OK]

Common Mistakes:

• Using hidden which removes from accessibility tree
• Using invisible which hides visually but not accessible
• Using opacity-0 which hides visually but still interactive

5. You have a navigation menu that should be hidden on mobile but visible on larger screens. Which Tailwind classes correctly hide the menu on small screens but show it on medium and above?

hard

A. block md:hidden

B. invisible md:hidden

C. hidden md:block

D. hidden md:hidden

Solution

1. Step 1: Understand responsive classes

   hidden hides element by default (mobile), md:block shows element as block on medium screens and larger.

2. Step 2: Check other options

   invisible md:hidden hides but keeps space on mobile and hides on medium, so menu never visible. block md:hidden shows on mobile but hides on medium, opposite of requirement. hidden md:hidden hides always.

3. Final Answer:

   hidden md:block -> Option C

4. Quick Check:

   Hide mobile, show medium+ = hidden md:block [OK]

Hint: Use hidden for mobile, md:block to show on medium screens [OK]

Common Mistakes:

• Using md:hidden hides on medium screens instead of showing
• Using invisible which keeps space and confuses layout
• Using hidden md:hidden hides always