How to Set Up SureForms with WP Fastest Cache

Use this guide to configure WP Fastest Cache while keeping SureForms submissions, field validation, and payments working.

Before you begin

Update SureForms and your optimization plugin. Save your current settings and test changes on a staging site when possible. Avoid running the same JavaScript optimization in multiple plugins.

With SureForms 2.6.0 or later, form pages generally do not need a page-cache exclusion. SureForms uses a time-based security token instead of a WordPress nonce. Do not treat the token’s validity as an unlimited cache lifetime. For older versions, update or exclude pages containing forms.

1. Keep dynamic requests out of page caching

Open WP Fastest Cache → Exclude. Under Exclude Pages, click Add New Rule. Choose Contains and create a separate rule for each path below. Save each rule.

/wp-json/sureforms/
/wp-json/sureforms-pro/
/wp-admin/admin-ajax.php

/wp-json/sureforms/
/wp-json/sureforms-pro/
/wp-admin/admin-ajax.php

Contains rules cover matching child routes, including payment webhooks. Preserve existing exclusions. A page exclusion and a JavaScript exclusion serve different purposes; configure both.

The SureForms namespace covers submissions and Stripe webhooks. The Pro namespace covers Pro features and PayPal webhooks. admin-ajax.php handles requests such as payment intent creation. Omit the Pro rule if Pro is not installed.

Reference: WP Fastest Cache page exclusion methods

2. Exclude SureForms JavaScript

In the Exclude tab, find Exclude JS. Add a separate rule for each of the following URL fragments and save each rule. These identify the SureForms folders and external payment scripts.

plugins/sureforms/
plugins/sureforms-pro/
js.stripe.com
paypal.com/sdk/js

plugins/sureforms/
plugins/sureforms-pro/
js.stripe.com
paypal.com/sdk/js

If your version asks for a file URL instead, use the actual script URL shown in the browser. These broad folder rules cover both core scripts and feature bundles; add dependencies outside these folders separately.

Reference: WP Fastest Cache JS exclusion feature

SureForms scripts to identify

Core: formSubmit.js and frontend.min.js. Payments: stripe-payment.js and payment-manager.js. These are normally under the sureforms plugin folder.

Pro, when active: pageBreak.js, datePicker.js, conditional-logic.min.js, file-upload.js, signature.js, signature_pad.umd.min.js, repeater.js, and the Save & Resume bundle. Find their actual URLs under the sureforms-pro folder or the browser’s Network panel; filenames can change.

3. Check script loading options

Premium installations may include Render Blocking JS and Delay JS. Do not assume Exclude JS also controls every premium optimization. If forms only initialize after interaction, turn Delay JS off and retest. If moving scripts to the footer breaks the form, turn Render Blocking JS off while investigating.

Reference: WP Fastest Cache Render Blocking JS

A plugin folder exclusion does not necessarily exclude inline initialization code or WordPress dependencies. If the console reports a missing variable, ask support to identify the related script and its dependency rather than excluding all JavaScript.

4. Keep payment scripts external

For payment forms, ensure Stripe.js loads directly from Stripe and the PayPal SDK loads directly from PayPal. Do not combine them into local bundles, block them, or replace them with locally cached copies.

https://js.stripe.com/v3/
https://www.paypal.com/sdk/js

https://js.stripe.com/v3/
https://www.paypal.com/sdk/js

Use the actual SDK URL loaded by your form when an exact URL is required. PayPal URLs can include query parameters. These external scripts do not belong in your site’s page-cache URL exclusion list.

5. Clear the cache and test

Open Delete Cache and choose Delete Cache and Minified CSS/JS. The label can vary by version; clear both page cache and generated CSS/JS files.

Open the form in a private or incognito window. Test once, reload, then test again so the checks include cached pages. Repeat on desktop and mobile.

Submit a test entry. Confirm the success message or redirect and the saved entry under SureForms → Entries.

Check required fields, multi-step navigation, conditional logic, uploads, and other active Pro features.

For payments, use test or sandbox mode. Confirm fields load, payment completes, and the status updates. Check Save & Resume if enabled.

Troubleshooting

Temporarily turn off Combine JS and any enabled Minify JS, Render Blocking JS, or Delay JS options. Clear page and minified-file caches. Re-enable one option at a time after a successful test.

If submissions still fail, inspect the /wp-json/sureforms/ request in Developer Tools → Network. Check the status and JSON response. HTML can indicate caching, a redirect, or a security block; it does not prove a cache problem.