Multilingual Site Speed: Caching Translated Pages the Right Way

A ten-language site is, to your server, ten sites. Done right, every one of them is as fast as the original — because path-based language versions are perfectly cacheable.

How the layers stack

First request to /fr/about/: new sentences go once to your API, results persist in the translation cache, the rendered page persists in your page cache. Every later visitor gets pure cache — origin and edge alike. WP Rocket, LiteSpeed, W3TC and host-level caches all work unmodified (notes).

CDN behavior

Path-based languages flow through CDNs naturally; each edge location caches the locales its region requests. If you cache HTML at the edge, no vary headers or workers are required — another quiet win for the subdirectory structure.

Fonts and scripts

Non-Latin languages may pull different font subsets; self-host with font-display swap and preload only the default language’s subset. Core Web Vitals apply per URL — audit one page per script family (Latin, Cyrillic, CJK, RTL) rather than every page.