Bjoern

Janne Ala-Aijala

Changing the WordPress site language to any other than English slows down page generation times. A lot. This is caused by the slow and inefficient way of text domain loading. PO and MO files are designed to be used with PHP Gettext-extension. But since it’s an extension, it’s not installed by defalt on very hosting platform. To overcome this barrier, WordPress has re-implemented the whole MO file parsing in PHP, but WordPress’ implementation is quite slow and memory intense.
This plugin replaces the default MO-Reader with another implementation of MO parsing, which is faster than the default one. Only used text domains are loaded (since version 4.6 this is also WordPress’ default behaviour) and from these only used translations are loaded. It also makes use of hash tables included in mo files, which are ignored completely by WordPress’ default implementation. To boost the performance even more, the plugin also caches translations to the object cache, if one is installed. For optimal performance you need a fast object cache backend like Redis, Memcached or APC(u).
Fast Translate is a minimalistic fork of <a href="https://wordpress.org/plugins/wp-performance-pack" rel="ugc">WP Performance Packs</a> localization improvements. <a href="https://wordpress.org/plugins/wp-performance-pack" rel="ugc">WP Performance Pack</a> offers additional control and more optimizations for WordPress performance, e.g. use of PHPs native gettext extension, improved image handling and CDN support.

Fast Translate

Faster WordPress localization with cache support.

Sergey Biryukov

Creates a separate tiny .mo file to use on a site front-end. Allows to save some amount of RAM on a shared hosting server.
Thanks to MAX for the original non-plugin solution and to AlexPTS for the idea.

WPLANG Lite

Creates a separate tiny .mo file to use on a site front-end.

Fast Translate vs WPLANG Lite