Previously: corporate crimeblogging in the training set

Andrew Kraft, in Can YOU Say No to Google?, points out that Google is not the first company to make a report on how much the ads are cluttering up and slowing down a site.

This was built with publishers rather than sprung on them. The Chrome team spent the better part of this year talking to publishers of every size before shipping, and what came back was that they would love to be valued on something other than user match, and would believe it when they saw it. It also isn’t the first time somebody graded these metrics.

But now that there’s a Google metric—being offered for free, in a way that’s hard to avoid—that’s the metric. Kind of like how Google Analytics measurements of site traffic might not be the most accurate count, but they’re so widely available that’s what you’re expected to compare across sites. Or Google Core Web Vitals. It’s hooked up to the search rankings, so that’s what sites use.

He quotes Paul Bannister from Raptive saying

Having a single, public source that everyone can look at is better than 30 companies with slightly different standards that publishers can’t get transparency into.

That might be true as of day one, version one. But a publisher running non-Google JavaScript on their site is going to be like an IT manager picking a non-Excel spreadsheet to run on their Microsoft Windows systems. Over time the co-development of

  • Google Chrome’s JavaScript implementation

  • Google’s ad JavaScript

  • Google’s JavaScript performance metrics

are going to converge, and the right answer is going to be that the all-Google setup is the high-scoring one.

Google has been doing anticompetitive tricks all along, even during the antitrust cases. Since the big pivot to crime they haven’t been able to help themselves, it looks like. But now that the (non)remedy in the adtech case is out, they’re really cutting loose.

More later.