Before you start
- Catalogue, cart and checkout measurements.
- An isolated copy for cache or plugin changes.
Measure a complete journey
A store may load its homepage quickly while checkout remains slow. Measure a category, product, search, cart and confirmation. Record device, connection, login state and cache conditions. Repeat measurements to distinguish one-off delays from recurring problems.
- Choose representative simple and variable products.
- Compare visitors and signed-in customers on a copy when testing payments.
- Separate server response time from resources downloaded by the browser.
Prepare a copy and rollback point
Back up files and database before changing caching, themes or plugins. Use an isolated copy for significant changes. Prevent live payments, customer emails and renewals. Faster pages are useful only if the journey remains functional.
- Preserve current versions and settings.
- Prepare identical checks for every modification.
- Do not restore an old live-store database to undo optimization without preserving new orders.
Reduce catalogue weight
Use images suited to their displayed size and avoid loading large galleries everywhere. Review filters and variations: heavy catalogues can run expensive queries even with lightweight images. Measure a feature before replacing its implementation.
- Compress images and use modern formats where supported.
- Avoid loading unused widget scripts on every page.
- Retain enough product detail for customers to make informed purchases.
Cache without mixing customers
Page caching can help public pages, but cart, checkout and account content contains personal or changing information. Review exclusions at every layer, including the CDN. Server page caching and object caching require different configuration.
- Test two separate sessions with different carts.
- Check that stock and price changes become visible correctly.
- Do not enable a “cache everything” rule without exclusions and WooCommerce journey validation.
Review processing and integrations
Imports, searches, scheduled tasks and external calls can consume resources. Review WooCommerce → Status and available logs. Investigate delayed task queues before deleting anything: some tasks perform important store operations.
- Schedule large imports outside busy hours where possible.
- Look for recurring errors and slow external-service responses.
- Do not delete orders, tables or tasks as “cleanup” without understanding their role.
Decide whether capacity should change
Repeat measurements and check ordering, refunds, accounts and emails. If limits are still regularly reached after optimization, gather workload requirements to compare suitable hosting or a VPS. More resources do not automatically fix inefficient queries.
- Compare identical operations using the same data and conditions.
- Assess peak periods rather than only low-traffic tests.
- Plan migration to preserve recent orders if changing hosting.
Related service
VPS hostingOfficial documentation
Labels and options vary with versions, plugins and your account. Refer to publisher documentation for your configuration.
WooCommerce — System status report