TECHNICAL OVERVIEW · TEN CURRENT COMMERCIAL CODEBASES
The current commercial audit covers 248 source/package files, 610 PHP functions/methods, 94 PHP classes and 65 WordPress hooks. This page translates that implementation depth into the architecture and capability boundaries a technical buyer should understand.
PLATFORM ARCHITECTURE
Private PHP administration operates beside a static public website. Engines use filesystem discovery, protected local state/JSON, explicit file transformations and Apache/LiteSpeed rules where relevant. Nginx requires equivalent server configuration for rule-based protections.
Plugins use WordPress hooks, capabilities, nonces, attachment/media APIs, settings and authenticated admin/AJAX workflows. They avoid treating WordPress as a directory of static HTML files.
The reviewed engines do not require an Omega telemetry account or mandatory Omega cloud processor for their principal image, performance, security, SEO or metrics functions.
COMPLETE PRODUCT ARCHITECTURE
These are condensed public technical maps. The individual commercial product pages contain the fuller buyer-facing function specification.
PURE HTML · 2.0.1
Responsive image engineering
Discovers local images, manages an Omega Media Library, converts supported sources to AVIF/WebP, generates responsive widths and browser-native <picture>/srcset delivery, applies backup-first HTML rewrites and provides SHA-256 duplicate safety.
Capability coverage: Full Site Image Discovery; Managed Omega Media Library; direct image upload; local AVIF/WebP conversion; width-specific variants; <picture>/srcset delivery; image registry and usage analysis; backup-and-apply responsive rewrites; duplicate preview/deletion safeguards; capability detection; ZIP output; dedicated administrator and protected local state.
PURE HTML · 2.0.1
Safe-first static performance optimisation
Provides Conservative, Balanced and Aggressive operating modes, read-only site preview, explicit transformations, timestamped backup/restore, guarded script deferral and managed Apache/LiteSpeed delivery rules.
Capability coverage: Conservative/Balanced/Aggressive modes; full-site read-only preview; explicit apply; timestamped backups; one-click restore; guarded defer; async/defer/module/nomodule/Cloudflare/inline-data protections; user safelist; emoji/head/oEmbed/REST cleanup; optional jQuery Migrate/feed/block CSS/WooCommerce CSS cleanup; compression/cache/keep-alive rules; compatibility analysis; canonical/resource-hint preservation.
PURE HTML · 2.0.1
Static-site security administration
Combines integrity baselines, malware/virus scanning, three vault workflows, IP controls, server hardening, logs and site/email/security audits in a private local-first dashboard.
Capability coverage: Private dashboard and login protection; file integrity baseline/change review; trusted backups; restore/mark-safe/accept-removal; File/Malware/Virus vaults; quick/full/single-file malware and virus scans; SHA-256 vault integrity; IP allow/block; .htaccess hardening; HTTPS/security headers/dotfile/directory protection; security logs; runtime/delivery, URL, phishing/message, browser-capability and SPF/DMARC/DKIM audits.
PURE HTML · 2.0.1
Whole-site technical SEO automation
Audits static HTML and manages page-aware titles, descriptions, canonicals, robots, social metadata, structured data and image SEO with explicit policy controls and protected backups before writes.
Capability coverage: Full-site SEO audit and page-context analysis; title/description/canonical/robots management; Open Graph/Twitter; keywords; WebSite/WebPage/Breadcrumb JSON-LD; primary image detection; Auto-Safe/Force/Off policies; backup-and-apply all pages; managed metadata cleanup; image SEO scan/registry/batching; optional missing-alt fill; caption/description registry; protected local settings/backups.
PURE HTML · 2.0.1
Local diagnostics, baselines and history
Runs six evidence-based diagnostic categories with full or individual scans, resumable jobs, scores, recommendations, baselines and history without presenting server-side evidence as browser Core Web Vitals.
Capability coverage: Full scan; save/reset baseline; individual category scans; resumable scan jobs; Performance, Images, SEO, Security, UX/Accessibility and Site Asset/Code Footprint diagnostics; compression/cache/resource/blocking/external-host/inline-code evidence; schema detection; category/composite scores; status labels; recommendations; latest scan/history/retention; staging targets; protected local JSON; no fabricated LCP/INP/CLS.
WORDPRESS PLUGIN · 2.0.0
WordPress-native image optimisation
Uses WordPress image APIs to create local AVIF/WebP responsive variants while preserving native attachment metadata, originals and normal WordPress media behaviour.
Capability coverage: wp_get_image_editor processing; AVIF/WebP; Omega 320/768/1536 widths; next-gen siblings for WordPress sub-sizes; AVIF-first/WebP-second <picture>/srcset; attachment/content filtering; automatic new-upload optimisation; quality controls; Media Library scans/status; authenticated resumable batches; separate Omega variant metadata; native/original preservation; SHA-256 orphan duplicate cleanup; atomic state; safe uninstall.
WORDPRESS PLUGIN · 2.0.0
Compatibility-aware runtime optimisation
Optimises WordPress at runtime through platform hooks with three operating modes, guarded defer logic, compatibility detection and opt-in higher-risk controls without rewriting posts, themes or plugin files.
Capability coverage: Conservative/Balanced/Aggressive modes; emoji/oEmbed/head cleanup; guarded dependency-aware defer; sensitive-handle safelist; optional jQuery Migrate/feed/REST cleanup; contextual block/WooCommerce CSS dequeue; cache-plugin/builder/WooCommerce/network-active compatibility detection; runtime diagnostics; runtime-only architecture; resource-hint preservation; no global async+defer or HTML whitespace minification.
WORDPRESS PLUGIN · 2.0.0
Local-first WordPress protection
Provides a local application firewall, login protection, IP controls, integrity monitoring, malware indicators, optional hardening and scheduled maintenance with restrained defaults.
Capability coverage: Local application firewall; malicious URI/payload detection; validated client IP handling; IP allow/block; optional trusted proxy headers; brute-force/login guard; lockout cleanup; file integrity baseline/scan; manual malware scan; protected atomic JSON state; optional security headers/HSTS/CSP/HTTPS; XML-RPC/pingback and author-enumeration controls; optional REST restriction; .htaccess hardening; logs/email notifications; scheduled maintenance; capability/nonce protection.
WORDPRESS PLUGIN · 2.0.0
WordPress-native technical SEO
Uses WordPress title, robots and wp_head APIs for metadata/schema automation, includes conflict-aware Auto-Safe behaviour and page-aware image SEO without destructive output buffering.
Capability coverage: Document title, description, canonical and robots automation; Open Graph/Twitter; keyword generation; primary image resolution; WebSite/WebPage/Breadcrumb schema; context resolver; Auto-Safe conflict policy and configurable output; no whole-page output buffering/third-party regex deletion; page-aware image SEO; existing metadata preservation; no file renaming or image-size metadata rewrite; new-attachment automation; authenticated batch scans; SEO-plugin detection.
WORDPRESS PLUGIN · 2.0.0
Administrator-triggered WordPress diagnostics
Runs bounded local diagnostics only when an administrator requests them, stores history locally and explicitly separates static/server evidence from browser-measured performance metrics.
Capability coverage: Admin-triggered full and single-category scans; Performance, Images, SEO, Security, UX/Accessibility and Plugin Footprint diagnostics; no public-view scanning; bounded scanner architecture; no fabricated FCP/LCP/CLS/INP/TBT; Lighthouse/CrUX guidance for browser CWV; history/retention/latest/individual retrieval/delete/clear; settings; protected AJAX/nonces; optional REST disabled by default; SSL verification preserved; no vulnerability API-key dependency; no telemetry.
CROSS-PLATFORM DESIGN DIFFERENCES
| Discipline | Pure HTML v2.0.1 | WordPress v2.0.0 |
|---|---|---|
| Images | Filesystem discovery, Omega Media Library, local conversion, responsive HTML rewrite with backups, referenced-path duplicate safety. | WordPress image editor/attachments, Omega + WP sub-size variants, attachment/content filters, separate Omega metadata, orphan-only duplicate deletion. |
| Performance | Read-only preview, explicit HTML transformation, timestamped backup/restore and managed Apache/LiteSpeed rules in addition to guarded cleanup/deferral. | Runtime-only hooks and dequeues; compatibility detection; no post/theme/plugin-file rewriting. |
| Security | Integrity baseline, multiple scan types, three vaults, IP manager, .htaccess hardening, delivery/URL/phishing/browser/DNS audits. | Application firewall, login guard, validated client IP handling, integrity/malware indicators, optional WordPress hardening and scheduled maintenance. |
| SEO | Page-by-page static audit and backup-before-write metadata/schema/image-SEO changes. | WordPress-native title/robots/wp_head APIs, context resolution and conflict-aware Auto-Safe output. |
| Web Metrics | Six categories including Site Asset/Code Footprint, resumable scan jobs, baseline and staging/target URL controls. | Six categories including Plugin Footprint, admin-triggered bounded scans, protected AJAX/nonces and optional REST disabled by default. |
SECURITY & SAFETY CONTROLS
Pure HTML engines use dedicated administrator authentication, secure sessions and CSRF controls. WordPress editions use administrator capabilities and nonces for protected actions.
Static engines that rewrite HTML create protected backups before managed changes. WordPress Image preserves native attachment metadata/originals, while WordPress Performance is runtime-only and avoids file rewriting.
Duplicate cleanup, malware handling, higher-risk performance cleanup and bulk SEO/image processing are previewed, batched, opt-in or otherwise constrained according to the product's architecture.
Metrics differentiates static/server evidence from browser-runtime telemetry. Security scan findings are indicators for administrator review rather than automatic proof that every matched file is malicious.
ENVIRONMENTAL DEPENDENCIES
AVIF/WebP generation depends on active GD/Imagick codec support. Apache/LiteSpeed can use supplied .htaccess workflows where applicable; Nginx needs equivalent server rules. WordPress editions require WordPress 6.0+ and PHP 7.4+ according to their current plugin headers; Pure HTML packages recommend PHP 8.1+ in their current documentation.
Each product is sold separately for US$89 one-time with a lifetime licence for the purchased version and unlimited sites, subject to the Terms & Licence.