Integrations

Integrations

Detection and coordination with other plugins, so two systems do not optimize the same thing twice.

Automatic protection

On by default. When a known analytics, advertising or consent plugin is active, its scripts are automatically excluded from JavaScript optimization and delay — because a deferred consent banner or a delayed analytics tag is a compliance and data problem, not just a performance one.

Detected plugins include Perfmatters, EWWW Image Optimizer, FlyingPress, WP Rocket, LiteSpeed Cache, WP Super Cache, W3 Total Cache, Autoptimize, Jetpack Boost, Akismet, Jetpack, Core Forms, Independent Analytics, Burst Statistics, Koko Analytics, Matomo, WP Statistics, Site Kit by Google, MonsterInsights, ExactMetrics and PixelYourSite.

The Integrations tab lists each with what it detected and what protection it applied.

Those hostname patterns are matched against scripts your site already loads. GT Performance never contacts them. See External Services.

Perfmatters ownership

Perfmatters overlaps GT Performance substantially. Rather than both acting, ownership is arbitrated per feature:

• automatic (default) — GT Performance yields any feature Perfmatters already handles
• Or assign ownership per feature manually

This prevents the classic double-optimization failure: two plugins both minifying the same file, or both lazy-loading the same image.

Conflicting cache plugins

If another plugin owns advanced-cache.php, GT Performance reports conflict and will not overwrite it. Same for object-cache.php. Disable the other plugin first — running two page caches is not a configuration, it is a bug.

Akismet and Jetpack

Safeguards keep their AJAX and REST routes out of caching and optimization, and preserve the comment-form fields Akismet relies on.

Core Forms

Polling endpoints are detected and excluded from caching, so a form that polls for state does not read a cached response.

Related

JavaScript Optimization · External Services · Troubleshooting