Third Parties (Web Almanac 2022)

	A	B	C	D	E	F
1	e	New Custom Metric Added?	Available in Previous Year?	Query	Link to Results Sheet	Comments
2	Prevalence and structure
3	Third party prevalence by rank	n	y	sql/2022/third-parties/number_of_third_parties_by_rank.sql sql/2022/third-parties/percent_of_websites_with_third_party.sql sql/2022/third-parties/top100_third_parties_by_number_of_websites.sql	percent_of_third_parties_by_content_type.sql number_of_third_parties_by_rank.sql top100_third_parties_by_number_of_websites.sql
4	Content-types	n	y	sql/2022/third-parties/percent_of_third_parties_by_content_type.sql sql/2022/third-parties/percent_of_third_party_requests_and_bytes_by_category_and_content_type.sql	percent_of_third_parties_by_content_type.sql percent_of_third_party_requests_and_bytes_by_category_and_content_type.sql
5	Third-party domains	n	y	sql/2022/third-parties/number_of_third_parties_by_rank.sql	number_of_third_parties_by_rank.sql
6	Third-party requests by type and rank	n	y	sql/2022/third-parties/percent_of_websites_with_third_party_by_ranking.sql	percent_of_websites_with_third_party_by_ranking.sql
7	Performance
8	Third party summary	n	n			WILLL NOT BE DONE. ALREADY COVERED IN ROW 10 AND 11 Results from https://github.com/GoogleChrome/lighthouse/blob/master/lighthouse-core/audits/third-party-summary.js
9	Using third-party domains versus self-hosting	n	n			WILL NOT BE DONE. Not possible to have a query here
10	Popular third-parties and their impact on render	n	y	sql/2022/third-parties/third_parties_blocking_rendering.sql sql/2022/third_parties_blocking_rendering_percentiles.sql	third_parties_blocking_rendering.sql third_parties_blocking_rendering_percentiles.sql
11	Popular third-parties and their impact on main thread	n	y	sql/2022/third-parties/third_parties_blocking_main_thread.sql sql/2022/third-parties/third_parties_blocking_main_thread_percentiles.sql	third_parties_blocking_main_thread_percentiles.sql third_parties_blocking_main_thread.sql
12	Timing-Allow-Origin header prevalence	n	y	sql/2022/third-parties/tao_by_third_party.sql	tao_by_third_party.sql
13	Page weight impact: Heaviest third-parties	n	y	sql/2022/third-parties/top100_third_parties_by_median_body_size_and_time.sql	top100_third_parties_by_median_body_size_and_time.sql
14	Page weight impact: Cacheability	n	y	sql/2022/third-parties/percent_of_third_party_cache.sql	percent_of_third_party_cache.sql
15	Page weight impact: Large redirects	n	y	sql/2022/third-parties/distribution_of_3XX_response_body_size.sql	distribution_of_3XX_response_body_size.sql	content_encoding.sqlcontent_encoding_by_content_type.sqlcontent_type.sql
16	Early-loaders: Are third party scripts loaded after first-party content, i.e. what is their position in tag?	n	n	sql/2022/third-parties/third_parties_blocking_rendering.sql	third_parties_blocking_rendering.sql	There is a query which might be similar to what we are after, but we need to go through the data to make sure it is what we need.
17	Early-loaders: Is async or defer used for third party scripts?	n	n	sql/2022/third-parties/scripts_using_async_defer_by_3p.sql sql/2022/third-parties/scripts_using_async_defer.sql	scripts_using_async_defer_by_3p.sql scripts_using_async_defer.sql
18	Are third parties serving compressed/optimized resources?	n	n	sql/2022/third-parties/content_encoding.sql sql/2022/third-parties/content_encoding_by_content_type.sql	content_encoding.sql content_encoding_by_content_type.sql	We could reuse the query from "Compression" chapter in 2020: https://almanac.httparchive.org/en/2020/compression#first-party-vs-third-party-compression
19	JavaScript (minified/compressed)	n	n	lighthouse_unminified_css_by_3p.sqldistribution_of_lighthouse_unminified_css_by_3p.sql	lighthouse_unminified_js_by_3p.sql distribution_of_lighthouse_unminified_js_by_3p.sql	We can use results from this audit: https://github.com/GoogleChrome/lighthouse/blob/master/lighthouse-core/audits/byte-efficiency/unminified-javascript.js and filter 3Ps in audit result
20	CSS (minified/compressed)	n	n	sql/2022/third-parties/lighthouse_unminified_css_by_3p.sql sql/2022/third-parties/distribution_of_lighthouse_unminified_css_by_3p.sql	lighthouse_unminified_css_by_3p.sql distribution_of_lighthouse_unminified_css_by_3p.sql	This audit could be used: https://github.com/GoogleChrome/lighthouse/blob/master/lighthouse-core/audits/byte-efficiency/unminified-css.js
21	Images (unoptimized)	n	n	sql/2022/third-parties/lighthouse_unminified_uses_optimized_images_by_3p.sql sql/2022/third-parties/distribution_of_lighthouse_unminified_uses_optimized_images_by_3p.sql	lighthouse_unminified_uses_optimized_images_by_3p.sql distribution_of_lighthouse_unminified_uses_optimized_images_by_3p.sql	https://github.com/GoogleChrome/lighthouse/blob/master/lighthouse-core/audits/byte-efficiency/uses-optimized-images.js
22	Best practices
23	Lazy-loading	n	n			Query covers lazy loading of images or iframes but does not distinguish between 3P and 1P. Also some 3P might intentionally not use loading=lazy if they are tracking pixels.
24	Usage of Lite-youtube	n	n	sql/2022/third-parties/usage_of_lite_youtube_embed.sql	usage_of_lite_youtube_embed.sql	Added lite-youtube-embed to Wappalyzer. https://github.com/wappalyzer/wappalyzer/pull/6252
25	Legacy APIs: unload event	n	n	sql/2022/third-parties/percent_of_third_parties_using_unload_listener.sql	percent_of_third_parties_using_unload_listener.sql	Data may be taken from Lighthouse
26	Legacy APIs: document.write	n	n	sql/2022/third-parties/percent_of_third_parties_using_document_write.sql	percent_of_third_parties_using_document_write.sql	Data may be taken from Lighthouse
27	Legacy JavaScript	n	n	sql/2022/third-parties/percent_of_third_parties_using_legacy_javascript.sql	percent_of_third_parties_using_legacy_javascript.sql	Data may be taken from Lighthouse
28	Usage of Partytown	n	n	sql/2022/third-parties/usage_of_partytown.sql	usage_of_partytown.sql
29	Correlation between CLS and 3P	n	n			We have discussed two options. Correlation between image size (pixels) and CLS and width/height attributes on 3P images: https://httparchive.slack.com/archives/C01CRFV97K4/p1653983305597959
30	Sustainability
31	CO2 emissions based on 3rd party script weight	n	n			Source: https://sustainablewebdesign.org/calculating-digital-emissions/
32	Security and privacy
33	Permissions-Policy header	n	n	sql/2022/third-parties/iframe_allow_attribute.sql sql/2022/third-parties/iframe_attribute_popular_hosts.sql	sql/2022/third-parties/iframe_allow_attribute.sql sql/2022/third-parties/iframe_attribute_popular_hosts.sql	We can reuse query from this figure: https://almanac.httparchive.org/en/2021/security#fig-21 It shows how many iframes have `allow` attribute to control feature policy. More info about allow attr: https://developer.mozilla.org/en-US/docs/Web/HTTP/Feature_Policy/Using_Feature_Policy#the_iframe_allow_attribute Also, https://github.com/HTTPArchive/almanac.httparchive.org/blob/main/sql/2021/security/iframe_attribute_popular_hosts.sql basically shows most popular 3Ps within iframes with `allow` attribute.
34	CSP usage	n	n	sql/2022/third-parties/csp_allowed_host_frequency.sql	csp_allowed_host_frequency.sql	There is this query: https://github.com/HTTPArchive/almanac.httparchive.org/blob/main/sql/2021/security/csp_allowed_host_frequency.sql that shows us most popular hosts in CSP. Theoretically this list should match with most popular 3Ps. We can check if it is true.
35	Accessibility
36	a11y tech usage	n	y	sql/2022/third-parties/a11y_technology_usage.sql	a11y_technology_usage.sql	Use data from Wappalyzer. For example, here is the list of popular a11y overlays: https://www.wappalyzer.com/technologies/accessibility/
37	a11y overall usage by domain and rank	n	y	sql/2022/third-parties/a11y_overall_tech_usage_by_domain_rank.sql	a11y_overall_tech_usage_by_domain_rank.sql
38	a11y usage by domain and rank	n	y	sql/2022/third-parties/a11y_technology_usage_by_domain_rank.sql	a11y_technology_usage_by_domain_rank.sql
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100