This plugin hasn’t been tested with the latest 3 major releases of WordPress. It may no longer be maintained or supported and may have compatibility issues when used with more recent versions of WordPress.

WP Performance Pack


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 Jetpack’s Photon.


CDN support

  • 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.
  • Fallback to local serving if CDN fails to return a valid response.
  • Dynamic image links: Image urls are generated dynamically when displaying post content.
  • Supported CDNs: CoralCDN, MaxCDN, Custom

Improve image handling

  • Don’t create intermediate images on upload.
  • Dynamically create intermediate images on access.
  • Either save or cache created images for fast subsequent access.
  • 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.
  • Adjust quality settings for intermediate images.
  • Regenerate Thumbnails integration: Hook into the thumbnail regeneration process to delete existing intermediate images. Supported plugins: Regenerate Thumbnails, AJAX Thumbnail Rebuild, Simple Image Sizes

Improve localization performance

  • Simple user interface to automatically set best available settings
  • Dynamic loading of translation files, only loading and localizing used strings.
  • Use of PHP gettext extension if available.
  • Disable Backend localization while maintaining Frontend localization.
  • Allow individual users to reactivate Backend localization via profile setting.
  • Just in time localization of javascript variables (requires WordPress version >= 4.7.4).
  • Caching of localizations to further improve translation performance. A persistent object cache has to be installed for this to be effective.
  • Debug Bar integration

Change or deactivate WordPress features

  • Disable header elements, such as generator name, feed links and more
  • Change heartbeat settings
  • Disable edit lock
  • Disable emoji support
  • Use persistent database connection


  • Enable only required modules. (v2.0)
  • Improved image handling, simple view (v.20)
  • Improved image handling, advanced view (v2.0)
  • Improve localization performance, advanced view (v2.0)
  • Change or disable WordPress features, advanced view (v2.0)
  • Debug Bar integration (v1.0)
  • MO-Dynamic benchmark: Comparing front page of a "fresh" WordPress 3.8.1 installation with active apc cache using different configurations. As you can see, using MO-Dynamic with active caching is just as fast as not translating the blog or using native gettext. Benchmarked version 0.6, times are mean of four test runs measured using XDebug.


Requires PHP >= 5.3 and WordPress >= 3.8.1

  • Download, install and activate. Usage of MO-Dynamic is enabled by default.
  • Gettext support requires PHP Gettext extension and the folder wp-content/wppp/localize must be writeable for php.
  • Caching is only effective if a persisten object cache is installed
  • Debugging requires Debug Bar to be installed and activated


Installation Instructions

Requires PHP >= 5.3 and WordPress >= 3.8.1

  • Download, install and activate. Usage of MO-Dynamic is enabled by default.
  • Gettext support requires PHP Gettext extension and the folder wp-content/wppp/localize must be writeable for php.
  • Caching is only effective if a persisten object cache is installed
  • Debugging requires Debug Bar to be installed and activated
How do I check if caching works?

Caching only works when using alternative MO implementation. To check if the cache works, activate WPPP debugging (requires Debug Bar) Plugin). This adds the panel WP Performance Pack to the Debug Bar. Textdomains using MO_dynamic implementation show information about translations loaded from cache. If no translations are getting loaded from cache, cache persistence isn’t working.

Which persisten object cache plugins are recommended?

Any persisten object cache will do, but it has to be supported in your hosting environment. Check if any caches like APC, XCache, Memcache, etc. are installed on your webserver and select a suitable cache plugin respectively. File based object caches should work always and might improve performance, same goes for data base based caches. Performance gains depend on the available caching method and its configuration.

Does WPPP support multisite?

Localization improvements are supported on multisite installations. When installed network wide only the network admin can see and edit WPPP options.
Image handling improvements are only available if WPPP is network activated

What’s the difference between Dynamic Image Resizer and WPPPs dynamic images?

In previous versions, WPPPs dynamic image resizing feature was based on Dynamic Image Resizer, at first with only some improvements. The first big change was a completely different way to serve the dynamically created images (using rewrite rules instead of the 404 handler), including support for the latest WordPress features. Since WPPP version 1.8 the way how creation of intermediate images at upload works also changed completely. Dynamic Image Resizer did prevent this by using different hooks called at upload. WPPP now overrides the registered image editors (those didn’t exist when Dynamic Image Resizer was written) to only create the necessary metadata. This is way more robust and also works when editing images with WordPress.

According to its author, Dynamic Image Resizer is intended only as a proof of concept. You might say, WPPPs dynamic image feature is the working implementation of that proof of concept.

Dynamic links broke my site, how do I restore static links?

Your first try should be the button « Restore static links » in WPPP settigns advanced view. That function will also be executed on deactivation of WPPP.
If any errors occur (please post them in the support forums so I can try to improve the restore function), you can execute the following SQL query manually to restore the static links:

UPDATE wp_posts SET post_content = REPLACE ( post_content, ‘{{wpppdynamic}}’, ‘http://your.base-url/wp-content/uploads/’ )

You have to change the base URL (third parameter of REPLACE) to your uploads URL!

How localization improvements work

WPPP overrides WordPress’ default implementation by using the override_load_textdomain hook. The fastest way for translations is using the native gettext implementation. This requires the PHP Gettext extension to be installed on the server. WPPPs Gettext implementation is based on Bernd Holzmuellers Translate_GetText_Native implementation. Gettext support is still a bit tricky and having the gettext extension installed doesn’t mean it will work.

As second option WPPP features a complete rewrite of WordPress’ MO imlementation: MO_dynamic (the alternative MO reader). The default WordPress implementaion loads the complete mo file right after a call to load_textdomain, whether any transaltions from this textdomain are needed or not. This needs quite some time and even more memory. Mo_dynamic features on demand loading. It doesn’t load a mo file until the first translation call to that specific textdomain. And it doesn’t load the entire mo file either, only the requested translation. Though the (highly optimized) search for an individual translation is slower, the vastly improved loading time and reduced memory foot print result in an overall performance gain.

Caching can further improve performance. When using MO_dynamic with activated caching, translations get cached using WordPress Object Cache API. Frontend pages usually don’t use many translations, so for all Frontend pages one cache is used per textdomain. Backend pages on the other hand use many translations. So Backend pages get each their own individual translation cache with one base cache for each textdomain. This base cache consists of those translations that are used on all Backend pages (i.e. they have been used up to admin_init hook). Later used translations are cached for each page. All this is to reduce cache size, which is very limited on many caching methods like APC. To even further reduce cache size, the transaltions get compressed before being saved to cache.

How dynamic image resizing works

Images don’t get resized on upload. Instead intermediate images and respective meta data are created on demand. WPPP extends all registered image editors to prevent creation of intermediate image sizes by overriding the multi_resize function. As the classes get extended dynamically this should work with any image editor implementation. Serving the intermediate sizes is done using rewrite rules. Requests to none existent intermediate images are redirected to a special PHP file which loads only a minimum of necessary WordPress code to improve performance. Redirection is done via htaccess. If the requested file does exists it is served directly.

When a none existend image is requested WPPP checks if the requested image size corresponds to a registered image size (either one of the default sizes « thumbnail », « medium » or « large » or any other sizes registered by themes or plugins). This check also tells WPPP if to crop the image while resizing. Only if this check passes the intermediate image is created. This prevents unwanted creation of thumbnails.


Read all 10 reviews

Contributors & Developers

“WP Performance Pack” is open source software. The following people have contributed to this plugin.


“WP Performance Pack” has been translated into 1 locale. Thank you to the translators for their contributions.

Translate “WP Performance Pack” into your language.

Interested in development?

Browse the code, check out the SVN repository, or subscribe to the development log by RSS.



  • [dynimg] Bugfix in wp_get_attachment_meta filter
  • [cdn] Bugifx in CDN down warning
  • [mo-dynamic] Futher performance improvements
  • [mo-dynamic] Added improvements by @mte90
  • [jit] Support for WordPress 4.8.1 added


  • [jit] Support for WordPress versions prior to 4.7 removed
  • Text and translation changes


  • [jit] Bugfix: Some scripts failed to localize.
  • [wpfeatures] NEW! Heartbeat frequency added.


  • [mo-dynamic] Bugfix: Translations using context failed.
  • text and readme changes


It’s been quite a while since the last update and meanwhile I reworked many parts of WPPP without releasing any updates or keeping a changelog. So the following is a very incomplete list of changes made since the last released version 1.10.4. Be cautious when using on a multisite installation. Version 2.0 isn’t testet on multisite yet.

  • [wpfeatures] NEW! New module « WP Features » allows to change or disable WordPress features, e.g. emoji support and edit lock, header elements
  • [dynimg] NEW! EXIF support for ImageMagick.
  • [dynimg] NEW! All registered image sizes are supported regardless of image metadata.
  • [dynimg] NEW! On upload no intermediate image metadata is created. Only when dynamically created intermediate images are saved to disc, the respective size information is added to image metadata.
  • [jit] Added support for WordPress versions 4.7.4, 4.7.5 and 4.8.