Does the plugin cache every page?
No. Admin, REST, feeds, errors, private requests, unsafe query strings, and dynamic WooCommerce routes bypass shared caching. The plugin prefers a correct dynamic response over a risky hit.
Does it improve Core Web Vitals?
Several features target the metrics directly, but results depend on hosting, theme, plugins, content, and traffic. Measure before and after on the same URL.
Can I run it beside another cache plugin?
Only with one page-cache owner. LiteSpeed has explicit modes; for other cache plugins, disable the competing page-cache module. Non-page-cache features can often coexist after testing.
Is native lazy loading enabled by default?
Yes. The browser/WordPress native path is preferred and the legacy JavaScript observer is opt-in. LCP guardrails protect above-the-fold content.
Where are credentials stored?
Use the WordPress Connectors or documented constants/environment paths for external services. Exports redact secret-shaped values. Never paste passwords, API keys, authorization headers, or cookies into documentation or bug reports.
Why does the reference show so many files?
The code reference is generated from the current recursive includes/ tree, including runtime classes, protected minify wrappers, entry points, and shipped templates.
What does wp wppo verify check?
It reports runtime, filesystem, cache, Redis, LiteSpeed, settings, cron, and uninstall-hygiene findings. Read the result before treating a warning as a release blocker.
Where can I report a problem?
Open an issue with versions, server software, reproduction URL, and a redacted wp wppo system-info output.