Pirkoo Wordpress Plugin - Rating, Reviews, Demo & Download
Plugin Description
Pirkoo, the On-board Diagnostics Scanner for WooCommerce, connects your store to app.pirkoo.com, where you and your team see how healthy your store is. The plugin has no screen in wp-admin: it adds Connect to Pirkoo under its name on the Plugins screen, and answers Pirkoo’s scans once the store is connected. Agencies follow all their clients’ stores in one place.
The dashboard shows:
- A store health score out of 100, with its risk level (80–100 low, 50–79 moderate, 0–49 high) and how many of the scanner’s 44 checks it is based on
- Needs attention: the problems that cost the most points, each linked to its check
- Store health trends: how your score changed since your previous and first scans, scan by scan
- Your store’s profile: sales and checkout over the last 30 days as counted on your store, products and inventory, payment and shipping methods, and traffic and marketing
- The scanner pipeline: all 44 checks, stage by stage (server, store pages, front end, database, background tasks, platform, security and email), coloured red, orange, yellow or green like a CI/CD pipeline. Click a check to see what was measured and against which reference
Every problem a check finds lowers the score by a share of what’s left: more for the cart, checkout, HTTPS, search visibility and registration, less for upkeep issues. Checks that couldn’t be measured, or don’t apply to your site (for example, search engines blocked on a staging site), are left out and counted.
Pirkoo’s scanner measures your store from outside, the way a shopper’s browser loads it, and adds the figures the plugin reads inside WordPress. The plugin changes nothing on your store.
How it works
- Install and activate the plugin. Nothing is sent yet.
- On the Plugins screen, click Connect to Pirkoo under Pirkoo’s name (administrators and shop managers).
- On app.pirkoo.com, log in with your email (a link is emailed to you, no password) and confirm the connection, right under the list of what is collected.
- Pirkoo scans the store once a day on its own, and whenever you click Scan now in the app; the dashboard shows the latest results and the score history.
- To stop, click Disconnect from Pirkoo on the Plugins screen, or disconnect the store in the app.
External services
This plugin uses Pirkoo (https://app.pirkoo.com), run by MB TVARKOM SOFTWARE (Lithuania), to scan your store and show the results. It contacts nobody until an administrator clicks Connect to Pirkoo on the Plugins screen and confirms on app.pirkoo.com, right under a list of what is collected, which accepts Pirkoo’s Privacy Policy. Before that, nothing is sent.
Connecting: the click sends your browser to https://app.pirkoo.com/connect with your store’s address, the plugin’s REST address on it, and a one-time code (valid 10 minutes). After you confirm there, app.pirkoo.com calls https://<your store>/wp-json/pirkoo/v1/connect with that code, and the plugin answers with a new connection secret. From then on the plugin answers only requests signed with that secret.
Each scan, when someone in your Pirkoo account starts one, and once a day on its own (between 02:00 and 05:00 in your store’s timezone): app.pirkoo.com calls https://<your store>/wp-json/pirkoo/v1/collect (signed), and the plugin answers with your store’s home URL, cart and checkout URLs, the site’s admin email, the store’s name, timezone, date and time formats and language, the titles your store gives its enabled payment and shipping methods (never their settings), the folder names of the installed plugins and whether each is active (so the app can tell which recommended plugins you already have), and:
- PHP, WordPress and WooCommerce versions
- Database and options table sizes, autoloaded options size, and the names and sizes of the 20 largest autoloaded options (never their contents)
- Names, sizes and estimated row counts of database tables no active plugin or theme matches, each with the name of the switched-off or not-installed plugin or theme it likely belongs to
- Number of active plugins, object cache type,
memory_limit,WP_MEMORY_LIMIT,max_execution_timeand whether OPcache is on - Action Scheduler task counts (pending, overdue, failed), how late WP-Cron is, failed tasks grouped by hook with their count and last error message (with emails, links, IP addresses and long numbers removed), and the hook names and times of tasks more than 15 minutes late (never their arguments)
- Orders in the last 30 days as a range (for example 50–200)
- Your store’s business context: country and currency; the number of paid and on-hold orders in the last 30 days, and of failed, pending and cancelled orders; gross sales in the last 30 days and the average order value, in your store’s currency; how many customers in the last 30 days were new and how many returning (two counts, no customer is identified); the number of published products and variations and whether stock management is on; the IDs of the enabled payment gateways and shipping methods (for example
stripe,flat_rate), never their settings or keys; whether checkout uses the Checkout block or the classic shortcode, and whether High-Performance Order Storage is on; the database and web server product; how many of your theme’s WooCommerce template overrides are outdated; how many plugins have an update waiting; the name of an active backup plugin, if any; the domain your store’s emails come from (never the address), for its SPF and DMARC records; and how many orders in the last 30 days came from each source type and from the 10 most common campaign sources, from WooCommerce Order Attribution - Site checks: whether a WordPress or theme update is waiting (from WordPress’s own update check), whether
WP_DEBUGandWP_DEBUG_DISPLAYshow errors on your pages, the site’s WordPress environment type (production, staging, development or local, so a staging copy isn’t marked down for blocking search engines or showing debug output), whether search engines are asked not to index the store, how many of your database tables use the MyISAM engine or a character set other than utf8mb4, how many expired transients are stored, how many administrator accounts exist (a count; no user is read), and whether the dashboard file editor is on; the upload limit, missing PHP extensions, free and total disk space, the server’s 1-minute load and CPU core count, and its total and available memory; how many plugins and themes WordPress paused after a fatal error, how many fatal errors your PHP error log shows for the last 7 days (the plugin reads the end of the log on your server and sends only the count), the automatic update settings for core and how many plugins update themselves, and whether permalinks are plain; the database’s response time to a trivial query and how many spam comments, auto-drafts and revisions older than 30 days it holds; how many WordPress core files differ from, or are missing against, WordPress.org’s official checksums; wp-config.php’s file permissions; whether a user named “admin” exists; and whether registration is open and the role new accounts get - Shop activity: how many products were added to the cart, checkout pages opened and orders placed over the last 30 days. The plugin counts these on your server in a small table of daily totals (its name ends in
pirkoo_funnel): no cookies, no browser script and nothing about the shopper. Logged-in administrators and shop managers aren’t counted. Days older than 35 are deleted, and uninstalling the plugin removes the table - A checkout profile: the plugin loads your checkout page once from your own server, with one product in a temporary cart that is never saved (nothing is ordered), and sends plugin, theme and hook names with their timings and call counts, database query shapes with every value replaced by
?, the host names (not the full addresses) of outside services called, object cache hit and miss counts, peak memory and the page’s server time. Analytics or marketing plugins that record checkout visits on the server may count that page load as one visit
Option, table, task and host names have email addresses, long numbers and identifiers replaced before they’re sent, and campaign names that look like one count as “other”. Pirkoo’s scanner then loads your homepage, cart and checkout pages like a visitor, checks your domain’s HTTPS certificate and its SPF and DMARC records in public DNS, and requests 18 well-known addresses on your store (backups of wp-config.php, .env, wp-content/debug.log, .git/config, database dumps, site archives and phpinfo pages) to see whether any can be downloaded. It reads at most 4 KB of each answer and keeps only how many were found.
WordPress.org: for the core files check, the plugin asks https://api.wordpress.org/core/checksums/1.0/ for the official checksums of your WordPress version and language, the same request WordPress makes for its own updates. It sends the version and language only. WordPress.org’s privacy policy: https://wordpress.org/about/privacy/
Disconnecting: Disconnect from Pirkoo tells https://app.pirkoo.com/api/stores/disconnect (signed with the secret) and deletes the secret; app.pirkoo.com can also ask https://<your store>/wp-json/pirkoo/v1/disconnect to delete it. After that the plugin answers nothing.
For a scan, the plugin never reads customers’ names, emails or addresses or order contents, and never sends option contents or task arguments.
WordPress management (from 0.4): app.pirkoo.com calls https://<your store>/wp-json/pirkoo/v1/inventory (signed) once a day and when you open its Plugins, Themes, Core, Vulnerabilities or PHP issues pages. The plugin answers with WordPress’s version and the newest one offered, each installed plugin’s and theme’s name, folder, version, author, whether it’s active, the update offered and whether it updates on its own, and the PHP errors of the last 7 days in the store’s PHP log, grouped (level, message, file and line, count, last time) with email addresses, IP addresses, links and long numbers replaced. To list updates, the plugin runs WordPress’s own update checks with WordPress.org. When an Owner or Admin of your Pirkoo company clicks Update in the app, app.pirkoo.com calls https://<your store>/wp-json/pirkoo/v1/update (signed) and the plugin updates that plugin, theme or WordPress the way Dashboard Updates does. Nothing is activated, deactivated or deleted from the app.
Monitoring (from 0.4, without the plugin’s involvement): app.pirkoo.com requests your store’s home page every 5 minutes from Amsterdam (uptime, response time, HTTPS certificate expiry), reads up to 200 of its public pages once a week to find broken links and images (never cart, checkout, account, admin or add-to-cart addresses), and once a day sends only the home page’s address to Google PageSpeed Insights (https://developers.google.com/speed/docs/insights/v5/about), which tests its performance; Google’s terms: https://developers.google.com/terms, privacy: https://policies.google.com/privacy. Vulnerabilities are found by comparing the inventory with Wordfence Intelligence’s public list (https://www.wordfence.com/threat-intel/), downloaded by app.pirkoo.com; nothing about your store is sent to Wordfence.
Relay mode (from 0.4, only for a store whose firewall blocks app.pirkoo.com’s requests, and only after an administrator accepts it while connecting): instead of answering the app’s requests, the plugin fetches them. It sends signed requests to https://app.pirkoo.com/api/stores/poll (the store’s address, to receive the app’s pending requests) and https://app.pirkoo.com/api/stores/result (the answer to each: the same data the routes above return), every 5 minutes from WP-Cron and when the app asks through the store’s home page (?pirkoo_poke=, signed by the app). While connecting, the plugin posts the new connection secret to https://app.pirkoo.com/api/stores/relay, and answers one request to the home page (?pirkoo_verify=) proving the store’s address. Nothing else changes: the same data, for the same purposes.
Store records (from 0.4): app.pirkoo.com calls https://<your store>/wp-json/pirkoo/v1/sync (signed) for the store’s records, a page at a time: the last 12 months when the store connects, then what changed, once a day. They are orders (number, status, dates, totals, payment method title, items with quantities, prices and attributes, coupons and refunds) with the billing customer’s name, email, phone, company, city, state, postcode and country; registered customers (name, email, phone, city, state, postcode, country, registration date); products and variations (name, SKU, prices, stock, categories, attributes); and coupons (code, type, amount, dates, use count). Never street addresses, shipping details, order notes, IP addresses or payment details. Pirkoo processes the shoppers’ data on your behalf, to show it to your team on app.pirkoo.com, keeps orders 12 months and deletes everything when you remove the store; ask privacy@pirkoo.com for a data processing agreement.
What Pirkoo keeps: each scan’s results and analysis linked to your store, for 12 months after the scan: the score and risk level, which checks cost points and how many, the measurements, and the full analysis this plugin shows you (the store data, business context and sales figures above, and what Pirkoo found in them), never the fix plan. They’re used to show you this dashboard and your score history, to answer you when you contact Pirkoo, and, across stores, to improve the scanner. Pirkoo also keeps the latest business context of your store (without sales amounts), replaced by each scan, for totals across stores and support. Each scan request (store, page addresses, time) is kept for 24 months, with the admin email erased from it after 90 days; the store’s contact email is deleted after 12 months without a scan.
Uninstalling the plugin deletes its settings, connection secret and table of daily totals from your store; records on our side follow the periods above. To have them deleted sooner, email privacy@pirkoo.com.
- Privacy Policy: https://pirkoo.com/privacy/ (also shipped with the plugin,
legal/privacy-policy.txt) - Terms of Use: https://pirkoo.com/terms/ (also shipped with the plugin,
legal/terms-of-use.txt)
Screenshots
No screenshots provided

