Skip to content

Faster JavaScript

JavaScript is a very important language for now and the future. Nowadays, there is no page that does not include some JavaScript code in it. Moreover, code written in JavaScript increases day by day. The more JavaScript code we have in our web pages, the worse performance we observe. This occurs because of some tricks in JavaScript as a language. In this writing, I will try to explain what are the problems and what possible solution we can have. Before going into detail, let me explain what I am going to talk about. The first one will be about scoping, second will be libraries and last one is DOM manipulation and properties.
JavaScript is a language that uses dynamic scoping. In each function, we have a default scope variables(window, navigator, document) that are pushed onto our stack. After those, each local variable is pushed onto stack with a separate block. Using local scope variables is faster than the global scope variables. At that point, we prefer using local variables. At least we can retrieve global variable and set it to a local variable. Note that, when we are creating a new variable, we should always use “var” since if we do not, they will have a global scope instead of local scope. Here is an example.

Furthermore, JavaScript provides closures where we can pass a variable to another function that is dynamically created. The variable we pass into other function comes from another scope so this will result in a performance issue. Therefore, we should set it to a local variable. Let us see another example for closures.

Our second point is using JavaScript Libraries which are very helpful most of the time. On the other hand, when you need performance, you may fail if you are using JavaScript Library. Let me explain by an example. We generally loop through each or foreach defined in most of the popular JavaScript libraries. However, this usage is very bad comparing it to a regular loop since in each iteration you create a function and destroy it afterwards. That means you create a local stack, pass variables into that and destroy it after execution. What is more, most of the JavaScript libraries creates their native object which are heavier than regular DOM elements. They include lots of functions and variables belong to library and you use just one or two of them. Consequently, you have waste of functions or variables. If you want faster code, you may use less JavaScript library help.
Last but very important is DOM manipulation and properties. In retrieving properties, we use generally things like which has a depth of two; meaning you pass through two variables to reach what you are looking for. The more depth you have in your variable, the slower your program will execute. As we have discussed in previous examples, you should retrieve the element and store it to a local variable. Moreover, if you are dealing with DOM, those retrieval times are much more slower. So, I suggest you to use local variables as often as you can.
When you load the page, all collections are stored in an HTML Collection object which understands all the updates on DOM manipulation. As a result, we have a very slow access(because it is fat) when we are dealing with this object which is everywhere. For instance, when we call getElementsByTagName, it returns us an HTML Collection. Using these collection variables is so slow and should be avoided. Let see this by an example.

As you can observe, HTML is dynamic i.e. when you change any element, it updates itself automatically but costly. When we create and append an element, we lose performance because browser calculates new position, size and etc. of div each time. Instead, we can use HTML fragments and append what we have created like a batch operation. Here is an example.

Throughout my journey, I have tried to explain some basic key points to have faster codes. The basic idea generally is to use local variables, use less Library support and do DOM manipulation in a right way.


  1. Kedar Kedar

    Nicely done. Really liked “createDocumentFragment” technique.

  2. james james

    “Nowadays, there is no page that does not include some JavaScript code in it”
    – there probably is, but I take your point as metaphor sir.

  3. Ramona Ramona

    Wow, I did not know much of the performance tips here. Thanks for sharing.

Leave a Reply

Your email address will not be published. Required fields are marked *