Prevent WP HTTP request to slow down your WordPress website and admin interface
Do you have a slow WordPress admin that takes longer than usual to load? Sometime longer than 5 seconds to load admin or login pages. In rare occasions WordPress may even timeout and show 504 page.
Reason may be slow external WP_HTTP requests. HTTP Requests Manager plugin will log all WP HTTP requests with time taken to complete each request. If there are multiple request per page they will be color grouped.
Plugin tested with PHP version 5.6, 7.x and up to 8.2.
Do not confuse WP_HTTP request with HTML requests that loads page assets like js, css, image, font
Plugin only detects and manages requests made using WP_Http class. Which is default method used and advised by WordPress for getting remote data and updates.
Plugin will not detect any requests made by other WordPress classes like WP_Http_Curl or PHP functions like curl_exec, fsockopen, file_get_contents etc.
Do not confuse it with HTML requests (loading assets like css, js, image) done by HTML page. WP_Http requests are performed only inside PHP files and not visible in web browser.
How plugin prevents slow pages containing WP_HTTP requests?
Plugin helps to prevent website slowdown by:
- Sets request timeout period to 1 second. Where default is 5.
- Limit number of request per page by 3. Default is unlimited.
- Limit WP HTTP request if page load time is longer than 3 seconds. Default is unlimited.
- Option to block all external requests or allow only requests to wordpress.org for plugin, theme and core updates.
Plugin has following operation modes in setting to manage WP HTTP requests. Here is what each mode does:
- Only log HTTP requests — logs all non cron requests. No blocking done.
- Only log HTTP requests (+ cron requests) — logs all requests including cron. No blocking done.
- Smart block — logs non cron HTTP requests and blocks request using following rules.
- Page processing time exceeded 3 seconds.
- Number of request for single page reached 3.
- Sets timeout for each request to 1 second.
- Sets number of redirects for request to 1.
- Apply custom rules for “Smart block” defined in settings.
- Prevent some built in requests: happy browser, maybe update, self pings.
- Skip limitations listed above for: file downloads (plugin, theme, other), requests inside cron jobs.
- Block external requests — all requests not matching your current domain will be blocked. No updates for WordPress core, plugins and themes. (+ Smart block features.)
- Block external requests (allow WordPress.org only) — all requests not matching your current domain and wordpress.org will be blocked. Allows updates for WordPress core, plugins and themes coming from wordpress.org website. (+ Smart block features.)
Custom rules only work in “Smart block” mode. It will not work in “Block external requests” or “Block external requests (allow WordPress.org only)” mode.
After using plugin for some time and knowing which requests are performed you can disable logging. Operation mode will remain unchanged. Request blocking will remain in tact. No new logs will be recorded. You can analyze old logs, they will not be deleted.
Custom rules for “Smart Block” mode
Allow or block some requests based on domain, plugin or all. Choose on which page type rule will be applied. For example you can block requests in frontend while allowing in other pages.
Finally you can define action as block or allow for custom rule. For example you can make sure that some plugin will always be allowed to send WP_HTTP request. This can be SEO or mail plugin that uses remote API for functioning.
- View blocked requests by this plugin. Show reason why it was blocked.
- View failed requests with error message.
- View what initiated HTTP request: WordPress core, plugin or theme.
- View on which page request was made. Also view page type is frontend, admin, login, cron, ajax or rest_api.
- View list of other requests made on same page view.
- View sent and received data.
- How long it took to get response in seconds.
- Check Point with page time and memory usage for most common hooks like plugins_loaded, init, wp_loaded, setup_theme, after_setup_theme, shutdown. This will give some idea about cause of slow pages.
- Only last 1000 records will be stored.
- Group requests by URL, domain, initiator, plugin, page, response status etc.
- Add custom rules (conditional logic) to block or allow certain requests.
Log summary populated for visible logs in selected page. Summary has following information cards:
- Blocked requests percentage. When hovered it will show request breakdown by core, plugins or theme.
- Number of requests per page. When hovered shows breakdown by page type: Frontend, admin, login, cron, ajax, rest_api.
- Request time / Page time percentage.
- Average page time.
- Average request time.
- Number of hosts. On hover shows breakdown of hosts.
- Check if your website slow because of WP HTTP requests. Average page load time, average request time and average number of requests per page shown as summary at the top of reports.
- Block all external request on development or localhost website. All updates will be blocked. You switch off blocking when you want to perform Core, Plugin, Theme updates. No need to use define(‘WP_HTTP_BLOCK_EXTERNAL’, true); in your wp-config.php. Plugin will prevent requests automatically when you choose “Block external requests” or “Block external requests (allow WordPress.org only)” operation mode.
- Block non WordPress request. No data will be sent to third parties. They are usually loading other website news, plugin/theme promotions, advertisements, sending usage statistics etc.
- Prevent your website from timeout. By blocking all requests if page generation time exceeds 3 seconds. Kill slow HTTP request with small timeout of 1 second. Slow request can be because of temporary network problem or remote website can be too busy to respond on time. Slow request is not your fault so your website should not suffer from it.
- Initial logging functionality was taken from Log HTTP Requests (version 1.4, year 2023) Github →
- Blocking, grouping and additional features added by veppa →
If you find this plugin useful to view WP_HTTP requests and speeding up your admin pages by blocking some requests then give good rating. Also check my other projects:
- Share button without plugin – add super fast native sharing button to your website. Tiny inline code, ad blocker safe, no external dependencies.
- bbPress WP Tweaks – add custom sidebar, additional widgets and forum columns for sites powered with bbPress forum plugin.
Visit veppa.com to learn from my WordPress tutorials.
- Download and activate the plugin.
- Browse to
Tools > HTTP Requests Managerto view log entries and choose operation mode. Operation mode “Smart block” will be activated by default.
How long logs stored in database?
There is no time limit to store logs. Last 1000 logs will be stored. On average it is about 10 days of logs.
Is it possible to pause plugin and only view recorded logs?
Yes, set operation mode to “Only log HTTP requests” and check “disable logging” checkbox in “Settings” tab. With these settings new logs will not be added and you can review already existing old logs.
Does plugin removes logs and options on uninstall?
Yes it removes logs and options stored in database when you uninstall this plugin.
Which pages are recorded?
All pages with WP_HTTP requests are recorded. Slow pages without any WP_HTTP requests are not recorded.
Ez dago berrikuspenik plugin honentzat.
Laguntzaileak eta Garatzaileak
“HTTP Requests Manager” software librea da. Ondoko pertsonek egin dizkiote ekarpenak plugin honi.Laguntzaileak
Garapena interesatzen zaizu?
1.2.3 – 30 November 2023
- Fixed: Domain select box population when adding new Custom Rule.
1.2.2 – 29 November 2023
- Fixed: Variable name typo inside get_arr_val function.
1.2.1 – 29 November 2023
- Fixed: Incorrect links in options page.
1.2.0 – 28 November 2023
- Added: Separate tabs for log, settings, more tools
- Added: Group request logs by URL, domain, page, page type, plugin, response status etc. Better for viewing important information.
- Added: Custom rules to block/allow by all/domain/plugin in everywhere/admin/frontend/ajax/cron/rest_api/login. Maximum 10 custom rules can be added. Custom rules apply only in smart block mode.
- Added: Option to disable logging. Old logs can be viewed. Plugin will work a bit faster when logging disabled.
- Added: Disable self ping (only when blocking in “smart block+” mode). Self ping sends pings to images and links on same domain. Post with 20+ links and images will take 10+ seconds to send self pings.
- Added: Disable auto update check on admin page in “smart block+” mode. _maybe_update_core, _maybe_update_themes, _maybe_update_plugins slows down admin pages up to 5+ seconds on first visit after 12 hours and can even timeout. Update checks via cron is not effected.
- Fixed: Undefined array key “file” error
- Update: Store last 1k records
1.1.0 – 12 June 2023
- Added: Separate table to log page info like check point with time and memory usage.
- Added: New tab to show Check Points for page with time and memory usage in request details popup window.
- Fixed: Remove plugin tables on uninstall.
- Update: Reduced response body before sending to view in admin panel. This will reduce loaded json data size.
- Update: Clear log button now recreates tables which will eliminate table inconsistency with new versions of plugin in future.
1.0.7 – 5 June 2023
- Initial release. Log HTTP Requests (version 1.4) used as base.