PerfLocale for Publishers
Run a news site, magazine, or blog in multiple languages - without slowing down pages your readers load ten times a day, and without confusing Google about which version to rank.
The tradeoffs publishers usually get stuck with
Content-heavy sites suffer most from multilingual plugin overhead: thousands of posts, high traffic, tight caching requirements. Many plugins add database queries on every archive load, break pagination in unexpected ways, or fight with your CDN. Editorial teams end up avoiding features just to keep the site fast.
PerfLocale is built to stay out of the way. Features below come from actual publisher pain points.
What you get
Fast archives and category pages
Listing 20 posts per page on a category archive should be one database query, not twenty. PerfLocale batch-loads translations so the number of queries stays constant whether you display 5 posts or 50. Your main news feed feels just as snappy in French as in English.
Search engines understand your language structure
Every page gets the right hreflang tags, sitemap alternates, and canonical URLs. Google shows French readers your French version in search results, not the English one auto-translated by the browser. Works with Yoast, Rank Math, AIOSEO, SEOPress, and others - your existing SEO setup keeps its say.
Stories flow naturally from draft to published in each language
Each language version has its own publish date, author, and editorial state. Write the English story today, publish the French version tomorrow after the desk reviews it - without confusing the archive, the RSS feed, or the sitemap.
Plays well with CDNs and page caches
Cache-Tag headers let Cloudflare, Bunny, Fastly, and KeyCDN purge exactly the pages that changed when you translate or re-edit a story - not the whole site. If one language's homepage needs invalidating, the other stays hot in cache.
Translation memory for recurring content
News desks write the same phrases a lot: "Reporting from", "File photo", "Story developing". The translation memory recognizes these and suggests the previously-approved rendering, so your translators aren't re-translating boilerplate every night.
Serve the right language based on visitor location
Optional GeoIP redirect puts first-time visitors on the version most likely to match their browser language or country. Respects their choice afterward via a cookie so they don't get bounced around on every reload. Opt-in and GDPR-respectful.
Numbers that matter
Less than 5 ms of overhead per page. 3-layer caching so most operations never touch your database on a warm cache. Benchmarks are published with the test scripts - you can rerun them on your own setup to verify before committing.
For a publisher running half a million monthly pageviews, this is the difference between "we need to upgrade the server to add Spanish" and "we added Spanish last Thursday and nobody noticed".