Leveraging the power of service design to boost web performance
summary
Case study of a professional development site that spent $2.5M reveals specific failures: homepage shows 3.5s first paint (desktop) and 4s (mobile), with 12s time to interactive (desktop) and 15s time to interactive (mobile); portal pages are worse. Causes are unminified CSS/JS, static assets fetched per page, excessive JavaScript execution, huge network payloads and marketing-requested high‑res images/12 fonts. Service‑design audit maps end‑to‑end journeys, then targets fixes: minification, caching/CDN, asset strategy, and earlier cross‑team inclusion of developers and support.
AI-written summary · about
chapters (6)
- 0:00Intro
- 1:43Whats the issue
- 3:19What is service design
- 6:14Service design with performance audit
- 12:35User centric metrics
- 15:35What next
related talks
40m“Performance by Design”
25mGetting your Team Passionate About Web Performance to Achieve Performant Web Apps
39mGiving you ways to increase, but also explain site performance, to your boss.
23mPerformance Optimizations for Progressive Web Apps
29mWeb Performance Kinetosis
32mEverything you need to know about Web Performance
29mHigh Performance in the Critical Rendering Path
36mNobody cares about web performance. It's hard, expensive and unneeded