Capture performance data of certain timing points with in the page load based
on existing Navigation Timing API methods.
The Navigation Timing API is provided
in all modern desktop browsers and most Android mobile browsers.
How to
-
If the timer that you want to capture
applies only to certain pages on your site, enter the URL pattern to match those
pages.
You can use an asterisk as a wildcard to replace one or more characters
(for example, */example/example-abc/*). mPulse looks for the first matching query string
parameter for the page that has a URL pattern match.
Note: For the best results, avoid using a
regular expression in the URL pattern.
-
From the Start and End menus, select the
corresponding timing attributes that you want applied to the timer. You can define a
client-side custom timer using a URL pattern with any of these values.
- Connect Start / Connect End
- Load Event Start / Load Event
End
- DOM Complete
- DOM Content Loaded Event Start / DOM
Content Loaded Event End
- DOM Loading
- DOM Lookup Start / DOM Lookup
End
- DOM Interactive
- Fetch Start
- Navigation Start
- Redirect Start / Redirect End
- Response Start / Response End
- Request Start
- Secure Connect Start
- Unload Event Start / Unload Event
End