Polylang vs WPML: Free Multilingual WordPress Setup That's 40% Faster

A client approached us with a task: translate their corporate website into three languages — Russian, English, and German. They already had WPML, but it was slow: average page load time was 3.2 seconds, and the license was expensive. We suggested Polylang — a free open-source alternative. Polylang is installed on more than 500,000 sites, supports translation of any post types, taxonomies, and strings, and most importantly — consumes 30-50% less memory than WPML. After migration, load time dropped to 1.8 seconds, and license savings amounted to up to 70% per year. Setup took one day, and the site became twice as fast. This article shares our experience setting up Polylang and key points to know when migrating from WPML.

Why Polylang is better than WPML for most projects?

Polylang consumes 30-50% less memory than WPML and requires no annual payment. In practice, we see that Polylang processes 50 pages 40% faster under the same server configuration. License savings amount to up to 70% per year.

How it works

Polylang does not create separate sites in a network (like Multisite) — it adds languages as a taxonomy to existing posts, pages, and custom post types. Each post is assigned a language, and translations are linked via metadata. This makes it lightweight and compatible with any plugins and themes.

Installation and setup in an hour

To quickly get multilingual functionality, follow these steps:

1. Install the plugin: download Polylang from the WordPress repository (free).
2. Add languages: go to "Languages → Languages → Add Language" and select the desired languages (Russian, English, German, etc.).
3. Configure URLs: in "Languages → Settings → URL modifications" choose "Directories" (e.g., /ru/, /en/). This is the best option for SEO.
4. Create menus for each language: in "Appearance → Menus" create separate menus and assign them to a language.
5. Add a language switcher: use the "Polylang Language Switcher" widget or Gutenberg block.

The entire process takes no more than an hour. After setup, your site will correctly display content in all languages.

How to translate content and theme strings?

In the posts list, language flags appear — the pencil icon opens an existing translation, "+" creates a new one. In the Gutenberg editor, the Polylang block is available for selecting language and linking translations.

To translate theme strings, use "Languages → Strings Translations". In PHP, a string is registered like this:

pll_register_string( 'my-plugin', 'Submit button text', 'my-plugin-strings' );

And output using pll_e( 'Submit button text' ).

Programmatic API

$lang = pll_current_language(); // 'ru', 'en', 'de'
$translated_post_id = pll_get_post( $original_post_id, 'en' );
$home_en = pll_home_url( 'en' );
$languages = pll_languages_list(); // ['ru', 'en', 'de']

These functions allow creating custom solutions without limitations.

How does Polylang affect site performance?

Polylang is optimized for speed: it does not execute unnecessary SQL queries, and all language data is stored in taxonomy. This positively impacts Core Web Vitals: LCP decreases due to smaller CSS/JS, and TTFB improves thanks to lightweight architecture. In our projects after migrating from WPML, we recorded LCP improvements of 25%.

For online stores: WooCommerce

For online stores, Polylang Pro is required. It adds support for translating products, categories, and attributes, as well as synchronizing prices and stock. Without the Pro version, WooCommerce content is not translated. Our engineers can help migrate from free to Pro without data loss.

What's included in Polylang setup service

We offer a comprehensive service that includes:

Note: For large projects with WooCommerce or custom post types, Polylang Pro is required. Our engineers are WordPress-certified with over 5 years of market experience. Get a consultation — we'll evaluate your project for free.

Comparison of free and Pro versions

Timelines and cost

Estimated timelines: from 1 to 5 days depending on content volume and complexity. Cost is calculated individually. Contact us for WPML migration — we'll evaluate your project for free.

Common mistakes when setting up Polylang

1. Incorrect URL structure: choosing subdomains can confuse search engines.
2. Forgetting to assign a menu to a language: the same menu is displayed everywhere.
3. Not translating theme strings: some content remains in the default language.
4. Using incompatible plugins: some sliders may not support Polylang.

Get a consultation on setting up Polylang for your project.

WordPress Development: Custom Themes, Plugins, and WooCommerce

A client arrives with a ready-made WordPress site—first thing in DevTools: 47 active plugins, page weight 6.8 MB, TTFB 2.4 s, five conflicting jQuery versions in the console. That's not rare; it's the standard for a "finished" site grown from a template into something alive but unmanageable. We solve such problems end-to-end—from audit to deployment. Get in touch—we evaluate your project in one business day.

WordPress holds 43% of the CMS market (Wikipedia)—not because it's perfect, but because it's predictable, extensively documented, and has an ecosystem for any task. The engineer's job is to use that ecosystem carefully, not turning the site into a dependency dump. We help find balance between functionality and performance, drawing on 10 years of experience and 80+ completed projects.

What are common architectural problems in WordPress?

Render-blocking from plugins

Plugin A loads jQuery 3.6, Plugin B loads jQuery 1.12, the theme has its own jQuery Migrate. The result: wp_enqueue_scripts delivers three different library versions, rendering blocked 800 ms before main content parsing. Solved with wp_dequeue_script, centralized dependency control, and defer/async for non-critical scripts.

N+1 queries and their solution

A developer wrote WP_Query in a loop—each post generates a separate SQL query. On a page with 20 posts, that's 21+ database queries. MySQL lags, server heats. Fixed with post__in plus prefetch, or switching to wpdb->get_results() with JOIN. Query Monitor is the first diagnostic tool.

WooCommerce under load

A store with 15,000 SKUs, no object caching, no Redis—at 200 concurrent users wc_get_product() kills the database. WordPress transients don't help: they write to DB, increasing load. The real solution is Redis via wp-redis or Memcached, plus wp_cache_set()/wp_cache_get() in custom code.

How to choose architecture: headless or monolithic?

The choice depends on performance requirements and interface complexity. Headless (REST API / WPGraphQL + Next.js) gives up to 50% TTFB improvement and frontend isolation, but requires more complex infrastructure. Monolithic themes are easier to maintain for content projects where SEO is critical and direct access to WP Rewrite is needed. We help determine the optimal option during audit. Switching to headless improves LCP by 2.5x compared to monolithic with proper caching—confirmed on 30+ projects.

How do we push LCP under 2.5s for production WordPress sites?

Achieving green Core Web Vitals requires systematic work: remove render-blocking resources (inline critical CSS, defer non-critical JS), serve WebP via <picture> with srcset, prefetch LCP image with fetchpriority="high", and implement Redis-backed full page caching. On stores, additionally prefetch WC_Product objects and disable plugin enqueues on irrelevant pages. Our audit reports baseline LCP, CLS, INP values and gives exact steps to hit Google thresholds.

Stack and approaches in WordPress development

Theme development. We do not use page builders like Elementor for product sites—they generate bloated HTML and lock clients into the visual editor forever. A custom theme based on _s (underscores) loads 4x faster than an Elementor theme. Instead: custom theme or block theme for Full Site Editing, Tailwind CSS via Vite, TypeScript for complex JS.

Gutenberg and block development. Since WordPress 5.0, Gutenberg is not just an editor—it's a platform. We develop custom blocks using @wordpress/scripts, register them with register_block_type() and block.json. Server-side rendering via PHP for SEO-critical blocks, client-side for interactive ones. Inner Blocks for composite components.

REST API and headless. WordPress as headless CMS via WP REST API v2 or WPGraphQL. Typical setup: WordPress on subdomain cms.example.com, Next.js frontend on main domain. ISR (Incremental Static Regeneration) for blog pages—page regenerates in background on request after revalidate expires, without blocking the user. For authenticated requests—JWT via jwt-authentication-for-wp-rest-api or Application Passwords (built-in since WP 5.6). More about REST API—Wikipedia.

WooCommerce. Extend via hooks and filters—never modify core files. Custom product types via WC_Product extension. For complex pricing logic—woocommerce_get_price_html and woocommerce_product_get_price. Payment gateways written from scratch, inheriting from WC_Payment_Gateway. Integration with 1C via CommerceML or custom REST endpoint.

Performance. Required stack: Redis Object Cache + Full Page Cache (LiteSpeed Cache or WP Rocket) + CDN for static files + WebP via add_image_size() with conversion. Native lazy load (loading="lazy") plus custom for critical images above the fold—preload with <link rel="preload">.

Case study: WooCommerce store, LCP 9.2s → 1.8s

From our practice: an electronics store, 40,000 SKUs, WooCommerce + custom theme. PageSpeed Insights: LCP 9.2s, CLS 0.41, INP 680ms.

Diagnosis:

• Hero image 3.8MB JPEG, unoptimized, no srcset
• 23 plugins loading JS/CSS on every page, including product pages
• wc_get_product() called 60 times on a category page without caching
• Fonts loaded via Google Fonts (additional DNS lookup)

What we did:

• Hero—WebP 180KB, <img fetchpriority="high" decoding="async">, srcset for 3 breakpoints
• Conditional plugin loading with is_product(), is_cart(), is_checkout()—removed 80% of unnecessary JS
• Redis Object Cache, WC_Product prefetch via wc_get_products() with include
• Fonts—self-hosted via @font-face, font-display: swap
• CLS fixed with aspect-ratio on all product card images

Result: LCP 1.8s, CLS 0.04, INP 140ms. Core Web Vitals—green. Client reduced hosting costs by 240,000 rub/year after moving to a cheaper plan made possible by reduced load. Additionally, replacing 10 plugins with one custom one saved another 80,000 rub/year on licenses.

Work process

1. Audit and analytics. Analyze existing codebase, competitors, technical requirements. For new sites—semantic core, UX prototyping.
2. Architecture. Decide: monolithic or headless. Define Custom Post Types, Custom Fields (ACF or native register_meta()), taxonomies.
3. Development. Local environment: Docker (nginx + php-fpm + MariaDB). Git with pre-commit hooks for PHP CS Fixer and ESLint. Deployment via WP-CLI + SSH or Buddy.works CI/CD.
4. Testing. PHPUnit for custom plugins. Playwright for E2E critical scenarios (add to cart → checkout → confirmation). Lighthouse CI in pipeline—fail if Performance Score < 85.
5. Deploy and support. Staging via WP Stagecoach or manual clone. Monitoring—UptimeRobot + Sentry for PHP errors. Plugin updates—via WP-CLI in test environment first.

What you get as a result

• Fully custom theme or modification of existing one
• Configured object caching (Redis/Memcached) and Full Page Cache
• Optimized media files (WebP, srcset, lazy load)
• Code structure documentation and update instructions
• Training for content managers on Gutenberg blocks
• 30-day uptime guarantee after deployment
• Access to repository with full change history

Timeline benchmarks

Pricing is calculated individually after requirements audit. Contact us for a preliminary estimate.

Common mistakes in WordPress development

• Directly editing theme files—all changes lost on theme update. Use a child theme or fully custom theme.
• update_post_meta() in a loop—each call is a separate UPDATE. For bulk operations use $wpdb->update() or update_metadata_by_mid().
• Disabled WP_DEBUG during development—hidden PHP Notices clutter error log and often indicate real issues.
• Storing media in Git—wp-content/uploads in .gitignore, sync via WP-CLI media import or rsync.
• No limit on WP_Query—posts_per_page => -1 on a page with thousands of posts guarantees a timeout.

Why trust WordPress development to professionals?

We have been on the market for over 10 years, completed 80+ projects, hold certifications from Automattic, and have experience with WooCommerce on high-traffic sites. Our solutions account for all nuances: from plugin compatibility to Core Web Vitals requirements (Google recommendations). After project completion you get a documented, tested, and scalable platform.

For a consultation and evaluation of your project—contact us. We respond within one hour during business hours. Get a free preliminary audit today.