Common WordPress Problems and How to Fix Them
Most WordPress problems look worse than they are. A blank page, an alarming error message or a form that quietly stops sending emails usually traces back to a handful of causes: a plugin or theme change, an outdated PHP version, a server limit or a misconfigured setting.
Most common WordPress issues can be diagnosed with basic checks. Review what changed recently, turn on error logging, test one variable at a time, and always take a full backup (files and database) before you change anything.
That backup matters more than any other step in this guide. Before you deactivate a plugin, edit a file or roll back an update, make sure you have a restorable copy of your site. Many hosts offer one-click backups, and a reputable backup plugin works too. A backup you’ve never tested isn’t a safety net, so confirm you know how to restore it.
Regular professional WordPress maintenance helps reduce the risk of unexpected errors through planned updates, backups and ongoing technical checks.
The six problems below are the ones site owners ask about most often. For each, you’ll find the likely causes, what to check first and when to stop and ask for help.
WordPress White Screen of Death
Quick answer: The white screen of death (WSOD) is a blank page with no error message. It’s usually caused by a PHP error, a faulty plugin or theme, or the site running out of memory.
WordPress often hides errors from visitors for security reasons, so a fatal PHP error can look like an empty page. The most common triggers are:
- A plugin or theme that was just installed, updated or edited
- A PHP memory limit that’s too low for what the site is doing
- A plugin or theme that isn’t compatible with your PHP version
- A corrupted file after an interrupted update
What to Check First
1. Think About What Changed
Did you update, install or edit something shortly before the screen went blank? That’s your main suspect.
2. Check Whether the Admin Area Works
If /wp-admin loads but the front end doesn’t, the theme may be involved. If both are blank, investigate plugin conflicts, PHP errors and server-level issues.
3. Deactivate the Suspect Plugin First
If you can still reach the dashboard, deactivate the most recently changed plugin from the Plugins screen. If you can’t log in, use FTP or your host’s file manager to rename only that plugin’s folder inside wp-content/plugins, for example by adding -off to the end of the name.
4. Switch Themes Temporarily, If a Fallback Exists
If the problem looks theme-related, activate a default theme such as Twenty Twenty-Five (or whichever current default Twenty-series theme you have). Check that one is actually installed under wp-content/themes before you try. If you can’t reach the dashboard, renaming the active theme’s folder makes WordPress fall back to an installed default theme, and if none is installed you may be left with a different error.
Renaming the entire wp-content/plugins folder (for example to plugins-disabled) switches off every plugin on the site. That includes checkout and payment tools, contact forms, membership systems and security plugins. Use this method only if you can’t reach the dashboard, haven’t received a recovery-mode link and understand what will stop working while the plugins are off. Once the site loads, rename the folder back, then reactivate plugins one at a time, because WordPress may leave them deactivated.
When to Investigate PHP Errors or Debug Logs
If the quick checks don’t solve it, look at what PHP is actually reporting. In your wp-config.php file, you can enable logging with WP_DEBUG and WP_DEBUG_LOG, with WP_DEBUG_DISPLAY set to false so visitors don’t see errors. WordPress will then write errors to wp-content/debug.log. The log usually names the exact file and line that failed, which often points straight to the plugin or theme responsible.
Editing wp-config.php incorrectly can cause a new error of its own, so take a backup of the file first. Add the debug constants above the comment that says to stop editing, because anything placed below it may not take effect. When you’ve finished troubleshooting, turn debugging off again and confirm that logging has stopped. Consider deleting or restricting access to the log file too, since it can contain technical details you don’t want exposed.
There Has Been a Critical Error on This Website
Quick answer: This message means WordPress hit a fatal error it couldn’t recover from. It’s most often caused by a plugin or theme conflict, or by code that isn’t compatible with your PHP version. WordPress usually emails the site administrator a recovery-mode link.
Since WordPress 5.2, the platform has had a built-in fatal error handler. When it catches a serious error, it shows this message to visitors and sends a recovery-mode email to the administrator address on file.
How to Approach It Safely
1. Search Your Inbox for the Recovery Email
Check spam folders and the address set under Settings → General. The email may identify the plugin or theme associated with the error and provide a recovery-mode link.
2. Use the Recovery-Mode Link
It lets you log in with the faulty extension paused, so you can deactivate or update it from the dashboard. This is the safest route because nothing else on the site is switched off.
3. Disable Only the Affected Plugin or Theme
If there’s no email, use FTP or your host’s file manager to rename only the plugin or theme folder named in the error. Disabling the whole plugins folder is a last resort, for the reasons explained in section 1.
4. Check PHP Compatibility
In your hosting control panel, see which PHP version the site runs. A recent PHP upgrade can break older plugins, and a very old PHP version can break newer ones. Your hosting dashboard and the plugin’s documentation should list supported versions.
5. Read the Debug Log
If the error is still unclear, review the relevant entries in wp-content/debug.log and look for PHP errors, fatal errors or warnings recorded when the problem occurred. Note the file path and line number mentioned in the log, as these can help identify the plugin, theme or code responsible. Avoid sharing the log publicly because it may contain sensitive technical information.
Avoid editing plugin code on a live site as a first resort. A small typo can turn a recoverable error into a longer outage. If you do need to make changes, make them one at a time and keep a note of each so you can undo them.
WordPress Website Loading Slowly
Quick answer: Slow WordPress sites are usually caused by oversized images, missing caching, too many or poorly built plugins, or underpowered hosting. Test your site, fix the biggest issue first, and re-test after each change.
Speed affects both visitor experience and search visibility, so it’s worth methodical attention rather than random tweaks.
Practical Performance Checks
- Measure First Run your key pages through Google PageSpeed Insights or a similar tool. Note the largest issues rather than chasing a perfect score.
- Optimise Images Resize images to the dimensions they’re displayed at, compress them, and use modern formats such as WebP where your setup supports it. Enable lazy loading for images below the fold.
- Use Caching Page caching serves stored versions of pages instead of rebuilding them for every visitor. Many hosts include server-level caching; otherwise, a well-regarded caching plugin can do the job. Run only one caching solution at a time to avoid conflicts.
- Audit Plugin Overhead Plugins can add processing, database queries or front-end assets, although their performance impact varies. Review plugins you no longer need and investigate the ones contributing to slow requests. A diagnostic tool such as Query Monitor can show which plugins or database queries are slowest.
- Review Hosting Resources If your site has outgrown a basic shared plan, you may see slow server response times no matter how well it’s optimised. Check your host’s resource usage reports, PHP version and available memory.
- Keep the Database Tidy Large amounts of post revisions, expired transients and spam comments can add weight over time.
Remember: Change one thing at a time and re-test so you know what actually helped.
Plugin or Theme Conflicts
Quick answer: A plugin or theme conflict happens when two pieces of code interfere with each other, causing errors, layout problems or broken features. Find it by identifying recent changes, then testing on a staging site by disabling extensions one at a time.
Conflicts often appear right after an update, or when a new plugin overlaps with something you already use, such as two SEO plugins or two caching tools.
A Safe Way to Find the Cause
- List recent changes. Which plugins, themes or settings changed in the days before the problem began? Your hosting logs or an activity-log plugin can help.
- Use a staging site where possible. Many hosts offer one-click staging, which creates a private copy of your site. Troubleshooting there means visitors never see broken pages.
- Deactivate plugins one at a time, testing the problem after each, until it disappears. Then reactivate the others.
- Test with a default theme on staging, such as Twenty Twenty-Five, to rule your theme in or out. Changing themes can affect layouts and functionality, so avoid doing this on the live site whenever possible, and make sure a default theme is installed on the staging copy first.
- Check the plugin’s support forum or changelog. Other users have often reported the same issue, and a fix may already exist.
On a live site, plan before you deactivate. Switching off a payment gateway, membership plugin, booking system or security tool without preparation can interrupt orders, lock users out or leave the site exposed. If you must troubleshoot live, do it during a quiet period, note what each plugin does, and put up a brief maintenance notice if necessary.
WordPress Contact Form Not Working
Quick answer: If a WordPress contact form isn’t delivering messages, the cause is usually a wrong notification address, spam filtering, or the server’s default mail function being blocked. Configuring authenticated SMTP or a transactional email service often resolves WordPress email-delivery problems.
Forms fail in two ways: the form itself doesn’t submit, or it submits but the email never arrives. The second is far more common, and it can go unnoticed for weeks.
What to Check
- Form Settings Confirm the “send to” address is correct and typed without errors. Check the “from” address too: it should be an address on your own domain, not the visitor’s address, which mail providers often treat as spoofing.
- Spam Filtering Look in the junk folder of the receiving mailbox. Also review any anti-spam tools on the form, such as reCAPTCHA, honeypot fields or Akismet, in case they’re blocking genuine entries.
- SMTP Configuration By default, WordPress sends mail through the server’s basic mail function, which many hosts restrict and many inboxes distrust. An SMTP plugin connects your site to a proper email service, such as your email provider or a transactional email service, using authenticated credentials. Adding SPF and DKIM records for your domain helps receiving servers verify your messages, but it doesn’t guarantee inbox placement, so keep testing.
- Test Submissions After each change, send a test from the live form and check both the inbox and the spam folder. Test from a different email address than the one receiving the messages.
- Plugin Conflicts and JavaScript Errors If the form won’t submit at all, check your browser’s developer console for errors and test with other plugins temporarily disabled on staging.
Helpful tip: Some form plugins can store submissions in the WordPress database, depending on the plugin and its settings. Where available, enable entry storage and include those records in your backup strategy.
WordPress Updates Breaking a Website
Quick answer: Updates can break a site when new code isn’t compatible with other plugins, your theme or your PHP version. Reduce the risk by backing up first, checking compatibility, testing on staging and knowing how to roll back.
Updates are important, especially security patches, so the goal isn’t to avoid them. It’s to apply them carefully.
A Safer Update Routine
- Back Up First. Take a full backup of files and database immediately before updating.
- Read the Changelogs. Read the changelogs, especially for major version releases and anything critical to your business.
- Check Compatibility. Confirm that your theme and key plugins support the new WordPress version and your PHP version.
- Test on Staging. Apply updates there first and check key pages, forms, checkout and logins.
- Update in Small Batches. Update in small batches, not everything at once, so a problem is easy to trace.
- Schedule Updates for Quiet Periods. Schedule updates for quiet periods and test the live site right afterwards.
If an Update Breaks the Site
If you can safely access the dashboard, try reverting the recent change. Keep in mind that reverting a plugin or theme may not undo database changes made during the update. If the update changed data structures, restoring a verified pre-update backup may be the safer option, so check compatibility and recovery requirements before attempting a rollback. If the site remains broken, restore the backup or use your host’s recovery options. Then contact the developer’s support with the exact error message, and wait for a confirmed fix before updating again.
When Should You Get Professional WordPress Help?
DIY troubleshooting is a good first step. But bringing in a professional is the right call when:
- The same error keeps coming back after you’ve fixed it, which suggests an underlying cause
- Recovery attempts fail, or you’re not sure a backup is complete and restorable
- You suspect a security problem, such as unfamiliar admin users, redirects to other sites, unexpected files or spam pages
- The affected feature is business-critical, such as an online store, bookings or lead forms, where each hour of downtime has a real cost
- The fix requires editing code, server settings or the database, and a mistake could cause data loss
If your website has a persistent error, broken functionality or an issue you cannot safely resolve, our WordPress troubleshooting and one-time fix service can help identify the cause and restore normal operation.
If You Suspect a Hack
If you suspect a hack, stop and preserve the evidence. Don’t delete unfamiliar files, remove suspicious users or keep making repeated changes before the site has been investigated. Doing so can destroy evidence of how the intruder got in and may let the problem return. Take a backup first where feasible, even of the compromised site, and keep a note of anything you’ve already changed. Hacked sites need careful cleaning and a proper investigation into the cause.
A good WordPress developer will start by taking a backup, reproduce the problem on staging and explain what caused it, not just patch the symptom. Ask what they’ll check, how they’ll protect your data and how they’ll prevent a repeat.
Can't Fix the WordPress Issue? We're Here to Help.
Still struggling with a WordPress error, broken functionality or a website that won't load properly? Don't waste hours troubleshooting it alone. Contact Pegasus Digital Crew today.
We'll review your issue and help you understand the next steps. If we can't resolve the issue, you won't be charged for the fix. No unnecessary spending, no pressure. Just practical WordPress support when you need it.
Frequently Asked Questions
What is the most common WordPress error?
Plugin and theme conflicts cause a large share of WordPress problems, and they can show up as the white screen of death, the critical error message or broken page layouts. Recent updates and PHP version mismatches are the usual triggers.
Is it safe to troubleshoot WordPress on a live website?
It can be, but it carries risk. Whenever possible, reproduce and test on a staging copy. If you must work on the live site, take a fresh backup first, change one thing at a time and avoid disabling business-critical plugins during busy periods.
How do I fix the WordPress white screen of death?
Start by thinking about what changed recently. Deactivate the most recently changed plugin from the dashboard, or rename just that plugin’s folder via FTP if you can’t log in. Switch to a default theme if one is installed, and check your PHP memory limit. If it persists, back up wp-config.php, enable debug logging and read wp-content/debug.log to find the failing file. Disabling every plugin by renaming the whole plugins folder should be a last resort, because it switches off forms, checkout and security tools too.
Why didn’t I get the WordPress recovery-mode email?
The email goes to the administrator address in Settings → General, so it may have been sent to an old or mistyped address, or to spam. Some servers also block or fail to send WordPress emails. In that case, use FTP or your host’s file manager to disable only the plugin or theme named in the error.
How often should I back up my WordPress site?
It depends on how often your content changes. A site that rarely changes may need weekly backups, while a store or membership site should back up daily or in real time. Always take an extra backup before updates or major changes, store copies off the server and test a restore periodically.
Why is my WordPress contact form not sending emails?
The usual causes are an incorrect recipient address, messages landing in spam, or the host’s default mail function being unreliable. Configuring authenticated SMTP or a transactional email service, along with SPF and DKIM records, often resolves delivery problems. Then send test submissions to confirm.
Can updating WordPress break my website?
Yes, particularly when plugins or themes haven’t been updated for compatibility. Back up first, check compatibility notes, test on staging and update in small batches so any problem is easy to trace and reverse. If an update changed the database, restoring a verified backup may be safer than reverting the plugin alone.
When should I hire a WordPress developer?
Consider it when errors keep returning, you can’t recover the site, you suspect a hack, or the problem affects sales or leads. Professional help is also sensible for work that involves code, server configuration or database changes.