Imagine opening your browser to check your shop’s website and seeing a blank white screen. Or worse — a full page that reads, “There has been a critical error on this website.”
Your stomach drops. Your customers are seeing the same thing. Orders are lost by the minute. And the worst part? You have no idea how to fix it, and the person who built your website is on holiday.
Take a breath. You don’t need to be a programmer to solve most website errors. What you need is a method. In this post, I’m going to walk you through exactly how to be your own PHP code checker and fixer — without writing a single line of code.
What Actually Goes Wrong When Your Website Breaks
Most small business websites run on WordPress, which is powered by a programming language called PHP. Think of PHP as the engine that builds your pages every time someone clicks. When a theme update, a plugin update, or a change on your web host clashes with existing code, the engine stalls — and you get an error screen.
What causes these failures? Often it’s a plugin that hasn’t been updated in months colliding with a newer one. A recent update to your theme could carry a bug. Or the memory limit on your server is simply too small. The exact reason doesn’t matter yet. What matters is finding which piece — which plugin or which theme — is to blame.
If you ignore it, the cost is real. A business website down for a day can lose hundreds or thousands of dollars in direct sales. Search engines also notice; a site that keeps breaking gets demoted in rankings, which means fewer visitors for weeks afterward.
But here’s the good news: WordPress has an official, free tool that lets you test your site with everything switched off — and it takes about ten minutes.
Be Your Own PHP Code Checker and Fixer: The 5-Step Method
There’s a free plugin called Health Check & Troubleshooting, maintained by the WordPress team. It’s the closest thing to a built-in PHP code checker and fixer helper. Here’s how to use it, in the exact order.
Step 1: Install the plugin. Log in to your WordPress dashboard (go to yoursite.com/wp-admin). Click Plugins > Add New, search for “Health Check & Troubleshooting.” Install and activate it.
Step 2: Enter Troubleshooting Mode. In your left menu, click Tools > Site Health, then click the Troubleshooting tab. Click Enable Troubleshooting Mode. This temporarily disables all your plugins and switches to a standard WordPress theme — but only for you. Your customers still see your normal website, so you can investigate without losing a single sale.
Step 3: Test your site. Open your main website address in a new browser tab. If the error is gone, you’ve found the problem: it’s a conflict between your plugins or your theme. If the error still appears, the issue is deeper — jump to Step 5.
Step 4: Find the exact culprit. While still in troubleshooting mode, go back to the Site Health screen and enable plugins one at a time (there’s an “Enable” button next to each one). After each plugin, reload your test tab. The plugin that brings back the error is your problem. Update that plugin to its latest version. If there’s no update available and it hasn’t been updated in over a year, it’s dead weight — swap it out for a replacement plugin that does the same job, then delete the old one.
If you’ve enabled every plugin and everything still works, the problem is your theme. In troubleshooting mode, you can switch to a default WordPress theme (like “Twenty Twenty-Four”) and test again. If that fixes it, your theme has the conflict. Update it — or if the theme is outdated, consider switching to a lighter, better-maintained one.
Step 5: Read the error log (your site’s black box). If troubleshooting mode didn’t fix anything, you need to see the actual error message. This is where a real PHP code checker comes in: error logs. Every time a PHP error happens, a record of it is saved on your server. To see it, log in to your hosting account — the company you pay for your website, such as GoDaddy, HostGator, or Bluehost. Open cPanel. Under the Metrics or Logs section, click Errors (in some cPanels it’s simply labeled Error Log). You’ll see lines like: PHP Fatal error: ... on line 12 of /public_html/wp-content/themes/.... That line tells you exactly which file is failing. Copy it and keep it.
If you can’t even log into WordPress at all (blank white screen), don’t panic. Open File Manager in cPanel. Go to public_html > wp-content. You’ll see a folder named plugins. Right-click it and rename it to plugins_off. Now load your website. If it comes back, your problem is plugin-related. Rename the folder back to plugins, then rename individual plugin folders inside it one at a time (for example, a folder named woocommerce is the WooCommerce plugin — rename it to disable it) and reload the site each time. When the site breaks, you’ve found the culprit.
When Your Website Isn’t WordPress: What Still Works
If your website was custom-built by a local freelancer or an agency, there is no single standard admin panel — so I won’t invent menu buttons and settings pages that may not exist on your setup. What I can tell you is one thing that’s true for virtually every website: your web host keeps an error log. This applies whether you’re on cPanel, Plesk, or a custom hosting dashboard. Look for anything called Error Log, Logs, or Developer Tools in your hosting account and open it. Lines that say “PHP Fatal error” or “PHP Warning” show the exact file and line number of the problem. That handful of text is the single most valuable thing you can obtain. Even if you can’t read it yourself, having the exact error log written down turns a vague “it’s broken” conversation into a solvable task.
One more genuinely useful move: ask your hosting company’s support chat to increase your PHP memory limit. It’s a common cause of sudden white screens, and for most business sites it’s a quick, harmless adjustment the host can make on their end.
What This Costs You Every Day You Ignore It
A broken website doesn’t just cost you the orders you lose while it’s down. It pushes customers to competitors. It leaves a bad impression. Search engines notice the downtime and drop you in results, and you’ll spend money on ads just to win back the visitors you used to get for free. Every day you wait is a day you’re paying — whether in lost sales or in later repair costs.
The steps above take about an hour. Even if you only complete Step 1 and Step 2, you’ll learn a huge amount about where the problem is coming from — and that’s the difference between panicking and being in control.
If you followed the steps above and your website is still broken — or you’d rather not risk making things worse yourself — that’s exactly when DevCev Digital can help, with a fast fix and a clear explanation of what went wrong.