This document discusses automated browser performance testing. It describes measuring the perceived performance of specific interactions for a single user through tools like Chrome DevTools. The author discusses challenges of browser performance testing, such as network times, JavaScript execution, reflows, and on mobile browsers. The author also describes designing a JIRA browser performance test suite called Soke that defines timed sections and interactions to test JIRA performance and catch issues. The document emphasizes the importance of quantitative performance testing, being holistic in approach, and maintaining vigilance to address performance issues.