Content configuration for tree-shaking in Tailwind - Performance & Optimization

Performance: Content configuration for tree-shaking

HIGH IMPACT

This affects the final CSS bundle size and page load speed by removing unused styles.

Reducing CSS bundle size by removing unused Tailwind styles

Tailwind

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

Including all relevant files ensures Tailwind removes unused styles, shrinking CSS bundle.

📈 Performance Gainreduces CSS size by 50-80%, improves LCP by 200-500ms

Reducing CSS bundle size by removing unused Tailwind styles

Tailwind

module.exports = {
  content: ['./src/**/*.{js,jsx,ts,tsx}'],
  // missing some HTML or template files
  theme: { extend: {} },
  plugins: [],
};

Not including all files where Tailwind classes appear causes unused styles to remain, increasing bundle size.

📉 Performance Costadds 100-200kb extra CSS, blocks rendering longer, slows LCP

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Incomplete content config	N/A	N/A	High due to large CSS	[X] Bad
Complete content config	N/A	N/A	Low due to small CSS	[OK] Good

Rendering Pipeline

Tailwind's content configuration affects CSS generation before the browser renders. Smaller CSS means faster style calculation and paint.

→Style Calculation

→Layout

→Paint

⚠️ BottleneckStyle Calculation due to large CSS files

Core Web Vital Affected

LCP

This affects the final CSS bundle size and page load speed by removing unused styles.

Optimization Tips

1Always include all files where Tailwind classes appear in the content config.

2Missing files cause unused CSS to remain, increasing bundle size and slowing load.

3Smaller CSS bundles improve LCP by reducing style calculation and paint time.

Performance Quiz - 3 Questions

What happens if Tailwind's content configuration misses some files with CSS classes?

A JavaScript bundle size increases

B CSS bundle size decreases automatically

C Unused CSS stays in the bundle, increasing CSS size

D Browser ignores missing classes

DevTools: Network

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

What to look for: Smaller CSS file size indicates effective tree-shaking; large CSS means unused styles remain

Practice

1. What is the main purpose of the content configuration in Tailwind CSS?

easy

A. To tell Tailwind which files to scan for class names to include in the final CSS

B. To set the colors used in the Tailwind theme

C. To define custom animations in Tailwind

D. To specify the font sizes available in Tailwind

Solution

1. Step 1: Understand the role of content configuration

   The content setting tells Tailwind which files to look at for CSS class names.

2. Step 2: Identify the effect on CSS output

   By scanning these files, Tailwind can remove unused styles, making the CSS smaller and faster.

3. Final Answer:

   To tell Tailwind which files to scan for class names to include in the final CSS -> Option A

4. Quick Check:

   Content config = file paths for class scanning [OK]

Hint: Content config points to files Tailwind scans for classes [OK]

Common Mistakes:

• Confusing content with theme colors
• Thinking content sets animations or fonts
• Ignoring the importance of accurate file paths

2. Which of the following is the correct way to specify the content array in tailwind.config.js for scanning HTML and JS files in the src folder?

easy

A. content: ['./src/**/*.{html,js}']

B. content: './src/**/*.{html,js}'

C. content: ['./src/*.{html,js}']

D. content: ['./src/**/*.(html|js)']

Solution

1. Step 1: Understand the glob pattern syntax

   The pattern ./src/**/*.{html,js} means all files ending with .html or .js in any folder inside src.

2. Step 2: Check the array syntax

   The content property expects an array of strings, so it must be wrapped in [ ].

3. Final Answer:

   content: ['./src/**/*.{html,js}'] -> Option A

4. Quick Check:

   Array with glob pattern and braces = correct [OK]

Hint: Use array with glob and braces for multiple extensions [OK]

Common Mistakes:

• Forgetting the array brackets
• Using parentheses instead of braces in glob
• Missing the double asterisk for recursive search

3. Given this tailwind.config.js snippet:

module.exports = {
  content: ['./app/**/*.html'],
  theme: { extend: {} },
  plugins: [],
}

Which files will Tailwind scan for class names?

medium

A. Only HTML files directly inside the app folder

B. All HTML files inside the app folder and its subfolders

C. All files inside app folder with any extension

D. Only JavaScript files inside the app folder

Solution

1. Step 1: Analyze the glob pattern './app/**/*.html'

   The ** means any subfolder inside app, and *.html means all HTML files.

2. Step 2: Determine which files match

   So, Tailwind scans all HTML files in app and any nested folders.

3. Final Answer:

   All HTML files inside the app folder and its subfolders -> Option B

4. Quick Check:

   Double star + .html = all HTML recursively [OK]

Hint: Double star means recursive folders, *.html means HTML files [OK]

Common Mistakes:

• Thinking it scans only top-level files
• Assuming it scans all file types
• Confusing file extensions in pattern

4. You notice your Tailwind CSS file is very large and includes unused styles. Which of these is the most likely cause related to content configuration?

medium

A. You did not install the Tailwind plugin

B. You forgot to add @tailwind base; in your CSS

C. The content paths are missing or incorrect, so Tailwind scans no files

D. You used too many custom colors in the theme

Solution

1. Step 1: Understand tree-shaking in Tailwind

   Tailwind removes unused CSS by scanning files listed in content.

2. Step 2: Identify impact of wrong content paths

   If content is empty or wrong, Tailwind can't find used classes and keeps all styles.

3. Final Answer:

   The content paths are missing or incorrect, so Tailwind scans no files -> Option C

4. Quick Check:

   Wrong content paths = no tree-shaking [OK]

Hint: Check content paths if CSS is too big [OK]

Common Mistakes:

• Blaming CSS directives instead of content config
• Ignoring the importance of file paths
• Assuming plugins affect CSS size directly

5. You want to optimize your Tailwind CSS build by including only classes used in your React components inside src/components and your HTML files in public. Which content configuration is best?

hard

A. content: ['./src/**/*.{js,jsx,ts,tsx,html}', './public/**/*.{js,jsx}']

B. content: ['./src/components/*.js', './public/*.html']

C. content: ['./src/components/**/*', './public/**/*']

D. content: ['./src/components/**/*.{js,jsx,ts,tsx}', './public/**/*.html']

Solution

1. Step 1: Include all React component file types in src/components

   React components use extensions js, jsx, ts, tsx, so include these with a recursive glob.

2. Step 2: Include all HTML files in public folder recursively

   Use ./public/**/*.html to cover all HTML files in public and subfolders.

3. Step 3: Avoid overbroad or incomplete patterns

   content: ['./src/components/**/*.{js,jsx,ts,tsx}', './public/**/*.html'] precisely targets needed files without extra unrelated files.

4. Final Answer:

   content: ['./src/components/**/*.{js,jsx,ts,tsx}', './public/**/*.html'] -> Option D

5. Quick Check:

   Specific extensions + recursive glob = best practice [OK]

Hint: List exact file types and folders with recursive glob [OK]

Common Mistakes:

• Using too broad globs that include unused files
• Missing some React file extensions
• Not using recursive glob for nested files