Troubleshooting
Step-by-step diagnostic workflows for cache headers, script timing, and third-party plugin integrations.
Understanding the X-Rapida-Cache header
Section titled “Understanding the X-Rapida-Cache header”To determine how Rapida is treating any request, inspect the X-Rapida-Cache HTTP response header using browser Developer Tools (Network tab) or curl:
curl -I https://example.com/Possible header values
Section titled “Possible header values”X-Rapida-Cache: HIT: The request was answered directly from the pre-generated static HTML file on disk. WordPress core was not booted.X-Rapida-Cache: MISS: No cached file existed for this URL. The page was generated by PHP, served to the browser, and saved to disk for subsequent requests.X-Rapida-Cache: BYPASS; reason=<reason>: Caching was skipped for a deliberate technical reason.
Common bypass reasons
Section titled “Common bypass reasons”reason=logged_in: The visitor has an active WordPress authentication cookie. By default, logged-in users receive dynamic pages to prevent leaking private administrative or customer data.reason=cart_session: A WooCommerce cart or customer session cookie (woocommerce_items_in_cartorwp_woocommerce_session_*) is present.reason=excluded_url: The URL matches a pattern defined in Never cache URLs.reason=query_param: The request contains an unlisted query parameter (e.g.?search=custom).reason=method_not_get: The HTTP request usedPOST,PUT, orDELETE.reason=woocommerce_endpoint: The request hit/cart/,/checkout/, or/my-account/.
Resolving JavaScript timing issues
Section titled “Resolving JavaScript timing issues”When Delay JavaScript is active, non-essential scripts wait until the user interacts with the page (mouse movement, scroll, keypress, or touch).
Symptoms of script timing conflicts
Section titled “Symptoms of script timing conflicts”- An interactive slider or carousel appears empty on initial load.
- Form validation scripts fail to bind on page open.
Resolutions
Section titled “Resolutions”- Test with norapida: First verify if the issue exists when Rapida is completely bypassed by appending
?norapidato the URL. If the issue persists, the conflict lies in your theme or other plugins. - Add exclusions: Under Rapida > CSS & JS > Delay JavaScript, locate Exclude from delay and add the script handle or file name (e.g.
swiper.min.jsorcustom-slider). - Use Safe Mode: Enable Delay third-party scripts only so local theme and plugin scripts execute immediately while external analytics and trackers are deferred.
Verifying drop-in permissions and WP_CACHE
Section titled “Verifying drop-in permissions and WP_CACHE”Rapida requires WordPress to load wp-content/advanced-cache.php on every page request.
Symptoms
Section titled “Symptoms”X-Rapida-Cacheheader is missing completely from response headers.- Health check warns that the drop-in is inactive.
Resolutions
Section titled “Resolutions”- Verify that
wp-config.phpcontains the cache constant near the top:define( 'WP_CACHE', true ); - Verify that
wp-content/advanced-cache.phpexists and has correct read permissions (0644). - If another plugin previously owned
advanced-cache.php, delete the old drop-in file and re-save settings in Rapida to regenerate the symlink/file.
Redis and Object Cache Pro compatibility
Section titled “Redis and Object Cache Pro compatibility”Rapida manages full-page static caching (HTML documents on disk). It does not replace or conflict with in-memory object caches like Redis Object Cache or Object Cache Pro.
- Rapida works harmoniously alongside Redis.
- When Rapida purges a page, it does not wipe the Redis database cache.
- The Tools tab in Rapida detects active Redis configurations and displays an informational status card.