Request for "profile this device", to put soft limits on codec options

**Is your feature request related to a problem? Please describe.**
Took a screenshot of a webpage on my android device, intending to post it on twitter.
See also any other scenario where a screenshot or recently-taken photograph is to potentially be loaded over a connection with flaky/metered uploads, or scenario where uploading a photo is time sensitive.

**Describe the solution you'd like**
An option *somewhere* to profile the time it takes to compress a device viewport-sized image under common codecs (either providing an example, or by merely taking the current viewport and resizing one of the example images), with a view to placing a soft constraint on codec options known to cause increases in encoding (perhaps with a dialog to proceed/cancel before spinning up a webworker?).
Research-based or user-selected configuration of "soft-block options likely to cause encoding to take longer than X seconds".

**Does other service/app have this feature?**
Unknown.

**Additional context**
example images can be provided, although the context here is with a 720x1280 PNG android device screenshot.

an image that takes an amount of time approaching 1 minute (or more) to encode with optipng on a desktop machine takes an intolerable amount of time to encode on a low-midrange mobile device.

No file, test, or entry point is named. Start by reviewing the profiling proposal for viewport-sized images, common codecs, and slow optipng-style encoding; done would mean profiling informs soft codec limits and a proceed/cancel choice before encoding.

Written by the indexing model from the issue text.