Interpretation of Web page Diagnostics Web Subdivision diagram

Web Page Diagnostics (hereinafter referred to as WPD), this is a very important part of the LR analysis, to make it clear that this section of the content will let you take a lot less detours, many environmental problems can be through it to locate, such as the client, the network. Through it you can be better to locate the problem of the environment or the application itself, of course, more importantly, the Web page itself problems.

Web Page Diagnostics: Page diagnostic diagram, also called page decomposition General diagram

Page decomposition shows how a particular transaction responds to the test process, and then analyzes whether the related transaction is running properly. The file structure under this view is broadly similar to a series of client requests such as Actions/transaction/web_url (or submit_form_request) in scripts, which is a three-tier architecture. Transactions is composed Web Page DiagnosticsThe most basic unit of the view. The user can right-click on transaction and then go to Web Page diagnostics for  The transaction interface, which analyzes the pages below this transaction. There are two points to note: 1) If the transaction structure has more than one level, such as Action/load_home_page, then the user will only be allowed to enter the child directory Load_home_page, Even if the user selects the action system, it automatically jumps to the subordinate directory. 2) for a page request under a transaction, LR provides an operation that is either a break or a view page in browser.  because Web_url function is loads the specified Web page (GET request), So there will be a request to return multiple times, the content returned from the server includes but not limited to HMTL, pictures, script files, and generated two request links. For example, the request to open the Web Tours home page:  web_url ("Webtours", "url=http://127.0.0.1:8080/webtours/", "resource=0", "Reccontenttype =text/html "," referer= "," Snapshot=t2.inf "," mode=html ", last);  response from the server: http://127.0.0.1:8080/ Webtours/http://127.0.0.1:8080/webtours/welcome.pl?signoff=truehttp://127.0.0.1:8080/webtours/images/hp_ logo.pnghttp://127.0.0.1:8080/webtours/home.html...  and submit login account  web_submit_form ("login111.pl",  " Snapshot=t3.inf ", itemdata, " Name=username "," Value=zhutao ", enditem, " Name=password "," Value= Zhutao ", enditem, " name=login.x "," value=55 ", enditem, " NAME=LOGIN.Y "," value=3 ", enditem, last); Although the requested URL address is not explicitly specified here,It is also equivalent to sending a request (login request) to the server, so it is also possible to get response:http://127.0.0.1:8080/webtours/login.pl-note, the script library that handles the client's request, PL stands for Perl. If your site is using JavaScript, you will need to download a script file with a. js suffix. http://127.0.0.1:8080/WebTours/login.pl?intro=truehttp://127.0.0.1:8080/WebTours/images/flights.gifhttp:// 127.0.0.1:8080/webtours/images/signoff.gif...  Web Page Diagnostics ViewFurther refinements can be made in the following four ways: Download time Breaddown (Download period breakdown) Component breakdown (Over time) (component breakdown (varies over times) Download temporal breakdown ( Over time) (download time breakdown (over the period) breakdown time to primary buffer (over time) (first time breakdown of buffers (varies over times) The Web page Diagnostics General diagram is based on transaction analysis, taking into account the preliminary analysis of the page.   The following seven charts are the further refinement of the Web page Diagnostics view, as can be seen from the name, is that the primary parsing object is the next level of the transaction-the page.

• page Component breakdown:  

  The average response time for each element in the page is the percentage of the total page response time

• Page Component breakdown (Over time): in

  During the entire test, the response times for each element in the page (for example, browser cache is set in runtime) The resource files on the page will only be downloaded for the first time, and the subsequent page response time will not include the time of these elements, which is not visible in page Component breakdown, because page Component breakdown is the average time during the entire test period. Of course, if the cache is enabled, you can see it through the over time graph)

• Page Download time Breakdown : The response times for each element in the page is split, The response time is divided into the following sections: DNS resolution,connection,first buffer,ssl handshaking,receive,ftp authentication,client,error
• Page Download time breakdown : During the entire test process, the response times of each element in the page are divided by a graph
• time to first buffer breakdown: The first buffer is split into network times and The client HTTP request is sent to the receive server-side reply packet (ACK) for network time, from the receive to ACK to complete first buffer accepted as server time
• time to first buffer Breakdown (Over time): basic above, any second of
• downloaded Component size (KB): size of each element in the page (KB)

Introduced so much, how to analyze it concretely?

First open the Web Page Diagnostics diagram and take a look at the following example download time graph:

There are two problems:

1, receive time is very long

This is generally a network problem, of course, if you confirm that the network is not a problem, then you have to look at the client is not a problem (the client may also cause the receive too long, this must be noted)

2, page problems

The page contains a lot of pictures, and the picture does not seem to be optimized, the biggest unexpectedly has 163K, write down, this is the evidence Oh;)

Many times, you can see if there is a network problem according to the dns,connection,receive, according to the client to determine whether there is a customer problem.

Look, it's quite simple! ^_^

Take a look, Page Component breakdown (over time)

It is clear that the page elements have been cache, indicating that the scene enabled the browser cache, the page response time only includes the red and blue lines.

Time to first Buffer breakdown, the diagram is not affixed, this diagram is very important, but also the most complex, where the value is not absolute, when the network condition is not good, the server time is likely to include network times, Because many page elements are smaller (less than 4k), the transfer is done in first buffer, so be sure to pay attention to the analysis.

Interpretation of Web page Diagnostics Web Subdivision diagram