PERFLOCALE
PerfLocale compatibility with REEID Translate
PerfLocale compatibility with REEID Translate is being evaluated from available plugin evidence. Implements a “3-layer cache” intended to reduce database touch for multilingual requests (performance-first design). No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for PerfLocale.
Official plugin information supports the compatibility context documented for this category.
AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.
PLUGIN PROFILE
PerfLocale is documented in the Performance category with 7 concrete capabilities identified in the current evidence.
EVIDENCE COVERAGE
Plugin capabilities are documented from available official evidence. Translation support is listed only when concrete visitor-facing content is explicitly established.
COMPATIBILITY REVIEW
How PerfLocale compatibility is evaluated
01 · Review official plugin evidence
Establish documented plugin behaviour before making any multilingual compatibility claim.
02 · Identify visitor-facing content
Determine whether the documented behaviour exposes human-readable values that visitors can see.
03 · Separate content from functionality
Keep structure, configuration, logic, integrations and runtime behaviour outside translation scope unless concrete content values are identified.
04 · Confirm translation scope
Publish supported content only when concrete visitor-facing values are explicitly established and can be validated.
PLUGIN INTELLIGENCE
What the official plugin evidence shows
Plugin capabilities
- Implements a “3-layer cache” intended to reduce database touch for multilingual requests (performance-first design).
- Supports multiple URL routing modes for language selection (subdirectory, subdomain, per-domain, and query-parameter), with auto-detection from URL/cookie/browser/edge/CDN hint.
- Provides SEO-related language output via hreflang tags and sitemap alternates, including integration with multiple named SEO plugins.
- Integrates with page-cache plugins by ensuring language-specific URL variants are cacheable while marking responses uncacheable when language is decided by non-URL factors (e.g., cookie/redirect), using WordPress nocache_headers().
- Includes an optional edge-worker integration that exposes a public REST endpoint for routing/language metadata and returns cache-control headers plus an ETag for revalidation; payload is described as non-sensitive and filter-extendable with invariants.
- Offers machine translation and external translation integrations that are disabled by default and require explicit configuration (API keys / enabling settings), with described outbound-call behavior only for translation actions.
- Provides export/import and migration tooling with batch processing and transaction safety (rollback on failure) and includes a stated export file handling approach (authenticated, nonce-checked admin download; server-specific access controls).
CONTENT BOUNDARY
PerfLocale capabilities and translation scope are documented separately.
The available evidence documents plugin functionality, but does not currently establish a specific visitor-facing translation surface.
Functional capability alone is not treated as evidence that a value should be translated.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.
COMMON QUESTIONS
PerfLocale and REEID Translate FAQ.
What does PerfLocale do according to the available plugin evidence?
PerfLocale has 7 concrete capabilities documented from the currently available official plugin evidence. See the Plugin Intelligence section for the individual capabilities.
Is a REEID translation surface currently confirmed for PerfLocale?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for PerfLocale?
The evidence must identify concrete visitor-facing values such as labels, titles, descriptions, messages or other human-readable content that can be validated through the integration workflow.
RELATED GUIDES
Continue through the compatibility library.
INTEGRATION EVIDENCE
Evaluate PerfLocale in a multilingual WordPress workflow.
REEID documents PerfLocale functionality separately from evidence-backed translation support so compatibility claims remain specific and testable.
Translation scope will be published when concrete visitor-facing content is established by evidence.