Skip to main content
How Can We Help?

Cache Issues

Posted
Updated
ByEmily Gomez
WordPress caching and performance tools can sometimes cause an older version of a page to appear instead of the experience you expect during an experiment.
If a test is Active but you’re seeing outdated content, a Variant isn’t appearing correctly, or recent experiment changes aren’t showing, caching may be involved.

Signs of a Cache Issue

Caching may be affecting your experiment if:
  • An old version of a page continues to appear.
  • Recent changes to a Variant aren’t showing.
  • A Variant works in Preview but behaves differently on the live website.
  • Different browsers or visitors see unexpectedly different content.
  • Clearing your website cache temporarily resolves the issue.
Before troubleshooting caching, confirm that the experiment itself is Active and configured correctly.

Clear Your WordPress Cache

If your website uses a WordPress caching or performance plugin, start by clearing its cache.
The exact process depends on the plugin you’re using, but most caching tools provide an option to Clear Cache, Purge Cache, or similar.
After clearing the cache:
  1. Return to the page included in your experiment.
  2. Reload the page.
  3. Check whether the expected content appears.
  4. Preview the Variant to confirm it displays correctly.
Remember that Bluvia A/B Testing uses cookies to maintain a visitor’s assignment to the Control or a particular Variant. Refreshing the page won’t necessarily assign you to a different experience.
Use Preview when you need to inspect a specific Variant.

Clear Other Website Caches

Your WordPress caching plugin may not be the only layer of caching on your website.
Your hosting provider may also use server-level or managed WordPress caching.
If clearing your WordPress cache doesn’t resolve the issue, check whether your hosting environment provides its own cache controls and clear those caches as well.

Check JavaScript Optimization

Some performance plugins do more than cache pages. They may also modify how JavaScript is delivered.
Features such as:
  • JavaScript minification
  • Script combining
  • Deferred JavaScript
  • Delayed JavaScript execution
  • Script optimization
can change when or how scripts run on the page.
If clearing the cache doesn’t resolve the issue, temporarily reviewing these settings may help determine whether a JavaScript optimization feature is interfering with the experiment.
For more detailed troubleshooting, see JavaScript Conflicts.

Pause the Experiment When Troubleshooting

If you need to determine whether the problem exists independently of the experiment, temporarily pause the test.
Then:
  1. Pause the experiment.
  2. Clear the relevant website caches.
  3. Visit the original page.
  4. Confirm that the page displays and functions correctly.
  5. Preview the Variant separately.
  6. Compare the original experience with the Variant.
If the problem still occurs while the experiment is paused, the issue may be related to your WordPress website or caching configuration rather than the experiment itself.
Once troubleshooting is complete, review the experiment before resuming it.

Check Your CDN

If you’ve cleared your WordPress and hosting caches but continue seeing outdated content, your website may also be using a Content Delivery Network (CDN).
A CDN can maintain its own cached copy of your website independently of WordPress.
Clearing your WordPress cache doesn’t necessarily clear your CDN cache.
If your website uses a CDN, continue with CDN Problems.

Be Careful With Cache Exclusions

Some caching tools allow you to exclude specific pages, cookies, scripts, or URLs from caching.
These settings can be useful when troubleshooting, but avoid making broad exclusions unless you understand how they’ll affect your website’s performance and caching behavior.
If you determine that Bluvia A/B Testing requires a specific compatibility adjustment for your caching setup, contact Support before making extensive configuration changes.

After Making Changes

Once you’ve cleared or adjusted your caching configuration:
  1. Clear the affected caches again.
  2. Confirm the original page works correctly.
  3. Preview your Variants.
  4. Confirm the expected functionality works.
  5. Resume the experiment if you paused it.
  6. Monitor the test to confirm the issue has been resolved.
Avoid stopping the experiment while troubleshooting unless you’re finished with the test. A paused experiment can be resumed, while a stopped experiment is completed and cannot be resumed.

Still Having Trouble?

If clearing your caches and reviewing your performance settings doesn’t resolve the issue, contact Bluvia A/B Testing Support.
When contacting Support, include:
  • The experiment name.
  • The URL where the issue occurs.
  • A description of what you’re seeing.
  • Whether the issue affects the Control, Variant, or both.
  • The caching or performance plugin you’re using.
  • Your hosting provider’s caching solution, if applicable.
  • Whether the Variant works correctly in Preview.
  • Whether clearing the cache temporarily resolves the issue.
This information can help the Support team determine whether caching is interfering with the experiment.

Related Articles

Continue with: