Omega Web Metrics — Troubleshooting
Omega Web Metrics is a diagnostic engine. It does not modify your site, server, plugins, themes, or configuration. If the scanner reports issues, this does not mean the plugin is malfunctioning — it means your site has issues that require manual or developer-level fixes.
Scan Does Not Start
- Ensure PHP 7.4+ is installed (PHP 8.0+ recommended).
- Disable any security plugin blocking admin‑AJAX or REST requests.
- Clear any caching layer (Cloudflare, LiteSpeed, Nginx cache, hosting cache).
- Ensure your host allows loopback requests and background processes.
Scan Freezes or Times Out
- Increase PHP
max_execution_time to at least 120 seconds.
- Increase PHP
memory_limit to 256M or higher.
- Disable object caching (Redis, Memcached) temporarily.
- Disable HTML/JS/CSS minification during the scan.
- Ensure your host does not block internal HTTP requests.
Missing or Partial Results
- Ensure the scanned page is publicly accessible.
- Disable maintenance mode or coming‑soon plugins.
- Disable login‑wall plugins that block non‑logged‑in requests.
- Clear CDN cache and disable “cache everything” rules temporarily.
Incorrect or Unexpected Metrics
- Clear CDN cache (Cloudflare, BunnyCDN, Fastly, etc.).
- Disable HTML minification or optimization plugins temporarily.
- Ensure no server‑level caching is serving stale content.
- Check that your host is not stripping security headers.
Security Scan Shows Issues That Cannot Be Fixed Automatically
This is expected. Omega Web Metrics identifies issues that no WordPress plugin can fix automatically, including:
- HTTPS redirect
- HSTS header
- Security headers (CSP, X‑Frame‑Options, etc.)
- Cookie flags (Secure, HttpOnly, SameSite)
- FORCE_SSL_ADMIN in wp-config.php
- WP_DEBUG in wp-config.php
- Database prefix changes
- Mixed content
- Cloudflare/Nginx/LiteSpeed header overrides
These require manual fixes by a developer or hosting provider. Omega Web Metrics is working correctly when it reports these issues.
Plugin Impact Scan Shows High Impact Plugins
This does not indicate a problem with Omega Web Metrics. It means:
- The plugin loads many scripts or styles
- The plugin uses external resources
- The plugin adds REST routes, AJAX actions, or cron jobs
- The plugin stores large autoloaded options
- The plugin has a large file footprint
These issues require manual optimization or replacement of the plugin. Omega Web Metrics does not modify plugin code.
Why Omega Web Metrics Cannot Fix Issues Automatically
Many issues detected by Omega Web Metrics require:
- Editing
wp-config.php
- Editing
.htaccess or Nginx config
- Changing server or CDN settings
- Modifying plugin or theme code
- Database migrations
These actions cannot be performed safely by any WordPress plugin. They must be done manually by a qualified developer.
Still Having Issues?
See the Support page for guidance on reporting reproducible plugin issues.
Note: Support does not include fixing issues detected by the scanner. These require manual developer action.