WP Rocket, caching, and common setups

Overview

The Allspice WordPress plugin is designed to be compatible with modern publisher stacks - including common themes, caching tools, CDNs, and ad network setups.

Allspice loads asynchronously and only on detected recipe pages, which helps minimize performance impact and reduce conflicts.

That said, some plugins (especially caching/minification/optimization plugins) can change how scripts are loaded, delayed, or rewritten - so this page outlines what to expect and how to resolve the most common compatibility issues quickly.

If Allspice is not loading, it's almost always caused by one of these: script delay, aggressive minification, caching rules, or a conflicting overlay UI.

Prerequisites

Before troubleshooting compatibility, confirm:

• Your domain is linked and verified in the Allspice Publisher Portal
• The Allspice plugin is installed and activated
• You have at least one public recipe post that includes valid recipe content
• You've clicked Sync with Allspice in the plugin settings (recommended after any Portal changes)
• You see at least one recipe and one button successfully synced in plugin settings.

Supported WordPress Environments

Allspice is designed to work with:

• Standard WordPress installations
• Most modern themes
• Recipe posts with structured recipe data (JSON-LD recommended)

Allspice may be limited or require additional configuration on:

• Private staging sites behind authentication
• Sites blocking crawlers, bot traffic, or external requests
• Pages without reliable recipe markup

Caching & Optimization Plugins

Allspice is compatible with most caching systems, but compatibility depends on how aggressively those tools modify JavaScript loading.

Common caching/optimization tools include:

• WP Rocket
• Autoptimize
• LiteSpeed Cache
• W3 Total Cache
• WP Super Cache
• NitroPack
• Perfmatters
• Cloudflare optimization features (see CDN section)

What can cause issues

Caching/optimization plugins can interfere if they:

• delay JavaScript execution
• defer or async scripts incorrectly
• combine/minify scripts in a way that changes execution order
• block third-party scripts
• remove attributes or rewrite script tags

WP Rocket

If any of the following settings are enabled, please exclude "allspice":

• Minify JavaScript files
• Delay JavaScript execution
• Combine JavaScript files

After making this change, you should clear the WP Rocket cache.

Recommended settings (general)

If Allspice fails to load or appears inconsistently, try:

• disabling "Delay JavaScript execution" for Allspice scripts
• excluding Allspice scripts from minification/combination
• excluding Allspice scripts from "optimize delivery" rules

Ad Networks & Ad Tech

Allspice is built to coexist with ad-heavy recipe sites and common ad stacks.

This includes setups like:

• Mediavine
• Raptive
• other header bidding / ad manager configurations

Footer and floating ad behavior

Allspice is designed to avoid blocking common placements such as:

• sticky footer ad units
• floating video ad units near the bottom of the viewport

Engagement / "Save" Tools (Grow, Slickstream, etc.)

Allspice can coexist with engagement tools, but we generally recommend avoiding overlapping UI on recipe pages.

Tools in this category include:

• Grow by Mediavine
• Slickstream
• other overlays, save widgets, and engagement layers

Recommended approach

If you are already running a "save" tool or engagement overlay:

• Allspice replaces the core "save and return" workflow
• Running multiple overlays can clutter recipe pages and reduce engagement

Slickstream note

If you are currently using Slickstream, we recommend not showing redundant save UI on recipe pages after Allspice is enabled. Allspice provides a modern, cooking-specific experience and engagement may decrease if Slickstream is also enabled.

Security, Firewall, and CDN Tools

Allspice is compatible with most common security layers, but security tools can block script or content behavior if configured too aggressively.

Examples:

• Wordfence
• Sucuri
• SolidWP
• Cloudflare WAF
• bot protection / challenge pages

When issues occur

You may see loading failures if:

• external scripts are blocked
• JavaScript execution is restricted
• firewall rules block Allspice endpoints
• bot challenges prevent page access during verification or crawling

If a security plugin is blocking third-party scripts, you may need to allowlist Allspice domains or disable specific protections on recipe pages.

Page Builders & Theme Frameworks

Allspice generally works with modern WordPress builds including:

• Elementor
• WPBakery
• Divi
• Gutenberg / block themes
• classic editor themes

In rare cases, builders can affect where buttons render or how HTML is structured - especially if recipe content is inside custom modules.

Known Issues & Recommended Settings

Below are the most common patterns we see and the fastest resolutions.

Issue: Widget doesn't show on some recipe posts

Common causes:

• recipe content missing structured data
• the post is not recognized as a valid recipe
• caching is serving outdated markup
• changes weren't synced yet

Recommended fix:

• ensure JSON-LD recipe schema exists
• press Sync with Allspice in plugin settings
• clear site cache (if applicable)

Issue: Widget loads sometimes, but not always

Common causes:

• script delay or optimization rewrites
• caching variations by device or user agent
• conflicts with other overlays or injected scripts

Recommended fix:

• exclude Allspice scripts from "Delay JS"
• disable script combination for Allspice
• test with overlays disabled

Issue: Custom button actions don't trigger

Common causes:

• custom button class not applied correctly
• action mapping not configured in Publisher Portal
• changes not synced yet

Recommended fix:

• confirm action selection in Publisher Portal
• press Sync with Allspice
• verify the correct class name is applied

When to Contact Support

If you've tested the above and Allspice still isn't working properly, please contact support by filing a ticket in the Publisher Portal.