WordPress 'Connection Timed Out' Error: Fix (2026)
Quick answer
'Connection Timed Out' on WordPress means a PHP process ran longer than the max_execution_time (usually 30s) before responding. It happens when a plugin does heavy work synchronously — image regeneration, bulk imports, backup runs on shared hosts. Raise max_execution_time to 300, WP_MEMORY_LIMIT to 256M, and identify the slow plugin with Query Monitor.
Fix #1 — Raise PHP limits
Add to wp-config.php: `define('WP_MEMORY_LIMIT', '256M');`. Add to .htaccess (or php.ini): `php_value max_execution_time 300` and `php_value memory_limit 256M`. On managed hosts, use their PHP settings panel.
Fix #2 — Identify the slow plugin
Install Query Monitor. Reload the slow page. Query Monitor shows the top queries, hooks, and HTTP requests by time. The single slowest plugin is your culprit.
Prefer we just fix it?
Site is down or blocking real customers right now? Our emergency team is live around the clock — median response 12 minutes, flat $149 for the fix. Learn more about emergency WordPress help or grab a slot below.
Fix #3 — Move heavy work to WP-CLI or cron
Bulk image regeneration, import jobs, and backup runs should never happen via wp-admin on a shared host. Use WP-CLI over SSH (`wp media regenerate --yes`) or trigger them via server cron so a browser timeout doesn't matter.
Fix #4 — Ask host about CPU throttling
Shared hosts throttle CPU per account. If you hit the limit, requests get killed. Check your host's resource usage graph and upgrade to a plan with higher CPU/EP allowance if you're regularly at the ceiling.
When to call for help
Persistent timeouts usually mean a plugin needs replacement or the host needs upgrading. Our performance audit starts at $149 and includes Query Monitor + New Relic diagnosis.
Common questions
Why does WordPress say Connection Timed Out?+
A PHP process took longer than max_execution_time (default 30 seconds) to complete. Common culprits: bulk image regeneration, backup plugins scanning large sites, imports/exports, or CPU throttling on cheap shared hosts.
How do I fix WordPress timeout errors?+
Raise max_execution_time to 300, WP_MEMORY_LIMIT to 256M, install Query Monitor to find the slow plugin, and move heavy work (image regen, imports, backups) to WP-CLI over SSH so browser timeouts don't kill them.
Does upgrading PHP fix timeout errors?+
It helps — PHP 8.2/8.3 is 30-40% faster than 7.4, so slow work finishes inside the timeout window more often. But if a plugin is fundamentally inefficient, PHP upgrades alone don't solve it — you need to fix the plugin or replace it.
Is Connection Timed Out a host problem?+
Sometimes. Cheap shared hosts (SiteGround StartUp, Bluehost Basic) throttle CPU aggressively. If you hit the ceiling, PHP processes get killed. Check your host's resource usage panel — if you're regularly at 100%, you need a bigger plan or a better host.
Want this handled for you?
Book a call and we will review your site before recommending anything.