FASTVPS / PRACTICAL GUIDE

Before an online shop campaign: performance and order checks

Before advertising brings more visitors, check the journey from product to completed order. A practical plan for measurements, caching, controlled rehearsals and coordination with the team responsible for your store.

1. Describe the campaign through specific scenarios

A promotion concentrates visitors on particular products and time periods. Record when it starts, which landing pages it uses, which coupons apply and who will watch incoming orders. Ask the marketing team how visits are expected to be distributed throughout the day. A daily total alone does not describe the busiest moments.

Keep a baseline from normal operation and agree what a successful rehearsal means. You need completed purchases, correct amounts and acceptable responses at the important steps. Do not turn a visitor count into a specific vCPU or RAM requirement without evidence.

  • Arrive from an advertisement, open a product and choose a variation.
  • Search, add items to the basket and apply a coupon planned for the campaign.
  • Calculate delivery charges and complete checkout using the payment methods that will be available.

2. Check mobile usability and application response

Try the campaign page on a phone and a desktop. Check that terms are readable, product options work and pop-ups do not cover the purchase button. Repeat the journey as a guest and as a signed-in test customer.

Core Web Vitals describe loading, interaction responsiveness and visual stability through LCP, INP and CLS. They help assess the page experience. A good result from one measurement does not establish how many simultaneous purchases the application can handle.

3. Check exactly what the cache stores

In WooCommerce, cart, checkout and customer account pages must be excluded from shared full-page caching because their contents depend on the individual customer. Check the exclusions at every layer you use: plugin, server and CDN.

Use two separate test sessions with different baskets and compare quantities, discounts and totals. After changing the price of a test product, confirm that the new price appears. A fast page that displays the wrong basket or an outdated total has failed the check.

4. Arrange a small, agreed traffic rehearsal

Plan load testing with the application owner and hosting provider. Start in an isolated test environment and increase traffic gradually using realistic journeys. Record differences from production: a smaller server or different database limits the conclusions you can draw from the result.

Agree the time window, maximum load, stopping criteria and the person who can stop the exercise. Exclude live payment providers, outgoing email and other external services unless appropriate test facilities and permission are in place. Testing the production store requires separate coordination.

5. Verify the order beyond the payment screen

Use the payment system's test environment and your own test details. WooPayments test mode creates orders and can send order emails even though no real funds are collected. Isolate outgoing notifications and invoicing, warehouse and delivery integrations before testing.

Check successful payment, rejection and the return from the provider's page. Match each outcome to the order status and correct total. Record delayed updates, duplicate orders or stock discrepancies. Seeing a confirmation page is not sufficient evidence of a correct order.

6. Choose changes from the findings

Collect response times for each step, failed requests and corresponding server measurements. Review CPU, available memory, storage delays, database behaviour and plugins with the technical team. WordPress optimisation spans application and infrastructure; a hosting upgrade should address an evidenced constraint.

Before launch, keep a short list of completed checks, outstanding issues and an owner for each action. Decide who will coordinate changes during an incident and how new orders will be preserved if recovery is needed. Send FastVPS the campaign window and findings for a requirements review. Application management, testing and additional resources must be confirmed within the agreed service scope.

Sources & further reading

Prepared with AI assistance and checked against the sources above. Service scope is confirmed in your FastVPS order.

← All guides & news

FASTVPS NEWSLETTER

Guides worth keeping.

Practical hosting, business email and backup advice, about once a month.