The core of JavaScript performance optimization is to improve user experience and reduce resource consumption. The following are key practices: 1. Reduce DOM operations and build batch updates through DocumentFragment or offline; 2. Use throttle and debounce for high-frequency events such as scroll and resize to control the execution frequency; 3. Use efficient loops, prioritize for for or for...of to avoid traversing the array and cache the array length; 4. Avoid memory leaks, remove event listeners in time, clear useless references, and use global variables with caution; 5. Use asynchronous modes such as setTimeout, requestIdleCallback or Web Workers to split time-consuming tasks to avoid blocking the main thread; 6. Use dynamic import() to achieve lazy loading and code segmentation to reduce the initial load burden; 7. Keep the initialization order of object attributes consistent in the V8 engine, and avoid dynamically adding attributes to improve the optimization effect of hidden class. These strategies work together to significantly improve application response speed and operation efficiency, ultimately achieving a smooth user interaction experience.
JavaScript performance optimization isn't just about making code run faster — it's about creating smoother user experiences and reducing resource consumption. Here are practical, real-world tips that make a difference.

1. Minimize DOM Manipulation
The DOM is slow. Every time you access or modify it, the browser may need to reccalculate layout (reflow) and repaint, which hurts performance — especially in loops.
Do this instead:

- Batch DOM updates.
- Work with DocumentFragment or build HTML strings offline.
- Use virtual DOM libraries (like React) to minimize direct manipulation.
// ? Bad: Touching DOM in a loop for (let i = 0; i < items.length; i ) { const el = document.createElement('li'); el.textContent = items[i]; list.appendChild(el); // Triggers reflect each time } // ? Good: Use DocumentFragment const fragment = document.createDocumentFragment(); for (let i = 0; i < items.length; i ) { const el = document.createElement('li'); el.textContent = items[i]; fragment.appendChild(el); } list.appendChild(fragment); // One reflow
2. Debounce and Throttle Expensive Events
Events like scroll
, resize
, and input
can fire dozens of times per second. Running heavy logic on each event kills performance.
- Throttle : Run a function at most once every X million seconds.
- Debounce : Run only after the event stops firing for X millionseconds.
function throttle(func, delay) { let inThrottle; return function () { if (!inThrottle) { func.apply(this, arguments); inThrottle = true; setTimeout(() => inThrottle = false, delay); } }; } // Usage window.addEventListener('resize', throttle(handleResize, 100));
Useful for:

- Auto-suggest inputs (debounce)
- Infinite scroll (throttle)
- Drag-and-drop handlers
3. Use Efficient Loops and Array Methods
Not all loops are created equal. Avoid for...in
for arrays. Prefer for
or for...of
for large datasets.
Also, know when to use which array method:
-
map
,filter
,reduce
are clean but create new arrays — costly for huge lists. - For performance-critical loops, use traditional
for
orwhile
.
// ? Fast for large arrays for (let i = 0; i < arr.length; i ) { ... } // ? Slower due to function call overhead arr.forEach(item => { ... });
Tip: Cache array length in loops:
for (let i = 0, len = arr.length; i < len; i ) { ... }
4. Avoid Memory Leaks
JavaScript has garbage collection, but you can still leak memory by:
- Forgetting to remove event listeners.
- Keeping references to unused objects (especially in closings).
- Using global variables excessively.
Fix:
- Always remove event listeners:
elem.removeEventListener()
. - Set unused references to
null
. - Use browser dev tools (Memory tab) to detect leaks.
// Bad: Anonymous functions can't be removed button.addEventListener('click', () => { ... }); // Good: Named or stored function function handleClick() { ... } button.addEventListener('click', handleClick); // Later: button.removeEventListener('click', handleClick);
5. Optimize with Asynchronous Patterns
Long-running tasks block the main thread, freezing the UI. Break them up using:
-
setTimeout
orsetImmediate
to yield control. -
requestIdleCallback
for low-priority work. - Web Workers for CPU-heavy tasks (eg, parsing large JSON).
function processLargeArray(arr, callback) { const chunkSize = 1000; let index = 0; function processChunk() { const end = Math.min(index chunkSize, arr.length); for (let i = index; i < end; i ) { // process arr[i] } index = end; if (index < arr.length) { setTimeout(processChunk, 0); // Yield to UI } else { callback(); } } processChunk(); }
6. Lazy Load and Code Splitting
Load only what's needed. Use dynamic import()
to split code and load modules on demand.
// Load heavy module only when needed button.addEventListener('click', () => { import('./heavyModule.js').then(module => { module.render(); }); });
This reduces initial load time and memory usage.
7. Use Object Property Order and Avoid Hidden Classes (V8)
In V8 (Chrome, Node), objects with the same property creation order share "hidden classes," improving performance.
Avoid:
function User(name) { this.name = name; } function Admin(name) { this.role = 'admin'; // Different order = different hidden class this.name = name; }
Instead, initialize properties in the same order.
Also, avoid adding properties after creation:
const obj = {}; obj.x = 1; obj.y = 2; // Dynamic add — slower
Prefer:
const obj = { x: 1, y: 2 };
Basically, optimize where it matters: avoid DOM thrashing, control event frequency, manage memory, and split heavy work. Most gains come from smart patterns, not micro-optimizations.
The above is the detailed content of JavaScript performance optimization tips. 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

JavaScript's garbage collection mechanism automatically manages memory through a tag-clearing algorithm to reduce the risk of memory leakage. The engine traverses and marks the active object from the root object, and unmarked is treated as garbage and cleared. For example, when the object is no longer referenced (such as setting the variable to null), it will be released in the next round of recycling. Common causes of memory leaks include: ① Uncleared timers or event listeners; ② References to external variables in closures; ③ Global variables continue to hold a large amount of data. The V8 engine optimizes recycling efficiency through strategies such as generational recycling, incremental marking, parallel/concurrent recycling, and reduces the main thread blocking time. During development, unnecessary global references should be avoided and object associations should be promptly decorated to improve performance and stability.

There are three common ways to initiate HTTP requests in Node.js: use built-in modules, axios, and node-fetch. 1. Use the built-in http/https module without dependencies, which is suitable for basic scenarios, but requires manual processing of data stitching and error monitoring, such as using https.get() to obtain data or send POST requests through .write(); 2.axios is a third-party library based on Promise. It has concise syntax and powerful functions, supports async/await, automatic JSON conversion, interceptor, etc. It is recommended to simplify asynchronous request operations; 3.node-fetch provides a style similar to browser fetch, based on Promise and simple syntax

JavaScript data types are divided into primitive types and reference types. Primitive types include string, number, boolean, null, undefined, and symbol. The values are immutable and copies are copied when assigning values, so they do not affect each other; reference types such as objects, arrays and functions store memory addresses, and variables pointing to the same object will affect each other. Typeof and instanceof can be used to determine types, but pay attention to the historical issues of typeofnull. Understanding these two types of differences can help write more stable and reliable code.

Hello, JavaScript developers! Welcome to this week's JavaScript news! This week we will focus on: Oracle's trademark dispute with Deno, new JavaScript time objects are supported by browsers, Google Chrome updates, and some powerful developer tools. Let's get started! Oracle's trademark dispute with Deno Oracle's attempt to register a "JavaScript" trademark has caused controversy. Ryan Dahl, the creator of Node.js and Deno, has filed a petition to cancel the trademark, and he believes that JavaScript is an open standard and should not be used by Oracle

Which JavaScript framework is the best choice? The answer is to choose the most suitable one according to your needs. 1.React is flexible and free, suitable for medium and large projects that require high customization and team architecture capabilities; 2. Angular provides complete solutions, suitable for enterprise-level applications and long-term maintenance; 3. Vue is easy to use, suitable for small and medium-sized projects or rapid development. In addition, whether there is an existing technology stack, team size, project life cycle and whether SSR is needed are also important factors in choosing a framework. In short, there is no absolutely the best framework, the best choice is the one that suits your needs.

IIFE (ImmediatelyInvokedFunctionExpression) is a function expression executed immediately after definition, used to isolate variables and avoid contaminating global scope. It is called by wrapping the function in parentheses to make it an expression and a pair of brackets immediately followed by it, such as (function(){/code/})();. Its core uses include: 1. Avoid variable conflicts and prevent duplication of naming between multiple scripts; 2. Create a private scope to make the internal variables invisible; 3. Modular code to facilitate initialization without exposing too many variables. Common writing methods include versions passed with parameters and versions of ES6 arrow function, but note that expressions and ties must be used.

Promise is the core mechanism for handling asynchronous operations in JavaScript. Understanding chain calls, error handling and combiners is the key to mastering their applications. 1. The chain call returns a new Promise through .then() to realize asynchronous process concatenation. Each .then() receives the previous result and can return a value or a Promise; 2. Error handling should use .catch() to catch exceptions to avoid silent failures, and can return the default value in catch to continue the process; 3. Combinators such as Promise.all() (successfully successful only after all success), Promise.race() (the first completion is returned) and Promise.allSettled() (waiting for all completions)

CacheAPI is a tool provided by the browser to cache network requests, which is often used in conjunction with ServiceWorker to improve website performance and offline experience. 1. It allows developers to manually store resources such as scripts, style sheets, pictures, etc.; 2. It can match cache responses according to requests; 3. It supports deleting specific caches or clearing the entire cache; 4. It can implement cache priority or network priority strategies through ServiceWorker listening to fetch events; 5. It is often used for offline support, speed up repeated access speed, preloading key resources and background update content; 6. When using it, you need to pay attention to cache version control, storage restrictions and the difference from HTTP caching mechanism.
