third-party-web
Version:
Categorized data on third party entities on the web.
15 lines (11 loc) • 1.18 kB
Markdown
A shortcoming of the attribution approach has been fixed. Total usage is now reported based on the number of _pages_ in the dataset that use the third-party, not the number of _scripts_. Correspondingly, all average impact times are now reported _per page_ rather than _per script_. Previously, a third party could appear to have a lower impact or be more popular simply by splitting their work across multiple files.
Third-parties that performed most of their work from a single script should see little to no impact from this change, but some entities have seen significant ranking movement. Hosting providers that host entire pages are, understandably, the most affected.
Some notable changes below:
| Third-Party | Previously (per-script) | Now (per-page) |
| ----------- | ----------------------- | -------------- |
| Beeketing | 137 ms | 465 ms |
| Sumo | 263 ms | 798 ms |
| Tumblr | 324 ms | 1499 ms |
| Yandex APIs | 393 ms | 1231 ms |
| Google Ads | 402 ms | 1285 ms |
| Wix | 972 ms | 5393 ms |