Yoav Weiss has been working on mobile web performance for longer than he cares to admit, on the server side as well as in browsers. He now works as part of Google Chrome developer relations team, helping to fix web performance once and for all.
He takes image bloat on the web as a personal insult, which is why he joined the Responsive Images Community Group and implemented the various responsive images features in Blink and WebKit. That was his gateway drug into the wonderfully complex world of browsers and standards.
When he’s not writing code, he’s probably slapping his bass, mowing the lawn in the French countryside, or playing board games with his family.
Taking Back Control Over Third-party Content
We have a complex love-hate relationship with the third-party content on our sites, and it has taken a turn for the worse. On the one hand, third-party content often pays the bills. On the other hand, recent developments have increased its “cost.” HTTP/2 means third-party content is even more of a performance burden than before; the weight of that content is taking up an ever larger percentage of our site’s overall bytesize; ad-blockers mean users have had enough; and projects like Google AMP and Facebook Instant Articles mean that embedders feel the same. Our lack of control over what third parties are doing on our sites is showing. How can we gain it back?
Yoav Weiss explores mitigation tactics as well as a long-term plan to restore sanity to the ecosystem, arguing that we need mechanisms that put developers back in the driver’s seat as well as smarter ad blockers so that responsible third parties can remain a source of income.