Configure Omega Performance Engine Pro

1. Start in Conservative mode and run the read-only Full Site Preview before applying anything.
2. Review each planned file transformation and server-rule change before Apply.
3. After Conservative testing, move to Balanced only if guarded script deferral is appropriate.
4. Maintain a safelist for sensitive scripts such as checkout, payment, analytics, CAPTCHA or site-specific dependencies when needed.
5. Treat Aggressive options as individual opt-ins; test jQuery Migrate/feed/block CSS/WooCommerce CSS removals separately.
6. Use managed Apache/LiteSpeed .htaccess delivery rules only on compatible servers; translate them manually for Nginx.
7. Keep the timestamped backup until the optimized site has been thoroughly validated.

1. Extract at public_html and open /omega-performance-engine/.
2. Create the private Omega administrator.
3. Start in Conservative mode.
4. Run Full Site Preview and review planned changes.
5. Apply only after the preview is satisfactory.
6. Test the public site and important forms/checkout/scripts.
7. Move to Balanced and preview guarded deferral if desired.
8. Enable Aggressive controls individually only where testing confirms compatibility.
9. Use Restore if a change needs to be rolled back.

• Read-only preview is separate from apply.
• Every changed file is backed up before write.
• Restore includes changed HTML and previous .htaccess state.
• Guarded defer excludes sensitive script classes and configured safelist matches.
• Aggressive CSS/jQuery/feed removals are opt-in.
• No global HTML whitespace minification.

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.