-
Notifications
You must be signed in to change notification settings - Fork 110
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
Explore/research MozJPEG #294
Comments
MozJPEG, as in the encoder?? The only research I'm aware of are the ones that were associated w/ the original release announcement in 2014.
Dated, but maybe it helps. |
This is what I found on this topic:
Since MOZjpeg is a fork of the default encoder (jpeg-turbo) hosts need to build and install the encoder replacing the default one.
Yes but we need to recompile PHP with MozJPEG instead of libjpeg Is MozJPEG compression detectable from image meta (if not stripped)? No, afaik isn't possible
Mozjpeg weighs 10% more than Webp at the same SSIM (source) and does not support alpha channel. However, it can be advantageous if the original is an already over-compressed jpg, it seems to degrade the original image less than the competitors, maybe because the same codec
No, afaik isn't possible
I think it's a very specific setup that few people currently have with php (whereas it is much easier with nodejs). I installed it but it is not currently working with Wordpress, I should replace cjpeg (system wide) but don't know if it's worth it, at least for the moment. |
Stumbled upon this issue after reading Is WebP Really Better Than JPEG? by @joppuyo, which compares JPEG, MozJPEG, WebP, and AVIF using the Kodak image dataset at different image sizes (500x, 100px, 1500px).
But as with most things, there were caveats with this test.
|
I wonder why this isn't enabled by default when available? |
Because libjpeg is the default JPEG library in most Linux distributions and other operating systems. If you wanna use MozJPEG, you will need to explicitly install it and recompile ImageMagick/GD using MozJPEG. This is really an issue with the server environment and not the application code so WordPress can’t really influence what’s going on under the hood. It will simply use whatever JPEG library the server administrator has installed. |
Noting here that we should be able to achieve MozJPEG compression using client side image processing, maybe something to explore as part of that work. |
+1 The current solution (wasm-vips) uses MozJPEG under the hood already. |
Feature Description
Contributors have pointed out that MozJPEG compression provides benefits over traditional JPEG compression without the potential compatibility issues WebP present.
The goal of this issue is to research MozJPEG further to evaluate its benefits and see how it can be used in WordPress.
Here are some initial questions to consider:
dssim
from original - level of effort (===energy) to compress/decompress.The text was updated successfully, but these errors were encountered: