A store audit that names the plugin setting to change.
WooCommerce stores differ by plugin stack. The audit reads the rendered page, then explains each fix in WordPress terms.
Woocommerce stores in our scans average 64 out of 100 across 24 audits.
In short
What does a WooCommerce store audit check?
A WooCommerce store audit loads your home page and a product page at desktop and mobile sizes and runs 200+ checks on speed, conversion, trust, tracking and discovery. It reads the rendered page, so it sees the combined result of your theme and every plugin.
Problems that come with a large plugin stack
01
Plugin scripts loading on every page
A form or slider plugin that loads its scripts and styles sitewide adds weight to pages that never use it.
02
Two plugins writing the same tracking tag
A theme option and an analytics plugin each add Google Analytics, and one property double counts.
03
A slow server response
Without page caching, a busy product page waits on the database and the server takes well over 800ms to answer.
04
Duplicate structured data
WooCommerce and an SEO plugin can each output Product data, which gives search engines two versions to choose between.
05
No cookie consent that actually blocks
A banner that loads while the tags fire anyway protects nobody and can break local rules.
06
Images uploaded at camera size
Full-size uploads served into small slots add megabytes to the page and push Largest Contentful Paint past 2.5 seconds.
What the audit gives a WooCommerce store
Fixes for WordPress
Steps point at the plugin setting to open or the snippet to remove instead of telling you to improve performance.
Page weight and scripts
See how much each page transfers and which third-party scripts load, which is where a large plugin stack costs most.
Tracking checks
Whether the Meta Pixel and Google Analytics 4 fire once, and whether a cookie consent mechanism is present.
A report that shows its work
Open any finding to see the page, element or measured value it came from. The Store Health Score is calculated from every finding, so the number reflects all of them, not only the ones shown first.
Example report
Store Health Score
Grade C, 200+ checks
How a WooCommerce store is scored
Speed
Largest Contentful Paint, Interaction to Next Paint from real visitors, server response time, page weight, image formats and third-party script weight, taken from Google PageSpeed Insights.
Conversion and UX
Whether the price and buy button fit the first phone screen, how many angles the gallery shows, breadcrumbs, search, tap targets and what the first screen says the store sells.
Trust and policies
Returns, shipping, privacy and terms pages that shoppers can find, review ratings on the product page, a way to make contact and a store served over HTTPS.
Tracking and tech
Whether the Meta Pixel fires PageView, whether Google Analytics 4 collects, duplicate properties, double-loaded tags and a cookie consent mechanism.
Store discovery
Indexability, canonical URLs, Product structured data with a real price and availability, and what a shared link looks like.
200+
checks in total. Each area is scored on its own, then weighted into the single Store Health Score.
Checks that matter on a WooCommerce store
The share of audited stores that fail each check, among the stores where it applies.
WooCommerce fixes the report points to
Heavy page weight
A 4MB home page with several slider and form plugin scripts.
The fix
In the plugin settings, load scripts only on the pages that use them, and resize images to the slot they fill.
Two analytics tags
The theme and an analytics plugin both add Google Analytics.
The fix
Keep one source. Turn off the tracking option in the theme or in the plugin.
Slow server response
The server takes more than a second to answer the first request.
The fix
Turn on page caching in your caching plugin or at your host, then run the audit again to see the new time.
Checking a WooCommerce store by hand, and checking it here
By hand
- Deactivate plugins one at a time to find the slow one
- View page source to hunt for duplicate tags
- Compare structured data in a separate testing tool
- Check each fix did not break checkout
With CROMagnet
- Every script and its weight listed in one report
- Duplicate tags and pixels flagged with the requests that show it
- Product structured data checked for a real price and availability
- A history that marks regressions after each change
How it works on a WooCommerce store
The audit works on a store you do not own, so the same steps apply to a competitor or a prospect.
01 Paste your store address
Any public WooCommerce store works, with no plugin to install.
02 The audit loads two real pages
A browser opens your home page and a product page at desktop and mobile sizes.
03 Work through the critical issues
Start with the red group and follow the steps for your setup.
04 Re-run after each plugin or theme update
An update that reopens an old problem shows up as regressed.
Keep a WooCommerce store checked
Pro, $19 a month
For a store owner who wants to find what is costing sales and prove it got fixed.
- 15 audits a month
- 1 sites
- 1 seat
- 7-day money-back guarantee
001 Does the audit need a WordPress plugin?
No. It reads public pages, so nothing is added to your site.
002 Can it tell me which plugin is slowing the store?
It lists the scripts that load and their weight, which points you to the plugin behind each one.
003 Is my hosting the problem?
The speed checks include server response time. A slow server shows up as its own finding.
004 Does it work with any theme?
Yes. It reads the rendered page, so the theme does not matter.
005 Does it check the checkout page?
It checks the public pages: home and product. Pages behind a login are not read.
More ways to use the audit
See where your store stands today.
Free, and the report link works as soon as the audit starts.