Brizy disable optimization

Mary Rusnak

• April 15, 2026 14:20

Are there hooks to disable the optimizations from Brizy?

0

• 

  Ariel H.

  • April 15, 2026 15:25

  Hi Mary,

  Thank you for reaching out.

  At the moment, I’m not aware of any available hooks to disable Brizy’s built-in optimizations. These are handled internally by the builder and aren’t currently exposed for selective control.

  

  As a workaround, you may set the image property to Original, which will ensure that the original image is rendered instead of an optimized version.

  Please let me know if you have any questions or need further assistance.

  Kind regards,
  Ariel H.

  1
• 

  Mary Rusnak

  • April 15, 2026 21:58

  Hi Ariel,

  Thank you for the update.

  To clarify, I’m specifically looking for developer‑exposed filters—the kind of internal switches that Brizy registers through WordPress’ hook system to enable or disable individual optimization layers. These are the same types of controls typically used to toggle features such as lazy‑loading behavior, asset‑processing routines, CDN usage, SVG handling, or font‑processing logic.

  If Brizy exposes any of these filters—whether for asset loading, optimization, or performance‑related subsystems—that’s the information I’m trying to locate.

  If you can confirm whether such filters exist (and what their names or purposes are), that would be extremely helpful.

  0
• 

  Mary Rusnak

  • April 16, 2026 01:34

  Can you recommend some pages or asset paths to exclude in NitroPack?

  0
• 

  Ariel H.

  • April 16, 2026 02:34

  Hi Mary,

  Thank you for the update.

  At the moment, Brizy doesn’t expose developer-level filters or hooks to selectively disable individual optimization layers (e.g., lazy loading, asset processing, fonts).

  For NitroPack, we recommend excluding Brizy-related assets to avoid conflicts:

  /wp-content/plugins/brizy/  
  /wp-content/plugins/brizy-pro/  
  /wp-content/plugins/brizy/public/editor-build/  
  /wp-content/uploads/brizy/

  You may also want to disable CSS/JS combine, inline processing, and lazy loading if issues persist. After making these changes, please clear your cache/CDN and test again.

  Could you also share what specific issues you're encountering and why you need these controls? We can check if this has already been addressed in a similar case or suggest a more targeted solution.

  Best regards,  
  Ariel H.

  0

Please sign in to leave a comment.