21: Web Performance: Content Caching and CDNs

Development Best Practices

In this episode we're happy to welcome back Robert Boedigheimer, Microsoft MVP, Pluralsight Author and MDC Speaker for part two in our series on web perfromance. If you haven't listened to part one, I'd suggest pausing this one and listening to the previous episode, which lays the groundwork for much of what we'll talk about today.
In this episode, Robert and I talk about synthetic vs real user monitoring, how FAST your web page needs to be, content expiration and CDNs. We end by swapping internet topology war stories.
1:10 Synthetic Monitoring vs Real User Monitoring
2:25 How fast does my website need to be?
5:00 Abandonment rate
6:25 Content expiration
9:35 Changing cached content
12:25 Content Delivery Networks
15:40 Types of content in CDNs
16:15 Internet topology war stories
SpeedCurve: https://www.speedcurve.com
Response header to clear browser cache of site resources: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Clear-Site-Data
Google Engineers in a Bar - Bandwidth vs. Latency: https://docs.google.com/a/chromium.org/viewer?a=v&pid=sites&srcid=Y2hyb21pdW0ub3JnfGRldnxneDoxMzcyOWI1N2I4YzI3NzE2&b=2)
Up-to-date browser support tables: https://caniuse.com/
Find Robert at @boedie on Twitter.
Please be sure to listen in a few weeks to Part Three of our web performance series with Robert, which will cover minification, compression, bundling, and the tricky topic of images.
The Development Best Practices Podcast is brought to you by ILM Professional Services. Creating performant web applications is not simple, particularly if this is something you don't do regularly. ILM does a LOT of work creating highly performant web applications - applications that load fast and safely. We'd love to help you - please reach out to us at ilmservice.com so we can discuss how.
Finally, if you like what you heard in this episode, please tell a friend about us. If you have any feedback on this episode or have a topic you'd like us to cover, please email us at [e-mail].