Extracting critical CSS in Tailwind - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

What is the main purpose of extracting critical CSS in a Tailwind CSS project?

Why do developers extract critical CSS when using Tailwind CSS in their web projects?

A To load only the CSS needed for above-the-fold content, improving page load speed.

B To remove all unused CSS classes from the Tailwind library permanently.

C To convert Tailwind CSS classes into inline styles for every HTML element.

D To bundle all Tailwind CSS styles into a single large CSS file for caching.

💡 Hint

Think about what 'critical' means in the context of page loading.

Extracting critical CSS means isolating the styles needed to render the visible part of the page first. This helps the browser show content faster, improving user experience.

📝 Syntax

intermediate

Which Tailwind CSS configuration snippet correctly enables purging unused styles for production?

Select the correct Tailwind CSS config code that removes unused CSS classes during production builds.

Tailwind

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

A

module.exports = {
  purge: ['./src/**/*.{html,js}'],
  theme: { extend: {} },
  plugins: [],
}

B

module.exports = {
  content: ['./src/**/*.{css,scss}'],
  theme: { extend: {} },
  plugins: [],
}

C

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

D

module.exports = {
  purge: false,
  theme: { extend: {} },
  plugins: [],
}

💡 Hint

Look for the modern property name used to specify files for purging.

In Tailwind CSS v3+, the content key replaces purge to specify files to scan for used classes. This enables removing unused styles.

❓ rendering

advanced

What will be the visible effect of extracting critical CSS on a slow network?

Imagine a webpage styled with Tailwind CSS where critical CSS is extracted and inlined in the HTML. What will the user see first on a slow network?

A The page shows a blank white screen until all CSS files finish loading.

B The entire page appears unstyled until the full CSS file downloads.

C Only text content appears with default browser styles, no colors or layout.

D The above-the-fold content styled correctly appears quickly, while other styles load later.

💡 Hint

Think about what 'critical CSS' means for initial rendering.

Inlining critical CSS means the browser can style the visible part of the page immediately, improving perceived load speed on slow connections.

❓ selector

advanced

Which CSS selector targets only the critical CSS classes extracted for above-the-fold content?

Given that critical CSS classes are prefixed with critical-, which selector matches only those classes?

A [class^='critical-']

B .critical-

C [class*='critical']

D .critical *

💡 Hint

Look for a selector that matches class names starting with a specific string.

The attribute selector [class^='critical-'] matches elements whose class attribute starts exactly with 'critical-'.

❓ accessibility

expert

How does extracting critical CSS affect accessibility during page load?

When critical CSS is extracted and inlined, what accessibility benefit does this provide to users relying on screen readers or keyboard navigation?

A It hides non-critical content from screen readers until full CSS loads.

B It ensures content is visually styled and structured immediately, helping screen readers interpret layout faster.

C It disables all animations to avoid distractions for keyboard users.

D It automatically adds ARIA labels to all elements during initial load.

💡 Hint

Think about how faster visual rendering helps assistive technologies.

Critical CSS makes the page visually complete faster, so screen readers and keyboard users get a meaningful layout and content structure sooner.

Practice

1. What is the main purpose of extracting critical CSS in a Tailwind project?

easy

A. To increase the size of the CSS file

B. To add more colors to the website

C. To disable all animations on the page

D. To load only the CSS needed for the visible part of the page first

Solution

1. Step 1: Understand what critical CSS means

   Critical CSS means the styles needed to show the visible part of the page immediately.

2. Step 2: Identify the benefit of extracting critical CSS

   Extracting critical CSS helps load only these important styles first, speeding up page load.

3. Final Answer:

   To load only the CSS needed for the visible part of the page first -> Option D

4. Quick Check:

   Critical CSS = Load visible styles first [OK]

Hint: Critical CSS loads visible styles first to speed up page [OK]

Common Mistakes:

• Thinking it adds more styles instead of reducing initial load
• Confusing critical CSS with full CSS bundle
• Believing it disables animations

2. Which Tailwind CLI flag is used to extract critical CSS automatically?

easy

A. --extract-critical

B. --critical-css

C. --extract-css

D. --critical-extract

Solution

1. Step 1: Recall the Tailwind CLI flag for critical CSS extraction

   The correct flag is --extract-critical as per Tailwind documentation.

2. Step 2: Compare with other options

   Other options are incorrect or do not exist in Tailwind CLI.

3. Final Answer:

   --extract-critical -> Option A

4. Quick Check:

   Flag for critical CSS = --extract-critical [OK]

Hint: Remember the exact flag: --extract-critical [OK]

Common Mistakes:

• Mixing flag words or order
• Using similar but invalid flags
• Forgetting the double dash prefix

3. Given this Tailwind CLI command:
tailwindcss -i input.css -o output.css --extract-critical
What will happen when you open the webpage using output.css?

medium

A. The CSS file will be empty

B. Only the CSS needed for the visible part loads first, improving speed

C. No CSS will load because the flag disables styles

D. The entire CSS loads at once, no speed improvement

Solution

1. Step 1: Understand the effect of --extract-critical flag

   This flag extracts and includes only critical CSS for initial load.

2. Step 2: Predict the webpage behavior

   The page loads faster because only needed styles for visible content are loaded first.

3. Final Answer:

   Only the CSS needed for the visible part loads first, improving speed -> Option B

4. Quick Check:

   --extract-critical improves load speed by loading visible styles first [OK]

Hint: Flag extracts visible styles first, speeding page load [OK]

Common Mistakes:

• Thinking the flag disables CSS
• Assuming full CSS loads immediately
• Believing CSS file becomes empty

4. You ran tailwindcss -i input.css -o output.css --extract-critical but the page still loads slowly. What could be a reason?

medium

A. You forgot to include the generated output.css in your HTML file

B. The flag --extract-critical disables all CSS animations

C. Tailwind CLI does not support critical CSS extraction

D. You need to add --fast-load flag instead

Solution

1. Step 1: Check if CSS file is linked in HTML

   If the generated CSS file is not included in the HTML, styles won't apply, causing slow or broken page.

2. Step 2: Verify other options

   Other options are incorrect: the flag does not disable animations, Tailwind supports extraction, and --fast-load is not a valid flag.

3. Final Answer:

   You forgot to include the generated output.css in your HTML file -> Option A

4. Quick Check:

   Missing CSS link = no styles applied [OK]

Hint: Always link generated CSS file in HTML to see styles [OK]

Common Mistakes:

• Assuming flag disables animations
• Thinking Tailwind lacks critical CSS support
• Using non-existent CLI flags

5. You want to optimize a large Tailwind project by extracting critical CSS only for the homepage visible content. Which approach is best?

hard

A. Manually copy visible styles into a separate CSS file without using Tailwind CLI flags

B. Include the entire Tailwind CSS file on all pages without extraction

C. Run Tailwind CLI with --extract-critical on homepage CSS and load it first, then lazy-load other styles

D. Disable Tailwind CSS and write all styles in plain CSS

Solution

1. Step 1: Use Tailwind CLI with --extract-critical for homepage

   This extracts only the CSS needed for visible homepage content, improving load speed.

2. Step 2: Load extracted CSS first and lazy-load others

   Loading critical CSS first ensures fast rendering; lazy-loading other styles avoids blocking.

3. Final Answer:

   Run Tailwind CLI with --extract-critical on homepage CSS and load it first, then lazy-load other styles -> Option C

4. Quick Check:

   Extract critical CSS + lazy load others = best optimization [OK]

Hint: Extract critical CSS for visible content, lazy-load rest [OK]

Common Mistakes:

• Loading full CSS without extraction
• Manually copying styles risking errors
• Disabling Tailwind CSS unnecessarily