AI agents: read this page as markdown at /docs/built-in-checks/react-component-renders.md, or start from the full AI-readable index at /llms.txt.

React component renders

Meticulous counts how many times each React component renders as a session replays against the code under test, and compares each component's total against the same session replayed on the base commit — matched by source location, so minified names don't break the comparison. Render regressions rarely show up visually — the page looks identical while a component quietly re-renders hundreds of extra times. This check surfaces those regressions on the pull request, with a per-component breakdown of which components re-render more and in which sessions. Third-party components (from node_modules) are ignored, since library-internal render counts are noisy.

The React component renders check in the Meticulous UI: a failed check reporting components that rendered more than on base, with a summary table and a per-component breakdown of base vs. head render counts

Verdicts and CI

By default, a component that renders at least 100% more than on base marks the Meticulous React component renders status check as failed on the pull request, requiring the author to acknowledge the result in Meticulous before the pull request can proceed. A component that renders at least 50% more is reported as a warning that leaves the check passing. The thresholds are configurable per project.

The check can also be made informational only: every regressed component is then reported as a warning and the status check never fails, so you can see what it finds without blocking any pull request.