NATIVE LAZYLOAD
Native Lazyload compatibility with REEID Translate
Native Lazyload compatibility with REEID Translate is being evaluated from available plugin evidence. Lazy-loads images and iframes in post content using the browser’s native `loading` attribute. No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for Native Lazyload.
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
Native Lazyload 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 Native Lazyload 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
- Lazy-loads images and iframes in post content using the browser’s native `loading` attribute.
- Falls back to a JavaScript-based `IntersectionObserver` solution when native `loading` support is unavailable.
- Adds a `noscript` variant that still includes the `loading` attribute when JavaScript is disabled but browser support exists.
- Has no settings screen; it works by activation alone.
- Supports opting out per image or iframe by adding the `skip-lazy` class.
- Includes a filter to disable the fallback script and rely only on native `loading` support.
- Is built to avoid breaking AMP compatibility.
CONTENT BOUNDARY
Native Lazyload 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
Native Lazyload and REEID Translate FAQ.
What does Native Lazyload do according to the available plugin evidence?
Native Lazyload 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 Native Lazyload?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for Native Lazyload?
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 Native Lazyload in a multilingual WordPress workflow.
REEID documents Native Lazyload 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.