by Bjoern 1 (0 reviews)

Fast Translate

Name: Fast Translate
Author: Bjoern

Faster WordPress localization with cache support.

Fast Translate ranks #44,230 among WordPress.org plugins with 10+ active installations, is #322 of 833 in the Language Tools category, a 1/5 rating from 0 reviews, and was last updated Dec 12, 2019. Data from WordPress.org, refreshed twice daily — see methodology.

Tested up to WP 5.3 (Current: 7.1.4)

vtrunk Current Version vtrunk

Updated 6 years ago Last Update on 12 Dec, 2019

Refreshed 1 week ago Last Refreshed on

#322 of 833 in Language Tools Top 50% by installs No update in over a year

View on WordPress.org

Rank

#44,230

— No change

Active Installs

10+

-37.5%

KW Avg Position

— No change

Downloads

3.8K

+1 today

Support Resolved

— No change

Rating

20%

Review 1 out of 5

1 (0 reviews)

Next Milestone 20

Total Progress 50%

10+ 20+

21,057

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 5 more installs to reach 20+

Rank Changes

Current #44,230

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

1.0

0 reviews

Overall 20%

0 (0%)

Track This Plugin

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

Start Tracking Free

Plugin Details

Version: trunk
Last Updated: Dec 12, 2019
Requires WP: 4.0+
Tested Up To: 5.3
PHP Version: N/A
Author: Bjoern

Support & Rating

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

Keywords

l10n localization performance speed translation

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,757

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

#294

WPML Multilingual & Multicurrency for WooCommerce

100K+ installs

#330

View all Language-tools plugins

Frequently Asked Questions

Common questions about Fast Translate

Any persisten object cache will do, but it has to be supported in your hosting environment. Check if any caches like APC(u), 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.

Yes

Fast Translate overrides WordPress' default implementation by using the override_load_textdomain hook. It uses a complete rewrite of WordPress' MO imlementation. The default WordPress implementaion loads a complete mo file whenever a single translation from it is needed. This needs quite some time and even more memory. Fast Translate features on demand loading. It doesn't load a mo file until the first translation call to that specific textdomain (so does WordPress since version 4.6). 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 Fast Translate with an installed and activated object cache, translations get cached using WordPress Object Cache API. Front end pages usually don't use many translations, so for all front end pages one cache is used per textdomain. Back end pages on the other hand use many translations. So back end 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 back end 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.