- [Narrator] At the beginning of the course…we mentioned that, we do have now…new metrics to measure web performance.…Such as thirst meaning full paint.…But how can we measure that in the browser…for our real users.…There is a new API on top of the performance API…that is not yet available on every browser.…It has started in chrome, we just call the Paint Timing API.…Its as good idea to use it with performance observers…and not directly with get entries like type,…because we don't know when that will happen.…
So this is then the Paint Timing API.…Am going to create an observer for it.…So its going to be the paint observer,…new performance observer the same as before.…That we'll receive a list.…That's an error function.…And then we are going to observe for the entrytypes…that its paint.…Here we might have a problem.…Because if you try to observe of an invalid entrytype…for example, in the browsers there is not compatible…with that API, this will throw an exception.…
So when you know that might not be there its a good idea…
- 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.