- [Instructor] We haven't really mentioned…that the first API available for web performance…was the Navigation Timing.…And at the time, there were no other ideas…so they created this object-based API,…pretty simple,…that for example if you want to get all the timings…you should just use performance.timings.…And if you want to get one particular timing…of all the ones that we've seen before,…you can just say for example…performance.timing.domInteractive…and that will give you the timestamp,…the unique timestamp in milliseconds…of that particular time.…
But after that API, we've seen that the working group…has created other ideas that we will cover…in the next chapter and all of them…are based on the same interface that we now know…as the performance timeline API.…So that's why now we have a new version…of the Navigation Timing API following the…performance timeline spec.…And that's the level two.…In this case, the performance.timings…object is deprecating,…so it's still there but it's deprecating,…we should stop using it for the future.…
- Understanding the Performance APIs
- Navigation Timing
- Calculate milestones in the Performance Timeline
- Measuring the timing of navigation, resources, servers, and more
- Reading network and device information
- Optimizing code
Skill Level Advanced
Designing Websites for Performancewith Brian Wood43m 32s Intermediate
1. Reactive Web Performance
2. Performance Basics
3. Measure Performance
4. Decision-Making Helpers
5. Execute Code More Efficiently
Next steps1m 31s
- Mark as unwatched
- Mark all as unwatched
Are you sure you want to mark all the videos in this course as unwatched?
This will not affect your course history, your reports, or your certificates of completion for this course.Cancel
Take notes with your new membership!
Type in the entry box, then click Enter to save your note.
1:30Press on any video thumbnail to jump immediately to the timecode shown.
Notes are saved with you account but can also be exported as plain text, MS Word, PDF, Google Doc, or Evernote.