Configure Omega Web Metrics Pro

1. Set the correct Base URL/target path before scanning.
2. Run & Save Baseline before major site changes when you want a comparison point.
3. Use Full Scan for broad evidence or individual category scans for focused reassessment.
4. Let resumable scan jobs complete category by category and review evidence before acting on a score.
5. Use history to compare state over time rather than treating a single composite score as an absolute verdict.
6. Use Lighthouse/CrUX separately when browser Core Web Vitals such as LCP, INP and CLS are required.

1. Extract at public_html and open /omega-web-metrics/.
2. Create the dedicated Omega administrator.
3. Set the Base URL and target path in Settings.
4. Run Full Scan or Run & Save Baseline.
5. Review category evidence, scores and recommendations.
6. Make site changes in the appropriate engine/workflow.
7. Rerun only the affected category or the full scan.
8. Use history/baseline comparison to track change over time.

• Scans are diagnostic/read-focused.
• No browser Core Web Vitals are fabricated from server HTML.
• History/evidence stays local.
• Private dashboard actions require authentication and CSRF validation.
• No external metrics API key or telemetry account required.

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.