ReqLock disarms outbound internet requests from WordPress core, your theme, and plugins — on both the server and the browser. Keep working when the internet is cut, kill slow third-party calls, and stop phoning home.
Also written RequestLock or Request Lock.
The same kill-switch that keeps you online through an outage also makes a noisy WordPress install faster, more private, and easy to run offline.
Keep the site working when international internet is cut or restricted. Pages serve from local assets and wp-admin stops hanging on dead requests.
Slow or dead third-party calls fail instantly instead of stalling front-end and back-end page loads on long network timeouts.
Strip analytics, trackers, external fonts and phone-home requests, so nothing about your visitors quietly leaves the server.
Turn any install into a self-contained, offline-capable environment — no external calls or tracking from a staging copy.
ReqLock works where other plugins can't — intercepting calls before they leave the server and scrubbing what the browser would otherwise fetch.
Hooks pre_http_request and short-circuits external hosts before the request ever leaves your server.
wp_remote_* calls to external hostsBuffers page output and strips external resource tags and known inline trackers — leaving a traceable comment, never a request.
<script> & <link> stylesheets (Google Fonts)No theme edits, no build step, no configuration required to start. Safe to keep installed permanently.
Copy the reqlock folder into wp-content/plugins/ and activate it from the Plugins screen.
Open Settings → ReqLock. Every blocking layer has its own toggle; your domain and subdomains are always allowed.
Flip the master switch on when the internet is cut — or leave it on for good as a privacy & performance baseline.
Conservative, well-anchored matching that leaves SEO links and internal URLs untouched.
WP_HTTP_BLOCK_EXTERNAL conflictsFree and open source under GPL-2.0. Install from the WordPress directory or grab the source on GitHub.