-
Notifications
You must be signed in to change notification settings - Fork 973
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Why not progressive? #54
Comments
Decompression speed of progressive JPEGs is 10-200% slower; the slowdown is worse on underpowered devices. This matters even more when we have an image that is already cached on an underpowered mobile phone. |
If you're more concerned about bandwidth than CPU time, you can use MozJPEG's |
@robryk A website that is properly configured won't be serving small devices full-sized images, so your CPU concern won't have that much impact. Also with HTTP2 PJEPGs could be rendered to screen faster regardless. |
@tomByrer I would argue that a properly configured website will serve high density screens bigger images, if only because they have more pixels to display them. Coincidentally, those screens are often the smaller out there, in phones and tablets. So small devices are likely to get served bigger images than desktops and laptops. |
@JasonMrX If you're using Windows, try jpegtran_do_plus. I found it yesterday and it work well. |
@pieroxy Often mobile will have different 'art direction' (cropping) than a desktop or even 4k site would have. You're correct that DPI should be a concern for many web images; something I intend to address with progressive. A full explanation is worthy of a blog post, not a GH-issues discussion ;) |
Agreed. FYI I wrote a small piece a while back on how to compress images for high-dpi screens. |
hehehe :) |
... and would be much bigger than a lower compression of a non-retina version, so no, it was not my conclusion. :-) |
I thought that image-heavy websites prefer progressive mode than sequential mode (facebook, instagram), etc). I haven't done bench marking myself, but how much faster is sequential mode in terms of decompression speed?
The text was updated successfully, but these errors were encountered: