Skip to content
Available for new work
A glowing orange cart assembled from blocks. AI-generated image.AI-generated
WordPress

WooCommerce stores, kept fast as they grow.

Speed
Slow admin, slow checkout, fixed
Plugins
Audited, trimmed, replaced
Builds
Themes and custom plugins
Hosting
Caching and the database

WooCommerce slow?

The three numbers Google judges a slow store on

A slow WooCommerce store is rarely WordPress itself. It is plugins stacking scripts on every page, an unindexed database behind the slow backend, and add to cart doing too much work. I find which, template by template, and fix it at the source: a slow add to cart, a slow checkout, a backend that crawls when the catalogue grows.

Largest contentful paint≤ 2.5sgood ≤ 2.5s
poor > 4s
Interaction to next paint≤ 200msgood ≤ 200ms
poor > 500ms
Cumulative layout shift≤ 0.1good ≤ 0.1
poor > 0.25

Method · The bands are Google’s published Core Web Vitals thresholds. Each needle sits on the pass line, where a store needs to be; your own numbers come from the self-check or an audit.

WooCommerce work, by job

Slow stores, plugin conflicts, builds and moving off

Most people don’t search for a WooCommerce developer. They search for why the store is slow or broken. This is what each of those jobs involves.

Jump to a section
  1. A slow WooCommerce site, backend or checkout
  2. Plugin conflicts and updates that break things
  3. Custom WooCommerce builds
  4. PHP versions, hosting and keeping it updated
  5. When it is time to move to Shopify or Magento

WooCommerce slow

A slow WooCommerce site, backend or checkout

A WooCommerce store slows down in predictable places: too many plugins loading on every page, a database full of old sessions, orders and revisions, hosting that was fine at launch and isn’t now, and product pages built with a page builder that sends far more than it needs. A slow admin is usually the database; a slow checkout or add to cart is usually a plugin, a payment script or a server-side call that waits on something else.

Plugin conflicts

Plugin conflicts and updates that break things

Two plugins that both change the cart, a theme that overrides WooCommerce templates from three versions ago, an update that stops the checkout working. The fix is found on a copy of the store, not by guessing on the live one, and the update process is changed so it doesn’t happen again.

WooCommerce builds

Custom WooCommerce builds

WooCommerce suits a store where content matters as much as the catalogue, or where the business already runs on WordPress. Custom work covers product types WooCommerce doesn’t have, trade pricing, integrations with stock and accounts systems, and themes built without a heavy page builder.

Hosting and updates

PHP versions, hosting and keeping it updated

WordPress, WooCommerce and every plugin release updates constantly, and PHP versions go out of support. A store that hasn’t been updated in a year is a security risk and a harder upgrade. Updates are tested on a copy first, on hosting sized for the store.

Moving off WooCommerce

When it is time to move to Shopify or Magento

Sometimes the right answer is a different platform: a catalogue that has outgrown WordPress, or a team that doesn’t want to manage updates. I’ll say so when it is true, and the move keeps your rankings with every old address redirected.

WooCommerce questions

Why is my WooCommerce site so slow?
Usually plugins loading on every page, a bloated database, or hosting that no longer fits. Measuring each template on a copy of the store shows which it is before anything is changed.
Why is the WooCommerce admin slow?
Most often the database: years of sessions, orders and revisions, and plugins that run heavy queries on every admin page.
Can you fix a plugin conflict?
Yes, on a copy of the store first, then on the live one once the cause is proven.
Should we move off WooCommerce?
Not always. It suits content-led stores well. If the catalogue or the team has outgrown it, Shopify or Magento may be the better home, and I’ll say which.
Do you build on page builders?
Where a store already uses one, I work with it. New builds avoid heavy page builders, because they are a common cause of slow product pages.
Do you look after WooCommerce stores long term?
Yes, with updates tested on a copy before they reach the live store.

Available for new work

UK based · PHP · Python · JS · TS. Every first call is free.