A scan does not run on the public site
That is intentional. Scans are administrator-triggered and do not execute on ordinary public views.
TROUBLESHOOT OMEGA WEB METRICS · WordPress Plugin 2.0.0
Troubleshooting guidance for Omega Web Metrics WordPress Plugin 2.0.0, based on its audited architecture and technical boundaries.
Start with the least destructive correction. Restore/revert a high-impact change before experimenting further on a production site.
That is intentional. Scans are administrator-triggered and do not execute on ordinary public views.
The plugin does not invent FCP/LCP/CLS/INP/TBT. Use Lighthouse/CrUX or real-user browser tooling for those measurements.
Confirm WordPress HTTP requests to the target are permitted and SSL verification can complete normally.
Optional REST routes are disabled by default. Use the protected admin workflow unless an authenticated REST use case is deliberately enabled.
Footprint is bounded static analysis, not CPU/database/browser runtime profiling.
Server-side request evidence is not the same as real-user/browser performance. Accessibility checks are static heuristics, not a conformance certification. Plugin footprint is bounded static analysis, not runtime CPU/database profiling. SEO/security categories are diagnostic evidence, not guarantees of ranking or security.
Review the complete public-facing capability specification, pricing and licence information for Omega Web Metrics.