Site performance at Mister Spex - Lessions learned
summary
Mister Spex isolates customer‑centric metrics (Speed Index, time to first interactive), runs synthetic Chrome-based tests via SpeedCurve every four hours emulating an iPhone 6 or Moto G4 on slow 3G, and finds the critical rendering path dominates impact. Removing one blocking third‑party tracker yields 2.5s faster pages and a measured 9% conversion uplift. Discovery of a misbehaving pixel that blocks render for >20s drives daily third‑party monitoring, SLAs with upper/lower limits, and plans to add real‑user monitoring later.
AI-written summary · about
chapters (8)
- 0:00Mister Spex introduction
- 1:29Why site performance matters
- 4:45Engineering KPIs to customer metrics
- 8:25Critical rendering path
- 15:09Synthetic performance tests
- 19:31Hardware and third-party impact
- 23:12Performance as company process
- 26:05Summary and Q&A
related talks
18mWebsite performance from user perspective
57mHigh Performance Mobile
39mGiving you ways to increase, but also explain site performance, to your boss.
55mI Feel the Need for Web Page Speed
21mState of Performance
24mWeb Speed in Perfection
29mWeb Performance Kinetosis
30mFast Fashion - How Missguided Revolutionised their Approach to Site Performance