Performant Translations Plugin Now Available on

After an in-depth performance analysis earlier this year revealed that translations can impact server response times, WordPress contributors proposed half a dozen technical solutions for consideration to improve performance for the ~56% of sites that use translations.

Performant Translations, a feature project by the core Performance Team, is now available as a plugin on It incorporates some of the proposed solutions and speeds up translations by converting .mo files to .php files, allowing them to be parsed faster and stored in OPcache.

It supports multiple file formats (.mo.php, and .json) and multiple text domains and locales loaded at the same time. Existing .mo files get converted to .php files which are then loaded by WordPress.

A chart included on the plugin’s details page shows a significant page load time reduction when using the plugin, as compared to sites with translations that don’t use the plugin. The plugin brings translations very close to the same page load times as English (non-translated) sites.

“With enough testing and feedback, we hope to eventually merge this plugin into WordPress core,” Performance Team contributor Pascal Birchler said when announcing the plugin on X.

“In the coming weeks and months we will share more testing instructions and continue to improve the plugin. This will be made available via Performance Lab, too.”

Users who are testing the plugin can report issues on the support forum or create an issue on the GitHub repository.

Performant Translations is considered to be a beta testing plugin but can be tested and used in production at your own risk. It doesn’t require any changes to settings or configuration after installation. The plugin can be safely removed after testing, because it essentially cleans up after itself. All .php files it generates will be removed by the server once the plugin is deactivated and uninstalled.


8 responses to “Performant Translations Plugin Now Available on”

  1. The plugin brings translations very close to the same page load times as English (non-translated) sites.

    If I’ve understood the original discussion correctly, this statement is incorrect – you should be saying “US English sites”. WordPress is available for 7 English variants in total, only US English is the default, non-translated version.

      • I’m Polish. From my experience as a translator and former teacher of English as a foreign language, most people outside the UK don’t really care which variant they use, with some not being aware of the differences at all. It’s quite interesting because an overwhelming number of books for teaching EN focuses on the British variant, but because EU culture is so flooded with US influence, most people I know use a combination of the two… I would even argue – most tend to lean toward US English.

        Not that it matters really, the point is to get the message across.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.


Subscribe Via Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

%d bloggers like this: