When your WordPress website won’t load, the cause might be your browser, domain, hosting, or WordPress itself. Check where the failure starts before changing settings, and use the error message to choose the next step.
Start by finding out what “won’t load” means
A blank screen, a loading spinner, and a “site can’t be reached” message can point to different problems. Before reinstalling anything, record the exact message, the affected URL, and the time. Check the homepage, one inner page, and your usual WordPress login address.
This guide helps you narrow down an unexplained loading failure. If the problem began immediately after a known update, tell your host or developer which component changed. A clear starting point is more useful than a list of settings changed in a hurry.
1. Check another browser and network
Open the same address in a private window, then on another device. If practical, try mobile data instead of your usual Wi-Fi. Also check whether unrelated websites load normally.
- Only one browser fails: Investigate its stored site data or extensions before changing WordPress.
- Only one network fails: Local connectivity, DNS caching, or a network-specific block may be involved.
- Several devices and networks fail: Move on to the domain and hosting checks.
These comparisons are clues rather than a complete diagnosis. A firewall can block particular visitors, and a cached page can make an unavailable site appear healthy. Record what each test shows instead of assuming one successful visit proves the problem is over.
2. Use the message to choose a direction
- Domain not found or DNS error: Check domain registration and DNS configuration.
- Certificate or privacy warning: Ask your host to check the certificate and domain configuration. Do not ask customers to bypass the warning.
- Connection timed out: Ask hosting support to investigate reachability, capacity, and firewall rules.
- 500 Internal Server Error: Follow our WordPress 500-error troubleshooting guide.
- Critical error or blank page: Investigate a WordPress application failure, including plugins, themes, and custom code.
- Maintenance message: Use our maintenance-mode recovery guide.
If you use Cloudflare and see a Cloudflare-branded error, save the code, timestamp, and Ray ID for support. Different 5xx codes require different checks; use Cloudflare’s error documentation rather than assuming every error comes from a WordPress plugin.
3. Check the domain and hosting account
Sign in to the domain registrar and confirm the domain is active. Review any recent nameserver or DNS changes with the person who manages the website. A change intended for email or a migration can affect the website if the wrong records are edited.
Check your host’s service notices and account messages. Ask whether the server is available, whether the account has reached a resource limit, and whether the domain points to the intended hosting environment. Avoid changing DNS records repeatedly while waiting for a previous change to take effect.
A useful support request includes the exact URL, the first known failure time and timezone, the visible error, and whether another network shows the same problem. If the issue followed a migration, include that detail. GRIDD’s WordPress hosting setup service is relevant when the underlying configuration needs attention.
4. Investigate WordPress only when the evidence points there
If the dashboard works but the public site fails, review recent plugin, theme, cache, or redirect changes. Preserve a backup before making repairs, and test one change at a time. Prefer staging for broad conflict testing so normal visitors are not exposed to each experiment.
If neither the dashboard nor the public site works and you see a critical error, check the administrator email for a Recovery Mode link. WordPress may provide a way to access the dashboard with a faulty component paused for that session. See the Recovery Mode documentation for its scope and limitations.
An “error establishing a database connection” calls for checking database availability and configuration with your host. Do not delete tables or replace credentials based on guesses. Similarly, a single missing page does not justify reinstalling WordPress: compare its URL with a working page and review recent URL changes.
5. Treat a spinning page differently from an unreachable site
Sometimes the page appears but never finishes loading, or a button keeps spinning. Note whether text and images appear, whether the issue affects one feature, and whether it happens while logged out. A failing external service, script, or optimization setting may be involved even when the server responds.
Give your developer a reproducible example: the page, action, device, and approximate time. Browser network and console information can help identify the failed request, but avoid sharing screenshots that expose account details or private data. Changing multiple performance settings at once makes comparisons harder.
6. Confirm recovery beyond the homepage
After the cause is addressed, clear relevant caches if needed and retest the original failure from a clean session. Check mobile navigation, key landing pages, forms, and important transactions. Confirm that submissions arrive and that redirects lead to the intended page.
Keep a short incident record: what failed, what caused it, what changed, and how recovery was checked. That record can shorten a future investigation and help identify recurring hosting or maintenance issues.
Frequently asked questions
Should I restore a backup straight away?
Not without narrowing down the problem. A backup restore will not correct an expired domain or a local connection failure. It can also overwrite newer site data. Confirm the likely cause and the restore’s impact first.
Why does the website load for me but not a customer?
Compare browsers, networks, login state, and the exact URL. Differences in caching or access rules can produce different results. Ask the customer for the message and time without requesting their password.
Can a loading problem affect inquiries or donations?
Yes. Visitors may be unable to reach a form or complete a transaction even when other pages work. Prioritize those journeys in the recovery checks.
Get help finding the cause
If the cause remains unclear, GRIDD’s WordPress one-time fixes offer a starting point for investigation. Share the error, affected pages, and checks already completed. For more focused guides, visit our troubleshooting resource hub.