No, it does not copy them to a table. Any images that are optimized have their full path and filesize recorded in a table to prevent accidental re-optimization of the same image.
Ah I see so it means it records which images have been optimized in a table.
Is there any difference between EWW Image Optimizer and Smush.it..?
Yes, lots. I’ll try to pick some highlights, but many of them are alluded to on the plugin description page:
1. It can run natively on your server, which makes it blazing quick. JPGs can be optimized in mere milliseconds, without the added overhead of an http transfer to Yahoo’s servers, which may or may not even respond.
2. No file-size limits. Smush.it caps images at 1MB. In native/standard mode, there is no limit to file size. The photos aren’t transferred anywhere, so there is no need to limit how large of an image can be processed. The EWWW Cloud service is currently limited to 16 MB, which is just an arbitrary number I picked, haven’t had any requests to increase it (yet).
3. You are not limited to the Media Library. EWWW IO can optimize Theme images, plugins from Nextgen & Grand FlaGallery, and pretty much any plugin out there. It is hooked into the WP_Image_Editor class, so that any plugin generating images using the standard WP methods will be automatically optimized on creation. With the ability to specify custom folders to optimize, you can optimize images created by plugins that don’t do things the ‘proper’ way. You can even schedule the process to run every hour to make sure things don’t get out of hand for those types of plugins.
In short, I’ve worked hard to ensure that EWWW IO is the best image optimization plugin out there, and even better things are coming down the road in the near future.
Hey thanks, more comprehensive reply than I expected..!
Smush.It limit of 1MB is certainly annoying.
I used EWWW on non-media library assets — rather useful..!
Gonna make EWWW my go-to Image Optimizer from now..!
