JIT mode and on-demand generation in Tailwind - Performance & Optimization

Performance: JIT mode and on-demand generation

HIGH IMPACT

This affects the CSS bundle size and page load speed by generating only the styles actually used in the HTML at build or runtime.

Generating CSS styles for a website

Tailwind

/* Tailwind JIT mode enabled in config */
module.exports = {
  mode: 'jit',
  purge: ['./src/**/*.{html,js}'],
  // other config
};

Generates only the CSS classes actually used in your HTML and JS files, drastically reducing CSS size.

📈 Performance GainReduces CSS bundle size by 70-90%, speeds up LCP by loading less CSS.

Generating CSS styles for a website

Tailwind

/* Tailwind classic mode: all styles generated upfront */
@tailwind base;
@tailwind components;
@tailwind utilities;

Generates the entire Tailwind CSS library, resulting in a large CSS file with many unused styles.

📉 Performance CostAdds 300-500kb to CSS bundle, blocking rendering longer and increasing LCP.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Classic Tailwind (all styles)	Low (CSS only)	1 (initial load)	High (large CSS paint)	[X] Bad
Tailwind JIT mode	Low (CSS only)	1 (initial load)	Low (small CSS paint)	[OK] Good

Rendering Pipeline

JIT mode reduces the CSS size that the browser must download and parse, speeding up style calculation and layout.

→Style Calculation

→Layout

→Paint

⚠️ BottleneckStyle Calculation due to large CSS files

Core Web Vital Affected

LCP

This affects the CSS bundle size and page load speed by generating only the styles actually used in the HTML at build or runtime.

Optimization Tips

1Use Tailwind JIT mode to generate only the CSS you use.

2Smaller CSS bundles improve page load speed and LCP.

3Avoid generating the full Tailwind CSS library if not needed.

Performance Quiz - 3 Questions

What is the main performance benefit of Tailwind's JIT mode?

A It disables CSS animations for faster rendering.

B It preloads all CSS classes to avoid delays.

C It generates only the CSS classes used, reducing CSS file size.

D It bundles CSS and JS into one file.

DevTools: Network

How to check: Open DevTools, go to Network tab, reload page, filter by CSS files, and check the size of the Tailwind CSS file.

What to look for: Smaller CSS file size indicates JIT mode is working; large CSS file means classic mode or unused styles.

Practice

1. What is the main benefit of Tailwind's JIT mode?

easy

A. It preloads all possible CSS classes to avoid delays.

B. It generates only the CSS classes you actually use, making the site faster.

C. It disables CSS generation to speed up development.

D. It automatically converts CSS to JavaScript.

Solution

1. Step 1: Understand JIT mode purpose

   JIT mode creates CSS only for classes used in your files, not all possible classes.

2. Step 2: Compare options

   It generates only the CSS classes you actually use, making the site faster. matches this behavior; others describe incorrect or unrelated features.

3. Final Answer:

   It generates only the CSS classes you actually use, making the site faster. -> Option B

4. Quick Check:

   JIT mode = on-demand CSS generation [OK]

Hint: JIT means generate CSS only when needed [OK]

Common Mistakes:

• Thinking JIT preloads all CSS
• Confusing JIT with disabling CSS
• Assuming JIT converts CSS to JS

2. Which Tailwind config snippet correctly enables JIT mode?

easy

A. module.exports = { mode: 'jit', paths: ['./src/**/*.{html,js}'] }

B. module.exports = { jit: true, files: ['./src/**/*.{html,js}'] }

C. module.exports = { mode: 'fast', content: ['./src/**/*.{html,js}'] }

D. module.exports = { mode: 'jit', content: ['./src/**/*.{html,js}'] }

Solution

1. Step 1: Identify correct config keys

   Tailwind uses mode: 'jit' and content array for files.

2. Step 2: Check options

   Only module.exports = { mode: 'jit', content: ['./src/**/*.{html,js}'] } uses correct keys and values; others use wrong keys or values.

3. Final Answer:

   module.exports = { mode: 'jit', content: ['./src/**/*.{html,js}'] } -> Option D

4. Quick Check:

   Config keys = mode and content [OK]

Hint: Use mode: 'jit' and content array in config [OK]

Common Mistakes:

• Using wrong keys like jit or files
• Setting mode to 'fast' instead of 'jit'
• Using 'paths' instead of 'content'

3. Given this Tailwind config with JIT mode:

module.exports = { mode: 'jit', content: ['./index.html'] }

And this HTML:

<div class="bg-blue-500 p-4">Hello</div>

What CSS classes will be generated?

medium

A. Only styles for bg-blue-500 and p-4 classes.

B. All background and padding classes from Tailwind.

C. No CSS classes because JIT is disabled.

D. Only bg-blue-500 class styles, not p-4.

Solution

1. Step 1: Understand JIT CSS generation

   JIT mode generates CSS only for classes found in the content files.

2. Step 2: Check classes in HTML

   Classes bg-blue-500 and p-4 appear, so their styles are generated.

3. Final Answer:

   Only styles for bg-blue-500 and p-4 classes. -> Option A

4. Quick Check:

   JIT generates CSS only for used classes [OK]

Hint: JIT generates CSS only for classes in your files [OK]

Common Mistakes:

• Thinking all classes generate CSS
• Assuming JIT disables CSS generation
• Believing partial classes generate partial CSS

4. You enabled JIT mode but your new CSS classes are not applying after editing HTML. What is the likely cause?

medium

A. JIT mode requires restarting the browser manually.

B. You forgot to install Tailwind CSS.

C. The content array in Tailwind config does not include the edited files.

D. Tailwind CSS does not support dynamic class names.

Solution

1. Step 1: Check JIT file watching setup

   JIT mode watches files listed in content to generate CSS on changes.

2. Step 2: Identify cause of missing CSS

   If edited files are not in content, JIT won't generate CSS for new classes.

3. Final Answer:

   The content array in Tailwind config does not include the edited files. -> Option C

4. Quick Check:

   Content array must include all source files [OK]

Hint: Always list all source files in content array [OK]

Common Mistakes:

• Forgetting to update content array
• Assuming JIT needs browser restart
• Thinking Tailwind lacks dynamic class support

5. You want to use a dynamic class name in your HTML like bg-${color}-500 where color is a variable. How can you ensure Tailwind JIT generates the correct CSS?

hard

A. Add all possible classes like bg-red-500, bg-blue-500 explicitly in your files or safelist in config.

B. JIT automatically detects dynamic class names and generates CSS for all variations.

C. Disable JIT mode to generate all CSS classes at once.

D. Use inline styles instead of Tailwind classes for dynamic colors.

Solution

1. Step 1: Understand JIT limitation with dynamic classes

   JIT cannot detect dynamic class names built from variables in code.

2. Step 2: Provide all possible classes explicitly

   You must list all possible class names in your files or use the safelist option in Tailwind config.

3. Final Answer:

   Add all possible classes like bg-red-500, bg-blue-500 explicitly in your files or safelist in config. -> Option A

4. Quick Check:

   Dynamic classes need explicit listing or safelist [OK]

Hint: List all dynamic classes or safelist them in config [OK]

Common Mistakes:

• Expecting JIT to detect dynamic classes automatically
• Disabling JIT unnecessarily
• Using inline styles instead of Tailwind classes