Devenia Speed Optimization vs Web Plura Diagnostics – Site Health,

Devenia Speed Optimization scans image and video attachments on the WordPress installation. It finds oversized files, shows where they are used, and reports what should be reviewed first. The complete plugin is 100% free. Scans, reports, schedules, repair manifests, Media Library replacements, backups, and restores run on the WordPress installation. Media files and reports stay on that installation. Features Manual and scheduled local scans. Scan scheduling after media, content, and theme changes. Configurable image and video thresholds, scan limit, priority pages, and email alerts. File size, dimensions, generated sizes, upload data, and local-file reporting. Page evidence for content URLs, block references, featured images, and rendered sizes. Customer and operator reports with a local repair plan. Local repair manifests. Native Media Library replacement input. A persistent local backup before every approved replacement. Explicit replacement and restore confirmations. WP-CLI command: wp devenia-speed-optimization scan. Local WordPress abilities for settings, scans, reports, repair jobs, replacement, restore, and backups. Local operation All features run on the WordPress installation. Optional WordPress email alerts use the mail configuration of that installation. Links Stable plugin download: https://downloads.devenia.com/devenia-speed-optimization.zip Devenia Plugins: https://devenia.com/plugins/

Web Plura Diagnostics helps WordPress site owners, agencies, and support teams find problems that quietly hurt leads, sales, trust, and maintenance time. It runs inside wp-admin and turns local site signals into clear, prioritized action items. Use it when you need to answer practical questions before an update, launch, client handoff, or support call: Are forms, password resets, store emails, and lead notifications likely to work? Is the site showing health, hosting, cache, cron, or PHP warning signs? Which plugin, theme, or update risks should be checked before making changes? What should a business owner, developer, host, or support team fix first? What can be exported or shared without sending diagnostics to an external service? For every finding, the plugin focuses on: What is wrong Why it matters What business impact it may cause Who should fix it What to fix first No external account, no tracking, and no frontend scripts are required for the core diagnostics workflow. No external service requirement: core diagnostics, dashboard rendering, exports, and scheduled scans run locally in WordPress. No tracking: diagnostics scans do not send telemetry or site diagnostics to Web Plura by default. Free local checks remain available without an external account. Customer Problems It Helps Solve Missed leads from broken contact forms, weak email setup, or untested notification paths. Risky updates when a site has stale plugins, inactive code, commerce dependencies, or no clear pre-update checklist. Slow or unstable sites caused by cache gaps, low memory, cron pressure, upload limits, or hosting constraints. Confusing support handoffs where clients, developers, and hosts need the same problem summary. Reactive maintenance where issues are discovered only after checkout, login, email, or lead capture fails. Key Checks Fix First dashboard with score, priority groups, recommended actions, and recent-change history. Site Health-style checks for WordPress, database version, PHP limits, timezone, URL alignment, cache signals, and key file permissions. Email readiness checks for local mail transport, SPF, DKIM, DMARC, domain alignment, manual admin-triggered test email results, and optional bounded metadata-only test history. Diagnostics scans do not send email automatically. Lead Capture Health checks for form plugins, contact pages, SMTP readiness, privacy-page status, and form-plugin updates. Pre-update Safety checks for inactive plugins, theme update backlog, commerce plugins, builders, and cache plugins. Hosting Advisor checks for memory, cache, cron pressure, upload limits, execution limits, and host-support guidance. Cron & Background Jobs checks for WP-Cron configuration, overdue events, orphaned callbacks, repeated hooks, Action Scheduler presence, and WooCommerce queue backlog signals. Front-end Response checks for home URL HTTPS, response code, redirect signal, cache-control, compression header, and REST API response. Support-safe diagnostics snapshot with redacted environment, module scores, and top findings for support handoffs. Client-ready diagnostics with problem, impact, owner, urgency, next action, JSON/CSV exports, WP-CLI commands, and multisite network visibility. Good Fit For Site owners who want a clear first-pass health, email, performance, and update-readiness review. Agencies preparing client reports, maintenance checks, launch reviews, or pre-update safety notes. Support teams collecting safe local diagnostics before deeper troubleshooting. WordPress admins who want prioritized actions without telemetry or a required external account. Product page: https://wplura.com/products/web-plura-diagnostics Terms: https://wplura.com/terms Privacy: https://wplura.com/privacy External Services Web Plura Diagnostics is local-first. Diagnostics scans, dashboard rendering, exports, and scheduled scans run inside WordPress by default. The plugin links to Web Plura product, terms, and privacy pages for support and product information: Product page: https://wplura.com/products/web-plura-diagnostics Terms: https://wplura.com/terms Privacy: https://wplura.com/privacy The public WordPress.org package uses WordPress.org update checks. Direct/private Web Plura builds may request a signed Web Plura release manifest from https://api.wplura.com/v1/plugin/updates/web-plura-diagnostics/manifest and send only the plugin slug, current version, and release channel. Data, retention, and uninstall behavior: Diagnostics results, history snapshots, explain-mode preference, scheduled-scan settings, export metadata, and manual test-email metadata are stored locally in WordPress options/transients. Retention settings allow site admins to control how long local diagnostic history and email-test metadata are kept. Uninstall cleanup removes plugin-owned options, transients, scheduled scan hooks, and local diagnostic metadata.