Is this product sold separately?
Yes. This is an individual OmegaWebApps product priced at US$89 one-time. It is not sold as a required suite or subscription.
OMEGA PERFORMANCE ENGINE FAQ · WordPress Plugin 2.0.0
Omega Performance Engine FAQ
Frequently asked commercial, licensing and technical questions for Omega Performance Engine WordPress Plugin 2.0.0.
Commercial and technical questions
These answers reflect the current audited 2.0.0 product behavior and published commercial model.
How many websites can I use the purchased version on?
The commercial offer provides a lifetime licence for the purchased version for unlimited websites/client sites, subject to the Terms & Licence and applicable open-source rights.
Does the core engine require a cloud account?
No. The product is designed around local/server-side operation for its core functions. Third-party hosting, browsers and platform components still behave according to their own environments.
Are results guaranteed?
No. The engine provides the functions described on this page, but outcomes such as rankings, page-speed scores, security immunity, browser metrics or universal compatibility depend on factors outside the software itself.
Does the engine guarantee a Lighthouse score?
No. It changes specific optimization factors, while hosting, layout, browser, network and third-party resources remain material.
Is Aggressive mode required?
No. Higher-risk controls are opt-in. Conservative/Balanced operation is intentionally available for safer deployment.
Does it globally minify HTML whitespace?
No. The reviewed current versions intentionally avoid global HTML whitespace minification.
What version does this documentation cover?
This documentation covers Omega Performance Engine WordPress Plugin version 2.0.0.
Does the core product require an OmegaWebApps cloud account?
No required OmegaWebApps cloud-processing or telemetry account is part of the reviewed core operation.
How should production changes be tested?
Use backups, staged configuration and representative testing. Higher-risk controls should be enabled only after confirming compatibility with the actual site environment.
Need a capability-by-capability reference?
The Features page documents all 27 meaningful customer-facing capabilities identified for this product.
Open complete feature referenceProduct page and commercial specification
Review the complete public-facing capability specification, pricing and licence information for Omega Performance Engine.