27 documented capabilities
The Features reference below maps every meaningful customer-facing capability identified in the audited 2.0.0 product codebase.
OMEGA PERFORMANCE ENGINE DOCUMENTATION · WordPress Plugin 2.0.0
Omega Performance Engine documentation
Complete Omega Performance Engine WordPress Plugin 2.0.0 documentation covering all audited customer-facing capabilities, installation, setup, safety, troubleshooting and support.
PRODUCT OVERVIEW
What Omega Performance Engine does
A runtime-only WordPress performance plugin that works through WordPress hooks instead of rewriting post content, themes or plugin files. Version 2.0.0 intentionally removed unsafe global async+defer and HTML whitespace minification behaviour.
Local-first operation
The core functions described on this page are designed to operate locally on the customer website/server rather than requiring an OmegaWebApps cloud processing subscription. This reduces dependency on remote processing services and keeps operational state under the website owner’s control, subject to the hosting/platform environment.
Platform-specific architecture
WordPress-native hooks, capabilities, nonces, media/admin APIs and bounded administrator workflows.
Documentation map
Use the section that matches the job you are performing.
Features
Complete audited capability reference with descriptions.
Open FeaturesInstallation
Requirements, preflight checks and installation procedure.
Open InstallationSetup
Recommended configuration order and safe production workflow.
Open SetupFAQ
Commercial and product-specific technical answers.
Open FAQTroubleshooting
Common failure modes and corrective actions based on the engine boundaries.
Open TroubleshootingSupport
What to check, what information to collect and where to get help.
Open SupportCore operating workflow
- Back up the WordPress site/database and install/activate the plugin.
- Open Omega Performance and start in Conservative.
- Review runtime diagnostics and compatibility indicators.
- Test the public site, login, forms, checkout and builder output.
- Move to Balanced if guarded deferral is appropriate.
- Enable Aggressive controls one at a time only after confirming the relevant assets are unnecessary.
- Revert the mode/setting if a third-party integration requires a resource Omega was asked to remove/defer.
Requirements
- WordPress 6.0+.
- PHP 7.4+.
Safety architecture
- No post/theme/plugin file rewriting.
- Guarded defer respects dependency ordering and skips sensitive handles.
- Higher-risk removals are opt-in.
- Resource hints are preserved.
- No global async+defer behavior.
- No global HTML whitespace minification.
- Compatibility analysis is read-focused and avoids frontend transient writes.
Technical boundaries
Runtime optimization cannot guarantee a fixed browser performance score. Cache/CDN layers, themes, builders, ecommerce, analytics and third-party scripts can materially affect results. Aggressive options require site-specific testing.
Product page and commercial specification
Review the complete public-facing capability specification, pricing and licence information for Omega Performance Engine.