SSiddiq.in
WordPress + WooCommerce · done fast

Most slow WooCommerce stores aren't broken. They're just carrying 8 plugins that stopped earning their keep in 2022.

We've rebuilt enough Woo stores to know: the difference between a 4-second cart page and a 1-second cart page is almost always fragment caching and five deletions. Speed is a discipline problem, not a hosting problem.

Audit our Woo store
Why the cart page is slow · the anatomy

Five requests happen before the buyer sees the total.

wc-ajax=get_refreshed_fragments
Uncacheable AJAX on every page — even the homepage
→ Enqueue only on cart/checkout
cart_hash / applied_coupon
Recomputed on every request
→ Object cache (Redis / Memcached)
Product variation loads
One AJAX per variation attribute
→ Prefetch all variations server-side
Shipping calc
Called on address blur, without debounce
→ Debounce 400ms + cache by postcode
Tax calc
Called with every quantity change
→ Server-side estimate, precise on submit
Plugin discipline · the honest list

Ten plugins we recommend. Six we uninstall on sight.

Ship-with
  • • WooCommerce (obviously) + a modern block theme
  • • Rank Math (SEO — replaces Yoast + 3 others)
  • • Cloudflare + APO (caching that actually works with Woo)
  • • Razorpay / Cashfree / Stripe gateway (region-routed)
  • • Woo Cart Abandonment (only if you'll actually action it)
Usually a mistake
  • × Elementor Pro on cart/checkout (kills fragment caching)
  • × "All in One SEO" alongside Yoast (pick one)
  • × Every "one-click upsell" plugin (adds 400KB, converts 0.5%)
  • × WPML with 6 languages when you have 3 markets (heavy)
  • × WP Rocket + Autoptimize + LiteSpeed Cache (pick one)
  • × Any plugin that hasn't shipped an update in 12 months
Payment gateway routing

One store · different gateways per country · zero manual work.

Buyer countryPrimary gatewayReason
IndiaRazorpay + CashfreeBest UPI success rates, INR native
USA / EU / UKStripe (Apple Pay + Google Pay)Highest checkout completion, wallets
UAE / GCCStripe + Tabby (BNPL)Card + growing BNPL adoption
Rest of worldStripe fallbackBroadest card + wallet coverage

WooCommerce FAQ

Shopify for teams that want to focus 100% on merchandising and never touch hosting. WooCommerce when you need catalog complexity Shopify limits (deep configurators, region-specific pricing, B2B tiered), or when you're already invested in WordPress content and don't want two CMSes.

Performance hotspots

Seven places a WooCommerce store bleeds performance — in order of frequency.

Cart & checkout hit the DB on every request
By design, cart isn't cached. Fix: object cache (Redis), avoid heavy hooks in cart context, defer non-critical fragments.
wp_options autoload bloat
Plugins dump JSON into autoloaded options. Every request loads it. Audit `SELECT * FROM wp_options WHERE autoload = 'yes'` — cap at ~1MB.
Transient explosion
Poorly-behaved plugins write unlimited transients. Schedule a weekly `wp transient delete --expired` + monitor row count.
Unbatched product imports
CSV of 5000 products via UI = timeout. Use WP-CLI + WooCommerce CLI in chunks of 100, with `wp cache flush` between.
Image sizes not regenerated
Themes register sizes; existing images never get them. Run `wp media regenerate` after theme change or you serve 2400px hero as 200px thumb.
Plugin overload
Every activated plugin adds hooks that run on every request. Under 20 active plugins is a good ceiling; audit quarterly.
PHP workers saturating
Not a code problem — a sizing problem. Cart pages need 6–10 workers per CPU. Alerts on queue depth, not CPU.

A Woo store fast enough to convert.

Book a store audit
Right tech, honest advice

Not sure if this is the right stack for you?

Tell us your goals — we'll recommend the right technology honestly, even if it isn't this one.

  • Personal reply from Siddiq within 24 hours
  • Honest advice — no pushy sales, no fake urgency
  • Clear next steps, timeline, and estimate

We only use your details to reply to this enquiry. Privacy.