29 documented capabilities
The Features reference below maps every meaningful customer-facing capability identified in the audited 2.0.0 product codebase.
OMEGA WEB METRICS DOCUMENTATION · WordPress Plugin 2.0.0
Omega Web Metrics documentation
Complete Omega Web Metrics WordPress Plugin 2.0.0 documentation covering all audited customer-facing capabilities, installation, setup, safety, troubleshooting and support.
PRODUCT OVERVIEW
What Omega Web Metrics does
A stability-first diagnostic plugin that does not run scans on ordinary public views and does not send telemetry. It measures server/delivery evidence and static markup heuristics while explicitly reserving LCP, CLS and INP for browser tools.
Local-first operation
The core functions described on this page are designed to operate locally on the customer website/server rather than requiring an OmegaWebApps cloud processing subscription. This reduces dependency on remote processing services and keeps operational state under the website owner’s control, subject to the hosting/platform environment.
Platform-specific architecture
WordPress-native hooks, capabilities, nonces, media/admin APIs and bounded administrator workflows.
Documentation map
Use the section that matches the job you are performing.
Features
Complete audited capability reference with descriptions.
Open FeaturesInstallation
Requirements, preflight checks and installation procedure.
Open InstallationSetup
Recommended configuration order and safe production workflow.
Open SetupFAQ
Commercial and product-specific technical answers.
Open FAQTroubleshooting
Common failure modes and corrective actions based on the engine boundaries.
Open TroubleshootingSupport
What to check, what information to collect and where to get help.
Open SupportCore operating workflow
- Back up normally and install/activate the plugin.
- Open Omega Web Metrics in wp-admin.
- Run the Full Scan or an individual category manually.
- Review measured evidence and category findings.
- Use Lighthouse/CrUX separately for browser runtime Core Web Vitals.
- Make site changes and rerun the relevant category.
- Use stored history to compare diagnostic state over time.
- Delete/clear old scan history as needed.
Requirements
- WordPress 6.0+.
- PHP 7.4+.
- WordPress HTTP requests to the configured/local target must be permitted for server-side diagnostics.
Safety architecture
- 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.
Technical boundaries
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.
Product page and commercial specification
Review the complete public-facing capability specification, pricing and licence information for Omega Web Metrics.