JSX vs HTML differences in React - Performance Comparison

Performance: JSX vs HTML differences

MEDIUM IMPACT

This affects how the browser parses and renders UI elements, impacting initial load and update speed.

Rendering UI elements in React

React

const element = <div className="container">Hello</div>; ReactDOM.render(element, root);

JSX compiles to React.createElement calls, enabling React to build a virtual DOM efficiently and update only changed parts.

📈 Performance GainSingle virtual DOM creation, minimal reflows, faster updates

Rendering UI elements in React

React

const htmlString = '<div class="container">Hello</div>'; ReactDOM.render(<div dangerouslySetInnerHTML={{__html: htmlString}} />, root);

Passing raw HTML strings requires React to dangerously set innerHTML, causing slower parsing and potential security risks.

📉 Performance CostBlocks rendering while parsing HTML string, triggers extra DOM parsing and potential reflows

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Raw HTML string in React	Direct DOM insertion	Multiple reflows if content changes	High paint cost due to full DOM updates	[X] Bad
JSX with React.createElement	Virtual DOM diffing minimizes DOM ops	Single reflow on updates	Lower paint cost by updating only changed nodes	[OK] Good

Rendering Pipeline

JSX is compiled to JavaScript calls that create virtual DOM nodes. React compares these nodes to update the real DOM efficiently, reducing costly layout and paint operations.

→Parsing

→Virtual DOM Creation

→Diffing

→Layout

→Paint

⚠️ BottleneckParsing raw HTML strings and updating DOM directly

Core Web Vital Affected

LCP

This affects how the browser parses and renders UI elements, impacting initial load and update speed.

Optimization Tips

1Always use JSX in React to leverage virtual DOM for efficient updates.

2Avoid inserting raw HTML strings directly to prevent extra parsing and reflows.

3JSX improves Largest Contentful Paint by reducing direct DOM manipulations.

Performance Quiz - 3 Questions

Why is using JSX better than raw HTML strings in React for performance?

A JSX compiles to virtual DOM calls that minimize direct DOM updates

B JSX loads faster because it is plain HTML

C Raw HTML strings are faster because they skip React

D JSX reduces network requests

DevTools: Performance

How to check: Record a React render and look for scripting and rendering times; compare raw HTML string insertion vs JSX component render.

What to look for: Long scripting times and forced reflows indicate raw HTML string usage; efficient virtual DOM updates show shorter scripting and paint times.

Practice

1. Which attribute should you use in JSX to add CSS classes to an element?

easy

A. cssClass

B. class

C. className

D. styleClass

Solution

1. Step 1: Recall JSX attribute rules

   In JSX, the HTML attribute class is replaced by className because class is a reserved word in JavaScript.

2. Step 2: Identify correct attribute for CSS classes

   Therefore, to add CSS classes in JSX, you must use className.

3. Final Answer:

   className -> Option C

4. Quick Check:

   JSX uses className, not class [OK]

Hint: Remember: JSX uses className, not class for CSS classes [OK]

Common Mistakes:

• Using 'class' instead of 'className' causes errors
• Confusing 'className' with 'cssClass'
• Trying to use 'styleClass' which doesn't exist

2. Which of the following is the correct way to write a label with a 'for' attribute in JSX?

easy

A. Name

B. Name

C. Name

D. Name

Solution

1. Step 1: Understand JSX attribute naming

   In JSX, the HTML attribute for is replaced by htmlFor because for is a reserved word in JavaScript.

2. Step 2: Check correct casing and spelling

   The correct attribute is htmlFor with capital F, so <label htmlFor="inputId">Name</label> is correct.

3. Final Answer:

   <label htmlFor="inputId">Name</label> -> Option A

4. Quick Check:

   Use htmlFor, not for in JSX labels [OK]

Hint: Use htmlFor (camelCase) instead of for in JSX labels [OK]

Common Mistakes:

• Using 'for' attribute directly causes syntax errors
• Writing 'htmlfor' with lowercase f is incorrect
• Using non-existent attributes like 'forId'

3. What will be the rendered output of this JSX code?

const element = <input type="checkbox" checked="true" />;
ReactDOM.render(element, document.getElementById('root'));

medium

A. A checkbox input with checked attribute as string

B. A checked checkbox input

C. Syntax error due to checked attribute value

D. An unchecked checkbox input

Solution

1. Step 1: Analyze checked attribute in JSX

   In JSX, checked="true" without curly braces sets the prop to the string "true".

2. Step 2: Understand rendering of boolean attributes

   React renders <input type="checkbox" checked="true" />. Browsers treat the presence of the checked attribute (any non-empty value) as checked for uncontrolled checkboxes.

3. Final Answer:

   A checked checkbox input -> Option B

4. Quick Check:

   Attribute presence checks uncontrolled checkbox [OK]

Hint: checked="true" renders checked checkbox (attribute presence) [OK]

Common Mistakes:

• Thinking checked="true" leaves checkbox unchecked
• Expecting string value to cause syntax error
• Confusing uncontrolled render with controlled components

4. Identify the error in this JSX snippet:

const element = <div class="container">Hello</div>;

medium

A. Using class instead of className

B. Using double quotes instead of single quotes

C. Missing closing tag for div

D. Using semicolon inside JSX

Solution

1. Step 1: Check attribute names in JSX

   JSX does not use the HTML attribute class. Instead, it uses className because class is a reserved word in JavaScript.

2. Step 2: Verify other parts of the snippet

   The quotes and closing tag are correct. The semicolon is outside JSX and valid in JavaScript.

3. Final Answer:

   Using class instead of className -> Option A

4. Quick Check:

   JSX requires className, not class [OK]

Hint: Replace class with className in JSX attributes [OK]

Common Mistakes:

• Using class attribute causes React warnings or errors
• Thinking quotes style causes errors
• Confusing semicolon placement inside JSX

5. You want to apply inline styles to a JSX element to make text red and bold. Which is the correct way?

hard

A. Text

B. Text

C. Text

D. Text

Solution

1. Step 1: Understand JSX style attribute syntax

   In JSX, the style attribute expects a JavaScript object, so you use double curly braces: the outer for embedding JS, the inner for the object.

2. Step 2: Check property names and values

   CSS properties use camelCase in JSX, so fontWeight is correct. Values are strings like 'red' and 'bold'.

3. Final Answer:

   <div style={{color: 'red', fontWeight: 'bold'}}>Text</div> -> Option D

4. Quick Check:

   Use double braces and camelCase for inline styles [OK]

Hint: Use double braces and camelCase keys for JSX inline styles [OK]

Common Mistakes:

• Using string style attribute instead of object
• Missing curly braces around style object
• Using CSS property names with hyphens instead of camelCase