Actually your process seems pretty easy to automate. Reload a page until you get the minimum set needed to reproduce the current DOM.

With JavaScript in play, even reloading the exact same page might yield a different DOM

Or corporate websites where something as simple as looking at my schedule has a “query run” time

That has exponential complexity, is network-bound (slow) and still doesn't handle many cases (for example a "current DOM" where all relative links and images are broken).

Compared to GGP's approach of having a human do it, this is still fast.

Also not sure why you'd want to share a link to a page where all the images and links are broken in the first place.

Should be O(n) unless you're trying to optimize for every single permutation of query param, right? I'd assume the majority of the time the individual params would be independent from one another. Plus you'd only need to do it once in a while for any given base url and persist the result.

If that's what Chrome is doing, verifying that the shortened URL produces the same DOM, then I wouldn't have a problem with that.

Except many pages have unique data on each load

I do the same thing.

That being said, a huge majority of users wouldn't take these extra steps.