If the dimensions of an image element are already known (e.g. specified with the width/height attributes, inline in the style attribute, etc.) then there's no need to issue a range request for the first chunk of the image. This should help improve performance since there will be less of these range requests competing for network resources.

This would also help reduce the number of additional requests that get sent to servers when LazyImages is enabled.

This would also mean that a different solution for measuring data savings will be needed, since Chrome won't be able to use the response headers on the range response.