JMeter can’t generate real users, only virtual. This happens because every browser has its' own technology of rendering pages while loading. Therefore, we use the browser to discover the system performance that the user will be dealing with. Selenium is the most appropriate tool for this question, because it allows the simulation of the user’s actions in real browser.
What is Selenium? Selenium automates browsers. That's it.
Selenium can be used for creating functional tests for web-based applications; or to automate some of the more mundane administrative activities. Another problem that can easily be solved with the help of Selenium is reproducing real browser performance.
And that is what Selenium is used for by Blazemeter.
So, how it is implemented? Login to Blazemeter with valid account and create a new test. Upload custom test plan in *.jmx format and expand “User Experience Monitoring with Selenium”.
In this case, the specification is for the same landing pages as for the HTTP samples in the test plan.
Save & Start the test as usual. A brief interlude while Blazemeter collect statistics. Then switch to the “Load Report”, ”Real Browser Report” tab.
What did we get?!?!?!
Based on the *.jmx test-plan, each landing page a separate browser will be opened. Note the changing render times while the test is executing. This graph alone will be not enough for the exhaustive analysis of testing process. So, scroll down to the bottom of page, where there is a module (Similar to firebug in Mozilla Firefox). It allows you to observe result of each individual request.
This information should be more than enough to investigate any issues with real-browser performance.
Like any good prophet, BlazeMeter spots n solves issues before they occur.
Download BlazeMeter's free plugin to JMeter
You can download the BlazeMeter plugin to JMeter here. (Make sure you download it to <jmeterdir>/lib/ext.)
Instructions on how to use BlazeMeter's free plugin to JMeter.