WooCommerce performance audit: know what's holding back your sales.

Before paying for optimizations, know which ones will pay off. The audit measures, quantifies and prioritizes: you walk away with an action plan ranked by impact, not a list of guesses.

Why audit before optimizing?

"WordPress is slow" is not a diagnosis. On a WooCommerce store, slowness always has precise, measurable causes: a script hitting the server on every page, autoloaded options bloating every SQL query, a legacy checkout, undersized hosting. The problem: these causes are invisible to the naked eye, and fixing them in the wrong order means paying for days of work for marginal gains.

The audit flips the logic. Measure first, quantify each problem, then rank actions by gain-to-effort ratio. You then decide with full knowledge: do it yourself, hand me the work, or give the report to your developer.

The express version of my method is public: the 15-minute audit. This page describes the full audit, the one that goes deep.

Free audit or full audit?

To know where you stand

Free audit

€0
  • External analysis, no admin access: the URL is enough
  • Field Core Web Vitals + key page loading behavior
  • Concise diagnosis: your top 3 to 5 priorities
  • Response within 48 hours, no commitment
Start for free
To know what to do, in what order

Full audit

€990
Net price · Fully deducted if you hire me after
  • Front end, database, checkout, infrastructure
  • Impact-ranked, quantified, actionable PDF report
  • Video debrief with a commented action plan
  • Delivered within 5 business days of receiving access
Request my audit

What the full audit covers.

01

Front end and Core Web Vitals

LCP, INP and CLS from field data (CrUX) and lab tests, measured on your page types: home, category, product, cart. Full waterfall: page weight, request count, third-party scripts, fonts, images, CSS and JavaScript loaded needlessly page by page.

02

The database

Autoloaded options (total weight and guilty plugins), slow queries and their origin, accumulated transients, WooCommerce tables (orders, sessions, Action Scheduler), and whether a Redis object cache makes sense for your catalog.

03

Checkout and purchase funnel

Checkout type (legacy or blocks), superfluous fields, payment gateway scripts, cart fragments, cache behavior on cart, checkout and account pages: the pages that take the money must neither slow down nor be cached by mistake.

04

Infrastructure

Real TTFB without cache, PHP version, server cache and CDN configuration (Cloudflare where applicable), hosting sized against your traffic and catalog. That's often where the glass ceiling hides.

The deliverable: a plan, not a novel.

An impact-ranked PDF report in three tiers. Each point is quantified (metric before, expected gain) and actionable by me, by you or by your team. The debrief happens over video: we walk through the plan and you ask all your questions.

  • 1
    Quick wins. Immediate impact, low risk, often done in a few hours.
  • 2
    Intermediate optimizations. A few days of work: assets, database, Cloudflare, checkout.
  • 3
    Structural work. HPOS migration, theme, data architecture, each with an effort estimate.

How it works.

  1. 1
    You request the audit through the form, with your store's URL.
  2. 2
    Scoping. I confirm the scope, you send the access (a dedicated admin account is enough in most cases).
  3. 3
    Audit. About two days of analysis, with zero changes to your site.
  4. 4
    Debrief. PDF report within 5 business days, then a video call for the action plan.

They've seen it firsthand.

"Solved a complex problem in a matter of hours."

Verified client review, Malt

"Didn't try to inflate the price. Generous with advice he wasn't obliged to give us."

Verified client review, Malt

"Exceptionally fast, effective and relevant. Complete work in record time."

Verified client review, Malt

All reviews can be found on my Malt profile. Developer for over 20 years, registered in the French business register since 2002.

Frequently asked questions about the performance audit

What's the difference between the free audit and the full audit?

The free audit analyzes your store from the outside, with no admin access: real-world Core Web Vitals, loading behavior of your key pages, issues visible from the browser. It results in a concise diagnosis listing your top priorities. The full audit goes where an external analysis can't: SQL queries and autoloaded options, server configuration and real TTFB, payment gateway scripts, cache behavior page by page. It produces a comprehensive PDF report ranked by impact, with an estimated gain per action, and ends with a video debrief. If the free audit answers "do I have a problem?", the full audit answers "which ones, in what order, for what gain and what effort".

Do you need admin access?

For the full audit, yes: part of the measurements (SQL queries, autoloaded options, plugins, configuration) can only be seen from the inside. A dedicated administrator account is enough; you create it for the audit and delete it afterwards. I make no changes during the audit: reading and measuring only. Access to your hosting (or its metrics) sharpens the server diagnosis but isn't blocking. For the free audit, no access at all: the URL is enough.

What if the audit finds nothing serious?

That's good news, and the report will tell you so honestly: there's no optimization to sell at all costs. You walk away with measured confirmation that your store is healthy, the few remaining improvement points, and a baseline to monitor over time. In practice, on a store that has never been audited, the list of profitable improvements is rarely empty.

Will my site be modified or slowed down during the audit?

No. The audit is strictly read-only: measurements, exports, analysis. No setting is changed, no feature is touched. The only temporary addition is a measurement tool (such as Query Monitor), enabled for the readings then removed, with negligible impact. Any load testing is done during off-peak hours and with your approval.

Can my developer work from the report?

Yes, that's a requirement of the deliverable: each recommendation states the problem, the measurement that proves it, the fix to apply and its risk level. Your developer or agency can execute it as is. And if you'd rather hand me all or part of the work, the €990 audit fee is deducted from the optimization quote.

Why €990 when plugins promise to optimize for €50?

An optimization plugin applies generic settings without knowing what slows down your store specifically. It compresses, defers, caches, and sometimes breaks things. The audit does the opposite: it identifies your exact causes and their order of priority. That's what saves you from paying for useless optimizations, or worse, hiding a structural problem (database, hosting) behind a cache. The plugin is a tool; the audit decides whether you need one, and which.

Ready to know what's holding your store back?

Start with the free audit, or go straight to the full audit: either way, you'll finally know where the loading time goes, and what it costs you.

Request my audit