Now that you have stored your data client side, discover the performance gains you have gotten from it.
- [Instructor] If you have been following … along since the beginning, … you remember that I talked about profiling … and the importance of benchmarking in chapter 1. … Now that we have implemented static file caching … and client side dynamic data storage, … we need to re-profile our application … and compare it to our original benchmarks. … When we started the shop page on my machine, … took 218 milliseconds to load on first page load … and 832 milliseconds on subsequent page loads. … We made some improvements to this using static file caching … in the previous chapter … where we looked at the homepage times. … Now let's smash our application again … and see what improvements indexedDB has given us. … On first page load we've got 891 milliseconds to finish … and 894 to load, so about the same as what we had. … Now on subsequent page loads, … where it's using the static file cache … and the dynamic data in indexedDB, … we should see a performance improvement. … So here we can see now the load is 108 milliseconds …
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.