WO2015195407A1

WO2015195407A1 - Method and apparatus for monitoring and determining page load times

Info

Publication number: WO2015195407A1
Application number: PCT/US2015/034842
Authority: WO
Inventors: Curtis Kent Shrote; Richard Allen Norman
Original assignee: Thomson Licensing
Priority date: 2014-06-19
Filing date: 2015-06-09
Publication date: 2015-12-23

Abstract

Methods, apparatus and a system for monitoring a load time for a web page are provided. A request for a web page from a client device is received at a server. Web bugs are embedded within a code for the web page. The web bugs provide instructions to a client device for providing information to the server. The web page is transmitted to the requesting client device. A first call is received from the client device including information indicative of a start time for rendering the web page. The information indicative of the start time is logged in a memory. A second call is received from the client device including information indicative of an end time for rendering the web page. The information indicative of the end time in a memory is logged. The loading time of the requested web page is determined from the logged information.

Description

METHOD AND APPARATUS FOR MONITORING AND DETERMINING PAGE LOAD TIMES TECHNICAL FIELD OF THE INVENTION

The present disclosure generally relates to systems and methods for monitoring characteristics of a web page, and more particularly, to methods, an apparatus and a system for monitoring and determining a load time for a web page. BACKGROUND OF THE INVENTION

The profitability of many websites is driven largely by online advertising as well as the many features associated with the website. A website that is frequently visited will be more profitable. To attract many users, it is important that users have an excellent user experience that will facilitate multiple views to the website. An important factor associated with user experience is the loading time for a website which can be measured through web analytics data. At present, web analytics data can be collected from cookies or using web bugs.

Often, the web bug uses executable Javascript code to report the content of the respective web page by sending a message with information about the particular page within which the web bug was included. When using this technique, the user's browser sends clickstream data directly to a site analysis application. The HTTP request header, which requests delivery of the web bug, also supplies certain types of information about the client, such as what types of encoding this user agent supports, the IP address of the computer that fetched the web bug, the URL of the page on which the web bug is located, the URL of the web bug, the time the web bug was viewed, the type of browser that fetched the web bug, or a previously set cookie value. Web bugs can be used for advertising, behavioral targeting, and other processes, to gather information about visits to websites.

Graphic User interface (GUI) administration page load time of a Home Router is often a key concern for not only the home users of the device but also the Internet Service Provider (ISP) that fields the device as well as for the host of the web page being loaded. Faster page load times result in high customer satisfaction and fewer customer complaints to ISP call centers. Home routers maintain many parameters that define the operational characteristics of the router but also present real time data concerning the operation and performance of the router.

Some web based companies use web bugs to determine metrics concerning popularity/usage rankings of web sites and content. Normally, the web bug is placed at the end or the beginning to track if a page was accessed. However, there exists no easy solution currently to monitor the performance of a router and the speed at which a web page loads.

SUMMARY OF THE 1NVEN1TON

In one embodiment, a method for monitoring a load time for a web page is provided. A request for a web page from a client device is received at a server. Web bugs are embedded within a code for the web page by a processor. The web bugs provide instructions to a client device for providing information to the server. The web page is transmitted to the requesting client device. A first call is received at the processor from the client device including information indicative of a start time for rendering the web page by the client device. The information indicative of the start time is logged by the processor in a memory. A second call is received at the processor from the client device including information indicative of an end time for rendering the web page by the client device. The information indicative of the end time in a memory is logged by the processor. Optionally, the loading time of the requested web page is determined from the logged information by the processor. In addition, intermediate web bugs positioned at intervals within the web page source code can be installed to track load times of page sub-sections.

In another embodiment, a server for monitoring a load time for a web page is provided. The server includes an input/output port for receiving a request for a web page from a client device. A processor embeds web bugs within a code for the requested web page, the web bugs providing instructions to a client device for providing information to the server. A storage device is connected to the processor. When the processor receives a first call from the client device including information indicative of a start time for rendering the web page by the client device. The processor logs the information indicative of the start time in the storage device. The processor receives a second call from the client device including information indicative of an end time for rendering the web page by the client device and logs the information indicative of the end time in the storage device. The processor determines a loading time of the requested web page from the logged information.

In a further embodiment, a method of monitoring a load time of a web page by a client device is provided. A request for a web page is transmitted at a client device. The web page is received from a server. The web page is rendered on a display at the client device and a web bug indicating a start of a web page within code of the web page is detected. The web bug is executed and a time stamp indicating a start time of rendering the web page is attached to metrics captured based on instructions within the web bug. The metrics including the time stamp are provided to the server. A web bug indicating an end of a web page is detected within code of the web page. The web bug is executed and a time stamp indicating an end time of rendering the web page is attached to metrics captured based on instructions within the web bug. The metrics including the time stamp are provided to the server and a loading time of the requested web page is determined based on the metrics provided to the server.

BRIEF DESCRIPTION OF THE DRAWINGS

These and other aspects, features and advantages of the present disclosure will be described or become apparent from the following detailed description of the preferred embodiments, which is to be read in connection with the accompanying drawings. In the drawings, like reference numerals denote similar elements throughout the views:

FIG. 1 depicts a high level block diagram of a system for monitoring a load time for a web page in accordance with an embodiment of the present principles;

FIG. 2 depicts a high level block diagram of an apparatus for monitoring a load time for a web page by a web page host in accordance with an embodiment of the present principles;

FIG. 3 depicts a flow diagram of a method for monitoring the load time for a web page in accordance with an embodiment of the present principles; and

FIG. 4 depicts a flow diagram of a method for monitoring the load time for a web page in accordance with an alternate embodiment of the present principles.

It should be understood that the drawing(s) is for purposes of illustrating the concepts of the disclosure and is not necessarily the only possible configuration for illustrating the disclosure. DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

Embodiments of the present principles advantageously provide methods, an apparatus and a system for monitoring and determining a load time of a web page. Although the present principles will be described primarily within the context of a host server and a specific client device, the specific embodiments of the present principles should not be treated as limiting the scope of the invention. It will be appreciated by those skilled in the art and informed by the teachings of the present principles that the concepts of the present principles can be advantageously applied by any access device or content rendering device, such as but not limited to, a server, a gateway, a router, a content playout device and the like.

In the claims hereof, any element expressed as a means for performing a specified function is intended to encompass any way of performing that function including, for example, a) a combination of circuit elements that performs that function or b) software in any form, including, therefore, firmware, microcode or the like, combined with appropriate circuitry for executing that software to perform the function. The present principles as defined by such claims reside in the fact that the functionalities provided by the various recited means are combined and brought together in the manner which the claims call for. It is thus regarded that any means that can provide those functionalities are equivalent to those shown herein.

Moreover, all statements herein reciting principles, aspects, and embodiments of the present principles, as well as specific examples thereof, are intended to encompass both structural and functional equivalents thereof. Additionally, it is intended that such equivalents include both currently known equivalents as well as equivalents developed in the future, i.e., any elements developed that perform the same function, regardless of structure.

The functions of the various elements shown in the figures can be provided through the use of dedicated hardware as well as hardware capable of executing software in association with appropriate software. When provided by a processor, the functions can be provided by a single dedicated processor, by a single shared processor, or by a plurality of individual processors, some of which can be shared. Moreover, explicit use of the term "processor" or "controller" should not be construed to refer exclusively to hardware capable of executing software, and can implicitly include, without limitation, digital signal processor ("DSP") hardware, read-only memory ("ROM") for storing software, random access memory ("RAM"), and non-volatile storage. Moreover, all statements herein reciting principles, aspects, and embodiments of the invention, as well as specific examples thereof, are intended to encompass both structural and functional equivalents thereof. Additionally, it is intended that such equivalents include both currently known equivalents as well as equivalents developed in the future (i.e., any elements developed that perform the same function, regardless of structure).

Thus, for example, it will be appreciated by those skilled in the art that the block diagrams presented herein represent conceptual views of illustrative system components and/or circuitry embodying the principles of the invention. Similarly, it will be appreciated that any flow charts, flow diagrams, state transition diagrams, pseudocode, and the like represent various processes which may be substantially represented in computer readable media and so executed by a computer or processor, whether or not such computer or processor is explicitly shown.

Furthermore, because some of the constituent system components and methods depicted in the accompanying drawings can be implemented in software, the actual connections between the system components or the process function blocks may differ depending upon the manner in which the present principles are programmed. Given the teachings herein, one of ordinary skill in the pertinent art will be able to contemplate these and similar implementations or configurations of the present principles.

In the claims hereof, any element expressed as a means for performing a specified function is intended to encompass any way of performing that function including, for example, a) a combination of circuit elements that performs that function or b) software in any form, including, therefore, firmware, microcode or the like, combined with appropriate circuitry for executing that software to perform the function. The disclosure as defined by such claims resides in the fact that the functionalities provided by the various recited means are combined and brought together in the manner which the claims call for. It is thus regarded that any means that can provide those functionalities are equivalent to those shown herein.

Embodiments of the present principles are directed towards methods, an apparatus and a system for determining and tracking the load time of a web page as well as the load time for sub-sections of the web page. In various embodiments of the present principles, in order to time the load time of a web page, web bugs are installed at the start of the web page source code, analogous to the starting of a stop watch, at the end of the web page source code, analogous to the stopping of a stop watch and at intervals within the web page source code. The intermediate web bugs positioned at intervals within the web page source code can be installed to track load times of page sub-sections. In accordance with various embodiments of the present principles, the web bugs can be installed both at the beginning and at the end of at least one page within the Graphic User Interface (GUI) administration pages in order to determine page load times, for example, within a testing environment and potentially within a fielded real user environment. Additionally, intermediate web bugs can be installed to track load times of page sub-sections. The web bugs provide the capability of relaying several key metrics including but not limited to:

1 - the access time of the page (start of page web bug);

2 - the aggregate amount of time that it took for the server to create and send the data and for the client device to render the webpage (end of page web bug);

3 - if the webpage was entirely loaded (if both start and end web bugs were triggered the page load was successful); and

4 - performance of sub-section load times (example: sections containing statistical real time data concerning, in this case, browser metrics that must be pulled from the hardware).

If these data points are logged to a server, then the data can be further aggregated in order to develop trends which can lead to at least the following improvements and efficiencies:

1 - speed improvements;

2 - detection of browser defects (incomplete page loads, long load times due to memory leaks, hardware router over-loading, poorly designed APIs, etc.); and

3 - determination of rank order popularity of specific pages which can feed back to ISPs concerning web data value added.

FIG. 1 depicts a high level block diagram of a system 10 for monitoring a load time for a web page in accordance with an embodiment of the present principles. The system 10 of FIG. 1 illustratively includes a web server 20 for creating and sending a web page and a user or client device 30 for rendering the web page, connected together via the internet 40. When a user at a client device 30 is interested in downloading a web page, the user submits a request for the web page, for example, by typing the web page address in an address bar of a browser on the client device 30. When the request for the web page is made as indicated by the arrow labeled 50 in FIG. 1 , the request is communicated to the web server 20 via the internet 40 as indicated by the arrow labeled 60 in FIG. 1. In one embodiment of the present principles, in response to the request, the web server 20 transmits a signal including the requested web page including web bugs embedded therein to the client device 30 via the internet 40 as indicated by the arrows labeled 70 and 80 in FIG. 1. Upon receipt of the signal including the requested web page, the client device 30 begins downloading the web page. As previously described, embedded within the signal being downloaded by the client device 30 are web bugs, in one embodiment, in the form of instructions requesting certain files. In response to the downloaded instructions, a call back to the web server 20, indicated by the reference numerals 90 and 100 in FIG. 1 , is made via the internet 40. The call back to the web server 20, in one embodiment of the present principles, communicates metrics as well as a time stamp. The instructions embedded in the web bug can indicate the beginning or end of the web page being downloaded by the user. Additional instructions can indicate positions within the signal identifying certain sub-sections within the web page. Upon receipt of these instructions, the web server 20 logs the receipt of the call back from the client device 30 including the time stamp.

Upon initiating the download, the client device 30 is instructed to call back to the web server 20 to communicate a signal including metrics and a time stamp indicating the start of the download by the client device 30. Upon receipt of this call back, the web server 20 logs the time stamp indicating the start of the download. Upon completing the download of the web page, the client device 30 is again instructed to call back to the web server 20 to communicate a signal including metrics and a time stamp indicating the end of the download by the client device 30. Upon receipt of this call back, the web server 20 logs the time stamp indicating the end of the download. The web server 20 is able to determine the load time of the web page by the client device 30 from these log entries generated by instructions in the web bugs. In alternate embodiments of the present principles, upon detecting web bugs during the downloading of certain sub-sections of the web page, the client device 30 is instructed to call back to the web server 20 to communicate a signal including metrics and a time stamp indicating the start and end times of the download of the respective sub-sections by the client device 30.

Upon receipt of such a call back, the web server 20 logs the time stamp indicating the start and end times of the download of the respective sub-sections. This allows the web server 20 to monitor the load times of sub-sections of the web page that are of interest to the web server 20. Additionally in various embodiments of the present principles, the client device 30 can also provide to the web server 20 an access time of the page (start of page web bug); the aggregate amount of time that it took for the web server to create and send the data; the time it took for a client browser to render the webpage (end of page web bug); and information indicating whether the webpage was entirely loaded. From the determined load times, the system 10 is able to determine the typical performance of the user base fielded environment using real time data to determine typical load times. The load time provides information on how fast users are rendering the respective web page and allows for a host or a web developer to adjust the web pages to load quicker so they are more amenable to users. The load times also provide information regarding the performance of the browser at the client device 30.

In various embodiments of the present principles, the web bugs can be implemented in a variety of technologies such as java script tags, html, etc. Examples of typical html formats for web bugs embedded within a web page are as follows:

A web bug indicating the start of a web page can be formatted as: i! ¾[SM§i§jHQJ5rociiJ¾lD

A web bug indicating the end of a web page can be formatted as:

in accordance with embodiments of the present principles, any parameters that would be of use for metric collection can be included after the '?' in the URL. in various embodiments of the present principles, when a user or client device 30 accesses a GUI administration page, i.e., "Page A", the page can have a web bug embedded therein. An example for the format of such a web bug can include: ctiD

The triggering of such a web bug results in an entry being placed in a log of an external server, i.e., the host/web server 20, representing the start of a web page load. As the web page continues to load, several intermediate sub-sections can be stamped with a load time. Examples of formats for web bugs embedded within the web page to monitor the load time of these sub-sections can include:

When the web page completes loading, a final web bug is executed triggering placement of an entry in a log of an external server, i.e., host/monitor 20, representing the end of a web page load. An example of a format for the web bug indicating the end of a web page load can include:

The exemplary formats for the web bugs presented above are for purposes of example only. The web bugs of the present principles can take numerous different forms other than those shown above. The form of the web bug can also be dependent on a number of different factors including the technology used to implement the web bug.

FIG. 2 depicts a high level block diagram of an apparatus for monitoring a load time for a web page by a web page host in accordance with an embodiment of the present principles. The host/web server 20 of FIG. 2 illustratively comprises a processor 220 as well as a memory 230 for storing control programs, instructions, software, data, web bug information and the like. The processor 220 cooperates with conventional support circuitry 240 such as power supplies, clock circuits, cache memory and the like as well as circuits that assist in executing the software routines stored in the memory 230. As such, it is contemplated that some of the process steps discussed herein as software processes can be implemented within hardware, for example, as circuitry that cooperates with the processor 220 to perform various steps. The host/web server 20 of FIG. 2 also contains input-output circuitry 250 that forms an interface between the various respective functional elements communicating with the server 200. As noted throughout this disclosure, the memory 230 can be a hard disk storage device, a static RAM, a DRAM, ROM, etc., or combinations of the same.

Although the host/web server 20 of FIG. 2 is depicted as a general purpose computer that is programmed to perform various control functions in accordance with the present invention, the invention can be implemented in hardware, for example, as an application specified integrated circuit (ASIC). As such, the process steps described herein are intended to be broadly interpreted as being equivalently performed by software, hardware, or a combination thereof.

In the embodiment of the host/web server 20 of FIG. 2, the processor 220 cooperates with the input/output circuitry 250 for receiving requests for, for example, web pages and calls from client devices 30 upon detection of web bugs. When the processor 220 receives a request for a web page, it creates and/or sends the web page to the requesting client device. As described above, when the processor 220 receives a call from a client device 30, the processor logs the time stamp included in the call in the memory 230. The processor will log the time stamp included with each call back and use the logged time stamps to determine how long individual client devices take to render a web page.

FIG. 3 depicts a flow diagram of a method for monitoring the load time for a web page in accordance with an embodiment of the present principles. More specifically, FIG. 3 provides a flow diagram describing a method performed at a client device for tracking the load time of a web page and/or page sub-sections. The method 300 begins at step 310 during which a request for a web page is transmitted to a server. For example, in various embodiments of the present principles, this can be accomplished automatically upon opening up of a web browser on an internet connected user/client device, typing an IP address in the address bar of a browser, selecting a link on a web page, initiating a search for a web page, etc. The method 300 can then proceed to step 320. At step 320, the requested web page is received. The method 300 can then proceed to step 330.

At step 330, the requested web page is downloaded and rendered on a display. The method 300 can then proceed to step 340.

At step 340, as downloading and rendering of the page is initiated, it is detected, in one embodiment, by the browser, if a web bug denoting the start of a web page is embedded within the web page. If a web bug denoting the start of a web page is not detected, rendering continues at step 340 until a web bug is detected or the page finishes loading. If a web bug is detected in step 340, the method 300 can then proceed to step 350.

At step 350, the web bug is executed and metrics concerning the start of the loading of the current web page are captured. That is, in one embodiment of the present principles, the client device attaches time stamp indicating a start time of a rendering of the web page to the metrics. The method 300 can then proceed to step 360.

At step 360, a signal including the metrics and time stamp are communicated to the web server. The web server logs the metrics and time stamp. That is, in one embodiment, execution of the web bug includes the client device attaching a time stamp to the metrics and transmitting the metrics conceming the start of loading of the current web page to the web server for logging the data. The method 300, can then proceed to step 370.

At step 370, as rendering of the web page continues, it is detected if a web bug denoting an end of the loading of the web page is embedded within the web page. If metrics of a web bug denoting an end of the web page are not detected in step 370, the web page continues to be rendered until a web bug denoting the end of a web page is detected or the page finishes loading. If a web bug denoting an the end of the web page is detected, the method 300 can then proceed to step 380.

At step 380, the web bug is executed and a time stamp indicating an end time of a rendering of the web page are captured. That is, in one embodiment of the present principles, the client device attaches time stamp indicating an end time of a rendering of the web page to the metrics. The method 300 can then proceed to step 390.

At step 390, a signal including the metrics and time stamp are communicated to the web server. The web server logs the metrics and time stamp. The method 300 can then be exited or alternatively can proceed to optional step 395 during which the load time of the web page is determined.

In alternate embodiments of the present invention, at least one intermediate metric checkpoint can be embedded within the web page, In such embodiments, web bug denoting at least one intermediate checkpoint can be detected as described above for start and end web bugs.

FIG. 4 depicts a flow diagram of a method for monitoring the load time for a web page in accordance with an alternate embodiment of the present principles. More specifically, FIG. 4 provides a flow diagram describing a method performed at a web server for tracking the load time of a web page and/or page sub-sections. The method 400 begins at step 410 during which a web server receives a request for a web page from a client device. The method 400 can then proceed to step 420.

At step 420, the web server embeds web bugs within the code for the web page, the web bugs providing instructions to a client device for providing information to the server. In embodiments of the present principles, such information includes information identifying at least a start of the web page and an end of the web page and, optionally, at intermediate positions within the web page identifying the start and end positions for sub-sections of the web page of interest. The method 400 can then proceed to step 430.

At step 430, the web server transmits the web page including the embedded web bugs to the requesting client device. As downloading of the page is initiated by the client device, the client device detects the embedded web bugs denoting the start of a web page and executes the web bug. The client device attaches a time stamp to the metrics and calls (communicates information to) the web server. The method 400 can then proceed to step 440.

At step 440, the web server receives a first communication from the client device comprising metrics including the time stamp indicating a start time of a loading of the web page. The metrics indicating the start time of loading of the web page can alternatively be captured by a web server, other than the primary content server, tasked with receiving web bug traffic. The web server capturing the metrics is determined by the embedded code within the web page code which directs the server to which the metrics are transmitted. The method 400 can then proceed to step 450.

At step 450, the web server logs the information indicative of the start time in a memory. The method 400 can then proceed to step 460. B

At step 460, the web server receives a second communication from the client device comprising metrics including at least a time stamp indicating an end time of the loading of the web page. That is, as the web page continues to load, the client device continues to render the web page and can detect web bugs denoting an end time of loading the web page and/or intermediate metric checkpoints. Upon detection of web bugs, the client device determines if the detected web bugs identify the end of the loading of the web page. A time stamp is attached to the metrics by the client device and transmitted to the web server. The method 400 can then proceed to step 470.

At step 470, the web server logs the information indicative of the end time in a memory. The method 400 can then be exited or proceed to optional step 480.

At optional step 480, the web server determines a loading time of the requested web page from the logged information.

In alternate embodiments of the present principles, the method 400 can further include optional step 452 during which the web server receives a communication from the client device comprising metrics including at least a time stamp indicating an intermediate checkpoint in the loading of the web page and optional step 454 during which the web server logs the information indicative of the intermediate checkpoint in a memory.

Although embodiments which incorporate the teachings of the present disclosure have been shown and described in detail herein, those skilled in the art can readily devise many other varied embodiments that still incorporate the principles of the teachings herein. Having described preferred embodiments of methods, an apparatus and a system for monitoring and determining a load time of a web page (which are intended to be illustrative and not limiting), it is noted that modifications and variations can be made by persons skilled in the art in light of the above teachings. It is therefore to be understood that changes may be made in the particular embodiments of the disclosure disclosed which are within the scope of the disclosure as outlined by the appended claims.

Claims

1. A method of monitoring a load time for a web page comprising:

receiving, at a server, a request for a web page from a client device;

embedding web bugs within a code for the web page, the web bugs providing instructions to a client device for providing information to the server;

communicating the web page to the requesting client device;

receiving a first communication from the client device including information indicative of a start time for a rendering of the web page by the client device;

logging the information indicative of the start time in a memory;

receiving a second communication from the client device including information indicative of an end time for a rendering of the web page by the client device; and logging the information indicative of the end time in a memory.

2. The method of claim 1 , comprising:

receiving a communication from the client device including information indicative of at least one intermediate checkpoint in the rendering of the web page by the client device; and logging the information indicative of the at least one intermediate checkpoint in a memory.

3. The method of claim 1 , comprising:

determining a loading time of the web page using the logged information.

4. The method of claim 3, wherein determining comprises using information received from the client device to determine at least

a) an access time of the page;

b) an aggregate amount of time for the server to create and send the data;

c) an aggregate amount of time for the client device to render the webpage;

d) whether the webpage was entirely loaded; and

e) performance of sub-section load times,

5. The method of claim 4, further comprising using data resulting from the determining to perform at least one of improving a loading speed of the web page, detecting browser defects and determining a popularity rank order of web pages.

6. The method of claim 1, wherein the step of embedding includes embedding one of a java script tag or html code within the code for the web page.

7. The method of claim 6, wherein the one of the java script tag or html code is embedded at a start of the code for the web page and an end of the code for the web page.

8. The method of claim 7, further comprising embedding the one of the java script tag or html code at intermediate points within the code for the web page identifying a start and end point for a sub-section of the web page.

9. An apparatus for monitoring a load time for a web page comprising:

a memory for storing at least one of program routines, web page load time information and data;

a processor for executing said program routines;

said apparatus configured to:

receiving a request for a web page from a client device;

embedding web bugs within a code for the web page, the web bugs providing instructions to a client device for providing information to the server; transmitting the web page to the requesting client device; receiving a first communication from the client device including information indicative of a start time for a rendering of the web page by the client device;

logging the information indicative of the start time in a memory;

receiving a second communication from the client device including information indicative of an end time for a rendering of the web page by the client device; and

logging the information indicative of the end time in a memory.

10. The apparatus of claim 9, wherein a web bug includes at least one of a java script tag and a html code.

11. The apparatus of claim 9, wherein web bugs embedded request a start time and an end time for rendering of the web page.

12. The apparatus of claim 9, wherein the web bugs embedded request a start time and an end time for rendering of sub-sections within the web page.

13. A method of monitoring a load time of a web page by a client device, comprising:

transmitting a request for a web page at a client device;

receiving the web page from a server;

rendering the web page on a display at the client device;

detecting a first web bug indicating a start of a web page;

executing the first bug and including a time stamp indicating a start time of a rendering of the web page in first metrics captured based on instructions within the first web bug;

providing the first metrics including the time stamp of the start time to the server;

detecting a second web bug indicating an end of a web page;

executing the second web bug and attaching a time stamp indicating an end time of a rendering of the web page in second metrics captured based on instructions within the second web bug; and

providing the second metrics including the time stamp of the end time to the server.

14. The method of claim 13 comprising:

determining a loading time of the requested web page based on the metrics provided.

15. The method of claim 14, further comprising:

detecting a web bug indicating a start of a sub-section of a web page within the code of the web page;

executing the web bug and attaching a time stamp indicating a start time of the sub-section to metrics captured based on instructions within the web bug;

providing the metrics including the time stamp to the server;

detecting a web bug indicating an end of a sub-section of a web page within the code of the web page;

executing the web bug and attaching a time stamp indicating an end time of the sub-section to metrics captured based on instructions within the web bug; and providing the metrics including the time stamp to the server.

16. The apparatus of claim 15, wherein the web bug being executed includes one of a java script tag or html code.