Optimizing React App Performance with useMemo and useCallback
Jul 29, 2025 am 01:04 AM
Use useMemo to memoize expensive computations like large list filtering, ensuring they only re-run when dependencies change. 2. Apply useCallback to preserve function identity when passing callbacks to optimized child components, preventing unnecessary re-renders. 3. Combine useMemo and useCallback with React.memo for maximum performance gains in deeply nested or frequently updated components. 4. Avoid common pitfalls: don’t over-memoize simple values, always include all dependencies in dependency arrays, and rely on ESLint rules to catch mistakes. 5. Only apply these optimizations when performance issues are confirmed through profiling, as unnecessary memoization adds overhead and can degrade performance. Used judiciously, useMemo and useCallback significantly enhance React app efficiency.
React’s declarative model makes building UIs intuitive, but as apps grow, performance can suffer from unnecessary re-renders and expensive recalculations. Two powerful hooks — useMemo and useCallback — help mitigate these issues by memoizing values and functions. When used correctly, they can significantly improve the efficiency of your React components.
Here’s how to use them effectively and avoid common pitfalls.
1. Understanding useMemo: Avoid Recomputing Expensive Values
useMemo lets you memoize expensive calculations so they only re-run when dependencies change.
const expensiveValue = useMemo(() => {
return computeExpensiveValue(a, b);
}, [a, b]);- The function inside
useMemo runs only whenaorbchanges. - Without
useMemo,computeExpensiveValuewould run on every render.
Use case example: You’re filtering or mapping a large list (e.g., 10,000 items). Without memoization, this happens on every render — even if the data hasn’t changed.
function UserList({ users, filter }) {
const filteredUsers = useMemo(() => {
return users.filter(user => user.name.includes(filter));
}, [users, filter]);
return (
<ul>
{filteredUsers.map(user => (
<li key={user.id}>{user.name}</li>
))}
</ul>
);
}? Do: Use
useMemofor costly computations involving large arrays, math, or data transformations.
? Don’t: Wrap every expression inuseMemo. For simple operations, the overhead isn’t worth it.
2. Using useCallback: Prevent Unnecessary Re-renders in Child Components
useCallback memoizes functions, which is useful when passing callbacks to optimized child components.
const handleClick = useCallback(() => {
console.log('Clicked!', id);
}, [id]);This ensures the function reference stays the same between renders — as long as id doesn’t change.
Why it matters: React components re-render when props change. If you pass an inline function, it’s a new object every time, triggering re-renders even if the logic is identical.
function Parent({ userId }) {
const handleSave = useCallback(() => {
saveUser(userId);
}, [userId]);
return <ProfileForm onSave={handleSave} />;
}
// Without useCallback, ProfileForm receives a new onSave every render? Do: Use
useCallbackwhen passing callbacks to pure orReact.memocomponents.
? Don’t: Use it everywhere — most components aren’t optimized, so it adds overhead with no benefit.
3. Combining useMemo and React.memo for Maximum Impact
To fully leverage useMemo and useCallback, pair them with React.memo.
const ProfileForm = React.memo(({ onSave }) => {
return (
<button onClick={onSave}>
Save
</button>
);
});Now, ProfileForm won’t re-render unless onSave changes — and with useCallback, it only changes when necessary.
This combo is especially effective in:
- Large lists with item actions
- Forms with multiple subcomponents
- Apps using frequent prop drilling (before context or state management)
4. Common Mistakes and Performance Trade-offs
While these hooks help, misuse can hurt performance.
? Over-memoizing
// Bad: Simple values don’t need memoization const firstName = useMemo(() => user.firstName, [user]);
This adds overhead with no gain — just use user.firstName.
? Missing or incorrect dependencies
// Wrong: Using `userId` but not listing it
const handleDelete = useCallback(() => {
deleteUser(userId); // userId might be stale
}, []); // ? Missing dependencyAlways include all values from the component scope (props, state, etc.) in the dependency array.
? Ignoring ESLint rules
Use the eslint-plugin-react-hooks plugin. It warns about missing dependencies and helps avoid bugs.
Bottom Line
- Use
useMemofor expensive calculations. - Use
useCallbackto preserve function identity for child components. - Combine with
React.memoto block unnecessary re-renders. - Avoid overusing them — memoization isn’t free.
Used wisely, useMemo and useCallback are powerful tools for optimizing React apps. But remember: premature optimization is the enemy. Measure performance first (with React DevTools), then optimize where it matters.
Basically, don’t add them unless you have a real performance issue or are building a frequently updated, deeply nested component.
The above is the detailed content of Optimizing React App Performance with useMemo and useCallback. For more information, please follow other related articles on the PHP Chinese website!
Hot AI Tools
Undress AI Tool
Undress images for free
Undresser.AI Undress
AI-powered app for creating realistic nude photos
AI Clothes Remover
Online AI tool for removing clothes from photos.
Clothoff.io
AI clothes remover
Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!
Hot Article
Hot Tools
Notepad++7.3.1
Easy-to-use and free code editor
SublimeText3 Chinese version
Chinese version, very easy to use
Zend Studio 13.0.1
Powerful PHP integrated development environment
Dreamweaver CS6
Visual web development tools
SublimeText3 Mac version
God-level code editing software (SublimeText3)
Hot Topics
Adding drag and drop functionality using the HTML5 Drag and Drop API.
Jul 05, 2025 am 02:43 AM
The way to add drag and drop functionality to a web page is to use HTML5's DragandDrop API, which is natively supported without additional libraries. The specific steps are as follows: 1. Set the element draggable="true" to enable drag; 2. Listen to dragstart, dragover, drop and dragend events; 3. Set data in dragstart, block default behavior in dragover, and handle logic in drop. In addition, element movement can be achieved through appendChild and file upload can be achieved through e.dataTransfer.files. Note: preventDefault must be called
Getting user location with HTML5 geolocation API
Jul 04, 2025 am 02:03 AM
To call GeolocationAPI, you need to use the navigator.geolocation.getCurrentPosition() method, and pay attention to permissions, environment and configuration. First check whether the browser supports API, and then call getCurrentPosition to obtain location information; the user needs to authorize access to the location; the deployment environment should be HTTPS; the accuracy or timeout can be improved through configuration items; the mobile behavior may be limited by device settings; the error type can be identified through error.code and given corresponding prompts in the failed callback to improve user experience and functional stability.
Using ARIA attributes with HTML5 semantic elements for accessibility
Jul 07, 2025 am 02:54 AM
The reason why ARIA and HTML5 semantic tags are needed is that although HTML5 semantic elements have accessibility meanings, ARIA can supplement semantics and enhance auxiliary technology recognition capabilities. For example, when legacy browsers lack support, components without native tags (such as modal boxes), and state updates need to be dynamically updated, ARIA provides finer granular control. HTML5 elements such as nav, main, aside correspond to ARIArole by default, and do not need to be added manually unless the default behavior needs to be overridden. The situations where ARIA should be added include: 1. Supplement the missing status information, such as using aria-expanded to represent the button expansion/collapse status; 2. Add semantic roles to non-semantic tags, such as using div role to implement tabs and match them
Securing HTML5 web applications against common vulnerabilities
Jul 05, 2025 am 02:48 AM
The security risks of HTML5 applications need to be paid attention to in front-end development, mainly including XSS attacks, interface security and third-party library risks. 1. Prevent XSS: Escape user input, use textContent, CSP header, input verification, avoid eval() and direct execution of JSON; 2. Protect interface: Use CSRFToken, SameSiteCookie policies, request frequency limits, and sensitive information to encrypt transmission; 3. Secure use of third-party libraries: periodic audit dependencies, use stable versions, reduce external resources, enable SRI verification, ensure that security lines have been built from the early stage of development.
Integrating CSS and JavaScript effectively with HTML5 structure.
Jul 12, 2025 am 03:01 AM
HTML5, CSS and JavaScript should be efficiently combined with semantic tags, reasonable loading order and decoupling design. 1. Use HTML5 semantic tags, such as improving structural clarity and maintainability, which is conducive to SEO and barrier-free access; 2. CSS should be placed in, use external files and split by module to avoid inline styles and delayed loading problems; 3. JavaScript is recommended to be introduced in front, and use defer or async to load asynchronously to avoid blocking rendering; 4. Reduce strong dependence between the three, drive behavior through data-* attributes and class name control status, and improve collaboration efficiency through unified naming specifications. These methods can effectively optimize page performance and collaborate with teams.
Using HTML5 Semantic Elements for Page Structure
Jul 07, 2025 am 02:53 AM
Using HTML5 semantic tags can improve web structure clarity, accessibility and SEO effects. 1. Semantic tags such as,,,, and make it easier for the machine to understand the page content; 2. Each tag has a clear purpose: used in the top area, wrap navigation links, include core content, display independent articles, group relevant content, place sidebars, and display bottom information; 3. Avoid abuse when using it, ensure that only one per page, avoid excessive nesting, reasonable use and in blocks. Mastering these key points can make the web page structure more standardized and practical.
HTML5 video not playing in Chrome
Jul 10, 2025 am 11:20 AM
Common reasons why HTML5 videos don't play in Chrome include format compatibility, autoplay policy, path or MIME type errors, and browser extension interference. 1. Videos should be given priority to using MP4 (H.264) format, or provide multiple tags to adapt to different browsers; 2. Automatic playback requires adding muted attributes or triggering .play() with JavaScript after user interaction; 3. Check whether the file path is correct and ensure that the server is configured with the correct MIME type. Local testing is recommended to use a development server; 4. Ad blocking plug-in or privacy mode may prevent loading, so you can try to disable the plug-in, replace the traceless window or update the browser version to solve the problem.
Embedding video content using the HTML5 `` tag.
Jul 07, 2025 am 02:47 AM
Embed web videos using HTML5 tags, supports multi-format compatibility, custom controls and responsive design. 1. Basic usage: add tags and set src and controls attributes to realize playback functions; 2. Support multi-formats: introduce different formats such as MP4, WebM, Ogg, etc. through tags to improve browser compatibility; 3. Custom appearance and behavior: hide default controls and implement style adjustment and interactive logic through CSS and JavaScript; 4. Pay attention to details: Set muted and autoplay to achieve automatic playback, use preload to control loading strategies, combine width and max-width to achieve responsive layout, and use add subtitles to enhance accessibility.
