Because of business pressure, we're trying to make it faster. Planning suffers and many things are not counted. For example, it is easy to forget about productivity and, at some time, to face the fact that the weaker cars and tablets of movable elements are scary and slowing down in convulsions. Let's see what we can do if you've encountered this problem or wanted to avoid it.
Let's start from a distance with that thing you read all this. Most screens update the image around 60 times a second, and it creates an illusion of motion. Every update, the image changes slightly, so we think all the changes are smooth. In fact, it's about footage like a movie.
If the image (in our case, the web page) fails to depict, we can find out that it's moving, the melting's gone, and we're missing footage. In order to show 60 personnel within 1 second (1000ms), we need to show a new staff in about 16, 6 ms. In other words, if we see traffic surges, a new image can't paint for 16 milliseconds.
In order to identify the problem, we need to consider the stages of how the browser creates a page and understand what the processor is doing instead of useful and necessary activities. The whole page collection process is described in detail in the work of Tali Garciele, " How the browser works " . If it's easier, the browser's downloading the html and cs on the nodes, shapes trees, combines them, and calculates how each knot should look.
There are two further processes:
- Layout - the position and size of the elements shall be calculated.
- Paint - The styles are applied and the elements are identified directly.
When you change something on the page, the browser has to reread and update the changed elements. In itself, the rewriting of elements is expensive in processor time, and it needs to be avoided without unnecessary need.
We can make sure we look at the Chrome Dev Tools and use the Timeline.