
KOCI CACHE
Koci Cache compatibility with REEID Translate
Koci Cache compatibility with REEID Translate is being reviewed using official plugin documentation. Serves static HTML pages via the advanced-cache.php drop-in before WordPress loads, bypassing PHP and database queries for anonymous visitors. No specific text shown to visitors is currently confirmed for translation.
AWAITING VERIFICATION
What Koci Cache does
Official plugin information supports the compatibility context documented for this category.
MANUAL REVIEW
This integration has not yet been manually verified by REEID.
PLUGIN PROFILE
Koci Cache is documented in the Performance category with 8 documented features.
DOCUMENTATION REVIEW
We use official plugin documentation to describe what the plugin does. Translation support is listed only for text that can be identified and tested.
COMPATIBILITY REVIEW
How Koci Cache compatibility is evaluated
01 · Review official plugin documentation
Confirm documented plugin behaviour before making multilingual compatibility claims.
02 · Identify text shown to visitors
Check whether the documented features display text that visitors can read.
03 · Separate content from functionality
Structure, settings, logic, integrations and runtime behaviour are not treated as translatable content unless they include specific visible text.
04 · Confirm what can be translated
List supported content only after specific text shown to visitors has been identified and can be validated.
PLUGIN INFORMATION
What the plugin does
Plugin capabilities
- Serves static HTML pages via the advanced-cache.php drop-in before WordPress loads, bypassing PHP and database queries for anonymous visitors.
- Automatically excludes logged-in users, cart/checkout pages, password-protected content, POST requests, and unallowed query strings from caching to ensure dynamic functionality.
- Provides granular cache invalidation that clears only affected posts, home pages, and related archives upon content updates, while offering manual full-flush controls.
- Includes optional CSS minification and cascade-safe combining, as well as JavaScript minification, deferring, and delay-until-interaction capabilities with exclusion rules.
- Offers media optimization features such as lazy loading for images and iframes (skipping LCP elements), setting missing dimensions, and self-hosting Google Fonts.
- Supports cache preloading via sitemap crawling after a full clear and optional link prefetching on hover to improve perceived performance.
- Maintains separate cache keys for URLs including language prefixes (e.g., /en/, /de/) to prevent cross-language contamination in multilingual setups.
- Respects developer hooks like koci_cache_is_cacheable and constants like DONOTCACHEPAGE, allowing programmatic control over cacheability and optimization.
TRANSLATION BOUNDARY
Koci Cache capabilities and translatable content are documented separately.
Official documentation describes the plugin functionality, but does not currently identify specific text shown to visitors that can be translated.
A feature is not considered translatable unless it includes text that users can read.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility. No specific content shown to visitors is confirmed for translation in this category.
FREQUENTLY ASKED QUESTIONS
Koci Cache and REEID Translate FAQ.
What does Koci Cache do?
Koci Cache has 8 documented features listed in its official documentation. See the Plugin Information section for details.
Does Koci Cache have any content currently confirmed for translation?
No specific content is currently confirmed for translation in this integration.
What needs to be confirmed before translating content from Koci Cache?
Official documentation must identify specific text, such as labels, titles, descriptions or messages, that can be tested in the integration.
RELATED GUIDES
Explore more compatibility guides.
COMPATIBILITY INFORMATION
Evaluate Koci Cache in a multilingual WordPress workflow.
REEID documents Koci Cache functionality separately from confirmed translation support so the distinction is clear.
Supported content will be listed when specific translatable text is identified in the official documentation.