New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use third-party-web's definition for 3P entities #7474
Comments
Just ran the numbers again, it's 88.22% of 3rd party script execution time. It's very top heavy so I've identified 99 entities that are 88.22% and the last 12% is spread across ~661 domains. If we need more coverage, I could keep going there 👍 |
can you share your bigquery scripts?
90% coverage sg.. Though we're using script execution time as the coverage metric. What if instead we use frequency reported in uses-long-cache-ttl details as the coverage metric? nahmean? |
The bigquery scripts are all in https://github.com/patrickhulce/third-party-web/tree/master/sql :)
or |
good call.
|
I published https://www.npmjs.com/package/third-party-web#npm-module It exposes I added a lot more entities based on the network requests query, but network requests are more spread out than script execution, so we have ~72% coverage at the moment. The top 50 entities get us 68% coverage, and the next 70 only get us 4% more...
|
(this is so awesome)
|
Btw forgot to update here but I've also exposed slimmer version of the package. You can do |
https://github.com/patrickhulce/third-party-web/blob/master/data/entities.json
We can use this for the 3rd party report filter and lightwallet/budgets.
Patrick said it accounts for 90% of JS execution on non-first-party origins, based on HTTPArchive data. 👍
(I imagine there may be a few blinds spots for requests that don't have JS execution.... ones that would show up in our Caching audit, e.g. We can take a look later)
The text was updated successfully, but these errors were encountered: