Rendering cost

What this means

A component renders when its state changes, when its parent renders, or when relevant context changes. Rendering is normal, but unnecessary expensive rendering can slow an app.

In beginner terms, this topic answers one practical question: "What should I write, and why does React care about it?" Do not try to memorize the syntax first. First understand the idea, then connect the syntax to that idea.

Why it matters

You do not need to fear every render. First make code correct and clear. Then measure and optimize real problems.

When you build real React screens, this idea helps you decide where data should live, what the user should see, and what should happen after an interaction. That is why this lesson is part of the main path instead of being an optional detail.

Step by step

1. Notice the UI problem this topic solves. 2. Look at the smallest possible example. 3. Change one value and predict what should appear. 4. Run the example and compare the result with your prediction. 5. Use the practice task before moving on.

Small example

console.log("Component rendered");

Common mistake

Do not optimize before you know there is a problem. Premature optimization makes code harder for beginners to understand.

Practice task

Add a console log to a component and click a state-changing button to observe rerenders.

Remember this

Rendering is normal; expensive unnecessary rendering is what you watch for.