Your WooCommerce store is slow. I'll find out exactly why.

What I check

The report answers one question: what exactly is slowing your store down — and what to fix first.

• Core Web Vitals & real loading speed

  What your visitors actually experience — LCP, INP, CLS measured on your real product and checkout pages, not a synthetic homepage test.

• Page caching

  Is your HTML cached at all? I check whether a logged-out visitor gets a ready-made page or a full PHP build on every single request.

• Database bloat

  Autoloaded options, orphaned sessions and years of post revisions being loaded on every page view.

• Plugin overhead

  Which plugins cost you the most milliseconds — measured per request, not guessed from the plugin list.

• WooCommerce-specific issues

  Cart fragments hammering admin-ajax, an Action Scheduler backlog, and the cart and checkout paths that quietly defeat your cache.

• Server configuration

  PHP version and worker count, object cache (Redis or Memcached), OPcache — the settings that decide your ceiling.

How it works

Three steps, in this order.

1. You email me your store URL

   I reply within a few hours to confirm the booking and send payment details — PayPal or bank transfer.

2. I run the full diagnosis

   External measurement first. Temporary admin access is optional; it's what unlocks the deeper server- and database-side checks.

3. Within 48 hours of payment, you get the report

   A PDF with findings ranked by impact, and concrete fixes you can hand to any developer — or ask me to implement.

What the report looks like

Measured numbers, ranked by impact — not a checklist of generic advice.

Who you're dealing with

Sara Rossi

I've spent nine years building for the web — mostly the unglamorous half of it: making things load, stay up and keep working long after launch.

I build my own developer tools, including custom API integrations and automation running on Cloudflare.

Italian, based in Brno (CZ) — audits delivered in English or Italian.

Questions

How do I pay?

After you book by email, I send you a PayPal link or bank transfer details. The 48-hour clock starts at payment.

Do I need to give you admin access?

No — the external audit works without it. Admin access is what enables the deeper server- and database-side checks, so you get more out of the report if you provide it.

What if you find nothing wrong?

Then the report says your store is healthy, and where the next bottleneck will appear as you grow. That answer is worth having.

Do you also fix the issues?

Yes — quoted separately after the report, once we both know the actual scope. You're never obligated; plenty of clients hand the report to their own developer.

What do I receive exactly?

A PDF, typically 6–10 pages, with findings ranked by impact: what's wrong, what it costs you in measured numbers, and what to do about it.

Refunds?

If the report doesn't identify at least three concrete improvements, you get a full refund.