Devenia Speed Optimization vs Quantely Activity

Devenia Speed Optimization scans local WordPress image and video attachments, finds oversized files that can slow pages, shows where they are used, and reports what should be reviewed first. Version 0.3.61 addresses the initial WordPress.org review feedback and improves customer-facing service wording. The plugin can be used for local reporting without connecting to Devenia or a payment provider. Paid Devenia service features are optional and require a site administrator to start or enable them. Features Manual and scheduled scans. Scan scheduling after media, content, and theme changes. Configurable image/video thresholds, scan limit, priority pages to check, scheduled scans, and optional email alerts. Customer-controlled image/video format policy for preserving URLs, sidecar modern formats with fallback, or explicit modern-format URL changes. File size, dimensions, generated sizes, upload data, and local-file reporting. Frontend page evidence for content URLs, block references, and featured images. Rendered-size checks for images used on real pages. Customer report, Devenia review data, and repair plan. Controlled repair plans for Devenia optimization service work. Safe replacement with backup, restore, and a replacement check. Tracked service requests from the customer report without automatic external email sending. Redo request status tracking, Devenia review notes, keep-current close action, new-version preview/apply, manual review handling, and restore-original action. Priority score and recommendation. WP-CLI validation command: wp devenia-speed-optimization scan. Optional automation tools for settings, scans, reports, repair jobs, replacement, restore, backups, service requests, and redo requests. External services The local scan, report, settings, scheduled scan, backup, restore, and WP-CLI features run on the WordPress site itself. They do not require an external Devenia connection. Optional paid Devenia service features can connect to Devenia’s service API at https://optiworker.devenia.com. This happens only after a site administrator configures or starts a Devenia service action such as checkout, paid image handling, redo review, full automation, service status updates, or replacement delivery. When these optional service features are used, the plugin may send the Devenia service API the site URL, site name, WordPress admin URL, plugin version, selected service request details, customer name/email entered for checkout, media attachment IDs, file names, file URLs, MIME types, file sizes, dimensions, file checksums, affected frontend page URLs, report findings, redo reason/notes, callback URLs, and site-specific service keys needed to deliver the requested service and update the local order status. If embedded checkout is shown for an optional paid Devenia service request, the plugin loads Airwallex’s hosted checkout component from https://static.airwallex.com/components/sdk/v1/index.js. Payment creation and payment status are handled through Devenia’s service API and Airwallex. The plugin does not store Airwallex merchant API credentials. Service links: Devenia terms of service: https://devenia.com/terms/ Devenia privacy policy: https://devenia.com/privacy-policy/ Devenia website: https://devenia.com/ Airwallex terms: https://www.airwallex.com/global/terms/sign-up-terms Airwallex website: https://www.airwallex.com/

Lightweight, privacy-conscious pageview and event logging plugin that runs inside your own website. Quantely Activity is built to capture activity reliably under imperfect conditions through server-side recording and optional client-side signals, while supporting filtering for bots, unwanted pages, IP sources and selectable WordPress logged-in roles. Quantely Activity can be used for: Monitoring site behavior Reviewing traffic patterns Security and bot analysis Feeding downstream analytics layers Quantely Activity is turn-key: install it, and pageviews and events should begin appearing shortly after. Raw activity data is retained for a configurable short period, helping keep the plugin lightweight and privacy-conscious. What Quantely Activity is Quantely Activity is a capture and monitoring layer. It is designed to record activity on your site in a structured and reliable way, with a strong focus on signal capture and data integrity. Unlike many analytics tools, it does not focus on marketing analytics, attribution modelling, or behavioral profiling. It also does not rely solely on browser JavaScript. A server-side baseline helps ensure pageviews are still captured when scripts or beacons fail. Hybrid capture engine The plugin combines server-side pageview capture with optional browser-side signals. Typical flow: Browser request ↓ Server pageview baseline ↓ Browser attach (Beacon) – engagement pings – interaction events ↓ Correlation via pageview identifiers ↓ Bot classification and exclusions ↓ Deduplication and storage This architecture helps keep capture reliable under real-world conditions where browser-only tracking can miss signals. Event correlation and deduplication Quantely Activity links browser-side signals back to the pageview where they occurred. Engagement pings, clicks, form submissions, and similar events can be correlated to their originating pageview. Built-in deduplication helps avoid duplicate records when similar signals are captured from both browser and server-side sources. This keeps the activity stream more accurate and easier to interpret. Fully on-site All captured activity is stored in your own WordPress database. Quantely Activity does not send captured activity data to external services. IP addresses are never stored in plain form, and the plugin does not perform cross-site tracking. Privacy-aware design The plugin is designed with privacy-conscious principles in mind: No plain IP addresses stored Short configurable retention window Optional honoring of GPC / DNT signals No external tracking services Data remains on your own site This gives site owners visibility into activity while keeping capture local and controlled. Hooks Quantely Activity exposes a small developer API for integrations and downstream processing. qmon_hit_before_insert — Filter a normalized hit array before it is stored. qmon_hit_recorded — Action fired after a hit has been stored. This is the main integration point for forwarding or persisting captured records. qmon_event_normalize — Filter a normalized event payload before it is finalized. qmon_event_db_dedupe_window_sec — Filter the database deduplication window for events. qmon_bot_verdict — Filter the bot-classification verdict before it is finalized.