by Björn Ahrens 4.4 (0 reviews)

WP Performance Pack

Name: WP Performance Pack
Author: Björn Ahrens

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

WP Performance Pack ranks #9,627 among WordPress.org plugins with 400+ active installations, is #115 of 752 in the Language Tools category, a 4.4/5 rating from 0 reviews, and was last updated Mar 28, 2025. Data from WordPress.org, refreshed twice daily — see methodology.

Tested up to WP 6.7 (Current: 7.1)

v2.5.4 Current Version v2.5.4

Updated 1 year ago Last Update on 28 Mar, 2025

Refreshed 7 hours ago Last Refreshed on

#115 of 752 in Language Tools Top 25% by installs No update in over a year

View on WordPress.org

Rank

#9,627

— No change

Active Installs

400+

-70.1%

KW Avg Position

33.5

0.5 better

Downloads

51.3K

+4 today

Support Resolved

— No change

Rating

88%

Review 4.4 out of 5

4.4 (0 reviews)

Next Milestone 500

Total Progress -6700%

400+ 500+

Ranks to Climb

Growth Needed

8,000,000

Active Installs

Pro

Unlock Exact Install Count

See the precise estimated active installs for this plugin, calculated from real-time ranking data.

Exact install estimates within tiers
Track install growth over time
Milestone progress predictions

Upgrade to Pro

Need 6,800 more installs to reach 500+

Rank Changes

Current #9,627

Change

Best #

Upgrade to Pro

Unlock 30-day and 90-day rank history charts with a Pro subscription.

Upgrade Now

Active Installs Growth

Upgrade to Pro

Active Installs 0,000,000+

Growth +0.0%

Peak 0,000,000

Downloads Growth

Downloads

Growth

Peak

Upgrade to Pro

Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.

Upgrade Now

Reviews & Ratings

4.4

0 reviews

Overall 88%

0 (0%)

Security History

Source: WPVulnerability

2 known vulnerabilities on record · 2 in the last 24 months · checked 1 month ago

Apr 9, 2025 UNPATCHED

WP Performance Pack [wp-performance-pack] <= 2.5.4 (unfixed + closed)

CVE-2025-32485 · No fix released
Mar 11, 2025

WP Performance Pack [wp-performance-pack] < 2.5.4 (closed)

CVE-2025-28938 · Fixed in v2.5.4

Track This Plugin

Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.

Start Tracking Free

Plugin Details

Version: 2.5.4
Last Updated: Mar 28, 2025
Requires WP: N/A+
Tested Up To: 6.7
PHP Version: N/A
Author: Björn Ahrens

Support & Rating

Rating: ★ ★ ★ ★ ☆ 4.4
Reviews: 0
Support Threads: 0
Resolved: 0%

Keywords

cdn disable gettext image resizing performance

Upgrade to Pro

Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.

Upgrade Now

Similar Plugins

Adminify – White Label, Admin Menu Editor, Login Customizer

6K+ installs

#2,756

Master Addons for Elementor – Elementor Addons, Widgets, Mega Menu Builder, Popup Builder, Widget Builder & Template Kits

Translate Wordpress with GTranslate

TranslatePress - Translate Multilingual sites with AI Translation

Connect Polylang for Elementor

100K+ installs

#293

WPML Multilingual & Multicurrency for WooCommerce

100K+ installs

#324

View all Language-tools plugins

TL;DR

AI summary of the plugin's readme

This plugin is for WordPress site administrators who want to speed up localization, image handling, and asset delivery without patching WordPress core. It reduces the performance and memory overhead of translation loading, defers thumbnail creation until needed, and offloads images to a CDN with local fallback.

Native gettext support
Dynamic loading of translations
Disable Backend localization
Translation caching via object cache
On-demand intermediate image creation
EXIF thumbnail as source
Regenerate Thumbnails integration
CDN support for images

Frequently Asked Questions

Common questions about WP Performance Pack

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.

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.

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

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.

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!

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.

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.

Most other plugins which allow you to disable widgets just unset the respective widgets in WordPress' global widget list. This doesn't prevent the widgets' code to be loaded. WPPP disables default loading of widgets completely and only loads those files required to create the enabled widgets. Available widgets are detected when the modules settings page is displayed by scanning the wp-includes/widgets folder for any classes extending WP_Widget. It only has a small impact on performance and memory usage but many small improvements can become quite big.