Configure Omega Performance Engine

1. Begin with Conservative mode and review runtime diagnostics/compatibility indicators.
2. Test public pages, wp-admin, login, forms, builders and ecommerce before moving to Balanced.
3. Balanced guarded deferral should remain dependency-aware and sensitive-handle aware.
4. Enable Aggressive removals one at a time and test the exact pages that depend on those assets.
5. Keep high-risk controls disabled when a theme, builder, cache plugin or WooCommerce context needs the resource.
6. Remember the plugin is runtime-only: it does not rewrite posts, theme files or plugin files.

1. Back up the WordPress site/database and install/activate the plugin.
2. Open Omega Performance and start in Conservative.
3. Review runtime diagnostics and compatibility indicators.
4. Test the public site, login, forms, checkout and builder output.
5. Move to Balanced if guarded deferral is appropriate.
6. Enable Aggressive controls one at a time only after confirming the relevant assets are unnecessary.
7. Revert the mode/setting if a third-party integration requires a resource Omega was asked to remove/defer.

• 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.

After configuration, test the pages, forms, checkout/payment flows, authentication, media, scripts/styles and integrations that matter to the site. Use staging where practical for higher-risk changes.