Configure Omega Web Metrics

1. Run scans manually from wp-admin; the plugin does not place scan work on normal public page views.
2. Use Full Scan for broad evidence or single-category scans after a targeted change.
3. Review server/static evidence separately from browser Core Web Vitals.
4. Use stored history to compare diagnostic state over time and clear/delete old scans when appropriate.
5. Keep optional REST routes disabled unless an authenticated use case requires them.
6. Use Lighthouse/CrUX separately for browser-measured FCP/LCP/CLS/INP/TBT.

1. Back up normally and install/activate the plugin.
2. Open Omega Web Metrics in wp-admin.
3. Run the Full Scan or an individual category manually.
4. Review measured evidence and category findings.
5. Use Lighthouse/CrUX separately for browser runtime Core Web Vitals.
6. Make site changes and rerun the relevant category.
7. Use stored history to compare diagnostic state over time.
8. Delete/clear old scan history as needed.

• No scan workload on ordinary public views.
• manage_options/capability checks and nonces protect scan actions.
• Optional REST routes are disabled by default and protected when enabled.
• No unauthenticated scan endpoint.
• SSL verification is not disabled.
• No fabricated browser Core Web Vitals.
• No required telemetry or vulnerability-service API key.

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.