Hey Alex,
after digging my head into Angular and SPAs for three years, 2017 brought me back to working on a traditionally architected news site. That's pretty refreshing!
One of my goals for the site is to make it load fast, display fast and be interactive very quickly. That works pretty well: Critical resources are inlined, others and fonts are preloaded but async, and JS is only 60 KB uncompressed.
Sadly all of these measures are rendered alomost useless once advertisement comes in. Advertisers have gone completely amok these days. Performance on the main thread takes a plunge due to:
And that's just the "visible" tip of the iceberg. Ads are huge problem for privacy and security:
The sad thing is: If you allow ads on your site, you open up Pandora's box. You never know what you get. You give off control.
Finally coming to my question (sorry for the long intro):
Apart of the Chrome team's engagement in the Coalition for Better Ads that focuses mostly on UX, do you put any thoughts in measures and standards that help limiting and controling 3rd party? I'd love to see a sandbox attribute for scripts, I'd love to have an API to distribute computing time per origin, I'd love to see iframes using a separate thread, and I'd love if browsers would proactively block a few of the things above so that we as 3rd party "partners" could point to the browser as the bad guy disallowing certain things.
No responses yet.