Skip to content
Website Rescue Rescue

General Website Problems

Website Is Blank

Intermediate Risk: medium

Last reviewed

Hosting access may not be needed Database access usually not needed

Graphic options · pick what to keep

browserMock

decisionTree

requestTimeline

statusBadge

Direct answer

A blank website usually means the browser got an empty or crashed response — HTTP 200 with no visible HTML, a PHP fatal with display turned off, a JavaScript error that stops rendering, or a CDN/cache serving an empty page — so check DevTools for status and response body before reinstalling WordPress.

“Blank” is not the same as “down.” The connection often succeeds, but visitors see a white screen, an empty tab, or a page with no content. This general triage guide separates true empty HTTP responses from WordPress white screens, hidden PHP errors, front-end JavaScript failures, and caching layers that stored a broken page — then points you to the specialized fix.

Intermediate

What the error means

A blank page can happen at several layers. The server may return HTTP 200 with an empty body, a minimal HTML shell, or HTML that PHP never finished because a fatal error occurred with display disabled. WordPress sites often show the white screen of death when a plugin or theme fatals early. JavaScript-driven sites can look blank when a bundle fails to mount. CDNs and full-page caches sometimes serve an old empty response even after the origin recovers. Unlike DNS failure (you never reach the server) or redirect loops (the URL keeps bouncing), a blank page usually means something answered — you need DevTools Network and server/PHP logs to see whether the body is empty, truncated, or hidden by CSS.

Common symptoms

  • Browser tab loads but shows a completely white or empty page with no text or images
  • DevTools Network shows HTTP 200 on the document but the response body is empty or nearly empty
  • View Source shows little or no HTML, or HTML stops mid-tag
  • Homepage is blank while wp-admin or a direct post URL still loads (or the reverse)
  • Blank page after a plugin, theme, PHP, or hosting change
  • Page title or favicon appears in the tab but the visible area stays white
  • Hard refresh or private window still blank; other sites on the same host work
  • Console shows JavaScript errors on sites that rely on a front-end framework

Most likely causes

  1. 01 PHP fatal error in WordPress core, plugin, or theme with WP_DEBUG_DISPLAY off
  2. 02 PHP memory limit or timeout killing the script before output
  3. 03 Empty or corrupted index file, or wrong document root after migration
  4. 04 Full-page cache or CDN serving a cached empty 200 response
  5. 05 JavaScript runtime error preventing a SPA or block editor front end from rendering
  6. 06 CSS or theme bug hiding all content (zero-height containers, display:none on body)
  7. 07 Database connection or query failure that returns no content without a visible error page
  8. 08 Output buffering or a plugin that strips HTML and exits silently

What changed before the problem started

  • WordPress core, plugin, theme, or PHP version update
  • New caching, optimization, or security plugin enabled
  • Host migration with incomplete files or wrong document root
  • wp-config.php debug settings changed or error display disabled
  • CDN or reverse proxy cache rule added or purged incorrectly
  • Manual edit to index.php, functions.php, or .htaccess

Troubleshooting steps

  1. 01

    Confirm blank versus “will not load”

    Note whether the browser shows a connection error, certificate warning, or redirect loop — those are different guides. If the tab finishes loading but stays white, open DevTools → Network, reload once, and inspect the main document request. Success signal: you know the HTTP status and whether any HTML arrived.

  2. 02

    Inspect the document response body and size

    In Network, click the document row and read Response/Preview. An empty body with 200 suggests PHP died before output or cache stored nothing. Substantial HTML that looks fine in View Source but renders white points to CSS or JavaScript. Success signal: you can classify “empty server response” vs “HTML present but not visible.”

  3. 03

    Check the browser console for JavaScript errors

    Open DevTools → Console on the blank page. Uncaught errors in app bundles, block themes, or page builders can halt rendering even when HTML exists. Disable browser extensions and retry in a private window. Success signal: errors name a script file or plugin asset, or console is clean and the problem is server-side.

  4. 04

    Enable WordPress debug logging without public display

    If this is WordPress, set WP_DEBUG true, WP_DEBUG_LOG true, and WP_DEBUG_DISPLAY false in wp-config.php. Reload the blank page, then read wp-content/debug.log via SFTP or host file manager. Success signal: log lines name a plugin, theme, or PHP fatal path.

  5. 05

    Bypass cache and CDN temporarily

    Purge CDN and plugin/page caches. Test with a cache-busting query string or the host’s temporary/direct URL. If the blank page only appears through the CDN hostname, the origin may be fine and the edge cached an empty response. Success signal: uncached origin shows content or a visible PHP error.

  6. 06

    Isolate plugins and theme if logs point to PHP

    Rename wp-content/plugins folders (except one at a time) or switch to a default theme via SFTP/database if admin is unreachable. Follow the white screen and critical error guides when fatals appear in logs. Success signal: front end returns content after a specific plugin or theme is disabled.

When to stop troubleshooting

Hand off when you lack SFTP, database, or host log access; when blank pages persist after plugin/theme isolation and cache bypass; when the site is revenue-critical and logs show repeated fatals you cannot safely disable; or when blank responses appear on a non-WordPress stack you cannot debug locally. Provide HTTP status, response size, console errors, debug.log excerpts, and recent change history.

Information to collect before requesting help

  • 01 HTTP status and response size of the main document request
  • 02 Whether View Source shows HTML or an empty/minimal body
  • 03 Browser console errors (screenshot or copy)
  • 04 Whether wp-admin, direct post URLs, or a host temp URL behave differently
  • 05 Recent plugin, theme, PHP, cache, or migration changes
  • 06 wp-content/debug.log or host PHP error log excerpts with timestamps
  • 07 CDN/proxy status and whether bypassing cache changes the symptom
  • 08 Platform or CMS and hosting control panel access level

How a professional repairs the problem

We classify blank pages by layer — empty HTTP body, hidden PHP fatal, cache poisoning, or front-end render failure — using Network inspection, log correlation, and controlled cache bypass. For WordPress we enable safe logging, isolate the failing plugin or theme path, restore a working theme, and verify a full HTML response through CDN and origin. For non-WP stacks we trace document root, build output, and JS bundle errors until the page renders with stable monitoring.

Frequently asked questions

Is a blank page the same as the white screen of death? +
Often on WordPress, yes — both usually mean a PHP fatal with errors hidden. This guide triages all blank-page causes including empty caches and JavaScript failures; the white screen guide goes deeper on WordPress-specific PHP isolation.
Why does View Source show HTML but the page looks white? +
The server sent content, but CSS may hide it, JavaScript failed before paint, or a blocking script never ran. Check Console and disable optimization plugins that defer critical assets incorrectly.
Can a CDN cause a blank page without a 5xx error? +
Yes. An edge can cache an empty 200 from a brief origin failure. Purge everything and test the origin directly before chasing WordPress plugins.
Should I reinstall WordPress when the page is blank? +
Not first. Reinstalling core rarely fixes plugin fatals or empty cache responses and can overwrite customizations. Find the fatal or empty response cause, then reinstall only if core files are verified missing or corrupted.
The site is blank only when logged out — what does that mean? +
Membership, cache, or security plugins sometimes serve different HTML by cookie. Test logged-out in private window, purge page cache, and check plugins that gate content or inject redirects for anonymous users.
What HTTP status should I expect on a blank WordPress site? +
Often 200, which is why blank pages feel mysterious. Sometimes 500 if the host shows a generic error page. Always record the actual status and body length — that chooses the next guide.

Repair dispatch

Still Need Help Fixing Your Website?

If you are not comfortable editing website files, changing server settings, repairing a database, or troubleshooting a live website, professional help may prevent additional damage or downtime. We will review the problem before accepting the repair.

  • You will receive a clear explanation of the likely cause.
  • We will tell you if the issue falls outside our repair scope.
  • No additional work will be performed without approval.
  • A backup should be created whenever access and website condition allow it.
Emergency repair Request diagnosis

Do not share passwords through an unencrypted contact form.

Written by Website Rescue

Last reviewed

Platform note: Full rescue available for WordPress and self-hosted sites. Wix, Squarespace, Webflow, Weebly, and similar closed builders have very limited backend access — fixes may not be possible. I will tell you honestly before we start.