WooCommerce Speed Test Plugin: Audit Your Store from WordPress Admin

Testing your WooCommerce store speed shouldn't require leaving your WordPress admin, navigating to an external tool, and copy-pasting URLs one by one. The WooCommerce Speed Audit plugin brings Google PageSpeed Insights directly into your dashboard — one click to audit your Shop, Cart, and Checkout pages with actionable results in plain English.

This guide covers how to install, configure, and use the plugin to understand exactly what's slowing your WooCommerce store down.

What the plugin does

The WooCommerce Speed Audit plugin is a free diagnostic tool that runs inside your WordPress admin. It does three things:

1. PageSpeed audit — tests your Shop, Cart, and Checkout pages through Google PageSpeed Insights (mobile strategy) and displays the results with letter grades, Core Web Vitals metrics, and ranked opportunities
2. Plugin compatibility scan — checks every active plugin against a database of known headless WooCommerce compatibility and categorises them as compatible, partial, or incompatible
3. Headless readiness score — calculates a 0–100% score based on your plugin mix, showing how ready your store is for a headless architecture upgrade

Installation

Method 1: Upload via WordPress admin

1. Download the plugin ZIP
2. In your WordPress admin, go to Plugins → Add New
3. Click Upload Plugin at the top of the page
4. Choose the downloaded ZIP file and click Install Now
5. Click Activate Plugin

Method 2: Upload via FTP/SFTP

1. Unzip the plugin file on your computer
2. Upload the wpbundle-speed-audit-plugin folder to /wp-content/plugins/
3. Go to Plugins in your WordPress admin and activate WooCommerce Speed Audit

Running your first audit

1. Go to WooCommerce → Speed Audit in your admin menu
2. Click Run Audit Now
3. Wait 30–60 seconds — the plugin sends each page to Google PageSpeed Insights for analysis

The audit tests three pages: your WooCommerce Shop page, Cart page, and Checkout page. Each gets its own score because they have very different performance characteristics:

• Shop page — usually your best score because it can be cached. Shows product listings, images, and filters.
• Cart page — typically slower because WooCommerce cannot cache it. Every load triggers PHP execution, database queries for cart items, and shipping/tax recalculation.
• Checkout page — often your slowest page. Cannot be cached, loads payment gateway scripts, validates nonces, and calculates real-time shipping rates.

Understanding the results

Performance scores

Each page gets a score from 0 to 100 with a letter grade:

• A (90–100) — Excellent. Rare for traditional WooCommerce.
• B (70–89) — Good. You've done solid optimisation work.
• C (50–69) — Average. Most WooCommerce stores land here.
• D (30–49) — Below average. Visitors are noticing.
• F (0–29) — Critical. Immediate action needed.

Core Web Vitals

The plugin shows six metrics for each page. The three that Google uses for search ranking are:

• Largest Contentful Paint (LCP) — when the main content loads. Under 2.5s is good. WooCommerce typically hits 3–6s due to PHP rendering.
• Total Blocking Time (TBT) — how long JavaScript blocks interaction. Under 200ms is good. WooCommerce often exceeds 500ms from jQuery, cart fragments, and plugin scripts.
• Cumulative Layout Shift (CLS) — visual stability. Under 0.1 is good. Common WooCommerce causes include images without dimensions and late-loading elements.

Top opportunities

The audit lists the top 5 speed improvements for each page, ranked by potential time savings. These are specific, actionable items like “Reduce unused JavaScript — potential savings: 1.2s” or “Properly size images — potential savings: 0.8s.”

Work through them top to bottom. The first item saves the most time and should be addressed first.

Plugin compatibility report

The scanner checks every active plugin and sorts them into categories:

• Compatible — works with a headless WooCommerce frontend (e.g., Yoast SEO, Stripe, WooCommerce Payments, image optimisers)
• Partial — works but may need configuration changes (e.g., caching plugins, security plugins)
• Incompatible — tied to the PHP frontend and replaced by headless components (e.g., Elementor, Divi, checkout customisers)
• Unknown — not yet assessed. Check with the plugin author for REST API support.

Configuring the API key (optional)

The plugin works without a Google API key by using the public PageSpeed Insights quota. However, the public quota is limited — if you get rate-limit errors, add a free API key:

1. Go to the Google PageSpeed API documentation
2. Create a free API key in the Google Cloud Console
3. Paste it into the PageSpeed API Key field in the plugin settings (below the audit results)
4. Click Save Settings

With an API key, you get a much higher daily quota and won't hit rate limits even if you run multiple audits per day.

What to do next

Once you have your audit results:

1. Fix the quick wins — work through the top opportunities for each page. Common fixes include image optimisation, disabling unused JavaScript, and enabling browser caching.
2. Re-run the audit — after making changes, click “Clear cache” in the plugin and re-run to measure improvement.
3. Check your compatibility score — if your headless readiness is 80%+, you're a great candidate for a headless upgrade that can push your score above 90.
4. Consider headless — if your optimised scores are still stuck below 70–80, the architecture is the bottleneck. WPBundle gives you a production-ready headless frontend without rebuilding your WooCommerce backend.