You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
According to this study, most users will not benefit from images with a DPR > 2. And pretty much zero users will benefit from a DPR > 3. This suggests:
At a minimum it is probably safe to remove any devices with dppx > 3 from the default devices list.
It may also be a good idea to remove any devices with dppx > 2.
Though as the study mentions, a dppx 2 image served on a dppx 3 screen might still be visibly reduced if the user is closer than an arm's length to the device. Worth weighing this concern against the bandwidth that would be saved sending dppx 3 images to mobile users on a slow connection... But in theory, it's the browser's job to make this calculation, and they will as long as a lower dppx is available. So the main benefit of limiting to 2dppx is reducing 1) build time, 2) size of generated images, 3) size of generated markup / css.
Since scalingFactor already optimizes the size of generated assets, it won't do too much there. But could make it much easier to optimize generated media-queries.
The text was updated successfully, but these errors were encountered:
According to this study, most users will not benefit from images with a DPR > 2. And pretty much zero users will benefit from a DPR > 3. This suggests:
Though as the study mentions, a dppx 2 image served on a dppx 3 screen might still be visibly reduced if the user is closer than an arm's length to the device. Worth weighing this concern against the bandwidth that would be saved sending dppx 3 images to mobile users on a slow connection... But in theory, it's the browser's job to make this calculation, and they will as long as a lower dppx is available. So the main benefit of limiting to 2dppx is reducing 1) build time, 2) size of generated images, 3) size of generated markup / css.
Since
scalingFactor
already optimizes the size of generated assets, it won't do too much there. But could make it much easier to optimize generated media-queries.The text was updated successfully, but these errors were encountered: