Make your WordPress site speak every language, without slowing it down

Yes. PerfLocale is free and open source under GPL-2.0+. All core features - content translation, string translation, URL routing, language switcher, SEO integration, and 20+ plugin/theme addons - are included at no cost.

Very little. The plugin’s own code typically adds around 1 ms per request on a multilingual site, and stays low even under heavy load (see the measured numbers). Larger sites — many translated posts across many languages — benefit from running a persistent object cache like Redis. PerfLocale is fully compatible with page-cache plugins (WP Super Cache, W3 Total Cache, LiteSpeed Cache, etc.); cached pages already include the translated output from the request that filled the cache. Real-world page speed depends mostly on your theme, hosting, and other plugins.

Yes - PerfLocale is built with privacy-first defaults that help your site stay GDPR-compliant. It integrates with the WordPress Privacy API so translator assignments appear under Tools → Export/Erase Personal Data, ships cookies with httponly / secure / SameSite=Lax flags, and caches GeoIP lookups as country codes only - visitor IP addresses are never stored. A perflocale/privacy/consent_given filter lets consent-management plugins (Cookiebot, Complianz, OneTrust) suppress GeoIP and browser-language redirects until visitors accept non-essential cookies. Review your machine-translation provider’s DPA before enabling that feature; the plugin auto-generates suggested privacy-policy text via wp_add_privacy_policy_content() for every feature you switch on.

Yes. Translate products, variations, categories, and attributes. Inventory syncs automatically across languages. Multi-currency support with automatic exchange rate syncing. Order emails are sent in the customer's language.

Yes. Built-in importers for WPML, Polylang, and TranslatePress read your existing data and rebuild equivalent translation groups in PerfLocale. Your source plugin’s data is read-only during the import, so you can re-run, abandon, or roll back from a backup without risk. Available from PerfLocale → Settings → Export & Import or via wp perflocale migrate <source>.

PerfLocale integrates with Elementor, Beaver Builder, Bricks, and Oxygen. Each builder's content is translatable, and Language Switcher widgets are provided for each.

Yes. PerfLocale detects text direction from the language configuration and works correctly with Arabic, Hebrew, and other RTL languages.

Yes. Each language version has its own URL, so page caches from WP Rocket, LiteSpeed Cache, W3 Total Cache, and others work naturally.

Yes. One-click translation with DeepL, Google Translate, Microsoft Translator, or LibreTranslate. Auto-translate on publish, monthly character limits, and a translation glossary for brand names.

Unlimited. Each language is just a row in the languages table — there’s no built-in cap. Adding more languages adds more URL filters per request, but the per-language cost is small and the caching layers scale linearly.

Yes. Activate network-wide or per subsite. Each subsite keeps its own languages, translations, glossary, and workflow state. New subsites auto-provision on creation; removed subsites clean up on deletion. WP-CLI commands run with --url for per-site scripting.

Yes. PerfLocale uses standard WordPress APIs — no custom database connection, no shell-out, no exotic dependencies — so it runs on every managed host without special configuration. It auto-detects an external object cache (Redis or Memcached) where the host provides one and uses it as the L2 cache layer.

Yes. Every translation is a regular WordPress post, so it appears in the standard /wp-json/wp/v2/ endpoints and in WPGraphQL with no extra work. There’s also a dedicated perflocale/v1/translations endpoint that returns translation groups so your frontend can resolve language alternates without N+1 lookups.

No. PerfLocale emits hreflang tags on every translated page and adds the alternates to your XML sitemap, so Google understands they’re language alternates of the same content rather than competing duplicates. The right URL gets served to each market without splitting search authority.

Yes. Run it on a staging copy — every feature works the same as production. If you’re already on WPML, Polylang, or TranslatePress, the built-in importers let you test a real migration end-to-end without touching your live database. Roll back from a backup if you don’t like the result.