Skip to main content Skip to content

WooCommerce doesn't have to be slow

A slow store costs you customers. We find the cause, whether it's in the server, the database, the cache or the code, and fix it in WordPress and WooCommerce.

Tablet showing load-time and traffic charts

What you notice, and where it usually comes from

The same slowness can have many causes. These are the most common ones we see in WooCommerce.

  • Product and category pages load slowly

    Usually no page cache, large images, or a theme and plugins that load too much on every page.

  • The admin is sluggish

    Often settings loaded on every request that have grown over the years, a full Action Scheduler queue, or orders still stored in the posts tables instead of WooCommerce's own order tables (HPOS).

  • Cart and checkout hang

    Those pages can't be cached as a whole. It comes down to the object cache, the cart's background updates, payment and shipping plugins, and the number of PHP workers.

  • The store goes down on busy days

    The server has too few PHP workers or too little memory for the peak, or the cache gets cleared just when it's needed most.

  • Search and filters take a long time

    Slow database queries without the right indexes, or a filter plugin that recalculates everything on every view.

  • Fast at night, slow during the day

    Usually shared hosting, where other sites take resources, or background jobs running while customers shop.

Server and caching

Your store is only as fast as the server allows

  • Server setupPHP version, OPcache and the number of PHP processes tuned to your traffic.
  • CacheA page cache for pages that are the same for everyone, and an object cache (e.g. Redis) for data that has to be fully up to date, like the cart and stock.
  • CDNImages and other static files are served from servers close to the customer, so your own server has less to do.

Database

The heart of your store

  • CleanupOld revisions, expired transients, sessions and spam that make every query heavier over time.
  • Queries and indexesWe find the slow queries and give the tables the indexes they're missing.
  • Order dataWooCommerce's own order tables (HPOS) and fewer settings loaded on every page view.

Code and plugins

We look into the code that runs your store

  • Code analysisWe profile the PHP code and find the functions, loops and hooks where the time goes.
  • PluginsWe measure each plugin's impact and fix, replace or remove the ones that cost the most.
  • Images, CSS and JavaScriptSmaller images in modern formats, and only the scripts and stylesheets the page actually uses.

Operations and monitoring

So the speed lasts once you have it

  • MonitoringResponse times and slow queries are measured continuously with tools like Query Monitor and New Relic.
  • Background jobsStock updates, order processing and scheduled tasks that mustn't slow the store down.
  • UpdatesApplied in a controlled way, so an update doesn't take the speed, or the site, down with it. On Premium, they're tested in a separate environment before they go live.

How we work

We measure before we promise, and we measure again afterwards.

1

A free first look

You send a link, and we look at the store. You get a short written assessment of where things are likely going wrong and what it will take.

2

Analysis

We measure the server, database, code and front end and find the exact causes. The measurement is also the baseline we compare against afterwards.

3

A clear plan

You get a plan that puts the improvements with the biggest impact first, and an estimate as a range of hours.

4

Optimization and a new measurement

We fix the causes and show you the difference, measured the same way as before.

A slow store costs sales every day, not just on Black Friday.

Customers give up before the page has finished loading, and patience is shortest at checkout. Google uses speed when it ranks pages. And a slow store is slow for you too, when you manage products, orders and stock.

What it costs

The first look is free. After that, you pay for the time the work takes, and you get an estimate before we start.

  1. 1

    A first look

    Free

    Write a few lines and a link. The developer looks at your store, and you get a short written assessment of what's wrong and what it will take. If you'd rather talk, we'll do it by phone.

  2. 2

    Reviews, fixes and projects

    DKK 800/hour excl. VAT

    Before we start, you get an estimate as a range of hours. You pay for the time the work actually takes, and we tell you if it looks like it's getting bigger.

  3. 3

    Ongoing operations

    from DKK 749/mo. excl. VAT

    Updates, monitoring of uptime and checkout, and help when something goes wrong. Three months to start, then one month's notice.

    See the plans

Questions about speed optimization

How much does speed optimization cost?

The first look is free. The review and the fixes cost DKK 800 an hour, excluding VAT, and you get an estimate as a range of hours before we start.

What is caching, and how does it make my store faster?

A cache is temporary memory. Instead of building the same page or the same data again on every visit, the server stores a finished version and serves it directly. In WooCommerce, that means pages, products and categories can be shown without asking the database every time.

What's the difference between a page cache and an object cache?

A page cache stores complete, finished HTML pages and suits pages that are the same for everyone, like categories and information pages. An object cache stores individual pieces of data, such as product information and prices, in memory (RAM). It helps most on the cart, checkout and account pages, which can't be cached as a whole.

Why does my store get slower as orders pile up?

Older WooCommerce setups store orders in the same tables as posts and pages. As orders grow, those tables get bigger and slower to search. We move orders to WooCommerce's own order tables, clean up, and cache what can be cached.

Do plugins always make my store slower?

No. Quality matters more than quantity. A well-written plugin that solves a specific need costs almost nothing. The problem is plugins that overlap or do heavy work on every page view. We measure each plugin's impact before we recommend anything.

How do product images affect speed?

Images are often the largest part of a product page. We compress them without visible quality loss, serve them in modern formats and at the size the screen needs, and let images further down the page wait until the customer scrolls.

My store is slow for customers abroad. What can we do?

Your server is probably in one country, so data has to travel further to customers elsewhere. A CDN serves the static files from servers close to the customer, and a good page cache makes the rest of the response fast.

Why does the speed vary during the day?

When many people visit the store at once, the server needs more processing power and memory. On shared hosting, other sites on the same server can also take resources from yours. We size the server and the cache for your busiest hours, not the average.

How do I know if the database needs optimizing?

Typical signs are slow product pages, a sluggish admin, searches that take time, and slow order processing. An analysis of the database shows exactly where optimization has the biggest effect.

Read more about speed

We measure before we promise. See our object cache benchmark, for example. Speed lasts best with a fixed maintenance plan.

How WordPress works: architecture and performance

We follow a request through the server, PHP, hooks, the database and the cache, and show where the time goes.

WordPress architecture and performance

HTTP/3: what does it mean for your store’s speed?

How HTTP/3 works, when it helps, and how to check for it and turn it on.

HTTP/3 and speed

Is your store too slow?

Send a link to your store. The developer looks at it and replies within 24 hours on business days with an assessment of what it will take.