Current time: 10-27-2020, 10:45 PM Hello There, Guest! (LoginRegister)

Post Reply 
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
WPT vs. Navigation API
08-02-2012, 04:36 AM
Post: #2
RE: WPT vs. Navigation API
Yes, loadEventStart is the same as WPT's Document Complete. If you run tests on WebPagetest using Chrome or Firefox you can actually see the W3C navigation timing times directly on the waterfalls. There is a pink area that spans the dom content loaded end-start and a light blue area for the load event (end and start). The W3C resource timing data is also in the raw data of the WPT results if you pull those.

They are usually really close but they have been off by a little bit historically as Chrome was not starting the navigation event early enough for the W3C navigation timing (few hundred ms off at most).

Take a look at the distribution of your RUM values to see what the spread looks like. Usually they are all over the place and averages can be influenced like crazy from outliers.
Visit this user's website Find all posts by this user
Quote this message in a reply
Post Reply 

Messages In This Thread
WPT vs. Navigation API - syncopate - 08-01-2012, 11:16 PM
RE: WPT vs. Navigation API - pmeenan - 08-02-2012 04:36 AM
RE: WPT vs. Navigation API - syncopate - 08-02-2012, 07:55 PM

Forum Jump:

User(s) browsing this thread: 1 Guest(s)