Now that you have implemented caching into your application, learn what performance gains this has given you.
- [Instructor] Now that we have cached all … of our static assets, … we need to check that we've actually improved … the performance of our application … so we need to profile it. … Before we made any changes, … the load times of the application running on my machine, … were 142 milliseconds for the first page load … and 129 milliseconds for subsequent page loads. … We need to take a measure of both … because the browser has its own cache, … which will make a difference here. … I've also included the DOM and the load times, … although they shouldn't change very much. … So let's go to the browser and have a look at … what our application does. … Now, first of all, … we'll do a hard refresh with no service worker installed. … So we can see what would happen loading the application … for the first time. … Here, we can see we get a finish time … of 143 milliseconds similar to before DOMContentLoaded 53 … and a load time of 144. … All similar to what we saw before. … This is because there's nothing in cache …
Skill Level Advanced
Web Programming Foundationswith Morten Rand-Hendriksen58m 44s Beginner
1. Front-End Performance Tools
- 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.