Gustav Ernberg von Heijne at performance.sync()
summary
Claims and concrete fixes: adding one second of latency measurably reduces viewable impressions and revenue from a global experiment, a publisher removing 2 seconds → +5% revenue confirms that, and adding a cache header stale-while-revalidate yields ~0.5% more revenue. The ecosystem forces: consent managers, header bidding, BFCache interactions and many third‑party scripts. Tools and outcomes: Chrome DevTools traces and network dependency arrows, the GPT library with new thread‑yielding config options, real experiments run and measurable revenue impact reported.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:06How display ads work
- 3:33Ad performance and revenue
- 5:40Ad serving dependencies
- 7:44Analyzing ads with DevTools
- 8:49Latency impact on revenue
- 10:12Milliseconds vs seconds
- 10:53Publisher latency case study
- 11:55Ad optimization challenges
- 12:58Key takeaways
