Many publishers use third-party speed and caching plugins alongside Ezoic's JavaScript integration to improve their site's performance and Core Web Vitals scores. While most of these tools are compatible with Ezoic, their JavaScript optimization features — such as minification, deferral, and lazy loading — can delay or block Ezoic's ad scripts if not configured correctly, which negatively impacts ad delivery and EPMV.
WP Rocket is compatible with Ezoic. To avoid conflicts, exclude the following domains from any delay, defer, or minification settings. In WP Rocket, navigate to Settings > WP Rocket > File Optimization and add these to the "Excluded JavaScript Files" field:
ezodn.comezoic.netezojs.comgatekeeperconsent.comAdditionally, navigate to Settings > WP Rocket > Media and exclude the following from iFrame lazy loading:
googlesyndication.comAll other WP Rocket optimizations can remain enabled.
Note: WP Rocket displays a warning in WordPress recommending that Ezoic users switch to cloud integration. This warning applies to the legacy WordPress plugin integration method only and can be safely ignored if you are using JavaScript integration.
W3 Total Cache is compatible with Ezoic. The main risk is its Minify feature, which can combine or defer Ezoic's scripts.
Navigate to Performance > Minify > Advanced and add the following to the "Never minify the following JS files" field (one per line):
ezojs.comezoic.netezodn.comgatekeeperconsent.comIf you have JS defer/delay enabled via Performance > General Settings > User Experience, also ensure the above domains are excluded from script delay. After saving, purge all caches to confirm the changes have taken effect.
Autoptimize is compatible with Ezoic. Its Aggregate JS files setting is the most common source of conflict, as it can pull Ezoic's scripts into a combined file where they will not execute correctly.
Navigate to Settings > Autoptimize > JavaScript Options and add the following to the "Exclude scripts from Autoptimize" field:
ezojs.comezoic.netezodn.comgatekeeperconsent.comIf you have the "Also defer inline JS" option enabled, ensure the above domains are also excluded from deferral. Save your settings and clear the Autoptimize cache.
LiteSpeed Cache requires more careful configuration alongside Ezoic.
If you are using Ezoic's JavaScript integration (recommended): LiteSpeed Cache can be used, but its JS/CSS optimization features must be configured carefully. Navigate to LiteSpeed Cache > Page Optimization > Tuning and add the following to both the JS Excludes and JS Deferred/Delayed Excludes fields:
ezojs.comezoic.netezodn.comgatekeeperconsent.comgooglesyndication.comIf you are using Ezoic's cloud integratoin: LiteSpeed Cache's caching features conflict with Ezoic's own CDN and caching layer. In this case, the LiteSpeed Cache plugin should be disabled, as Ezoic's caching replaces its functionality. You can continue using your LiteSpeed web server — it is only the WordPress caching plugin that needs to be disabled.
After making changes, navigate to LiteSpeed Cache > Toolbox and purge all caches.
NitroPack performs aggressive all-in-one optimization and is generally not recommended for use alongside Ezoic, as it applies minification, deferral, and CDN delivery in ways that are difficult to configure around Ezoic's scripts. Publishers using NitroPack frequently experience broken ad delivery.
If you are committed to using NitroPack, you will need to use its exclusion settings to prevent it from touching the same domains listed at the top of this article. However, given the difficulty of configuring this correctly, we recommend using Ezoic's own caching and speed tools (available under the Speed tab in your dashboard) instead, which are purpose-built to work alongside ad serving.
If you need further assistance with compatibility with Ezoic and your third-party tools, please log in via support.ezoic.com to make use of our dedicated resources for support. We're here to help!