WD07-2 reads:

Success Criterion - Third-party Implementation (Machine Testable)

Third-party content (including plugins, widgets, feeds, maps, carousels, etc) should be placed behind a click-to-load delay screen (using the "import on interaction" pattern), while alternatives to automated solutions such as chatbots should be offered.

I wonder if we could quantify when third-party is such that click-to-load screen saves data?

Ideas:

• “if the third-party content weighs more than x% of the page” (that way a tool could calculate?)
• maybe we need to also define what third-party is, an obvious example seems to be loading Google Maps in an iframe… is it maybe along the lines of 'content that uses script to load content from a third party'?
• include 'chatbots' (or 'chat widgets'?) into list of examples of third-party content, and make the last bit something like 'while alternatives are offered, for instance a link to a contact form as an alternative for a chat widget' ?