Fewer Requests Reported for a URL

WhyWhen doreviewing wethe seeStep lesserTimes Report generated from a Designer script, you may notice that the number of requests underreported for a given URL is lower than the number of requests shown in browser developer tools such as Firebug.

For example, when accessing www.appvance.com, Firebug may show 84 requests, while the Appvance IQ Stepreport timesmay Reports?show only 11 requests.

UserThis runsdifference is expected and is caused by how Appvance IQ determines when a designerstep scripthas and generates a Iteration summary / Step times report. In the report there is a column to view Request name, here user see lesser number of request for each action performed. But for same action when looked in Firebug user could see many number of requests.completed.

Example:

Why www.appvance.com,does inthis firebug we see 84 requests for appvance.comhappen?

but in APC report we just see 11 requests.

Reason: Appvance IQ does not wait untilfor lastevery page resource isto loadedfinish inloading before completing a pagestep.

to end

When a particular step. Since the moment the step startsstarts, itAppvance beginsIQ lookinglooks for the element neededrequired andby whenthat itstep. isAs accessiblesoon it executesas the element becomes available, Appvance IQ performs the requested action and passesproceeds to the next step,step.

regardless of

At the ongoingsame time, the browser may still be loading ofadditional css, js, ajax processes, images, etc. that are happeningresources in the background.background, such as:

• CSS files
• JavaScript files
• Images
• AJAX requests
• Other page resources

SoBecause inthese a given execution a particular step might get somebackground requests duringmay continue after Appvance IQ has already completed the timestep, itthey executes,may butnot be associated with that step in the nextStep Times Report.

Why can the request count change between executions?

The requests associated with a step can also vary from one execution theto sameanother.

For example, during one execution, a step mightmay nottake getlong anyenough for several background requests asto itoccur took less time. Therewhile the differencestep is active. Those requests may therefore appear in countthe report.

During another execution, the required element may become available faster. The step completes before those background requests occur, so fewer requests are associated with the step.

Therefore, the number of requests reported for requesta andstep stepsshould andnot be interpreted as the subsequenttotal impact on throughput calculation (sumnumber of allnetwork requests sizes)generated by the page.

This doesbehavior notcan happenalso inaffect protocolmetrics that depend on the request count or total request size, such as throughput calculations.

Protocol-based technologies

This behavior is specific to how browser-based steps are measured. Protocol-based technologies asthat HAR.use a HAR (HTTP Archive) capture network activity at the HTTP level and therefore provide a different view of the requests generated during the transaction.