Using the Page Load View

When you create a page load test, you get access to the Page Load view. The Page Load view uses the ThousandEyes standard layout, documented here.

This article highlights specifics shown in the Page Load view.

Example

This example shows the result of a globally distributed page load test against christianmingle.com, a dating site.

View Specifics

As with most pages in the ThousandEyes platform, the Page Load view shows two different views, depending on whether or not a location is selected. Differences are shown below:

  • Without a Location Selected

The computed averages area on this view is more complex than most others. When in the global view (no location selected), it shows the average DOM load and average page load times, followed by a warning if the page load was incomplete from any locations.

If the test obtains a DOM load time but no page load time from one or more locations, the DOM load time is incorporated into the average DOM load, while the average page load has one fewer measurement per incomplete location. Thus, average DOM load can be greater than average page load, even though DOM load time is always less than page load time.

In addition to this, a tabbed interface allows the user to switch between breakdowns of timing between domain and by provider. This can be helpful when you are troubleshooting a slow page load that is dependent on components from other domains.

Without a location selected, the timeline shows the average page load time, calculated from all locations globally. The following image shows an example of a timeline for the page load view:

The detailed metrics area shows a tabular view of by-location metrics for each of the locations used in the test. This includes location name, date and time that the data was collected, total wire size (calculated as the sum of the size of all component sizes as sent on the wire, where compression can be used), throughput (measured by total wire size/fetch time), the number of objects, component errors, and DOM and page load times.

  • With a Location Selected

The computed averages area on this view is more complex than most others. When in the location view (with a location selected), it shows the DOM load and page load times, followed by a warning if the page load was incomplete from any locations.

If the test obtains a DOM load time but no page load time, the DOM load time is displayed.

In addition to this, a tabbed interface allows the user to switch between breakdowns of timing between domain and by provider. This can be helpful when you are troubleshooting a slow page load that is dependent on components from other domains. The only difference from the global view is that the number of objects is shown.

With a location selected, the timeline shows a chart showing page load time for that location, charted against the global average page load times. The following image shows a sample for the page load times with a location selected. As you can see, the agent's data is charted in a blue line, whereas the global data is charted as an area.

When a location is selected in this view, detailed metrics are different from the global view. When a location is selected, the page load waterfall is shown, which includes the object name, domain, provider, size, and a waterfall, including start/end time, and fetch time breakdown for each component loaded. To see the waterfall detail, hover over a specific object's chart, and view the contents.

If an object indicates an error, you can open it directly by clicking the pop-out icon to the right of the name of the object.

A page load waterfall example is shown below.

Waterfall Example