DHTML and JavaScript Performance Tuning
- [ Introduction ]
- [ Designing for Clarity ]
- [ document.write ]
- [ Performance Design ]
- [ Using JS ]
- [ Objects ]
- [ Loops ]
- [ Strings ]
- [ Variables ]
- [ Animation ]
- [ DOM & XML ]
- Conclusion
Conclusion
Design for Code Clarity
So you've read most of this article and hopefully gotten some fresh ideas. Here are a few things to remember.
Code that is well designed is easier to develop, maintain, and performance-tune.
Each aspect of a web page has a different role and when the roles are in order, the web page will be more maintainable and more tunable (performance-wise).
By avoiding document.write, we can eliminate one of the biggest and most common mistakes most JavaScript authors make.
Once we have the proper approach, we can fine tune how our JavaScript performs. We can tune loops, shorten object references, create caches, use local variables, reduce string creation, get better DOM performance, and speed up our animation.
Design is king. Without efficient design, performance tuning is pointless.
Test Often
If you don't test your code, you won't know how fast it is performing. For some more tests, see Wolfgang Schwarz's JavaScript Performance Tests
- [ Introduction ]
- [ Designing for Clarity ]
- [ document.write ]
- [ Performance Design ]
- [ Using JS ]
- [ Objects ]
- [ Loops ]
- [ Strings ]
- [ Variables ]
- [ Animation ]
- [ DOM & XML ]
- Conclusion
AnimTree