OMEGA WEB METRICS PRO DOCUMENTATION · Pure HTML 2.0.1

Omega Web Metrics Pro documentation

Complete Omega Web Metrics Pro Pure HTML 2.0.1 documentation covering all audited customer-facing capabilities, installation, setup, safety, troubleshooting and support.

PRODUCT OVERVIEW

What Omega Web Metrics Pro does

A local-first diagnostic and scoring engine for static websites. It records server/delivery evidence, markup/resource diagnostics, baselines and history across six categories while explicitly separating those observations from browser-measured LCP, INP and CLS.

31 documented capabilities

The Features reference below maps every meaningful customer-facing capability identified in the audited 2.0.1 product codebase.

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

Private PHP administration and filesystem/server workflows for static sites.

Documentation map

Use the section that matches the job you are performing.

Features

Complete audited capability reference with descriptions.

Open Features

Installation

Requirements, preflight checks and installation procedure.

Open Installation

Setup

Recommended configuration order and safe production workflow.

Open Setup

FAQ

Commercial and product-specific technical answers.

Open FAQ

Troubleshooting

Common failure modes and corrective actions based on the engine boundaries.

Open Troubleshooting

Support

What to check, what information to collect and where to get help.

Open Support

Core operating workflow

  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.

Requirements

Safety architecture

Technical boundaries

Server request duration is not browser page-load time. Static accessibility heuristics do not measure contrast, focus order, assistive-technology behavior or interaction latency. SEO diagnostics are technical checks, not ranking guarantees. Asset/code footprint is a bounded static heuristic, not CPU/database/browser profiling.

Product page and commercial specification

Review the complete public-facing capability specification, pricing and licence information for Omega Web Metrics Pro.

View Omega Web Metrics Pro