---
title: "Discussion on \"How React Actually Renders (and Why Your App Re-renders Too Much)\" | Hashnode"
description: "Discussion on \"How React Actually Renders (and Why Your App Re-renders Too Much)\". I spent two days last week staring at the React Profiler, wondering why a simple filter dropdown was causing 47 components to re-render. Forty-seven. For a dropdown.\nThat's when I stopped just using R"
url: "https://hashnode.com/posts/how-react-actually-renders-and-why-your-app-re-renders-too-much/69c37e948a263e79cbefecc9"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [How React Actually Renders (and Why Your App Re-renders Too Much)](https://blog.kunalgoel.dev/how-react-actually-renders-and-why-your-app-re-renders-too-much?utm_source=hashnode&utm_medium=feed)

I spent two days last week staring at the React Profiler, wondering why a simple filter dropdown was causing 47 components to re-render. Forty-seven. For a dropdown. That's when I stopped just using R

Mar 25 · 5 min read · blog.kunalgoel.dev  
Read the article

## Written by

[kunal goel](https://hashnode.com/@frontend-guide)

@frontend-guide · Jaipur

  
[View profile](https://hashnode.com/@frontend-guide)

Full Stack Developer with 3+ years of experience building scalable SaaS web applications using the MERN stack (MongoDB, Express.js, React.js, Node.js). Skilled in developing responsive frontends with React/Next.js and TypeScript, designing RESTful APIs, and optimizing database performance. Experienced in CI/CD pipelines, Docker, and agile practices.

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
