Purging unused styles in Tailwind - Performance & Optimization

Performance: Purging unused styles

HIGH IMPACT

This affects page load speed by reducing CSS file size and improves rendering speed by minimizing style calculations.

Reducing CSS bundle size for faster page load

Tailwind

/* Tailwind config with purge enabled */
module.exports = {
  content: ['./src/**/*.{html,js,jsx,ts,tsx}'],
  theme: {
    extend: {},
  },
  plugins: [],
};

Only includes styles used in specified files, drastically reducing CSS size.

📈 Performance GainSaves 150-250kb, reduces LCP by up to 1 second on slow networks.

Reducing CSS bundle size for faster page load

Tailwind

/* Tailwind config without purge */
module.exports = {
  content: [],
  theme: {
    extend: {},
  },
  plugins: [],
};

Includes all Tailwind styles even if unused, causing large CSS files.

📉 Performance CostAdds 200-300kb to CSS bundle, blocking rendering longer.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
No purge (full Tailwind CSS)	Low (unaffected)	Low	High (large CSS causes slower paint)	[X] Bad
Purge unused styles enabled	Low (unaffected)	Low	Low (smaller CSS speeds paint)	[OK] Good

Rendering Pipeline

Purging unused styles reduces CSS file size, which speeds up CSS parsing and style calculation stages, leading to faster layout and paint.

→CSS Parsing

→Style Calculation

→Layout

→Paint

⚠️ BottleneckCSS Parsing and Style Calculation

Core Web Vital Affected

LCP

This affects page load speed by reducing CSS file size and improves rendering speed by minimizing style calculations.

Optimization Tips

1Always specify correct content paths in Tailwind config for purging.

2Test CSS file size in DevTools Network panel after build.

3Smaller CSS files improve LCP and overall page speed.

Performance Quiz - 3 Questions

What is the main benefit of purging unused Tailwind CSS styles?

A Adds more styles for better design

B Increases JavaScript bundle size

C Reduces CSS file size to speed up page load

D Improves server response time

DevTools: Network

How to check: Open DevTools > Network tab > Reload page > Filter by CSS > Check CSS file size and load time.

What to look for: Smaller CSS file size and faster load time indicate effective purging.

Practice

1. What is the main purpose of purging unused styles in Tailwind CSS?

easy

A. To remove unused CSS classes and make the site load faster

B. To add more CSS classes automatically

C. To change the colors of the website

D. To create new HTML elements

Solution

1. Step 1: Understand what purging means

   Purging means removing things that are not needed. In Tailwind CSS, it removes unused styles.

2. Step 2: Know why removing unused styles helps

   Removing unused styles makes the CSS file smaller, so the website loads faster.

3. Final Answer:

   To remove unused CSS classes and make the site load faster -> Option A

4. Quick Check:

   Purging = Remove unused styles = Faster site [OK]

Hint: Purging means removing unused CSS to speed up loading [OK]

Common Mistakes:

• Thinking purging adds styles instead of removing
• Confusing purging with changing colors or layout
• Believing purging creates new HTML elements

2. Which Tailwind config option tells Tailwind where to look for used CSS classes to purge?

easy

A. theme

B. content

C. plugins

D. variants

Solution

1. Step 1: Identify the config option for purging

   The content option lists files where Tailwind looks for class names to keep.

2. Step 2: Understand other options

   theme controls design tokens, plugins add features, variants control responsive states, so they don't control purging.

3. Final Answer:

   content -> Option B

4. Quick Check:

   content = files to scan for classes [OK]

Hint: Remember: content = where Tailwind looks for classes [OK]

Common Mistakes:

• Choosing theme instead of content
• Confusing plugins with purging config
• Using variants option wrongly

3. Given this Tailwind config snippet:

{
  content: ['./src/**/*.html'],
  theme: { extend: {} },
  plugins: []
}

Which files will Tailwind scan to keep CSS classes?

medium

A. All files in src folder and subfolders with .html extension

B. Only files named index.html in src folder

C. All JavaScript files in src folder

D. No files will be scanned

Solution

1. Step 1: Understand the glob pattern './src/**/*.html'

   This pattern means all .html files inside src and any subfolders.

2. Step 2: Match options with pattern meaning

   All files in src folder and subfolders with .html extension matches the pattern exactly. Options B and C are too narrow or wrong file types. No files will be scanned is incorrect.

3. Final Answer:

   All files in src folder and subfolders with .html extension -> Option A

4. Quick Check:

   ./src/**/*.html = all .html files in src and subfolders [OK]

Hint: ** means any folder depth, *.html means all HTML files [OK]

Common Mistakes:

• Thinking only top-level files are scanned
• Confusing file extensions scanned
• Assuming no files scanned without explicit mention

4. You set the content option incorrectly as ['./src/*.js'] but your classes are in HTML files inside subfolders. What problem will occur?

medium

A. Tailwind will include all styles correctly

B. Tailwind will generate duplicate CSS classes

C. Tailwind will throw a syntax error

D. Tailwind will purge needed styles causing missing styles on the site

Solution

1. Step 1: Analyze the content pattern './src/*.js'

   This pattern only scans JavaScript files directly inside src folder, not HTML or subfolders.

2. Step 2: Understand impact on purging

   Since HTML files with classes are not scanned, Tailwind thinks those classes are unused and removes them, causing missing styles.

3. Final Answer:

   Tailwind will purge needed styles causing missing styles on the site -> Option D

4. Quick Check:

   Wrong content path = missing styles after purge [OK]

Hint: Content must match all files with classes to avoid missing styles [OK]

Common Mistakes:

• Expecting Tailwind to scan files not listed
• Thinking wrong content causes errors instead of missing styles
• Assuming duplicate CSS classes will be generated

5. You want to purge unused styles but keep some dynamic classes added by JavaScript like bg-red-500 and text-xl. How can you ensure these classes are not removed?

hard

A. Write these classes directly in your HTML files only

B. Remove the content option entirely

C. Add these classes to the safelist option in Tailwind config

D. Use a plugin to disable purging

Solution

1. Step 1: Understand dynamic classes and purging

   Classes added by JavaScript are not in HTML files, so Tailwind may remove them during purge.

2. Step 2: Use safelist option to keep classes

   The safelist option lets you list classes to always keep, even if not found in scanned files.

3. Final Answer:

   Add these classes to the safelist option in Tailwind config -> Option C

4. Quick Check:

   Safelist = keep dynamic classes safe from purge [OK]

Hint: Use safelist to protect dynamic classes from purging [OK]

Common Mistakes:

• Removing content option disables purging but is not recommended
• Assuming writing classes in HTML fixes dynamic JS classes
• Thinking disabling purging plugin is best solution