Troubleshooting

CommerceGurus Turbo works well out of the box, but no two WooCommerce stores are quite the same. Themes, payment gateways, page builders and third-party plugins can all introduce their own CSS, JavaScript and caching behaviour.

If something doesn’t look or behave as expected, don’t start changing lots of settings at once. The quickest route to a solution is to isolate the module involved, make one change, and test again.

Start with a controlled comparison

CommerceGurus Turbo includes several diagnostic URL parameters. These temporarily bypass an optimization on the page you’re viewing, without changing the settings for everyone else.

• ?cgturbooff – disables all CommerceGurus Turbo optimizations
• ?cgturbojsoff – disables JavaScript optimization only
• ?cgturbocssoff – disables CSS optimization only
• ?cgturbopreloadoff – disables the Preload module only
• ?cgturbonocache – bypasses Page Cache and Edge Cache
• ?cgturbopagecacheoff – bypasses Page Cache only
• ?cgturboedgecacheoff – bypasses Edge Cache only

Add the relevant parameter to the end of the affected page URL. For example:

https://example.com/shop/?cgturbojsoff

If the URL already contains a question mark, add the parameter using an ampersand instead:

https://example.com/shop/?filter=shirts&cgturbojsoff

Compare the same page, at the same screen size, while logged out. If the problem disappears with a module disabled, you’ve identified which part of the optimization is involved. You haven’t necessarily identified the exact script, stylesheet or cache rule yet, but you now know where to look.

Test while logged out

Always check the storefront as a real visitor would see it. The easiest way to do this is in a private or incognito browser window.

The JS Optimizer is bypassed when the WordPress admin toolbar is present. This means a page can behave correctly while you’re logged in but differently for customers.

You can also enable:

WooCommerce > CG Turbo > Settings > General > Disable for Logged-in Users

This disables CommerceGurus Turbo optimizations for logged-in users. It’s useful while editing the site, but a logged-out test is still essential before considering an issue resolved.

JavaScript isn’t working

A menu that doesn’t open, an unresponsive slider, a form that won’t submit or an add-to-cart button that does nothing usually points to JavaScript.

1. Open the affected page while logged out and add ?cgturbojsoff to the URL.
2. If the feature now works, go to WooCommerce > CG Turbo > Modules  JS Optimizer.
3. If you are using Delay JS, test Defer JS with the Standard behaviour. Defer JS is less aggressive and may work better with themes or plugins that expect their scripts to initialize during the initial page load.
4. If you want to continue using Delay JS, identify the script that needs to run earlier and add the smallest reliable match to the Delay JS Exclusions list.
5. Test the complete dependency chain. Excluding the final theme or plugin script may not be enough if jQuery, a shared library or another required script is still being delayed.
6. Purge the relevant caches and test again in a fresh private window.

Pay particular attention to controls used for the visitor’s first interaction, such as the primary mobile navigation. These need to be initialized before that interaction or use a reliable interaction-replay path.

What Click Queue does

Click Queue is an advanced option for sites using Delay JS. If a visitor clicks an element before its JavaScript is ready, Click Queue can hold that interaction and replay it once the delayed scripts have loaded.

This can help with early interactions, but it isn’t a general repair tool. It won’t fix scripts loading in the wrong order, missing dependencies or JavaScript errors inside a theme or plugin. Get the dependency chain right first, then use Click Queue where interaction replay is genuinely required.

See the full JavaScript Optimization guide for an explanation of Delay JS, Defer JS, exclusions and Click Queue.

The layout is broken or styles are missing

If a page looks unstyled, has oversized icons or is missing part of its layout, compare it with CSS optimization disabled:

https://example.com/affected-page/?cgturbocssoff

If the page looks correct with that parameter:

1. Go to WooCommerce > CG Turbo > Modules > CSS Optimizer.
2. Click Clear Used CSS Cache.
3. Revisit the affected page while logged out so that its Used CSS can be regenerated.
4. Purge Page Cache and Edge Cache if either is enabled, then test the page again.
5. If the issue affects only one unusual or highly dynamic page, edit that page and disable CSS optimization using the CommerceGurus Turbo settings in the editor sidebar.

Clearing Used CSS is particularly important after changing your theme, editing a page template or updating a plugin that adds frontend styles.

See the CSS Optimization guide for more details. If Used CSS will not regenerate at all, see Oversized Icons or Missing Images.

Images aren’t loading correctly

First decide whether the image is missing completely or simply being lazy loaded too early.

1. Go to WooCommerce > CG Turbo > Modules > Lazy Load.
2. Check the Leading Images count. Important images near the top of the page, such as a hero image or main product image, should load immediately. Increase the count if one of these images is being lazy loaded.
3. If a slider, gallery or another section needs all of its images immediately, add the container’s CSS selector to Parent Container Exclusions.
4. To exclude an individual image, add no-lazy to the image element’s CSS classes.
5. Clear any page or edge caches and check the page again while logged out.

See the Lazy Loading guide for more details.

Page Cache isn’t working

Use ?cgturbopagecacheoff to compare the page without Page Cache, or ?cgturbonocache to bypass both Page Cache and Edge Cache.

If caching appears to be the problem:

1. Check that Page Cache is enabled under WooCommerce > CG Turbo > Modules.
2. Open the CommerceGurus Turbo Status page and review any warnings relating to WP_CACHE, the cache directory or the advanced-cache.php drop-in.
3. If a warning is shown, follow the specific guidance provided for your server configuration. WordPress, Bedrock and managed hosting environments don’t all define WP_CACHE in the same place.
4. Check that another full-page caching plugin or server-level cache isn’t trying to perform the same job.
5. Purge the cache and revisit the page while logged out.

WooCommerce pages containing customer-specific information, including the cart, checkout and account areas, are bypassed automatically.

See the Page Caching guide for configuration details.

Edge Cache isn’t syncing

If the problem only happens when Cloudflare Edge Cache is active, compare the page using:

https://example.com/affected-page/?cgturboedgecacheoff

Then work through the following checks:

1. Open WooCommerce > CG Turbo > Modules > Edge Cache and read the current connection or synchronization error.
2. Confirm that the correct Cloudflare zone is connected.
3. Check that the API token has all the permissions listed in the Edge Cache documentation.
4. Open the CommerceGurus Turbo Activity page and look for failed rule synchronization, purge or cache-warming events.
5. Reconnect the Cloudflare account only if the token has changed, the wrong zone is connected or the existing connection is no longer valid.

Disconnecting and reconnecting won’t correct an API token with missing permissions, so it’s worth checking the reported error first.

See the Cloudflare Edge Caching guide for the current setup and permission requirements.

Use the Activity Log

The Activity page records cache purges, cache warming, Cloudflare rule synchronization and related errors. It’s the best place to look when an operation appears to have started but hasn’t completed as expected.

For additional information, go to:

WooCommerce > CG Turbo > Settings > Advanced > Enable Debug Logging

Enable debug logging, reproduce the problem once, and then review the resulting log. Turn it off again when you’re finished; there’s little benefit in collecting detailed diagnostic information indefinitely.

Back up your settings before experimenting

If you’re about to make several changes, export your current configuration first:

WooCommerce > CG Turbo > Settings > Import / Export

The exported JSON file gives you a quick way to restore the previous configuration or copy the same setup to another site.

Importing a file overwrites the current CommerceGurus Turbo settings, so always export the existing configuration before importing another one.

Still having trouble?

You can contact our support team directly from the Help tab in the CommerceGurus Turbo settings area.

Include the affected URL, the diagnostic parameter that changed the result, the optimization mode you’re using and any relevant message from the Status or Activity page. That gives us something concrete to work with and usually makes the problem much quicker to identify.