Begin with a specific page and a clear symptom. For example, identify whether the home page is slow for visitors, the WordPress dashboard is slow for editors or checkout slows down during a busy period. These situations can have different causes. Record a baseline before changing settings so that you can compare the same page and task afterwards.

Caching can reduce repeated work, but it must suit the content being served. Public information pages can often benefit from page caching. Customer-specific pages need special handling. For WooCommerce, check that Cart, Checkout and My Account are excluded from inappropriate full-page caching and that the active cache integration respects customer sessions.

Avoid activating several tools that all perform the same optimisation without understanding their overlap. Minification, script delays or aggressive caching can interfere with menus, forms or checkout. Make controlled changes, clear the relevant cache and test both the visible page and the actions visitors need to complete. Use staging for changes with a wider effect.

Speed also depends on page weight, images, plugins, database work, external services and the resources available to your plan. Some PHP settings may be controlled by your service policy. We do not guarantee a particular score or speed multiplier. Read the timestamp on performance results, ask the WordPress AI Engineer to investigate persistent bottlenecks and judge success by both measured performance and working website functions.

Use a protected staging store with sandbox payments and fictional customer data. In one browser profile, sign in as test customer A and place a sample product in the cart. In a separate clean profile, sign in as test customer B and choose a different product. Do not reuse the same cookie jar.

1. Visit Cart, Checkout and My Account in each profile after applying one cache change.
2. Confirm that each session shows only its own basket and account information.
3. Open a public information page while signed out and compare its response with the original performance baseline.

Expected result: a public page can benefit from compatible caching while customer-specific responses remain correct. If customer B sees customer A's details, stop the rollout, record the affected URL and investigate the cache rule or integration before continuing. A faster timing does not compensate for incorrect customer data.

1. Measure a representative slow page before changing settings.
2. Apply one compatible cache or optimisation change and clear the relevant cached content.
3. Test logged-in areas, Cart, Checkout, My Account and forms as appropriate, including a separate customer session where needed.

Several overlapping optimisation plugins can make a problem harder to isolate. Confirm which layer is serving an old result before purging or disabling everything. AI speed advice and a score help prioritise investigation, but successful payment, login and correct customer-specific content remain essential verification.

• Preparing a WooCommerce store on NabWP
• Understanding NabWP Insights and website usage
• Creating and using a WordPress staging website
• Improving WordPress meta descriptions and investigating SEO issues

• NabWP Managed WordPress Hosting