Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared hosting Managed WordPress Cloud hosting VPS hosting By reader location Hosting finder
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Blog Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Troubleshooting

Why Is Your WordPress Website Broken? Causes and Fixes

Why Is Your WordPress Website Broken? Causes and Fixes

Short answer

A broken WordPress site almost always follows a recent change. The usual causes are a plugin or theme update, a PHP error or version change, cache or minify settings, wrong URLs after a migration, a JavaScript error, or malware. Undo the last change first, then check each cause in turn.

Key takeaways

  • Ask what changed just before the site broke, since that usually reveals the cause.
  • Plugin and theme conflicts are the most common reason for a broken site.
  • The debug log names the exact file behind a critical error or white screen.
  • Clear every cache layer and disable minify options when styling disappears.
  • Wrong site URLs after a migration cause missing styles and redirect loops.
  • Back up before updates and update one thing at a time.

Why is your WordPress website broken?

Most broken WordPress sites trace back to a recent change: a plugin or theme update, a PHP version switch, a caching or minification setting, a migration, or a hack.

Broken can mean many things. The page might load with no styling, show a critical error, have a jumbled layout, or lose features like menus, forms or sliders.

Start with one question: what changed just before it broke? Nine times out of ten, the answer points straight at the cause.

Common triggers include:

  • A plugin, theme or WordPress core update.
  • A new plugin you just installed.
  • A PHP upgrade by you or your host.
  • New cache, minify or CDN settings.
  • A move to a new host or domain.
  • Edits to code, such as a theme functions file.
  • Malware injected by an attacker.

If your site will not load at all, that is a different problem with different checks. See our guide on why a WordPress site is down instead.

What are the signs of a broken WordPress site?

Signs include missing styles, a white screen, a critical error message, broken layouts, missing images, dead buttons, redirect loops, and an admin area that will not load or save.

Match your symptom to a likely cause before you start changing things:

What you seeMost likely causeFirst thing to try
Plain text, no stylingCSS not loading, wrong URLs, cache or minify issueClear cache, check site URLs
There has been a critical errorPHP fatal error from a plugin or themeCheck admin email for recovery link
White screenFatal error with display off, memory limitEnable debug log
Layout jumbled after updateTheme or builder conflict, stale CSSRegenerate builder CSS, clear cache
Menus, sliders or forms deadJavaScript errorCheck browser console
Images missingWrong URLs after migration, file permissionsSearch-replace URLs
Too many redirectsSSL or URL settings mismatchCheck Site Address settings
Spam links or odd redirectsHacked siteRun a malware scan

The rest of this guide walks through each cause in the order most likely to fix it.

Did a plugin or theme update break your site?

Very often, yes: a plugin or theme update that clashes with another extension, your theme, or your PHP version is the single most common cause of a broken WordPress site.

To confirm, deactivate plugins one at a time, or all at once, and see if the site recovers. Our guide to fixing a plugin conflict walks through the process step by step.

If you cannot log in, rename the plugins folder inside wp-content using FTP or your host's file manager. That deactivates every plugin at once. Our guide on deactivating plugins without admin access shows each method.

To test the theme, switch to a default theme such as Twenty Twenty-Five. If the site looks normal, the theme is the issue.

The free Health Check & Troubleshooting plugin helps here. Its troubleshooting mode turns off plugins and switches theme for your session only, so visitors are not affected.

Once you find the culprit, roll it back to the previous version or wait for a fix. Our guide to rolling back a plugin update explains how.

Is a PHP error or fatal error breaking your site?

If you see a critical error message or a white screen, a PHP fatal error is almost certainly to blame, and the debug log will name the exact file and line.

Since WordPress 5.2, fatal errors trigger recovery mode. WordPress emails the admin a special link that lets you log in with the broken plugin paused. Our explainer on WordPress recovery mode covers how it works.

If no email arrives, turn on debugging. Add these lines to your config file above the line that says to stop editing:

define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );

Errors then go to wp-content/debug.log. The WordPress debugging documentation explains each constant.

Common messages and what they mean:

  • Allowed memory size exhausted. Raise the memory limit. See our guide to fixing the memory size exhausted error.
  • Call to undefined function. A plugin depends on another plugin or a newer PHP version.
  • Syntax error, unexpected. Someone edited a PHP file and left a typo.

Turn debugging off again once the site is fixed.

Did a PHP version change break WordPress?

A host upgrade to a newer PHP version can break old plugins and themes that use removed functions, while a very old PHP version can break new ones.

Check your current PHP version under Tools > Site Health > Info > Server. Then compare it with the WordPress requirements page and each plugin's stated requirements.

If the site broke right after your host changed PHP:

  1. Switch back to the previous version in your hosting panel, if allowed.
  2. Update plugins and themes that are out of date.
  3. Replace any plugin that has not been updated in years.
  4. Switch PHP forward again and retest.

Our guide on fixing a site broken after a PHP update covers this in more depth. The PHP supported versions page shows which versions still get security fixes.

Is caching or minification breaking your layout?

Yes, quite often: stale cached pages, combined CSS files or deferred JavaScript can strip styling or break menus and sliders, especially right after an update.

Clear every cache layer first:

  • Your caching plugin.
  • Your host's server cache.
  • Your CDN, such as Cloudflare.
  • Your browser, by opening a private window.

Our guide to clearing cache in WordPress covers each one.

If clearing cache does not help, turn off CSS and JavaScript optimization options one at a time. Combine CSS, Delay JavaScript and Remove unused CSS are frequent culprits.

Page builders store generated CSS files. After updates, regenerate them. In Elementor, the option is under the plugin's tools settings, often labelled regenerate CSS and data.

Can a migration or URL change break WordPress?

Yes. After moving hosts or changing domains, old URLs left in the database cause missing styles, broken images, redirect loops and login problems.

Check Settings > General. The WordPress Address and Site Address must both match your live domain, including https.

Then replace old URLs throughout the database. A search-and-replace plugin or WP-CLI handles serialized data safely. Do not run a raw SQL replace on serialized fields.

Other migration problems to check:

  • Permalinks. Go to Settings > Permalinks and click save to rebuild rewrite rules.
  • File permissions. Wrong permissions can block images and uploads. See our guide to setting correct file permissions.
  • Mixed content. Some resources still load over http, which browsers block on an https page.

Our guide to fixing broken links after migration goes deeper.

How do you find JavaScript errors that break features?

Open your browser's developer tools, go to the Console tab and reload the page, and any red errors will name the script that failed.

JavaScript errors stop menus, sliders, tabs, forms and block editor features from working. One broken script can stop every script that runs after it.

In Chrome, Edge or Firefox, press F12 or right-click and choose Inspect, then open Console. MDN has a guide to what browser developer tools are.

Look at the file path in each error:

  • A path containing /plugins/plugin-name/ points to that plugin.
  • A path containing /themes/ points to your theme.
  • A path to your cache folder suggests minification broke the script.

Could your WordPress site be broken because it was hacked?

Yes. Unexpected redirects, spam links, unknown admin users, strange files and Google warnings are signs of a hack rather than a normal bug.

Signs of a compromise:

  • Visitors are sent to spam or scam sites.
  • Search results show pages you never created.
  • New admin accounts you did not add.
  • Unknown PHP files in uploads or core folders.
  • Your host suspends the account for malware.

Run a scan with a security plugin and check the file list. If you confirm a hack, follow our guide to cleaning a hacked WordPress site. Restoring a clean backup and changing all passwords is often the fastest fix.

How do you stop your WordPress site breaking again?

Keep regular backups, test updates on staging, update one thing at a time, and use well-maintained plugins, so you can spot and undo a bad change quickly.

Good habits:

  • Back up before every update. See our WordPress backup guide.
  • Update one plugin at a time and check the site between each.
  • Use staging for major updates and PHP changes.
  • Remove unused plugins and themes.
  • Keep a change log so you know what changed and when.

If you are stuck after trying everything here, restore your most recent working backup. Then reapply changes one by one until you find the one that breaks the site.

Frequently asked questions

Why does my WordPress site look broken only on my computer?

Your browser is probably showing a cached copy of old styles or scripts. Open the site in a private window or another browser. If it looks fine there, clear your browser cache. If it looks broken everywhere, the problem is on the site itself.

Why did my WordPress site break without me changing anything?

Automatic updates, host-side PHP upgrades, expired licences for premium plugins, or an expired SSL certificate can all change things without you noticing. A hack is also possible. Check your host's notices and the update history before assuming nothing changed.

Can I fix a broken WordPress site without losing content?

Usually yes. Posts and pages live in the database, which plugin, theme and cache problems do not touch. Deactivating plugins or switching themes does not delete content. Take a backup before making changes so you can always go back.

How do I know which plugin broke my site?

Deactivate all plugins, check the site, then reactivate them one at a time until the problem returns. The last plugin you turned on is the cause. The debug log or browser console can also name the plugin folder directly.

Should I reinstall WordPress if my site is broken?

Reinstalling core files rarely helps, because most problems come from plugins, themes, settings or the database. Try the checks in this guide first. If core files were damaged by a hack or failed update, reinstalling them from the Updates screen is safe and keeps your content.

Sources

  1. Debugging in WordPress WordPress Developer Resources
  2. Health Check & Troubleshooting WordPress.org Plugins
  3. Requirements WordPress.org
  4. Supported versions PHP
  5. What are browser developer tools? MDN Web Docs

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

Written and checked byWPLegible Editorial Team Independent WordPress reviews and guides

Researched from the primary sources listed above and checked against our editorial rules before publishing.