How FluentC caches translations
FluentC stores translations locally instead of fetching them again on every request. What that means for page speed, server load and translation costs.
By FluentCUpdated 1 min read
A page should not need a fresh round trip to a translation service every time someone views it. FluentC stores translated content locally, so once something is translated it can be served without fetching it again.
What local caching is
Caching means keeping frequently used data on the user's device or a nearby server, so retrieving it takes less time and fewer resources. For a translation tool, that means keeping translated content locally and avoiding repeated calls to external translation services.
FluentC stores translations on the server or on the visitor's device, depending on configuration.
What it changes
Speed and load
- Pages load faster, because translations are not fetched from remote servers on every request.
- Visitors get content in their own language without waiting.
- Fewer requests go out to translation servers, which eases the strain on your own server too.
Cost
- In the WordPress plugin, less data moves between your server and the translation service, which matters most on high-traffic sites.
- Fewer API calls. Many translation services charge by the number of requests, so fewer calls can mean lower costs.
Stores, learning platforms and corporate sites with international audiences are typical cases. All of them serve the same translated content again and again.
Keeping the cache current
Cached translations need to follow your content. When a page changes, make sure its cached translation is updated to match.
Related
- How FluentC keeps translation costs down covers translation memory and batching alongside caching.
- Caching, translation memory and glossary in the WordPress plugin puts caching in the context of the rest of the plugin.
