Find solution
What are the test automation tools that use perl as the scripting language??

What are processes and tools that big name web sites use to test performance of javascript-heavy web sites?

  • There are already a lot of questions about what tools are available. I am more interested in what is actually in use by you, an employee of a highly recognized, highly trafficked site. - What do you do to test client-side, in-browser performance of your web applications? - What are the tools or techniques you use to find JavaScript, HTML, and CSS bottlenecks? - What are your most important metrics? - How do you identify the highest value areas to test? Or do you test absolutely everything?

  • Answer:

    Regarding the first and third question: To test & improve performance the most important thing is metrics. Regardless of the tools you use you need to know whether your performance improvements are working. Thus, you need to measure -at least-: the time it takes to download all the js your site needs to work, the time it takes for a user to receive the first usable chunks and time for page to be done downloading. All these, if possible, should be  measured by browser. If not, you should at least have detailed metrics of browser usage. And now, provided you got all this taken care of you can start using tools to improve problematic spots. Here are the usual suspects: Firebug, page speed, HTML5 timing api, webpagetest. For old browsers like IE7 dynatrace works really well. And fourth question: The highest values areas for the customers are the ones your customers/users use the most. Performance improvement should be done first on your highest traffic pages. The highest performance gains for your company are probably bandwidth reduction and cache hit ratio.

Nuria Ruiz at Quora Visit the source

Was this solution helpful to you?

Other answers

Tackling the 3rd part of your question... I'd argue that your most important metric is your conversion rate.  If you improve your speed, your conversion rate should also go up.  I tend to focus on the "perceived performance" far more than the actual onload time.  Generally speaking, optimizing for a fast onready is far  more valuable than optimizing for a fast onload.

Josh Fraser

You've asked at least 4 questions there - I'll try to address the first. I talk to a lot of companies about load testing and have concluded that every load testing tool is used by a big company somewhere. I've found that the larger companies are likely to use more than one tool - typically one expensive tool that is blessed by the QA group and others that are chosen based on ease of use and cost for individual projects and groups. I have not seen any indication that being "javascript-heavy" has any effect on this trend. Ok, I'll address a few more: The most important metrics for our customers is always the end-users response time (time to receive and render the page). As for testing everything: I've yet to see a project with the budget to performance test absolutely everything.

Chris Merrill

Related Q & A:

Just Added Q & A:

Find solution

For every problem there is a solution! Proved by Solucija.

  • Got an issue and looking for advice?

  • Ask Solucija to search every corner of the Web for help.

  • Get workable solutions and helpful tips in a moment.

Just ask Solucija about an issue you face and immediately get a list of ready solutions, answers and tips from other Internet users. We always provide the most suitable and complete answer to your question at the top, along with a few good alternatives below.