The Art of Ignoring Best Practices for React Performance

This ad is not shown to multipass and full ticket holders
React Summit US
React Summit US 2025
November 18 - 21, 2025
New York, US & Online
The biggest React conference in the US
Learn More
In partnership with Focus Reactive
Upcoming event
React Summit US 2025
React Summit US 2025
November 18 - 21, 2025. New York, US & Online
Learn more
Bookmark
Slides
Rate this content

Have you ever wanted to break the rules and be a React troublemaker? I’ll show you how ignoring React’s best practices can improve performance, all without major rewrites to your codebase. To understand how, we’ll learn when React decides to render and how to trick it to render less frequently. We’ll build components that don’t render anything, conditionally call hooks, and even use a piece of Svelte - all to quickly fix real performance problems I encountered at Microsoft.

This talk has been presented at React Summit 2024, check out the latest edition of this React Conference.

FAQ

The speaker is Tigerhooks, a senior software engineer at Microsoft who has worked on web browsers like Edge, Chrome, and Firefox.

The main topic is about breaking React best practices to improve performance, including techniques like conditionally calling hooks, using impure components, and incorporating a second UI library.

React rerenders components mainly due to state changes. When a state update occurs, the component and all its descendants rerender to keep the UI in sync with the state.

React.Memo is a higher-order component that prevents rerenders if the component's props haven't changed. It helps optimize performance by memoizing the component's output.

You can use React DevTools Profiler to track component rerenders. It has settings like 'Highlight Updates When Components Re-render' and 'Record Why Each Component Rendered While Profiling' to help identify rerenders.

The ExpensiveEffect component isolates state changes by running side effects and not rendering any children. This helps in preventing unnecessary rerenders of the entire component tree.

You can use Svelte's store API to manage state without affecting React's component tree. This allows you to update state and notify components without causing unnecessary rerenders.

Svelte stores provide a set method to update state and notify components watching the store. This reduces the need for React's useState and helps in preventing excessive rerenders.

Redux uses a static store reference passed through React context, updating only the necessary components. In contrast, the useReducer hook can cause the entire tree to rerender when any state changes.

Svelte stores know how many listeners are attached and can clean up based on listener presence. This helps in efficiently managing resources and avoiding memory leaks.

Tiger Oakes
Tiger Oakes
19 min
18 Jun, 2024

Comments

Sign in or register to post your comment.
Video Summary and Transcription
This Talk introduces the concept of being a 'React bad boy' by ignoring best practices and optimizing React rendering. It explains how to avoid unnecessary rerenders using React.memo and React DevTools. It also covers advanced techniques like isolating state changes and lazy loading hooks. The Talk explores reducing component rerenders using Svelte stores and optimizing with swap stores in Redux. These techniques improve React performance without the need for major refactors or rewrites.

1. Introduction to React Bad Boy

Short description:

Have you ever wanted to be a React bad boy? I'm going to show you the art of ignoring best practices. We'll talk about when does React decide to rerender, then how to isolate expensive hooks and state changes using impure components, and how to only update leaf components by using a different UI library.

Have you ever wanted to be a React bad boy? I know you've all been good engineers following all the best practices, but where has that gotten you? Into complex React projects with slow components? Then you find yourself wanting to smash your mechanical keyboard, wondering why you need to use unidirectional data flow to avoid calling React hooks conditionally, to store state using React's useState hook. You hear a little voice whispering, you can be a React troublemaker. You can break all of these rules. You think jaywalking, littering, and riding a motorcycle is bad. Wait until you conditionally call React hooks, build impure components, and even pull in a second UI library?

My name is tigerhooks. You can find me at notwoods and all the socials. I'm a senior software engineer working at Microsoft and I previously helped build three web browsers, Edge, Chrome, and Firefox. I've worked with React for over eight years, and I am going to show you the art of ignoring best practices. Any documentation you read comes with a hidden asterisk. It covers most cases, but we all have different setups and environments. This talk will show you the edge cases that you know when to follow and when not to follow best practices and how to get yourself on Santa's Nautilus this Christmas. Since we're in dangerous territory, use what I'm about to show you with caution. Some of these tricks can make your code hard to follow. Use your best judgment, evaluate tradeoffs, and communicate what you're trying to do. Here is what I'll show you today. We'll talk about when does React decide to rerender, then how to isolate expensive hooks and state changes using impure components, and how to only update leaf components by using a different UI library.

Let's start with the first topic. When does React rerender? Well, React starts with a simple rule. Every rerender starts with a state change. You might be thinking, wait, don't components rerender when their props change? When context changes? But no, the trick is that whenever a component rerenders, it also rerenders every descendant component. React uses rerenders to figure out what needs to change to keep your UI in sync with state. Your component will return a mix of other components and HTML elements. When another component is encountered, React will then proceed to render it, and that component will return another mix of components and HTML elements. Eventually, React will just be left with an HTML tree. Now that it's finished rerendering components, it will begin the process of virtual DOM diffing. React will compare the new HTML against the previously rendered HTML, and then update the nodes that have changed in the DOM. But React does not think too hard about what components to render. You might think that only components that read the state will update, but actually everything rerenders. It doesn't matter if the state is passed in as a prop, or if the component takes no props at all. Whenever this increment button is clicked, and the counter state is updated, the MyCounter component and all its descendants will re-render as indicated by these green flashes.

2. Avoiding Unnecessary Rerenders

Short description:

Even though the title component doesn't read the count state, it also re-renders. React.Memo can help reduce unnecessary re-renders. React DevTools can highlight re-rendered components and track down the cause. Check out Josh Komu's article for more details.

Even though the title component doesn't read the count state, it also re-renders. The only exception to this is React.Memo. Memo places an extra layer around a component, which tells React, if my props are the same, I pinky promise that I would return the exact same result. You can just remember what I returned last time. No need to render me again. Now whenever this increment button is clicked, and the counter state is updated, MyCounter will re-render, and then it will attempt to re-render its descendants. Title doesn't read the count state, so its props have not changed. As a result, it doesn't re-render, thanks to React.Memo. MyCounter display is still re-rendered, as this count prop is changing. Now Memo is a little bit weird with React.Context. Context acts like a second set of invisible props, past every component. So if your component is using React.Memo, the props and context it's reading must be exactly the same, or else the component will be caused to re-render. If you want to see whenever a component re-renders in your own code, React DevTools can help out. After opening your browser's developer tools, you can go to React's Profiler tab, click on the gear icon to open the extension settings, and then turn on a setting labeled, Highlight Updates When Components Re-render. This will cause green rectangles to flash around each re-rendered component in your UI. And if you're trying to track down what's causing a re-render in your code, you can turn on a different setting labeled, Record Why Each Component Rendered While Profiling. You can find it under the Profiler tab in React's DevTools settings dialog. Then, when you save a recording using React's Profiler, each render will be captured and you can see what triggered it. If you want to learn more, you can check out Josh Komu's excellent article with live samples you can play with.

3. Optimizing React Rendering

Short description:

React recommends writing components that render quickly. But when you have expensive components, you can trick React to re-render less often. Isolate state changes into a single leaf node using an effect component. This improves performance by detaching state from child components in the tree.

Now, React does recommend that instead of caring about how frequently you're re-rendering, you just simply write your components that render quickly. You know, sure, just have you and your entire team always write perfectly performing code. What could go wrong? But when, inevitably, you do end up with expensive components, we can trick React to re-render less often. That's when we start breaking the rules and ignoring best practices.

Now that we know that every re-render in React is triggered by a state's change, let's figure out how to avoid these state changes. For our second topic, we'll discuss an approach to avoid state changes by isolating expensive hooks. Now, what happens if we have hooks that fetch some data and then place it in state? After the effect runs, React will update. Let's start with an example hook called useGetData. It fetches some state value and they will call setState which triggers a re-render. But what happens if that first piece of state is used to fetch more data? For example, we might use an ID from the previous fetch to then start another fetch effect. After each effect runs, React will re-render again. That can be a lot of re-renders, even though we're not even using these in-between state values. If we only use the last piece of state in our UI, all those other re-renders were wasted work. Since each state update will cost the component and all of its descendants to render, that can result in a lot of components rendering unnecessarily.

How can we isolate this? Well, ideally, a chain like this should be refactored. Rather than using state to trigger effects, you can instead set up a promise chain inside a single effect. But that also requires time to be invested in code cleanup and taken away from future work. Instead, we can isolate the state changes into a single leaf node so that the rest of the tree doesn't need to update until the final value is ready. We'll write a specialized React component that just runs side effects and doesn't return any children, so it'll be cheaper to render. Here, we've made a component called ExpensiveEffect that is simply in charge of calling the useGetData hook. It will always return null. The final result from the hook will then be passed back up to the parent using props.setState, which will update the parent state. Now, all state changes in the expensive hook are isolated by this effect component. This does break unidirectional data flow. Instead, there's a small little loop-de-loop where we pass input into and then get output from the effect component. Now, data is getting fetched in ExpensiveEffect and then passed up to app, which is passed back down to UI. It's a quick refactor that can improve performance a lot by detaching state from child components in the tree. In Microsoft Loop, we had a component high in our tree that rendered five times due to intermediate state used in a hook. Wrapping that single hook in an effect component made this startup path five times faster. Any expensive components that have a lot of unnecessary state can benefit greatly from using effect components.

4. Advanced React Rendering

Short description:

This pattern introduces an additional superpower. You can conditionally render effect components, lazy load hooks, and use a convention for components that fetch data. This pattern is adopted from Android's Jetpack Compose, where hooks and components are all composables. Wrapping state changes in a child component prevents them from affecting the rest of the React tree.

This pattern also introduces an additional superpower. We can use all the flexibility we have when deciding when to render components unlike hooks. Want to conditionally call your hook? Well, you can just conditionally render the effect components. Need to lazy load your hook? Wrap the effect component with React.lazy and suspense. This effect suffix is a convention used to indicate this component doesn't render anything and it will just be fetching data.

This pattern is adopted from Android's Jetpack Compose, which is a library that has a very similar functionality to React. In Jetpack Compose, there is no difference between hooks and components. They are all composables. Composables that return data are camel case, like load data and mutable state of. Composables that show UI are Pascal case, like React, like app. And composables that just run some side effect are Pascal case but with an effect suffix.

By wrapping your state changes into a child component, we can prevent them from affecting the rest of the React tree. The effect component has no children of its own to re-render and it can't make sibling components render. We successfully isolated all of our state changes.

5. Reducing Component Rerenders

Short description:

Now let's discuss how to reduce the number of components in a tree that render. We can use Svelte stores, a portable use state alternative, to pass around state values without causing re-renders. By placing multiple hooks inside each leaf component, we can update the hook's internal state using the current value of the store, causing only the leaf components to re-render. This approach breaks out of the limitations of React's useState hook while keeping a similar API. DataModel stores can also be used outside of React, allowing for reactive state management in different contexts. Redux follows a similar performance optimization by passing around a static store reference using React context.

Now for our third topic, we'll discuss how to reduce the number of components in a tree that render. If our state is very high up, the entire app is going to re-render. Effect components does let us reduce how often this happens, but it does still need to happen at some point.

Now what if you have a large list or a piece of data is only used by maybe a time stamp in some list items? Do we really need to re-render the entire list just to update a few strings? We could use context to pass a value down from the grandparent to his grandchild, but re-renders still need to happen because we're using React.useState.

But what if we use state without useState? We would need to do what React does for us, store a piece of state, have a way to set that state, and also inform everyone who cares that the state changed. Well, React does do this pretty well, but other libraries can do it too. So let's just go ahead and start using a whole second competing UI library, Svelte.

The trick is, we're not actually using Svelte for his UI code. Instead, we'll unwrap the package and just use a special store API. Svelte stores act like a portable use state. They have a set method to update the state and components watching the store. You can even pass in a callback to update state based on the previous state value, just like React. The store API is independent of the rest of Svelte, so we don't need to worry about pulling in anything else. You can use eslint to disable direct Svelte imports in your code, and it only allows importing from Svelte slash store.

Now instead of passing around a raw state value, we can pass around a Svelte store instead. You can do so using props or context, like regular values. The store does not change identity, so changing values will not affect React.memo. Now, at some point, we do still need to convert from the Svelte store back into React.state. Instead of placing the hook inside the ancestor branch component, we can place multiple hooks inside each leaf component. We'll use React's built-in usync external store hook. It takes two callbacks, one used to subscribe to the store and watch for changes, and another to get the current value from the store. Whenever the store changes, React will use that as a signal to update the hook's internal state using the current value of the store, causing the component to re-render.

Now the intermediate components don't need to re-render at all. Only the leaf components get notified when the store changes, so no other components get re-rendered. By just passing around a static store object, we've broken out of the limitations of React's useState hook while keeping a similar API. Combined with effect components, we can prepare state and then pass it around without re-rendering the ancestors at all. By passing store.set to our effect component instead of React's setState callback, we never need to work with useState in our top component and therefore never need to re-render it. DataModel stores are also usable outside of React or any UI library, so you can manage reactive state in data model classes, in a worker, or even on the server. This is actually very similar to a performance optimization Redux does under the hook. Redux is just passing around a static store reference using React context.

6. Optimizing with Swap Stores

Short description:

Swap stores in Redux are similar to the useState API, providing better performance than useReducer for large reducer stores. Redux's useSelector updates grandchildren only when selected state changes. SlotStores, like Signals, wrap APIs to create a generic observable system, preventing excessive event listeners. This feature gives SlotStore an edge over other Signal libraries. A TC39 proposal to standardize Signals may bring this feature to other libraries. These tricks improve React performance without major refactors or rewrites.

React's state isn't involved until you've called Redux's useSelector hook. But swap stores are much closer to the useState API, so they need less boilerplate, especially for simple state. By the way, this does also mean that Redux will have better performance than React's built-in useReducer hook, especially if you have a giant reducer store.

Changing the value with useReducer will re-render the entire tree when anything changes, because it's being translated into React state at the top of the tree. In contrast, Redux's useSelector will just update grandchildren when the selected state changes. Now you might have also heard of this cool new API called Signals in other libraries like React and Solid. SlotStore has a somewhat similar API to Signals, so does that mean you could just use Signals instead? Yes. But, you know what, I like SlotStores. They have an extra feature over most Signal libraries. They know how many listeners are attached and can initiate and clean up based on whether or not they have any listeners.

This is really great for wrapping other APIs as a nice generic observable system, such as MatchMedia for listening to CSS media queries. We can wrap MatchMedia into a store that only will attack an event listener once, once at least one component has started subscribing to the store. Any subsequent components will not trigger this callback, so that we don't need to worry about tons of event listeners attached to original MatchMedia. Once all the components have unmounted and unsubscribed, we can clean up our event listener and avoid memory leaks. This feature gives SlotStore an edge over other Signal libraries, even over Slot's new prunes. But, a recent TC39 proposal to standardize Signals inside the JavaScript language also includes this extra feature. So, we might see it come to other Signal libraries, too.

These are all real tricks I use to improve performance on Microsoft products, like Microsoft Loop, while avoiding big refactors and rewrites. I'm sharing them with you so that you, too, can learn the art of ignoring best practices, but to improve your React performance. Thank you for listening. You can find my blog online at tigeroaks.com, and check out the app I work on at loop.microsoft.com.

Check out more articles and videos

We constantly think of articles and videos that might spark Git people interest / skill us up or help building a stellar career

A Guide to React Rendering Behavior
React Advanced 2022React Advanced 2022
25 min
A Guide to React Rendering Behavior
Top Content
This transcription provides a brief guide to React rendering behavior. It explains the process of rendering, comparing new and old elements, and the importance of pure rendering without side effects. It also covers topics such as batching and double rendering, optimizing rendering and using context and Redux in React. Overall, it offers valuable insights for developers looking to understand and optimize React rendering.
Building Better Websites with Remix
React Summit Remote Edition 2021React Summit Remote Edition 2021
33 min
Building Better Websites with Remix
Top Content
Remix is a web framework built on React Router that focuses on web fundamentals, accessibility, performance, and flexibility. It delivers real HTML and SEO benefits, and allows for automatic updating of meta tags and styles. It provides features like login functionality, session management, and error handling. Remix is a server-rendered framework that can enhance sites with JavaScript but doesn't require it for basic functionality. It aims to create quality HTML-driven documents and is flexible for use with different web technologies and stacks.
React Compiler - Understanding Idiomatic React (React Forget)
React Advanced 2023React Advanced 2023
33 min
React Compiler - Understanding Idiomatic React (React Forget)
Top Content
Watch video: React Compiler - Understanding Idiomatic React (React Forget)
Joe Savona
Mofei Zhang
2 authors
The Talk discusses React Forget, a compiler built at Meta that aims to optimize client-side React development. It explores the use of memoization to improve performance and the vision of Forget to automatically determine dependencies at build time. Forget is named with an F-word pun and has the potential to optimize server builds and enable dead code elimination. The team plans to make Forget open-source and is focused on ensuring its quality before release.
Using useEffect Effectively
React Advanced 2022React Advanced 2022
30 min
Using useEffect Effectively
Top Content
Today's Talk explores the use of the useEffect hook in React development, covering topics such as fetching data, handling race conditions and cleanup, and optimizing performance. It also discusses the correct use of useEffect in React 18, the distinction between Activity Effects and Action Effects, and the potential misuse of useEffect. The Talk highlights the benefits of using useQuery or SWR for data fetching, the problems with using useEffect for initializing global singletons, and the use of state machines for handling effects. The speaker also recommends exploring the beta React docs and using tools like the stately.ai editor for visualizing state machines.
Speeding Up Your React App With Less JavaScript
React Summit 2023React Summit 2023
32 min
Speeding Up Your React App With Less JavaScript
Top Content
Watch video: Speeding Up Your React App With Less JavaScript
Mishko, the creator of Angular and AngularJS, discusses the challenges of website performance and JavaScript hydration. He explains the differences between client-side and server-side rendering and introduces Quik as a solution for efficient component hydration. Mishko demonstrates examples of state management and intercommunication using Quik. He highlights the performance benefits of using Quik with React and emphasizes the importance of reducing JavaScript size for better performance. Finally, he mentions the use of QUIC in both MPA and SPA applications for improved startup performance.
Routing in React 18 and Beyond
React Summit 2022React Summit 2022
20 min
Routing in React 18 and Beyond
Top Content
Routing in React 18 brings a native app-like user experience and allows applications to transition between different environments. React Router and Next.js have different approaches to routing, with React Router using component-based routing and Next.js using file system-based routing. React server components provide the primitives to address the disadvantages of multipage applications while maintaining the same user experience. Improving navigation and routing in React involves including loading UI, pre-rendering parts of the screen, and using server components for more performant experiences. Next.js and Remix are moving towards a converging solution by combining component-based routing with file system routing.

Workshops on related topic

React Performance Debugging Masterclass
React Summit 2023React Summit 2023
170 min
React Performance Debugging Masterclass
Top Content
Featured Workshop
Ivan Akulov
Ivan Akulov
Ivan’s first attempts at performance debugging were chaotic. He would see a slow interaction, try a random optimization, see that it didn't help, and keep trying other optimizations until he found the right one (or gave up).
Back then, Ivan didn’t know how to use performance devtools well. He would do a recording in Chrome DevTools or React Profiler, poke around it, try clicking random things, and then close it in frustration a few minutes later. Now, Ivan knows exactly where and what to look for. And in this workshop, Ivan will teach you that too.
Here’s how this is going to work. We’ll take a slow app → debug it (using tools like Chrome DevTools, React Profiler, and why-did-you-render) → pinpoint the bottleneck → and then repeat, several times more. We won’t talk about the solutions (in 90% of the cases, it’s just the ol’ regular useMemo() or memo()). But we’ll talk about everything that comes before – and learn how to analyze any React performance problem, step by step.
(Note: This workshop is best suited for engineers who are already familiar with how useMemo() and memo() work – but want to get better at using the performance tools around React. Also, we’ll be covering interaction performance, not load speed, so you won’t hear a word about Lighthouse 🤐)
Next.js for React.js Developers
React Day Berlin 2023React Day Berlin 2023
157 min
Next.js for React.js Developers
Top Content
Featured WorkshopFree
Adrian Hajdin
Adrian Hajdin
In this advanced Next.js workshop, we will delve into key concepts and techniques that empower React.js developers to harness the full potential of Next.js. We will explore advanced topics and hands-on practices, equipping you with the skills needed to build high-performance web applications and make informed architectural decisions.
By the end of this workshop, you will be able to:1. Understand the benefits of React Server Components and their role in building interactive, server-rendered React applications.2. Differentiate between Edge and Node.js runtime in Next.js and know when to use each based on your project's requirements.3. Explore advanced Server-Side Rendering (SSR) techniques, including streaming, parallel vs. sequential fetching, and data synchronization.4. Implement caching strategies for enhanced performance and reduced server load in Next.js applications.5. Utilize React Actions to handle complex server mutation.6. Optimize your Next.js applications for SEO, social sharing, and overall performance to improve discoverability and user engagement.
Concurrent Rendering Adventures in React 18
React Advanced 2021React Advanced 2021
132 min
Concurrent Rendering Adventures in React 18
Top Content
Featured Workshop
Maurice de Beijer
Maurice de Beijer
With the release of React 18 we finally get the long awaited concurrent rendering. But how is that going to affect your application? What are the benefits of concurrent rendering in React? What do you need to do to switch to concurrent rendering when you upgrade to React 18? And what if you don’t want or can’t use concurrent rendering yet?

There are some behavior changes you need to be aware of! In this workshop we will cover all of those subjects and more.

Join me with your laptop in this interactive workshop. You will see how easy it is to switch to concurrent rendering in your React application. You will learn all about concurrent rendering, SuspenseList, the startTransition API and more.
React Hooks Tips Only the Pros Know
React Summit Remote Edition 2021React Summit Remote Edition 2021
177 min
React Hooks Tips Only the Pros Know
Top Content
Featured Workshop
Maurice de Beijer
Maurice de Beijer
The addition of the hooks API to React was quite a major change. Before hooks most components had to be class based. Now, with hooks, these are often much simpler functional components. Hooks can be really simple to use. Almost deceptively simple. Because there are still plenty of ways you can mess up with hooks. And it often turns out there are many ways where you can improve your components a better understanding of how each React hook can be used.You will learn all about the pros and cons of the various hooks. You will learn when to use useState() versus useReducer(). We will look at using useContext() efficiently. You will see when to use useLayoutEffect() and when useEffect() is better.
Introducing FlashList: Let's build a performant React Native list all together
React Advanced 2022React Advanced 2022
81 min
Introducing FlashList: Let's build a performant React Native list all together
Top Content
Featured Workshop
David Cortés Fulla
Marek Fořt
Talha Naqvi
3 authors
In this workshop you’ll learn why we created FlashList at Shopify and how you can use it in your code today. We will show you how to take a list that is not performant in FlatList and make it performant using FlashList with minimum effort. We will use tools like Flipper, our own benchmarking code, and teach you how the FlashList API can cover more complex use cases and still keep a top-notch performance.You will know:- Quick presentation about what FlashList, why we built, etc.- Migrating from FlatList to FlashList- Teaching how to write a performant list- Utilizing the tools provided by FlashList library (mainly the useBenchmark hook)- Using the Flipper plugins (flame graph, our lists profiler, UI & JS FPS profiler, etc.)- Optimizing performance of FlashList by using more advanced props like `getType`- 5-6 sample tasks where we’ll uncover and fix issues together- Q&A with Shopify team
React, TypeScript, and TDD
React Advanced 2021React Advanced 2021
174 min
React, TypeScript, and TDD
Top Content
Featured Workshop
Paul Everitt
Paul Everitt
ReactJS is wildly popular and thus wildly supported. TypeScript is increasingly popular, and thus increasingly supported.

The two together? Not as much. Given that they both change quickly, it's hard to find accurate learning materials.

React+TypeScript, with JetBrains IDEs? That three-part combination is the topic of this series. We'll show a little about a lot. Meaning, the key steps to getting productive, in the IDE, for React projects using TypeScript. Along the way we'll show test-driven development and emphasize tips-and-tricks in the IDE.