Automated perf. budgeting into your pipeline w/ sitespeed.io
summary
Shows concrete results: a working Jenkins pipeline that runs Sitespeed.io in Docker with budgets that can fail builds, HTML reports and video artifacts via the HTML publisher, and overrides per-project. Uses waterfall comparisons via compare.sitespeed.io and a private WebPageTest instance to catch regressions, and pushes metrics to Graphite/Grafana for trend monitoring. Mentions Browsertime, Coach, Lighthouse integration, and an experimental network replay and device-farm approach.
AI-written summary · about
chapters (20)
- 0:00Introduction
- 0:47Overview
- 3:12Chilli
- 5:26Bootcamp
- 5:48Performance is hard
- 6:53Fixing issues
- 8:21Performance
- 9:13Slow sites
- 9:33Profit
- 10:54Regression
- 12:09Budget JSON
- 12:32How can perf budgets help
- 13:58What metrics can you budget on
- 16:23Accessibility budgets
- 17:20Performance budgets
- 19:52Write your own perf metrics
- 21:22What happens when you make a mistake
- 27:04Jenkins DSL
- 29:04Other budgeting tools
- 30:25Regression analysis
related talks
42mFrontend Performance Testing and Monitoring with sitespeed.io
37mAutomated Performance Testing With WebDriver
36mProgrammatically Performant
21mThursday Lightning Demo Keynotes
59mFaster Websites with WebPageTest
43mAutomated Performance Testing With WebDriver
57mSite-Speed That Sticks
31mAutomated Performance Testing With WebDriver