External Call Optimizer

What It Does

External Call Optimizer is a background optimizer, with nothing to configure, for the HTTP requests WordPress makes behind the scenes: core update checks, plugin license pings, and telemetry. It does not log or display these calls — it prevents them happening more often than necessary. Two engines run together. The Gate Keeper handles a common failure mode: a broken object cache drops the update-check timestamp, so WordPress fires blocking api.wordpress.org requests on every admin page load instead of twice a day. It re-injects the last genuine timestamp so the 12-hour gate holds. The Call Optimizer spots third-party hosts polled 10 or more times an hour, clamps their timeout to 5 seconds, and serves cached responses for repeated GET/HEAD polls, so a slow or dead license server does not block your admin. Payment providers and api.wordpress.org are always excluded.

Features

• Gate Keeper: mirrors the last good update transient (plugins, themes, core) and re-injects its real timestamp when a flaky object cache drops it — so update checks fall back to ~2×/day instead of firing on every admin load
• Only ever re-injects a timestamp WordPress itself wrote, and only while it is still inside the 12-hour window — past that, the real check proceeds
• Honors deliberate transient deletion, so forced re-checks (e.g. clicking "Check again" on the Updates screen) always go through
• Counter of redundant update checks prevented, shown on the status card
• Call Optimizer: automatic, config-free — measures per-host request frequency with a lightweight rolling-hour counter (no request log, no database tables)
• Timeout clamp: hosts proven "chatty" (10+ requests in an hour) get their timeout clamped to 5 seconds (WordPress core's own interactive default), so a hanging endpoint costs seconds, not 30
• Response cache: repeated GET/HEAD polls to a chatty host are served from cache for up to 6 hours, so a dead license server does not block a page
• Safety rules: skips POST/PUT/DELETE, requests carrying Authorization headers or cookies, streamed downloads, and cron requests (for timeout clamping)
• Built-in payment host denylist (Stripe, PayPal, Square, Braintree, Authorize.net, Adyen, Mollie, Klarna, Przelewy24, PayU, tpay, Amazon Pay, and more) — these hosts are always skipped
• Commerce context detection: while a customer is on checkout, cart, wc-ajax, or Store API requests, no outbound call gets optimized at all
• api.wordpress.org is always protected — never clamped, cached, or blocked
• User exclude list: add your own never-optimize hosts, with wildcard support (*.example.com or example.com covering all subdomains)
• Status card shows whether the update gate is holding, whether your object cache is the root cause, and the prevented-check count
• In-page pause toggle to switch the optimizer off without disabling the module

How to Use

1. Enable the module

   External Call Optimizer is off by default — it intercepts outbound HTTP, so it is an explicit opt-in. Toggle it on in the WP Multitool dashboard.

2. Open the status page

   Go to WP Multitool > External Call Optimizer. The status card shows whether the 12-hour update-check gate is holding, and how many redundant checks have been prevented.

3. Add exclusions if needed

   If a plugin talks to an API that must never be slowed or cached (beyond the built-in payment denylist), add its host to the "Never optimize these hosts" list. Wildcards like *.example.com are supported.

4. Let it run

   There is nothing else to configure. The optimizer runs in the background. If the card reports "Gate at risk — the optimizer is holding it for you", your object cache is dropping writes — run Site Doctor to fix the root cause.

Settings

FAQ

Related Modules