Bjoern

WP Performance Pack is your first choice for speeding up WordPress core the easy way, no core patching required. It features options to improve localization performance and image handling (faster upload, reduced webspace usage). Combined with CDN support for images, both on Frontend and Backend, this offers similar image acceleration as <a href="http://jetpack.me/support/photon/" rel="nofollow ugc">Jetpack’s Photon</a>.
<h4>Features</h4>
Improve localization performance
Translating WordPress is slow and uses much memory because by default WordPress loads all translations upon each request. WPPP improves performance and memory usage by using native gettext or dynamic loading of translations. If an object cache is installed optional caching improves performance even further.
<ul>
<li>Use of PHP gettext extension if available.</li>
<li>Dynamic loading of translation files, only loading and localizing used text.</li>
<li>Disable Backend localization while maintaining frontend localization (with optional override by user)</li>
<li>Caching of translations to further improve performance. A persistent object cache has to be installed for this to be effective.</li>
</ul>
Improve image handling
Create intermediate image sizes on demand not on upload.
<ul>
<li>Don’t create intermediate images on upload, instead dynamically create intermediate images when accessed.</li>
<li>Choose to save intermediate image sizes or to recreate them upon each access. Created images can be saved into a folder different from the original images folder.</li>
<li>Use EXIF thumbnail (if available) as source for thumbnail images. This improves memory and cpu usage as the source for the thumbnail is much smaller.</li>
<li>Adjust quality settings for intermediate images.</li>
<li>Regenerate Thumbnails integration: Hook into the thumbnail regeneration process to delete existing intermediate images. Supported plugins: <a href="https://wordpress.org/plugins/regenerate-thumbnails/" rel="ugc">Regenerate Thumbnails</a>, <a href="https://wordpress.org/plugins/ajax-thumbnail-rebuild/" rel="ugc">AJAX Thumbnail Rebuild</a>, <a href="https://wordpress.org/plugins/simple-image-sizes/" rel="ugc">Simple Image Sizes</a></li>
</ul>
Disable WordPress default widgets (BETA)
Really disable WordPress’ default widgets. Other plugins which allow you to disable WordPress default widgets only hide them, but the widgets’ files will still be loaded. WPPP really removes the widgets: Files of disabled widgets won’t get loaded.
CDN support
<ul>
<li>Serve (dynamically generated) images through CDN. Applies to all images uploaded via media library both on frontend and backend. No need to save thumbnails locally.</li>
<li>Fallback to local serving if CDN fails to return a valid response.</li>
<li>Dynamic image links: Image urls are generated dynamically when displaying post content.</li>
<li>Supported CDNs: CoralCDN, MaxCDN, Custom</li>
</ul>
Change or deactivate WordPress features
<ul>
<li>Disable header elements, such as generator name, feed links and more</li>
<li>Change heartbeat settings</li>
<li>Disable edit lock</li>
<li>Disable emoji support</li>
<li>Use persistent database connection</li>
</ul>

WP Performance Pack

Boost WordPress performance: Faster localization, (on the fly) dynamic image resizing and CDN support for images.

Delicious Brains

Brad Touesnard

Image Processing Queue is an alternative to on-the-fly (OTF) image processing (e.g. <a href="https://github.com/syamilmj/Aqua-Resizer" rel="nofollow ugc">Aqua Resizer</a>) 
for WordPress themes.
Like OTF image processing, it allows theme developers to define image sizes for specific theme 
contexts rather than defining a size for all uploaded images. This greatly reduces the number of 
resized images and hence reduces disk space usage and the wait time when uploading an image.
Image Processing Queue differs from OTF image processing in how it behaves when an image doesn’t 
exist yet. OTF generates the image right away and the end-user has to wait for the image to be 
generated. With Image Processing Queue there’s no waiting. It immediately returns an image that 
already exists (that is the closest fit to the image size requested) and adds the image size to 
a queue. Image sizes are quietly generated in the background using <a href="https://github.com/A5hleyRich/wp-queue" rel="nofollow ugc">WP Queue</a>.
Image Processing Queue also accommodates responsive themes much better than OTF. It allows theme 
developers to define a list of image sizes that will work best for their theme’s responsive 
breakpoints. Images generated by Image Processing Queue are added to the post meta so that WordPress 
core’s responsive functions will automatically add them to the <code>srcset</code> and delete them from the 
filesystem when the image is deleted from the Media Library.

Image Processing Queue

It works!

tbh, it took me a few minutes to fully understand how this library would benefit my workflow and my clients - but once I started to grasp the changes in development and how I wouldn't be running Regenerate Thumbnails every time I needed a new image size, it clicked!

I think with some more detailed documentation and usage examples this could be a near perfect solution to the image size problem in many themes and plugins.



This could be a game changer!

Real intresting approach and something that should be considered for WP Core - especially the Batch Processing Stuff isn#t only useful for images ...

WP Performance Pack vs Image Processing Queue