WebPayesh

WebPayesh (وب‌پایش) is a site-care dashboard for WordPress. It helps agencies and site owners see health, performance risks, image issues, uptime history, and maintenance tasks in one admin screen — with careful, reversible tools where data is changed.

The plugin focuses on visibility first, then optional fixes with preview and rollback where applicable.

Who is it for?

• Agencies maintaining client sites under a support contract
• Store owners who need a quick WooCommerce health overview
• Admins who want image and speed guidance without installing a full suite of separate tools

Features

• Unified admin dashboard (Persian UI) with health score breakdown
• Contract end date alerts (contract end date and renewal tracking for agencies)
• Configurable support contact channels (phone, WhatsApp, Telegram, etc.) — nothing hard-coded in the UI
• Quick actions log and support/problem tickets for agency workflows
• Predictive warnings (trends, major updates, disk, contract)
• Full report export for clients
• Modular codebase (v2+) under includes/ and admin/

Health Monitoring

• Periodic health checks (cron) covering common failure signals
• Health score categories (performance, security, maintenance, backup, mobile, SEO-oriented signals)
• Active alerts inside the plugin screen (does not strip other plugins’ admin notices)
• Optional email alerts for critical findings
• Website “profile” history: stack info, past issues, support activity

Performance

• Speed checklist with clear done / not-done items aimed at sub-2s goals
• Built-in optional helpers (lazy load, page cache mode, minify/defer toggles) with Safe Mode
• Performance diagnosis with root-cause style hints (e.g. slow TTFB, heavy hero image)
• Emergency recovery via short-lived token + confirmation page (no public standalone recover.php)
• Guidance when a fix requires the host or another plugin (Redis, CDN, etc.)

Image Optimization

• Media library scan: formats, oversized files, missing ALT
• WebP conversion with Safe (sidecar) and Replace modes
• Exclude list, selection checkboxes, optional resize to max dimensions
• LCP-oriented controls (preload / no-lazy) for selected attachments
• Before/after savings summary for client reporting
• Rollback paths for optimized attachments where backups exist

Important: Always test image tools on a staging copy. Runtime coverage should include JPG, transparent PNG, large images, and non-ASCII filenames.

WooCommerce

When WooCommerce is active, WebPayesh can surface a WooCommerce Doctor overview, including signals such as:

• Checkout / cart related health indicators
• Failed orders and Action Scheduler backlog hints
• HPOS / webhooks / email related warnings where detectable

This is diagnostic guidance, not a replacement for WooCommerce’s own status tools.

Database Doctor

Safe-leaning maintenance workflow:

1. Analyze
2. Preview (tokenized)
3. Snapshot
4. Fix
5. Verify
6. Rollback (where a snapshot applies)

Supported operations include expired transients, post revisions, conservative “orphan option” candidates, and table optimize.

Orphan detection is heuristic and conservative (inactive plugin prefixes, never active-plugin prefixes, protected core keys). Always read the preview list before applying a fix.

Uptime Monitoring

• Internal ping / uptime checks on a schedule
• Outage records (start/end) and monthly availability style reporting in the UI
• Manual ping from the admin for verification

This is not a substitute for an external multi-region uptime service; it complements on-site monitoring.

Privacy

• No front-end visitor tracking in the current public release (traffic module removed from the UI). Use a dedicated analytics plugin if you need visitor statistics.
• Support contact fields are stored as WordPress options and are controlled by the site admin.
• Image optimization may store attachment post meta (e.g. backup paths, WebP paths). On uninstall, plugin options and that post meta are removed; generated image files on disk are kept so front-end URLs are not broken.
• Recovery tokens are short-lived and single-use.
• The plugin does not require an account on a third-party service to operate the core dashboard.