Changes between Initial Version and Version 1 of Ticket #57238, comment 8
- Timestamp:
- 02/02/2023 07:49:22 PM (21 months ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #57238, comment 8
initial v1 3 3 4 4 **File Size:** The HTML output provides a `srcset` and the web browser tries to get the smallest possible variant to saturate its needs. With the implicit assumption that a smaller image dimension is by tendency also smaller in file size. To fulfill the end goal: Consume as little network bandwidth as necessary for a fast loading time. There is no filesize stated per variant in the srcset b/c of that implicit assumption. Otherwise the srcset standard would probably have provided a means to indicate filesize-in-bytes per each img variant. Needing a little less of client-side image scaling (and hence RAM/GPU) may be a small benefit for low end devices, but negligible. **The main goal of Responsive Images is definitely asset loading speed**. How to achieve that sized images are smaller in file size too? 5 1. **Sophisticated:** By in depth analysis of perceptive quality in the input and then creating the output similarly too (but never higher)?5 1. **Sophisticated:** By in depth analysis of perceptive quality in the input and then creating the output similarly too, but never unnecessarily higher. 6 6 - ❌ Certainly not in Core. Too sophisticated. There are plugins which send the images via API to external specialized SaaS, e.g. https://wordpress.org/plugins/wp-smushit/ 7 7 2. ** By best practises:** Which ensure that the sized versions are by tendency never larger than the input and have a certain agreed-upon quality level.