How to Set Up SureForms with SiteGround Optimizer

Use this guide to configure SiteGround Optimizer 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

SiteGround Optimizer is listed as Speed Optimizer in current settings. Open Speed Optimizer → Caching. Next to Exclude URLs from Caching, click the pencil icon and add these paths, keeping existing exclusions.

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

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

Check that the saved rules also bypass child REST routes, not just the namespace URL. If your installed version requires explicit URLs, add the actual request URLs from your form’s Network log, including its active webhook URLs. The control applies to dynamic and file-based caching; availability depends on the hosting setup.

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: SiteGround cache exclusion controls

2. Exclude SureForms JavaScript

Open Speed Optimizer → Frontend → JavaScript. Use the exclusion control for Minify JavaScript Files and select the SureForms scripts. Repeat this for Combine JavaScript Files, then save each selection.

Select scripts by their displayed name or handle; this is not a text box for folder patterns. Match the selections to the SureForms script reference below. Include active Pro fields and payment scripts.

Reference: SiteGround frontend optimization settings

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

If Defer Render-blocking JavaScript is enabled, open Exclude from Deferral of Render-blocking JS and select the same SureForms and payment scripts. Save the changes. If a script is missing from the list, turn the affected optimization off while support identifies its handle; do not guess a handle.

Reference: SiteGround script exclusions and custom filters

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.

SUREFORMS  /  SITEGROUND OPTIMIZER

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

Use Purge Cache in Speed Optimizer’s caching controls or the WordPress toolbar. Clear any separate CDN cache, then reload the form as a visitor.

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

Turn off JavaScript minification, combination, and deferral temporarily. Purge the cache and retest, then re-enable each option separately. If an exclusion is missing, share the affected script URL with support.

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.