{"id":403536,"date":"2026-11-15T19:59:21","date_gmt":"2026-11-15T19:59:21","guid":{"rendered":"https:\/\/wordpress.org\/plugins\/on-board-diagnostics-scanner-for-woocommerce\/"},"modified":"2026-11-15T19:58:50","modified_gmt":"2026-11-15T19:58:50","slug":"pirkoo","status":"publish","type":"plugin","link":"https:\/\/wordpress.org\/plugins\/pirkoo\/","author":23581502,"comment_status":"closed","ping_status":"closed","template":"","meta":{"version":"0.4.0","stable_tag":"0.4.0","tested":"7.1.4","requires":"6.5","requires_php":"7.4","requires_plugins":null,"header_name":"Pirkoo","header_author":"tvarkom","header_description":"On-board Diagnostics Scanner for WooCommerce","last_updated":"2026-11-15 19:58:50","external_support_url":"","external_repository_url":"","donate_link":"","header_plugin_uri":"https:\/\/pirkoo.com","header_author_uri":"https:\/\/tvarkom.com","rating":0,"author_block_rating":0,"active_installs":0,"downloads":50,"num_ratings":0,"support_threads":0,"support_threads_resolved":0,"author_block_count":0,"sections":["description","faq","changelog"],"tags":{"0.4.0":{"tag":"0.4.0","author":"tvarkom","date":"2026-11-15 19:58:50","revision":3803795}},"upgrade_notice":[],"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3806072,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3806072,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256},"icon.svg":{"filename":"icon.svg","revision":3806072,"resolution":false,"location":"assets","locale":false}},"assets_banners":[],"assets_blueprints":{},"all_blocks":[],"tagged_versions":["0.4.0"],"block_files":[],"assets_screenshots":[],"screenshots":[]},"plugin_section":[],"plugin_tags":[434,1508,247,794,286],"plugin_category":[45,52,54],"plugin_contributors":[290538],"plugin_business_model":[],"class_list":["post-403536","plugin","type-plugin","status-publish","hentry","plugin_tags-dashboard","plugin_tags-health","plugin_tags-performance","plugin_tags-speed","plugin_tags-woocommerce","plugin_category-ecommerce","plugin_category-performance","plugin_category-security-and-spam-protection","plugin_contributors-tvarkom","plugin_committers-tvarkom"],"banners":[],"icons":{"svg":"https:\/\/ps.w.org\/pirkoo\/assets\/icon.svg?rev=3806072","icon":"https:\/\/ps.w.org\/pirkoo\/assets\/icon.svg?rev=3806072","icon_2x":false,"generated":false},"screenshots":[],"raw_content":"<!--section=description-->\n<p>Pirkoo, the On-board Diagnostics Scanner for WooCommerce, connects your store to <strong>app.pirkoo.com<\/strong>, where you and your team see how healthy your store is. The plugin has no screen in wp-admin: it adds <strong>Connect to Pirkoo<\/strong> 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.<\/p>\n\n<p>The dashboard shows:<\/p>\n\n<ul>\n<li><strong>A store health score<\/strong> out of 100, with its risk level (80\u2013100 low, 50\u201379 moderate, 0\u201349 high) and how many of the scanner's 44 checks it is based on<\/li>\n<li><strong>Needs attention<\/strong>: the problems that cost the most points, each linked to its check<\/li>\n<li><strong>Store health trends<\/strong>: how your score changed since your previous and first scans, scan by scan<\/li>\n<li><strong>Your store's profile<\/strong>: sales and checkout over the last 30 days as counted on your store, products and inventory, payment and shipping methods, and traffic and marketing<\/li>\n<li><strong>The scanner pipeline<\/strong>: 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<\/li>\n<\/ul>\n\n<p>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.<\/p>\n\n<p>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.<\/p>\n\n<h4>How it works<\/h4>\n\n<ol>\n<li>Install and activate the plugin. Nothing is sent yet.<\/li>\n<li>On the Plugins screen, click <strong>Connect to Pirkoo<\/strong> under Pirkoo's name (administrators and shop managers).<\/li>\n<li>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.<\/li>\n<li>Pirkoo scans the store once a day on its own, and whenever you click <strong>Scan now<\/strong> in the app; the dashboard shows the latest results and the score history.<\/li>\n<li>To stop, click <strong>Disconnect from Pirkoo<\/strong> on the Plugins screen, or disconnect the store in the app.<\/li>\n<\/ol>\n\n<h3>External services<\/h3>\n\n<p>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 <strong>Connect to Pirkoo<\/strong> 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.<\/p>\n\n<p><strong>Connecting<\/strong>: the click sends your browser to <code>https:\/\/app.pirkoo.com\/connect<\/code> 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 <code>https:\/\/&lt;your store&gt;\/wp-json\/pirkoo\/v1\/connect<\/code> with that code, and the plugin answers with a new connection secret. From then on the plugin answers only requests signed with that secret.<\/p>\n\n<p><strong>Each scan<\/strong>, 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 <code>https:\/\/&lt;your store&gt;\/wp-json\/pirkoo\/v1\/collect<\/code> (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:<\/p>\n\n<ul>\n<li>PHP, WordPress and WooCommerce versions<\/li>\n<li>Database and options table sizes, autoloaded options size, and the names and sizes of the 20 largest autoloaded options (never their contents)<\/li>\n<li>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<\/li>\n<li>Number of active plugins, object cache type, <code>memory_limit<\/code>, <code>WP_MEMORY_LIMIT<\/code>, <code>max_execution_time<\/code> and whether OPcache is on<\/li>\n<li>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)<\/li>\n<li>Orders in the last 30 days as a range (for example 50\u2013200)<\/li>\n<li>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 <code>stripe<\/code>, <code>flat_rate<\/code>), 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<\/li>\n<li>Site checks: whether a WordPress or theme update is waiting (from WordPress's own update check), whether <code>WP_DEBUG<\/code> and <code>WP_DEBUG_DISPLAY<\/code> show 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<\/li>\n<li>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 <code>pirkoo_funnel<\/code>): 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<\/li>\n<li>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 <code>?<\/code>, 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<\/li>\n<\/ul>\n\n<p>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.<\/p>\n\n<p><strong>WordPress.org<\/strong>: for the core files check, the plugin asks <code>https:\/\/api.wordpress.org\/core\/checksums\/1.0\/<\/code> 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\/<\/p>\n\n<p><strong>Disconnecting<\/strong>: <strong>Disconnect from Pirkoo<\/strong> tells <code>https:\/\/app.pirkoo.com\/api\/stores\/disconnect<\/code> (signed with the secret) and deletes the secret; app.pirkoo.com can also ask <code>https:\/\/&lt;your store&gt;\/wp-json\/pirkoo\/v1\/disconnect<\/code> to delete it. After that the plugin answers nothing.<\/p>\n\n<p>For a scan, the plugin never reads customers' names, emails or addresses or order contents, and never sends option contents or task arguments.<\/p>\n\n<p><strong>WordPress management<\/strong> (from 0.4): app.pirkoo.com calls <code>https:\/\/&lt;your store&gt;\/wp-json\/pirkoo\/v1\/inventory<\/code> (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 <code>https:\/\/&lt;your store&gt;\/wp-json\/pirkoo\/v1\/update<\/code> (signed) and the plugin updates that plugin, theme or WordPress the way Dashboard \u2192 Updates does. Nothing is activated, deactivated or deleted from the app.<\/p>\n\n<p><strong>Monitoring<\/strong> (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.<\/p>\n\n<p><strong>Relay mode<\/strong> (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 <code>https:\/\/app.pirkoo.com\/api\/stores\/poll<\/code> (the store's address, to receive the app's pending requests) and <code>https:\/\/app.pirkoo.com\/api\/stores\/result<\/code> (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 (<code>?pirkoo_poke=<\/code>, signed by the app). While connecting, the plugin posts the new connection secret to <code>https:\/\/app.pirkoo.com\/api\/stores\/relay<\/code>, and answers one request to the home page (<code>?pirkoo_verify=<\/code>) proving the store's address. Nothing else changes: the same data, for the same purposes.<\/p>\n\n<p><strong>Store records<\/strong> (from 0.4): app.pirkoo.com calls <code>https:\/\/&lt;your store&gt;\/wp-json\/pirkoo\/v1\/sync<\/code> (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.<\/p>\n\n<p><strong>What Pirkoo keeps<\/strong>: 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.<\/p>\n\n<p>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.<\/p>\n\n<ul>\n<li>Privacy Policy: https:\/\/pirkoo.com\/privacy\/ (also shipped with the plugin, <code>legal\/privacy-policy.txt<\/code>)<\/li>\n<li>Terms of Use: https:\/\/pirkoo.com\/terms\/ (also shipped with the plugin, <code>legal\/terms-of-use.txt<\/code>)<\/li>\n<\/ul>\n\n<!--section=faq-->\n<dl>\n<dt id=\"does%20it%20slow%20down%20my%20store%3F\"><h3>Does it slow down my store?<\/h3><\/dt>\n<dd><p>No. Apart from adding one to a daily total when a shopper adds to cart, opens the checkout or orders, the plugin runs only when Pirkoo scans the store (once a day, at night in your store's timezone, and when you ask): it collects its figures and loads your checkout once to profile it. Nothing runs in the background. The scanner runs on Pirkoo's servers and loads your public pages like one visitor would.<\/p><\/dd>\n<dt id=\"why%20does%20my%20store%20need%20to%20be%20public%3F\"><h3>Why does my store need to be public?<\/h3><\/dt>\n<dd><p>Pirkoo's scanner measures your store from the internet, like a shopper. Stores on localhost, behind a password or in maintenance mode can't be scanned, and app.pirkoo.com needs to reach the WordPress REST API at <code>\/wp-json\/pirkoo\/<\/code> (allow it in a security plugin or firewall that blocks it).<\/p><\/dd>\n<dt id=\"how%20often%20is%20my%20store%20scanned%3F\"><h3>How often is my store scanned?<\/h3><\/dt>\n<dd><p>Once a day on its own, between 02:00 and 05:00 in your store's timezone (skipped if a scan ran in the 12 hours before). You can also click <strong>Scan now<\/strong> in the app, from 10 minutes after the previous scan finishes, up to 30 times a day.<\/p><\/dd>\n<dt id=\"is%20pirkoo%20free%3F\"><h3>Is Pirkoo free?<\/h3><\/dt>\n<dd><p>Yes: the plugin is free, and so is the Pirkoo service at app.pirkoo.com for now. It's offered to a limited number of companies while we finish it: a company can use everything for its first 14 days; after that it's read-only (dashboards and history stay available; scans, the daily copies, updates and monitoring pause) unless we've agreed with it to go on. Write to support@pirkoo.com. We plan to offer paid plans later, with new terms published first.<\/p><\/dd>\n<dt id=\"does%20it%20send%20anything%20on%20its%20own%3F\"><h3>Does it send anything on its own?<\/h3><\/dt>\n<dd><p>No. Nothing is sent before the store is connected, and after that only when app.pirkoo.com asks the plugin for a scan's data: once a day, and when someone starts a scan. To stop, disconnect the store; to remove its settings, delete the plugin.<\/p><\/dd>\n<dt id=\"what%20if%20my%20wp-admin%20has%20another%20address%3F\"><h3>What if my wp-admin has another address?<\/h3><\/dt>\n<dd><p>The Connect and Disconnect links are built with WordPress's own admin address (<code>admin_url()<\/code>), which plugins that rename wp-admin (for example to \/meu-painel) change too, and app.pirkoo.com only calls <code>\/wp-json\/pirkoo\/<\/code>, never wp-admin.<\/p><\/dd>\n<dt id=\"who%20makes%20pirkoo%3F\"><h3>Who makes Pirkoo?<\/h3><\/dt>\n<dd><p>Pirkoo is made by tvarkom (MB TVARKOM SOFTWARE, Lithuania), which builds diagnostic tools for WooCommerce stores. Contact: support@pirkoo.com.<\/p><\/dd>\n\n<\/dl>\n\n<!--section=changelog-->\n<h4>0.4.0<\/h4>\n\n<ul>\n<li>Relay mode, for a store whose firewall blocks app.pirkoo.com: when the app can't reach the plugin, it offers to connect the other way round, and the store then calls app.pirkoo.com for its requests (when the app asks, and every 5 minutes).<\/li>\n<li>In Brazilian Portuguese too, as is app.pirkoo.com (choose the language in its account menu).<\/li>\n<li>Works behind more firewalls: the plugin's own signed routes pass a site that blocks the REST API for visitors who aren't logged in, and app.pirkoo.com reaches the plugin through <code>?rest_route=<\/code> when <code>\/wp-json\/<\/code> is blocked.<\/li>\n<li>Plugins, themes and WordPress core in app.pirkoo.com, with their updates, an Update button for Owners and Admins, known vulnerabilities and the store's PHP errors of the last 7 days.<\/li>\n<li>Each scan sends the installed plugins' folder names and whether each is active, so app.pirkoo.com can tick the recommended plugins your store already has.<\/li>\n<li>app.pirkoo.com shows your store's orders, refunds, customers, products, variations, categories, top sellers, products bought together, stock velocity, variation attributes and coupons: the plugin answers its signed requests for them (the last 12 months when you connect, then what changed, once a day).<\/li>\n<\/ul>\n\n<h4>0.3.2<\/h4>\n\n<ul>\n<li>The readme and the suggested privacy policy text describe Pirkoo's daily scans, and link the Terms of Use at https:\/\/pirkoo.com\/terms\/.<\/li>\n<li>The Privacy Policy and Terms of Use shipped with the plugin cover app.pirkoo.com: accounts, companies and daily scans.<\/li>\n<\/ul>\n\n<h4>0.3.1<\/h4>\n\n<ul>\n<li>Stores with plain permalinks or WordPress in a subfolder can connect: the plugin tells Pirkoo its REST address.<\/li>\n<li>Each scan sends the titles your store gives its payment and shipping methods, so the app shows them as your shoppers see them.<\/li>\n<\/ul>\n\n<h4>0.3.0<\/h4>\n\n<ul>\n<li>Pirkoo becomes a connector to app.pirkoo.com: Connect to Pirkoo and Disconnect from Pirkoo on the Plugins screen; scans start in the app, which asks the plugin for the store's data with signed requests.<\/li>\n<li>The WooCommerce \u2192 Pirkoo page, its dashboard and the store's key are removed (an update from 0.2.x deletes the key: connect the store again).<\/li>\n<li>The store's name, timezone, date and time formats and language are sent with each scan, for the app's pages.<\/li>\n<\/ul>\n\n<h4>0.2.3<\/h4>\n\n<ul>\n<li>Everything the plugin creates on your site is named after Pirkoo: its settings, its table of daily totals, its page's styles and the address the service checks when connecting (<code>\/wp-json\/pirkoo\/v1\/verify<\/code>).<\/li>\n<\/ul>\n\n<h4>0.2.2<\/h4>\n\n<ul>\n<li>Pirkoo's own address: the plugin now talks to https:\/\/api.pirkoo.com; the Privacy Policy is at https:\/\/pirkoo.com\/privacy\/; help at support@pirkoo.com and privacy requests at privacy@pirkoo.com.<\/li>\n<\/ul>\n\n<h4>0.2.1<\/h4>\n\n<ul>\n<li>The privacy policy shipped with the plugin is the current text, the same as tvarkom.com\/privacy\/.<\/li>\n<\/ul>\n\n<h4>0.2.0<\/h4>\n\n<ul>\n<li>The plugin's page is WooCommerce \u2192 Pirkoo.<\/li>\n<li>A new dashboard: the store summary, the store health score with how many checks it's based on, what needs attention first, your store's health trends, and your store's profile (sales and checkout as counted, catalog, operations, traffic and marketing).<\/li>\n<li>Every check now counts towards the score, by how much it matters; earlier scores keep the scoring model they were made with and aren't compared with new ones.<\/li>\n<li>The scan also sends the site's WordPress environment type, so a staging copy isn't marked down for blocking search engines or showing debug output.<\/li>\n<li>The store pipeline: every check as a coloured job, with what was measured and its reference.<\/li>\n<li>New checks: compression, WordPress and theme updates, debug output, search engine visibility, MyISAM tables and character set, expired transients, administrators and the file editor; upload limit, PHP extensions, disk space, server load and memory; paused plugins, fatal errors, automatic updates and permalinks; database latency and clutter; core files against WordPress.org's checksums, readable files, wp-config.php permissions, an \"admin\" username and open registration.<\/li>\n<li>Each scan now sends more store data (business context and a profile of one checkout page load), plus the site checks above, listed under External services; the plugin keeps a small table of daily shop totals.<\/li>\n<\/ul>\n\n<h4>0.1.0<\/h4>\n\n<ul>\n<li>First release: scan on demand (once a week), and a dashboard with the score, the points lost, server response, homepage weight, database and server figures, HTTPS and email records, and the score over time.<\/li>\n<\/ul>","raw_excerpt":"On-board Diagnostics Scanner for WooCommerce.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/403536","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=403536"}],"author":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/tvarkom"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=403536"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=403536"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=403536"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=403536"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=403536"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=403536"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}