Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>If you use Firefox, you can install <a href="http://en.wikipedia.org/wiki/Firebug" rel="nofollow noreferrer">Firebug</a> and use the profiler. </p> <p>You can read more about it in <em><a href="https://stackoverflow.com/questions/267618/understanding-firebug-profiler-output">Understanding Firebug profiler output</a></em>, and there is a tutorial in <em><a href="http://michaelsync.net/2007/09/09/firebug-tutorial-logging-profiling-and-commandline-part-i" rel="nofollow noreferrer">Firebug Tutorial – Logging, Profiling and CommandLine (Part I)</a></em>.</p> <p>If you use Internet Explorer, you can use <a href="http://ajax.dynatrace.com/ajax/en/" rel="nofollow noreferrer">dynaTrace Ajax edition</a>. </p> <p>Read more about it in <em><a href="http://blog.dynatrace.com/2009/11/17/a-step-by-step-guide-to-dynatrace-ajax-edition-available-today-for-public-download/" rel="nofollow noreferrer">A Step-by-Step Guide to dynaTrace Ajax Edition, available today for public download </a></em>.</p> <p>There's also a <a href="http://blog.chromium.org/2009/06/developer-tools-for-google-chrome.html" rel="nofollow noreferrer">built-in profiler in Google Chrome</a> that you can play around with.</p> <p>Both these solutions will help you narrow down what JavaScript function calls are the most costly, and with repeated profilings you will be able to see the effect your changes has.</p> <p>Using tools like these will not only make you a better programmer (if you take the lessons to heart, and avoid the same mistakes they point out in the future), they will also give you a new appreciation of what happens in your code, since you will get a behind-the-scenes glimpse you haven't seen before ;)</p> <p>Also, if you don't know <a href="http://developer.yahoo.com/yslow/" rel="nofollow noreferrer">YSlow</a>, like Wazzy is talking about - get to know it... maybe your problem isn't even slow JavaScript code :)</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload