Performance & Caching
Preload strategies, cache behavior and large-site guidance.
Preload strategies
Settings provide three frontend preload strategies:
- Current page languages — recommended balance
- Whole site cache — more aggressive preloading
- Active language only — smallest immediate payload
The best choice depends on site size and how often visitors switch languages.
Large websites
For sites with many pages and posts:
- use Translate Entire Site rather than manual per-page work
- allow queue/rendered-discovery workers to process in batches
- keep an Instant Languages admin screen open during initial translation if WP-Cron is slow
- avoid repeatedly starting duplicate site-wide jobs
Page caches
A WordPress/page cache can serve stale HTML or stale JavaScript after upgrading or changing translations. When testing:
- clear plugin cache
- clear host/server cache
- purge CDN if used
- hard-refresh browser
Dynamic sites
If the theme/plugin renders content differently for logged-in versus logged-out users, test both contexts after translation. The rendered-site crawler uses same-site requests and identity checks but may not reproduce every interactive browser state.