McMaster got a lot of attention recently, because of how fast it is compared to what many are used to. Wes Bos made a very nice video about the techniques used to make it fast. The folks from the Next.js community made a clone to show how you can achieve a similar page speed, they called it Next Faster.
BUT. Let's take a different angle and look at what the real world monitoring data says about McMaster's website performance.
- Is it really that fast? ðŸ’
- how are different users affected?
- what can we learn from this data?
- How do we run a performance audit on existing website?
From this perspective I had Erwin Hofman. Erwin is a Google Developer Expert (GDE) on Web performance and he's a lead developer/consultant at RUMvision.com.
In this video we did a live auditing of mcmaster.com and a bit about next-faster.vercel.app. We looked at:
- real world monitoring data and what they mean
- how different users experienced the performance
- what areas could be improved.
This is an opportunity to learn how to audit your own site, interpret the data, and learn web performance best practices.
Top comments (0)