Recently, I spent some time analyzing real-world mobile sites. Using the 1000/100/6 performance model 1 and digging into each application, the findings are fascinating.
I have written case study files for each site that contain all the findings.
- Graphical diagnosis of poor performance
- What actions should developers take
- How can Chrome’s tools be improved
- Questions and insights on rendering engine (Blink)
➜ Performance audit. CNet, Time, Google Play
In this document, we looked at CNET scrolling, CNET input latency, some of the very interesting challenges of responsive Time.com, and infinite scrolling for the Google Play desktop site.
The target audience is browser engineers and performance-conscious front-end developers. This is pretty advanced, but I’m digging deeper to determine how these sites work against the browser’s API and architecture.
Finally, we’ll use this research to improve Chrome DevTools and what you hear in your Chrome browser.
The Wikipedia Eng team is checking their performance millisecond by millisecond. Yes, this is a long paper print of Chrome DevTools timeline flames 🙂
BTW, use this link to view the same document, but with comments enabled).
1- More on this performance model in the future. Stay tuned.