Modern Performance Workflows
summary
Concrete demos of new DevTools plus automation: live use of individual request throttling and annotations, the recorder panel producing replayable scripts, and examples wiring browser automation into a DevTools MCP server or Playwright to capture Lighthouse timespan metrics and traces. CI integration with GitHub Actions and automated pull‑request tests runs end to end; demos work but are sometimes flaky, model‑dependent and cost‑sensitive, so expect practical recipes and caveats rather than magic fixes.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:03Talk goals and scope
- 3:12Lesser-known DevTools features
- 4:35Time spans for user journey testing
- 6:41Recorder panel for performance testing
- 8:06Request throttling in DevTools
- 12:20AI in performance debugging
- 14:47AI assistance panel in DevTools
- 16:52Code suggestions and AI in DevTools
- 18:58MCP servers for browser automation
- 23:30First pass for complex sites
- 29:43Automated Lighthouse time spans
- 33:12Dynamic GitHub Actions prompts
- 38:52Challenges of AI workflows
- 41:03Q&A
related talks
35mOptimise your Web Development Workflow
37mAutomated Performance Testing With WebDriver
21mThe Future of Performance Tooling
31mAutomated Performance Testing With WebDriver
43mAutomated Performance Testing With WebDriver
21mWorking Well, The Future of JavaScript Testing
25mAutomated Performance Testing With WebDriver
43mModern web debugging with devtools