FluentC and Weglot on large multilingual sites
What changes when a multilingual site gets big, high traffic, a lot of content and many languages, and how FluentC's caching, storage and pricing approach it.
By FluentC1 min read
A large multilingual site has more content, more traffic and more languages to manage, and the translation plugin has to keep up without slowing pages down. This article covers three areas where size matters, and what the FluentC WordPress plugin does in each.
Traffic
The FluentC plugin uses caching to keep the site responsive during peak traffic. Translations are stored locally and served from the cache rather than fetched each time. How that works is covered in How FluentC caches translations.
Database
The plugin stores translations in a streamlined format, which reduces database bloat and keeps queries fast as the volume of translated content grows. Translations without duplicate posts, pages or products covers the plugin's approach to storing translated content.
Cost
Weglot prices in tiers, and adding languages moves you into a higher tier. FluentC uses flat pricing with unlimited translations: the price depends on your number of languages, not on how much content you translate or how large the site becomes. See pricing.
For a feature-by-feature table, see FluentC vs Weglot.
