Precisely specify the need
The ‘dimensions’ for each feature must be precisely and entirely specified. It may be the image compression rate for the graphic interface, the maximum response time for a HTTP request or the number of items displayed in a list.
By ensuring the ‘dimensions’ and requirements for each feature best fit its purpose, you can avoid unnecessary quality. This is the opposite to usual convention. If it is not specified, the minimum quality or quantity should be used. For example, if the number of items in a list to be displayed is not specified, then it should be limited to 5, or the maximum number of items that can be displayed on the target application’s smallest screen.
Keep DOM access via JavaScript to a minimum
Accessing the DOM (Document Object Model) via JavaScript is a heavy process that uses a lot of processor power (CPU). Minimize this type of access as much as possible.
To do so, you can assign a node to variables that you will repeatedly use in the application’s lifecycle, which avoids traversing the tree each time the document is manipulated.
Libraries such as ‘Shadow DOM’ can also be used to optimize the tree though a batch system.








