Back to Community
Home / Community / Plugin → Breeze – wordpress cache plugin

Troubleshooting Common Breeze Cache Plugin Issues: Minification, Grouping, and Layout Breaks

35 threads Sep 10, 2025 Plugin → Breeze – wordpress cache plugin

Content

Breeze is a powerful caching plugin for WordPress, but like any complex software, it can sometimes cause unexpected issues on your site. Based on community reports, many common problems stem from its optimization features like minification and file grouping. This guide will help you diagnose and resolve the most frequent issues.

1. Site Layout Breaks or White Screen

The Problem: Enabling Breeze, even with default settings, can sometimes cause a completely broken layout or a white screen. The page may display garbled characters or fail to load entirely.

Why It Happens: This is often a conflict between Breeze's cache and other plugins or your theme. It can also be caused by a corrupt cache file.

How to Fix It:

  1. Purge All Cache: Your first step should always be to use the "Purge All Cache" option inside Breeze.
  2. Disable Specific Features: If purging doesn't work, try disabling features one by one, starting with Lazy Load Images and Cross-origin Safe Links, as these are frequently linked to layout problems.
  3. Rollback the Plugin: If a specific update (like version 2.0.16) caused the issue, temporarily rolling back to a previous version can be an effective workaround while waiting for a patch.

2. JavaScript Errors After Minification or Grouping

The Problem: After enabling JS minification or grouping, your browser's console shows errors like "Uncaught ReferenceError: jQuery is not defined" or "Uncaught SyntaxError: Unexpected token '%'".

Why It Happens: Breeze combines and processes JavaScript files. If a script depends on another script (like jQuery) being loaded first, or if it contains special characters, the processing can break the loading order or corrupt the code.

How to Fix It:

  1. Disable JS Grouping: This is the most common solution. Turn off the "Group JS" option in Breeze settings.
  2. Exclude Problematic Files: Identify which JavaScript file is causing the error (e.g., a theme script like `scripts.js` or a page builder file) and add it to the exclusion list in Breeze's advanced settings.
  3. Check Inline JS Settings: Ensure "Include Inline JS" is not ticked if you are experiencing issues with code being incorrectly grouped.

3. CSS Minification Breaking Styles

The Problem: Modern CSS functions like calc(), clamp(), and CSS variables (var()) break when CSS minification is enabled. Container queries with named containers can also fail.

Why It Happens: The minification process removes spaces to reduce file size. However, spaces around operators like + and - in calc() are required by the CSS specification. Similarly, a space between a container name and the opening parenthesis in a container query is mandatory.

How to Fix It:

  1. Exclude CSS Files: The most reliable fix is to add your theme's main stylesheet (often style.css) to the exclusion list in the Breeze settings.
  2. Disable CSS Minification: If multiple stylesheets are affected, you may need to turn off CSS minification entirely until the issue is resolved in a future plugin update.

4. Issues with Lazy Loading and Specific Plugins

The Problem: Lazy Load Images can conflict with other plugins, such as WP Download Manager, causing JavaScript errors because it modifies image tags and can introduce unescaped characters.

Why It Happens: Breeze's lazy loading feature replaces src attributes with a data attribute. If the original code contains complex HTML within a JavaScript string, the replacement can break the script's syntax.

How to Fix It:

  1. Disable Lazy Load: Turn off the Lazy Load Images feature.
  2. Use a More Specific Exclusion: Some users have reported that future updates may improve the logic for escaping quotes in replaced code.

General Troubleshooting Steps

If you encounter an issue not listed above, follow this standard procedure:

  1. Identify the Feature: Disable all Breeze features and then re-enable them one by one to identify which one causes the problem.
  2. Conflict Test: Temporarily switch to a default WordPress theme (like Twenty Twenty-Four) and disable all other plugins to see if the issue persists. If it resolves, reactivate your theme and plugins one by one to find the conflict.
  3. Check the Console: Always check your browser's Developer Tools Console (F12) for JavaScript errors, which provide crucial clues about what is breaking.
  4. Clear All Caches: Remember to purge Breeze, Varnish, and any other server-level caches after making any changes to your settings.

By methodically working through these steps, you can usually pinpoint and resolve the conflict, allowing you to benefit from Breeze's performance optimizations without breaking your site.

Related Support Threads Support