WordPress Website Down? What to Check First

WordPress Website Down? What to Check First

Table of Contents

WordPress Website Down? What to Check First

A WordPress website suddenly going down can be stressful, especially when it is generating leads, sales, bookings, or customer enquiries.

The good news is that a broken WordPress website does not necessarily mean that your data is lost or that the entire site needs to be rebuilt. In many cases, the cause is something relatively simple: a failed plugin update, PHP error, hosting issue, database connection problem, expired SSL certificate, or configuration conflict.

The key is to troubleshoot the problem in the right order.

In this guide, we explain what to check first when your WordPress website is down, what common error messages mean, and when it is better to get professional help instead of making further changes yourself.

1. Confirm That Your WordPress Website Is Actually Down

Before changing anything in WordPress, make sure the problem is not limited to your computer, browser, or internet connection.

Try opening the website:

  • in another browser;
  • in a private or incognito window;
  • from your phone using mobile data;
  • from another computer or internet connection.

Also try accessing the WordPress administration area directly:

yourwebsite.com/wp-admin/

If the website works from another device or network, the problem may be related to your browser cache, DNS cache, firewall, or local connection rather than WordPress itself.

If the website is unavailable everywhere, continue with the checks below.

2. Check the Error Message

The exact error displayed on the screen is one of the most useful clues when diagnosing a WordPress website.

500 Internal Server Error

A 500 Internal Server Error usually indicates a server-side problem.

Possible causes include:

  • a PHP error;
  • a faulty plugin;
  • a theme conflict;
  • corrupted .htaccess rules;
  • incorrect server configuration;
  • insufficient PHP memory.

If the error appeared immediately after installing or updating something, start there.

502 Bad Gateway

A 502 Bad Gateway error usually means that one server or service did not receive a valid response from another.

Possible causes include PHP processes, hosting infrastructure, a CDN or proxy, server overload, or temporary hosting problems.

503 Service Unavailable

A 503 Service Unavailable error means that the server is temporarily unable to process the request.

This can happen because of:

  • excessive server load;
  • hosting resource limits;
  • WordPress maintenance mode;
  • a malfunctioning plugin;
  • PHP problems.

504 Gateway Timeout

A 504 Gateway Timeout occurs when a server operation takes too long.

Heavy database queries, malfunctioning plugins, external API requests, insufficient hosting resources, or PHP processes can all contribute to this problem.

Error Establishing a Database Connection

This message means WordPress cannot communicate correctly with its database.

Possible causes include:

  • incorrect database credentials;
  • unavailable database server;
  • corrupted database tables;
  • hosting problems;
  • incorrect wp-config.php settings.

There Has Been a Critical Error on This Website

The WordPress critical error message usually indicates a fatal PHP error.

Plugins, themes, custom code, or PHP compatibility problems are common causes.

Before making changes, take a screenshot or copy the exact error message. It may make identifying the problem significantly easier.

3. Check Your Hosting

If the entire WordPress website is unavailable, your hosting account should be one of the first places you check.

Look for:

  • server outage notifications;
  • maintenance notices;
  • exceeded CPU or memory limits;
  • insufficient disk space;
  • PHP errors;
  • database server problems;
  • account suspension.

If several websites hosted on the same server or hosting account are down simultaneously, the problem is more likely to be related to the hosting environment than WordPress itself.

Server and PHP error logs can also provide valuable information about what happened immediately before the website stopped working.

4. Ask: What Changed Before the Website Went Down?

This simple question can save a lot of troubleshooting time.

Think about what happened shortly before the problem started.

Did you:

  • update WordPress?
  • update a plugin?
  • install a new plugin?
  • update the theme?
  • modify custom code?
  • change the PHP version?
  • change DNS settings?
  • configure caching or a CDN?
  • migrate the website?
  • change security settings?

If the website stopped working immediately after one of these actions, investigate that change first.

5. Check WordPress Plugins

Plugin conflicts are a common cause of WordPress problems.

If you can still access WordPress Admin, temporarily deactivate the plugin that was most recently installed or updated.

If /wp-admin/ is inaccessible, plugins can also be disabled through your hosting file manager or FTP/SFTP.

The plugin directory is normally located at:

/wp-content/plugins/

Temporarily renaming the plugins folder prevents WordPress from loading those plugins.

If the website starts working again, a plugin is likely responsible.

You can then restore the directory name and test the plugins individually to identify the problematic one.

Avoid deleting plugins or their data during initial troubleshooting unless you have a reliable backup.

6. Check the WordPress Theme

Themes can also cause fatal errors, particularly after WordPress, plugin, or PHP updates.

Potential causes include:

  • outdated theme code;
  • incompatible PHP functions;
  • child theme modifications;
  • custom functions;
  • page builder conflicts;
  • incomplete updates.

Temporarily switching to a standard WordPress theme can help determine whether your active theme is responsible.

Make sure you have a backup before making significant theme changes.

7. Check the PHP Version

WordPress, plugins, and themes all depend on PHP.

A website that worked yesterday can stop working after a hosting provider changes the PHP version or after an update introduces new PHP requirements.

Check which PHP version your hosting account currently uses.

An old plugin may not work with a newer PHP release, while newer WordPress software may no longer work correctly with an outdated PHP version.

Do not repeatedly switch PHP versions without checking compatibility first, as doing so can introduce additional problems.

8. Check the WordPress Database

If WordPress displays Error establishing a database connection, investigate the database before making unrelated changes.

WordPress database credentials are normally stored in:

wp-config.php

The problem could involve:

  • database username or password;
  • database hostname;
  • unavailable MySQL/MariaDB service;
  • corrupted tables;
  • hosting resource limits.

If nobody recently changed the website configuration and the database error appeared suddenly, check the hosting provider’s server status before modifying wp-config.php.

9. Check the .htaccess File

On Apache-based WordPress hosting, the .htaccess file controls important URL and rewrite behaviour.

Incorrect or corrupted rules can cause:

  • 500 errors;
  • redirect loops;
  • inaccessible pages;
  • broken WordPress permalinks.

Always make a backup of .htaccess before editing it.

Once access to WordPress Admin is restored, WordPress can often regenerate its standard rewrite rules by saving the Settings → Permalinks page again.

Custom .htaccess rules should not be removed permanently unless you know what they are used for.

10. Check SSL and HTTPS

Sometimes WordPress itself is working correctly, but visitors cannot access it because of an SSL problem.

Check whether:

  • the SSL certificate has expired;
  • automatic SSL renewal failed;
  • the domain points to the correct server;
  • www and non-www versions are configured correctly;
  • HTTPS redirects are working;
  • your CDN or proxy has the correct SSL configuration.

Browser security warnings can prevent visitors from using an otherwise functional website, so SSL problems should be resolved quickly.

11. Check DNS

DNS determines which server visitors reach when they enter your domain.

A DNS problem can therefore make a perfectly healthy WordPress installation appear offline.

Pay particular attention to DNS if you recently:

  • changed hosting providers;
  • changed nameservers;
  • modified DNS records;
  • enabled a CDN;
  • moved the website to another server.

DNS changes can also take time to propagate. During that period, the website may work for some visitors but not others.

12. Check Caching and CDN Services

WordPress websites often use several caching layers:

  • WordPress caching plugins;
  • server-side caching;
  • CDN caching;
  • reverse proxies;
  • browser caching.

An incorrect configuration or stale cache can sometimes make a website appear broken even when WordPress itself is functioning.

Purging the appropriate cache or temporarily bypassing the CDN can help identify the problem.

Be particularly careful when changing caching settings on WooCommerce or other dynamic websites.

13. Check WordPress Debug and Server Logs

When the cause is not obvious, logs are often more useful than guessing.

WordPress debugging and server logs may reveal:

  • the exact PHP error;
  • the affected PHP file;
  • the responsible plugin;
  • the responsible theme;
  • memory-limit problems;
  • database errors.

Debug information should normally be logged rather than displayed publicly on a production website because detailed errors can expose technical information about your server.

WordPress also provides built-in debugging tools that can help identify PHP errors. You can find instructions for enabling debugging in the official WordPress debugging documentation.

14. Restore a Backup When Necessary

If the website broke after an update or modification and repairing it would take longer than restoring a known working version, a backup may provide the fastest recovery route.

A complete WordPress backup should include:

  • website files;
  • the WordPress database.

However, restoring a backup should not be done blindly.

An e-commerce site, membership site, booking system, or active website may contain new orders, registrations, enquiries, or customer data created after the backup.

Whenever possible, preserve the current data before restoring an older version.

Regular WordPress maintenance: Website Maintenance 2025 – Keep Your Site Secure & Fast 

What NOT to Do When Your WordPress Website Goes Down

When a business website stops working, it is tempting to start changing everything.

That can make the original problem much harder to diagnose.

Avoid immediately:

  • reinstalling WordPress;
  • deleting plugins;
  • deleting the database;
  • replacing the theme;
  • modifying unfamiliar server files;
  • changing multiple settings simultaneously;
  • restoring an old backup without checking what data will be lost.

Instead, make one controlled change at a time and check the result.

Common website mistakes: Website Mistakes 2025 – Top Errors & How to Avoid Them

WordPress Website Down: Quick Troubleshooting Order

If your WordPress website is down, use this order:

  1. Confirm the website is unavailable to other users.
  2. Record the exact error message.
  3. Check your hosting and server status.
  4. Identify anything that changed recently.
  5. Check server and PHP error logs.
  6. Test recently updated plugins.
  7. Check the active theme.
  8. Check PHP compatibility.
  9. Check the database.
  10. Check .htaccess.
  11. Check SSL and DNS.
  12. Check caching and CDN configuration.
  13. Restore a known working backup if necessary.

Following a structured troubleshooting process reduces the risk of turning a relatively small WordPress problem into a much larger one.

When Should You Get Professional WordPress Help?

Professional website repair may be the safer option when:

  • both the website and WordPress Admin are inaccessible;
  • you repeatedly receive 500 or critical errors;
  • you cannot identify the faulty plugin or theme;
  • the database appears damaged;
  • the website may have been compromised;
  • an update caused multiple problems;
  • WooCommerce orders or customer data could be affected;
  • you do not have a reliable backup;
  • downtime is costing your business enquiries or sales.

The goal should not simply be to make the error disappear. The underlying cause should be identified so that the same problem does not return.

Need Help With a Broken WordPress Website?

If your WordPress website is down, displaying a critical error, or stopped working after an update, Verto.rocks can help diagnose and repair the problem.

Our website repair service can help with WordPress errors, plugin and theme conflicts, PHP problems, failed updates, database issues, SSL problems, redirects, configuration errors, and other technical website failures.

Visit our Website Repair page to tell us what happened and get help with your website.

Frequently Asked Questions

Why is my WordPress website down?

If your WordPress website is down, the cause could be a hosting outage, plugin or theme conflict, PHP error, database problem, failed update, DNS issue, or SSL configuration error. Start by checking whether the website is unavailable on multiple devices and then review your hosting status and recent website changes.

What should I check first when my WordPress website is down?

When your WordPress website is down, first record the exact error message and check whether your hosting server is online. Next, consider any recent WordPress, plugin, theme, PHP, DNS, or server changes. This can often narrow down the cause quickly.

Can a WordPress plugin cause my website to go down?

Yes. A faulty or incompatible plugin can cause PHP errors, critical errors, redirect loops, or even make the entire WordPress website inaccessible. If the problem started after installing or updating a plugin, temporarily disabling that plugin is a good troubleshooting step.

Why does WordPress say “There has been a critical error on this website”?

A WordPress critical error usually means that PHP encountered a fatal error. Common causes include incompatible plugins, theme code, custom functions, failed updates, or PHP version conflicts. Server error logs can often identify the exact file responsible.

Can I fix a WordPress website that is down without wp-admin access?

Often, yes. Even if /wp-admin/ is unavailable, troubleshooting can still be performed through your hosting control panel, file manager, FTP/SFTP, database tools, and server logs. However, make a backup before modifying website files or the database.

Will restoring a backup fix a WordPress website that is down?

A backup can restore a previously working version of the website, but it does not necessarily explain why the WordPress website went down. The original problem could return if it was caused by a plugin, PHP incompatibility, server configuration, or security issue. Active websites may also lose newer orders, enquiries, or other data when an older backup is restored.

How long does it take to repair a WordPress website?

It depends on the cause. Simple plugin conflicts or configuration errors may be identified quickly, while database corruption, malware, server problems, or multiple conflicting issues can require more investigation. Providing the exact error message and explaining what changed before the problem occurred can speed up diagnosis.

Who can help if my WordPress website is down?

If your WordPress website is down and you cannot identify the cause safely, a professional WordPress repair service can investigate the hosting environment, plugins, themes, PHP errors, database, SSL, DNS, and other potential problems. Verto provides WordPress website repair for businesses that need help getting their website working again.

WordPress Plugin Conflict: How to Find and Fix It Safely

WordPress Plugin Conflict - How to Find and Fix It Safely

Table of Contents

WordPress Plugin Conflict: How to Find and Fix It Safely

A WordPress website can suddenly stop working even when everything seemed fine a few minutes earlier. A page may turn blank, the admin area may become inaccessible, the layout may break, or you may see a critical error after updating a plugin.

One of the most common causes is a WordPress plugin conflict.

Plugin conflicts happen when two plugins interfere with each other, when a plugin conflicts with your theme, or when an update introduces code that is incompatible with your current WordPress or PHP version.

The good news is that plugin conflicts can usually be identified systematically. In this guide, we’ll explain the common symptoms, how to find the problematic plugin safely, and what to do if you can no longer access WordPress.

What Is a WordPress Plugin Conflict?

WordPress plugins extend the functionality of your website. They can add contact forms, payment gateways, SEO tools, caching, security features, page builders and thousands of other functions.

Problems can occur when two or more components try to perform incompatible actions.

A WordPress plugin conflict may involve:

  • two plugins conflicting with each other;
  • a plugin conflicting with your WordPress theme;
  • a plugin that is incompatible with your WordPress version;
  • an outdated plugin running on a newer PHP version;
  • JavaScript or CSS conflicts on the frontend;
  • caching or optimization plugins changing how another plugin works;
  • an incomplete or failed plugin update.

The conflict may affect the entire website or only one specific feature.

Common Signs of a WordPress Plugin Conflict

Plugin conflicts do not always produce an obvious error message.

Typical symptoms include:

  • a WordPress critical error;
  • a completely blank page;
  • wp-admin becoming inaccessible;
  • pages displaying incorrectly;
  • Elementor or another page builder failing to load;
  • contact forms no longer submitting;
  • WooCommerce checkout errors;
  • payment methods disappearing;
  • buttons or menus no longer working;
  • JavaScript errors;
  • unusually slow pages;
  • features disappearing immediately after an update.

If the problem appeared directly after installing or updating a plugin, that plugin should be one of the first things you investigate.

Before Troubleshooting: Make a Backup

Before disabling plugins or changing files, create a backup if you still have access to the website.

Ideally, the backup should include both:

  • website files;
  • the WordPress database.

If your hosting provider offers a staging environment, troubleshooting on staging is safer than experimenting directly on a live website.

For an e-commerce website, be particularly careful with database restoration. Restoring an old WooCommerce database can overwrite recent orders, customer accounts or other live data.

1. Check What Changed

Start with the simplest question:

What happened immediately before the problem started?

For example:

  • Was WordPress updated?
  • Was a plugin updated?
  • Did you install a new plugin?
  • Was PHP upgraded?
  • Did you change your theme?
  • Did a caching or optimization setting change?

If the site stopped working immediately after one particular update, you already have a strong candidate.

2. Disable the Suspected Plugin

If you can still access WordPress admin, go to:

Plugins → Installed Plugins

Deactivate the plugin you suspect is causing the problem.

Then test the affected page or function again.

If everything starts working, you have probably identified the source of the conflict.

Do not immediately delete the plugin. First determine whether an update, configuration change, rollback or alternative plugin can solve the problem.

3. Test Plugins One at a Time

If you don’t know which plugin is responsible, systematic testing is usually the fastest approach.

Deactivate non-essential plugins and then reactivate them individually while testing the website after each change.

The important part is to change one thing at a time.

If you disable or update several plugins simultaneously, you may fix the problem without ever discovering what actually caused it.

For a production WooCommerce store or another business-critical website, use a staging environment whenever possible.

What If You Can't Access WordPress Admin?

A plugin conflict can sometimes prevent access to /wp-admin/ completely.

In that situation, the plugin can still be disabled through your hosting File Manager or FTP/SFTP.

Navigate to:

/wp-content/plugins/

Each installed plugin normally has its own directory.

For example:

/wp-content/plugins/example-plugin/

Rename the suspected directory:

example-plugin-disabled

WordPress will no longer be able to load that plugin.

Try opening the website again.

If the site starts working, you have strong evidence that the plugin was involved in the problem.

4. Check for a Theme Conflict

Sometimes the plugin itself is not broken. Instead, the problem occurs only when it interacts with the active theme.

Testing with a default WordPress theme can help identify this type of conflict.

However, changing themes on a live production site can affect layouts, widgets and other settings.

For that reason, theme conflict testing is best performed on staging.

5. Clear All Caches

A site can appear broken even after the underlying problem has been fixed because an old version is still cached.

After troubleshooting, clear relevant caches such as:

  • WordPress caching plugin;
  • hosting/server cache;
  • CDN cache;
  • browser cache.

If JavaScript or CSS optimization is enabled, regenerate or purge optimized files as well.

6. Check WordPress and PHP Compatibility

A plugin may work correctly for years and suddenly fail after the server environment changes.

Check whether the plugin supports your current:

  • WordPress version;
  • PHP version;
  • WooCommerce version, if applicable;
  • page builder version.

Very old plugins that are no longer maintained are particularly risky.

If a plugin has been abandoned, replacing it with a maintained alternative may be safer than repeatedly repairing compatibility problems.

7. Enable WordPress Debugging Carefully

WordPress debugging can provide useful information when the visible error doesn’t reveal the cause.

WordPress includes built-in debugging options that can log PHP warnings and errors.

The official WordPress debugging documentation explains the available debugging settings and how they should be used.

On a live website, avoid displaying detailed PHP errors publicly because error messages may expose server paths or other technical information.

Logging errors privately is usually preferable.

Can You Simply Roll Back the Plugin?

Sometimes, yes.

If the problem began immediately after an update, returning temporarily to the previous working version may restore the website.

But a rollback should normally be treated as a temporary solution, particularly if the newer release contains security fixes.

You should still determine why the new version failed and whether the plugin developer has released a fix.

Plugin Conflicts and WooCommerce

Plugin conflicts can be particularly serious on WooCommerce websites because the visible website may continue working while checkout is broken.

A conflict might affect:

  • cart calculations;
  • payment gateways;
  • shipping methods;
  • checkout fields;
  • order creation;
  • transactional emails;
  • coupons;
  • taxes.

After making changes to a WooCommerce site, always test the complete purchase process rather than checking only whether the homepage loads.

If checkout itself is the problem, see our guide to WooCommerce Checkout Not Working: Common Causes and Fixes.

When Should You Get Professional Help?

Stop experimenting if troubleshooting risks making the problem worse or if the website is actively generating sales or enquiries.

Professional help makes sense when:

  • wp-admin is inaccessible;
  • the website shows a critical error;
  • checkout has stopped working;
  • you don’t have a reliable backup;
  • disabling plugins doesn’t identify the problem;
  • PHP errors continue after the suspected plugin is disabled;
  • the problem involves custom code;
  • the website needs to be restored quickly.

If your website is already broken, Verto offers Website Repair from €50.

GET HELP NOW

Preventing Future WordPress Plugin Conflicts

No WordPress website can be guaranteed never to experience a plugin conflict, but the risk can be reduced considerably.

Keep WordPress, themes and plugins maintained, remove extensions you no longer use, maintain reliable backups and avoid running abandoned plugins.

For important websites, test major updates on staging before deploying them to production.

A small amount of preventative maintenance is usually much easier than diagnosing a broken production website.

Final Thoughts

A WordPress plugin conflict can look serious, but the underlying cause is often identifiable.

Start by checking what changed, create a backup, isolate plugins systematically and avoid changing several things at once. If WordPress admin is inaccessible, plugins can often be disabled through the filesystem instead.

And if you’re dealing with a broader failure rather than an obvious plugin issue, see our guide:

WordPress Website Not Working? 12 Common Problems & Fixes

Frequently Asked Questions

What does “There has been a critical error on this website” mean?

It usually means WordPress encountered a fatal PHP error and couldn't complete the request. Plugins, themes, custom code, PHP compatibility and failed updates are common causes.

Can a WordPress plugin cause a critical error?

Yes. A plugin can trigger a fatal error because of a bug, failed update, PHP incompatibility or conflict with another plugin or theme.

How do I find which plugin caused a WordPress critical error?

Check the WordPress Recovery Mode email, PHP/error logs and recent plugin updates. Error logs may identify a file inside the affected plugin's directory.

Can I fix a WordPress critical error without wp-admin access?

Yes. Depending on your hosting setup, you can investigate the problem through a hosting control panel, file manager, FTP/SFTP, logs, Recovery Mode or WP-CLI.

Will restoring a backup fix a WordPress critical error?

It can, particularly if the error was caused by a recent change, but restoration isn't always the safest first step. On active WooCommerce sites, restoring an older database may also overwrite new orders and customer data.

How much does WordPress critical error repair cost?

Verto's website repair service starts from €50 for the first hour. If the issue requires additional work, the scope can be discussed before continuing.

WordPress Critical Error: What It Means and How to Fix It

WordPress Critical Error: What It Means and How to Fix It

Table of Contents

WordPress Critical Error: What It Means and How to Fix It

Seeing the message “There has been a critical error on this website” can be alarming — especially when your WordPress admin area or entire website suddenly becomes inaccessible.

The good news is that a WordPress critical error usually has an identifiable cause.

In many cases, the problem is related to a plugin, theme, PHP error, failed update or server configuration. The important part is finding the actual cause before making unnecessary changes.

This guide explains what a WordPress critical error means, the most common causes, what you can safely check yourself, and when it makes sense to get professional help.

Need help now?

If your website is currently down, Verto provides website repair from €50.

GET HELP NOW

What Is a WordPress Critical Error?

A WordPress critical error occurs when WordPress encounters a serious PHP error that prevents it from completing the request normally.

Instead of displaying the website or WordPress admin area, you may see:

Depending on the problem, the error may affect:

  • the entire website;
  • only the WordPress admin area;
  • one specific page;
  • checkout or another WooCommerce function;
  • a particular plugin feature;
  • only logged-in users.

The visible message itself doesn’t normally tell you exactly what went wrong.

You need to identify the underlying PHP error or determine what changed immediately before the problem appeared.

What Causes a WordPress Critical Error?

There isn’t one single cause.

Some of the most common are:

  • plugin conflicts;
  • failed plugin updates;
  • incompatible themes;
  • PHP version incompatibility;
  • PHP memory limits;
  • damaged WordPress files;
  • custom PHP code errors;
  • failed WordPress updates;
  • outdated plugins;
  • server configuration problems.

The timing of the error can provide an important clue.

If the website failed immediately after updating a plugin, for example, investigate that change first.

1. Check Your WordPress Recovery Mode Email

When WordPress detects certain fatal errors, it may send an email to the site’s administrator.

The subject may indicate that your site is experiencing a technical issue.

This email can be extremely useful because it may identify the plugin or theme responsible for the error.

It may also contain a special link that allows you to access WordPress using Recovery Mode.

Check the administrator email account configured in WordPress, including the spam folder.

However, don’t assume that no email means no useful diagnostic information exists. Email delivery can fail, and not every type of error triggers Recovery Mode.

2. Think About What Changed Before the Error

Before changing anything else, ask:

What happened immediately before the website stopped working?

Did you:

  • update WordPress?
  • update a plugin?
  • install a new plugin?
  • change the theme?
  • edit PHP code?
  • change the PHP version?
  • migrate the website?
  • change hosting settings?

If the critical error appeared immediately after one of these actions, you already have an important troubleshooting lead.

This is much safer than randomly disabling plugins or restoring old backups.

3. Check for a Plugin Conflict

Plugins are one of the most common sources of WordPress fatal errors.

A plugin may be:

  • incompatible with your WordPress version;
  • incompatible with your PHP version;
  • conflicting with another plugin;
  • damaged during an update;
  • dependent on another component that has changed.

If you still have access to WordPress admin, you can investigate recently updated or installed plugins.

If wp-admin is inaccessible, plugins can also be disabled using your hosting file manager or FTP.

However, be careful on WooCommerce and other business-critical websites. Disabling plugins on a live site can affect payments, orders, forms and other functionality.

If the problem is broader than the critical error

If you’re experiencing other WordPress failures as well, see our guide to common WordPress website problems and fixes.

4. Check Your Theme

Themes contain PHP code too, which means a theme can trigger a critical error.

This is particularly possible after:

  • a theme update;
  • a WordPress update;
  • a PHP version change;
  • editing functions.php;
  • adding custom theme code.

If the problem began immediately after changing the theme or editing theme files, investigate those changes.

Switching temporarily to a default WordPress theme can help isolate the cause, but again, do this carefully on a live website because changing themes can significantly affect the site’s appearance and functionality.

5. Check the PHP Version

WordPress runs on PHP.

Plugins and themes may require particular PHP versions, and older code can stop working when the server is upgraded.

For example, a hosting provider changing the site’s PHP version can expose compatibility problems in outdated plugins or custom code.

Likewise, using an outdated PHP version can create security and compatibility problems of its own.

Don’t randomly switch between PHP versions on a production site.

First check:

  • your current PHP version;
  • WordPress requirements;
  • plugin requirements;
  • theme requirements;
  • hosting logs.

The official WordPress requirements page provides current WordPress server requirements.

6. Increase the PHP Memory Limit — But Only If Memory Is the Problem

Some critical errors occur because WordPress runs out of available PHP memory.

An error log might contain a message similar to:

Allowed memory size exhausted

In that situation, increasing the PHP memory limit may resolve the immediate problem.

But don’t assume that every critical error is caused by insufficient memory.

A plugin consuming excessive memory can indicate a deeper problem. Simply increasing the limit repeatedly may hide the symptom rather than fix the cause.

Check the actual error first.

7. Enable WordPress Debugging Carefully

WordPress includes debugging functionality that can help identify PHP errors.

For troubleshooting, developers commonly use settings such as:

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

When configured correctly, errors can be written to a debug log without displaying technical information publicly to website visitors.

This is important.

Don’t leave PHP errors visible on a production website.

Error messages can reveal file paths and other technical information that visitors don’t need to see.

After troubleshooting, debugging should be returned to an appropriate production configuration.

8. Check Your Hosting Error Logs

Server and PHP error logs are often one of the fastest ways to diagnose a WordPress critical error.

Instead of guessing which plugin is responsible, the log may show:

  • the PHP error;
  • affected file;
  • line number;
  • plugin or theme directory;
  • memory problem;
  • missing function;
  • syntax error.

For example, if the error references a file inside:

/wp-content/plugins/example-plugin/

that gives you a much stronger lead than the generic critical-error message shown in the browser.

The file mentioned in the log isn’t always the root cause, but it’s an excellent starting point.

9. Check for a Failed WordPress Update

WordPress updates normally complete without problems, but interruptions can happen.

A failed or incomplete update may leave the site in an inconsistent state.

Possible symptoms include:

  • critical errors;
  • blank pages;
  • wp-admin inaccessible;
  • maintenance mode not disappearing;
  • missing files;
  • PHP errors.

If the problem started during an update, check whether the update actually completed.

Don’t immediately reinstall or overwrite everything. Preserve a backup and determine what failed first.

10. Check Custom Code

A small PHP syntax error can take down an entire WordPress website.

This commonly happens after editing:

  • functions.php;
  • custom plugins;
  • Code Snippets;
  • child themes;
  • WooCommerce customisations.

If the critical error appeared immediately after adding code, that code should be one of the first things you inspect.

Even something as small as an incorrect function call or compatibility problem can trigger a fatal PHP error.

Can You Fix a WordPress Critical Error Without wp-admin?

Yes.

Losing access to /wp-admin/ doesn’t mean the website cannot be repaired.

Depending on your hosting environment, troubleshooting can still be performed using:

  • hosting control panel;
  • file manager;
  • FTP/SFTP;
  • database tools;
  • PHP logs;
  • WordPress Recovery Mode;
  • SSH or WP-CLI where available.

For example, a problematic plugin can sometimes be disabled by renaming its directory.

However, don’t start deleting plugin directories or database records without understanding the consequences.

Disabling something is very different from deleting it.

Should You Restore a Backup?

Maybe — but not automatically.

A backup can be extremely valuable when a site breaks, particularly after a failed change.

But restoring an old backup has consequences.

On a simple brochure website, losing a few hours of changes may not matter much.

On a WooCommerce store, restoring an old database could potentially remove:

  • new orders;
  • customer registrations;
  • stock changes;
  • subscriptions;
  • recent settings;
  • other transactional data.

Before restoring a backup, determine what will actually be overwritten.

For WooCommerce-specific problems, see our guide to common WooCommerce checkout problems and fixes.

Don't Make Ten Changes at Once

One of the biggest troubleshooting mistakes is changing multiple things simultaneously.

For example:

  • disable five plugins;
  • switch themes;
  • change PHP;
  • clear every cache;
  • restore some files;
  • modify .htaccess.

And suddenly the website works.

Great — except now you don’t know what actually fixed it.

A better approach is:

  1. Record the current problem.
  2. Check recent changes.
  3. Check logs.
  4. Make one controlled change.
  5. Test.
  6. Record the result.
  7. Continue if necessary.

This makes troubleshooting much faster and reduces the risk of creating additional problems.

When Should You Get Professional Help?

It may make sense to get help when:

  • your business website is completely offline;
  • wp-admin is inaccessible;
  • the error appeared after an update;
  • you don’t have a current backup;
  • error logs contain unfamiliar PHP errors;
  • WooCommerce is affected;
  • customers cannot place orders;
  • you’re unsure which plugin caused the problem;
  • previous attempts have made the problem worse.

A critical error doesn’t necessarily require rebuilding the website.

Often, the correct fix is relatively small once the underlying cause has been identified.

Need Help Fixing a WordPress Critical Error?

If your website displays “There has been a critical error on this website”, Verto can investigate the problem and identify what’s causing it.

We troubleshoot WordPress problems including plugin conflicts, PHP errors, failed updates, theme problems, server issues and broken WooCommerce functionality.

Website repair from €50

No maintenance contract required.

If the problem requires substantially more work, we’ll discuss the scope with you before continuing.

GET HELP NOW

Frequently Asked Questions

What does “There has been a critical error on this website” mean?

It usually means WordPress encountered a fatal PHP error and couldn't complete the request. Plugins, themes, custom code, PHP compatibility and failed updates are common causes.

Can a WordPress plugin cause a critical error?

Yes. A plugin can trigger a fatal error because of a bug, failed update, PHP incompatibility or conflict with another plugin or theme.

How do I find which plugin caused a WordPress critical error?

Check the WordPress Recovery Mode email, PHP/error logs and recent plugin updates. Error logs may identify a file inside the affected plugin's directory.

Can I fix a WordPress critical error without wp-admin access?

Yes. Depending on your hosting setup, you can investigate the problem through a hosting control panel, file manager, FTP/SFTP, logs, Recovery Mode or WP-CLI.

Will restoring a backup fix a WordPress critical error?

It can, particularly if the error was caused by a recent change, but restoration isn't always the safest first step. On active WooCommerce sites, restoring an older database may also overwrite new orders and customer data.

How much does WordPress critical error repair cost?

Verto's website repair service starts from €50 for the first hour. If the issue requires additional work, the scope can be discussed before continuing.

WooCommerce Checkout Not Working? Common Causes and Fixes

WooCommerce Checkout Not Working? Common Causes and Fixes

Table of Contents

WooCommerce Checkout Not Working? Common Causes and Fixes

A WooCommerce store can look perfectly normal while one of its most important functions is broken: customers can’t complete their orders.

The problem may appear as a checkout page that keeps loading, a payment that fails, missing shipping options, an error after clicking “Place order”, or a checkout that simply does nothing.

Whatever the symptom, a broken WooCommerce checkout should be investigated quickly. Every customer who cannot complete a purchase is a potential lost sale.

In this guide, we’ll look at the most common reasons for a WooCommerce checkout not working, what you can safely check yourself, and when the problem may require deeper troubleshooting.

Need help with a broken checkout?

Verto provides WooCommerce and website repair from €50.

GET HELP NOW

WooCommerce Checkout Not Working? Start Here

Before changing plugins or settings, determine exactly where the checkout process fails.

Test your store as a customer would:

  1. Open the website in a private or incognito window.
  2. Add a product to the cart.
  3. Go to checkout.
  4. Enter valid billing and shipping information.
  5. Select a shipping method.
  6. Select a payment method.
  7. Attempt to place a test order.

Pay attention to the exact point where something goes wrong.

Does the checkout page fail to load? Does the payment method disappear? Does clicking Place order do nothing? Does the payment succeed but WooCommerce fail to create the order?

These symptoms can have very different causes.

If possible, also test on another browser and mobile device.

1. A WooCommerce Plugin Conflict

Plugin conflicts are among the most common causes of WooCommerce problems.

Your checkout may involve far more than WooCommerce itself. Depending on the store, it can interact with:

  • payment gateway plugins;
  • shipping plugins;
  • tax plugins;
  • multilingual plugins;
  • checkout customisation plugins;
  • security plugins;
  • caching and optimisation plugins;
  • analytics and tracking tools;
  • subscription or membership plugins.

An update to one plugin can create a compatibility problem with another.

If checkout stopped working immediately after a plugin update or installation, that change is an obvious place to investigate.

If you suspect a wider WordPress issue rather than a checkout-specific problem, see our guide to common WordPress website problems and fixes.

Don't deactivate everything blindly

On a live store, randomly disabling plugins can create additional problems.

Payment gateways, shipping methods and other plugins may be actively used by customers. Ideally, troubleshooting should be performed in a staging environment or during a controlled test.

2. The Checkout Broke After an Update

If your WooCommerce checkout worked yesterday and stopped after an update, check what changed.

The cause could be an update to:

  • WooCommerce;
  • WordPress;
  • your theme;
  • Elementor or another page builder;
  • a payment gateway;
  • a checkout plugin;
  • PHP;
  • another WooCommerce extension.

The latest update isn’t automatically the culprit, but the timing provides an important clue.

Check whether other users have reported compatibility problems with the same plugin version and review your WooCommerce system status for outdated templates or other warnings.

Avoid immediately rolling back multiple components. First identify which change is actually responsible.

3. Payment Gateway Problems

Sometimes checkout works until the customer attempts to pay.

Typical symptoms include:

  • card payments being rejected;
  • payment methods disappearing;
  • endless loading after clicking Place order;
  • customers being redirected to an error page;
  • payment succeeding but the order remaining unpaid;
  • orders being created twice;
  • customers returning from the payment provider to the wrong page.

Payment gateway problems can involve WooCommerce, but they can also originate outside your website.

Possible causes include:

  • incorrect API credentials;
  • expired API keys;
  • webhook problems;
  • payment provider outages;
  • test/live mode configuration errors;
  • unsupported currencies;
  • JavaScript conflicts;
  • security rules;
  • outdated payment plugins.

Before changing WooCommerce itself, check your payment provider’s dashboard and logs.

If multiple payment methods are available, testing another gateway can also help determine whether the problem affects checkout generally or one payment provider specifically.

4. JavaScript Errors Are Breaking Checkout

Modern WooCommerce checkout functionality depends heavily on JavaScript.

A JavaScript error can prevent buttons, payment fields or checkout updates from working correctly even though the page itself looks normal.

Symptoms may include:

  • Place order button does nothing;
  • checkout keeps spinning;
  • payment fields don’t appear;
  • shipping methods don’t update;
  • totals don’t recalculate;
  • fields stop responding.

JavaScript problems can be caused by themes, plugins, optimisation tools or third-party scripts.

Browser developer tools can reveal JavaScript errors, but interpreting them isn’t always straightforward. The script named in an error message isn’t necessarily the component that originally caused the conflict.

5. Caching or Optimisation Is Affecting Checkout

Caching can dramatically improve website performance, but WooCommerce contains dynamic pages that need special handling.

Pages such as:

  • Cart;
  • Checkout;
  • My Account

should not behave like ordinary static pages.

Problems can occur when caching, JavaScript delay, minification or CDN optimisation interferes with WooCommerce sessions or checkout scripts.

You may see strange behaviour such as:

  • carts becoming empty;
  • incorrect cart contents;
  • checkout fields not updating;
  • old prices appearing;
  • checkout failing intermittently;
  • one customer seeing information intended for another session.

If a problem started after changing caching or performance settings, review those changes carefully.

Simply clearing the cache may temporarily hide the problem without fixing the underlying configuration.

6. Shipping Methods Are Missing

A customer reaches checkout but sees:

“No shipping options were found”

or simply cannot select a shipping method.

Possible causes include:

  • incorrect shipping zones;
  • customer’s country or postcode not matching a zone;
  • product shipping classes;
  • minimum or maximum order requirements;
  • weight or dimension restrictions;
  • third-party shipping plugin errors;
  • API problems with a shipping carrier.

Test checkout using the same location and products as the affected customer.

A shipping method that works for one country or postcode may legitimately be unavailable for another.

7. Checkout Fields Are Causing Validation Errors

WooCommerce validates required checkout information before creating an order.

Problems can occur when:

  • required fields are missing;
  • custom fields are configured incorrectly;
  • address validation fails;
  • a checkout-field plugin conflicts with WooCommerce;
  • fields are hidden visually but still required;
  • multilingual versions use different field configurations.

The error message displayed to the customer can provide an important clue.

If you’ve customised the checkout form, test whether the problem occurs with the customisation disabled in a safe environment.

8. The Cart Empties Before Checkout

Few things are more frustrating for a customer than adding products to the cart only to find that they’ve disappeared.

This often points towards a session or caching problem.

Possible causes include:

  • page caching;
  • cookie problems;
  • inconsistent HTTP/HTTPS configuration;
  • domain or subdomain changes;
  • CDN configuration;
  • server-side caching;
  • WooCommerce session problems.

Test the problem in a private browser window and on another device.

If it only affects certain visitors, cookies or cached sessions become particularly important suspects.

9. WooCommerce Pages Are Configured Incorrectly

WooCommerce needs important pages and endpoints to function correctly.

Problems can appear after:

  • deleting a WooCommerce page;
  • changing page assignments;
  • changing permalinks;
  • migrating the website;
  • importing a database;
  • modifying checkout endpoints;
  • replacing checkout pages with custom templates.

Check WooCommerce settings to confirm the appropriate Cart, Checkout and My Account functionality is correctly configured.

If the checkout page itself returns a 404 or redirects somewhere unexpected, permalink and page configuration should be investigated.

10. Your Theme or Checkout Template Is Outdated

WooCommerce allows themes to override some of its templates.

This gives developers considerable control over store design, but those customised templates can eventually become outdated as WooCommerce evolves.

WooCommerce’s system status may report outdated template overrides.

An outdated template doesn’t automatically mean checkout is broken, but it can be an important clue when problems appear after a WooCommerce update.

Custom checkout templates should be reviewed carefully before simply replacing files, particularly if the store contains extensive design or functionality modifications.

11. PHP or Server Errors Are Interrupting Checkout

Checkout involves server-side processing as well as what customers see in their browsers.

PHP errors, insufficient memory or server resource problems can interrupt the process.

Possible symptoms include:

  • 500 errors;
  • blank checkout pages;
  • requests timing out;
  • Place order returning an error;
  • intermittent failures;
  • checkout working for small orders but failing for more complex ones.

Your hosting error logs can be extremely useful here.

If the server is generating fatal PHP errors, the generic message displayed to the customer may tell you very little about the actual cause.

12. A Third-Party Service Is Down

Your WooCommerce store doesn’t necessarily operate alone.

Checkout may depend on external services for:

  • payments;
  • shipping rates;
  • tax calculations;
  • fraud detection;
  • address validation;
  • subscriptions;
  • currency conversion;
  • inventory management.

If one of these services becomes unavailable or responds too slowly, checkout can fail even though nothing has changed on your website.

Check the service provider’s status page and logs before modifying your store.

This is particularly important when a problem appears suddenly without any recent WordPress or WooCommerce changes.

How to Troubleshoot a Broken WooCommerce Checkout Safely

When a live store is losing orders, it’s tempting to change everything until something works.

That’s risky.

A better process is:

  1. Reproduce the checkout problem yourself.
  2. Record the exact error or behaviour.
  3. Check whether all payment methods are affected.
  4. Test another browser and device.
  5. Check what changed recently.
  6. Review WooCommerce logs and system status.
  7. Check payment-provider logs if relevant.
  8. Confirm that you have a current backup.
  9. Use staging for disruptive testing whenever possible.
  10. Change one thing at a time and test again.

The goal isn’t simply to make checkout start working once.

You want to understand why it failed so the same problem doesn’t return tomorrow.

For additional technical reference, WooCommerce maintains official WooCommerce troubleshooting documentation.

Don't Test Risky Fixes on a Busy Live Store

A live WooCommerce store contains information that may be changing every minute:

  • new orders;
  • customer accounts;
  • stock levels;
  • payment records;
  • coupons;
  • subscriptions;
  • analytics data.

Restoring an old database backup or making uncontrolled changes can therefore have much greater consequences than doing the same thing on a simple company website.

A backup is essential, but “just restore yesterday’s backup” isn’t always a safe solution for an active online store.

You could restore checkout while simultaneously removing orders placed since that backup was created.

Use a staging environment whenever practical for potentially disruptive troubleshooting.

When Should You Get Help?

Consider professional WooCommerce troubleshooting when:

  • customers cannot place orders;
  • payments are failing;
  • you don’t know how long checkout has been broken;
  • checkout fails intermittently;
  • the problem involves PHP or server errors;
  • multiple plugins may be conflicting;
  • you’re uncomfortable testing on the live store;
  • you don’t have a safe staging environment;
  • previous fixes haven’t solved the underlying problem.

For an e-commerce business, checkout isn’t just another website feature.

It’s the point where visitors become customers.

Long checkout outages can easily cost more than fixing the problem.

Need Help With Your WooCommerce Checkout?

If your WooCommerce checkout is not working, Verto can investigate the problem and help identify what’s causing it.

We troubleshoot WooCommerce issues involving payment gateways, plugin conflicts, checkout errors, caching, failed updates, shipping problems and other website faults.

Website repair from €50

No maintenance contract required.

If the issue requires substantially more work, we’ll discuss it with you before continuing.

GET HELP NOW

Frequently Asked Questions

Why is my WooCommerce checkout not working?

Common causes include plugin conflicts, payment gateway problems, JavaScript errors, caching, incorrect shipping configuration, outdated templates and server-side PHP errors. Start by reproducing the problem and identifying exactly where checkout fails.

Why does nothing happen when I click Place order in WooCommerce?

A JavaScript error, payment gateway problem, checkout validation issue or server-side error may prevent the order from being processed. Browser and WooCommerce logs can help identify the cause.

Why are WooCommerce payment methods not showing at checkout?

Payment gateways may be restricted by currency, location, order value or configuration. Incorrect API credentials, plugin problems and JavaScript errors can also prevent payment methods from appearing.

Why does my WooCommerce cart keep emptying?

Caching, cookies, WooCommerce sessions, HTTP/HTTPS inconsistencies or CDN configuration can cause cart contents to disappear unexpectedly.

Can a plugin break WooCommerce checkout?

Yes. Checkout interacts with many plugins and third-party services. A plugin doesn't need to be specifically designed for checkout to create a JavaScript, PHP or compatibility conflict that affects it.

Should I restore a backup if WooCommerce checkout breaks?

Not automatically. On an active store, restoring an older database can remove orders, customer information or other changes made since the backup. Determine the cause first and use staging when possible.

How much does WooCommerce repair cost?

Verto's website repair service starts from €50 for the first hour. If more extensive work is required, the scope can be discussed before continuing.

WordPress Website Not Working? 12 Common Problems and How to Fix Them

WordPress Website Not Working? 12 Common Problems and How to Fix Them

Table of Contents

WordPress Website Not Working? 12 Common Problems and How to Fix Them

When your WordPress website suddenly stops working, the first question is usually simple: what happened?

Maybe the site shows a blank screen. Perhaps you see a critical error, pages refuse to load, the layout suddenly looks broken, or the website works for you but not for your visitors.

The good news is that many WordPress problems have identifiable causes. A failed update, plugin conflict, PHP error, caching problem, expired SSL certificate or hosting issue can all make a perfectly functional website appear broken.

In this guide, we’ll go through 12 common reasons why a WordPress website may stop working, what you can safely check yourself, and when it makes sense to get professional help.

Need help now?

If your website is currently broken and you don’t want to troubleshoot it yourself, Verto provides website repair from €50.

GET HELP NOW

1. Check Whether Your Website Is Actually Down

Before changing anything in WordPress, establish exactly what is happening.

Try opening the website:

  • in another browser;
  • in a private or incognito window;
  • on your phone using mobile data instead of Wi-Fi;
  • from another device.

If the website works elsewhere, the problem may be related to your browser cache, DNS, network connection or local device rather than WordPress itself.

If nobody can access the website, you’re probably dealing with a server, hosting, DNS or WordPress problem.

Also make a note of any error message you see. A 404, 403, 500, database error and WordPress critical error point towards very different problems.

Don’t start randomly disabling things until you know what symptom you’re trying to fix.

2. WordPress Shows “There Has Been a Critical Error on This Website”

One of the most alarming WordPress messages is:

“There has been a critical error on this website.”

Despite the wording, this does not necessarily mean your website has been permanently damaged.

A critical error is commonly caused by a PHP problem. Typical causes include:

  • a plugin conflict;
  • a faulty plugin update;
  • an incompatible theme;
  • unsupported PHP code;
  • insufficient PHP memory;
  • incompatible PHP versions.

WordPress may also send an administrator email containing information about the error and, in some cases, a recovery-mode link.

Check the administrator email account before making changes.

If the problem appeared immediately after installing or updating a plugin, that plugin is an obvious place to start investigating.

Be careful with random fixes

Searching the error message often produces tutorials recommending changes to wp-config.php, PHP files or your database.

Those techniques can be useful when performed correctly, but don’t edit important WordPress files without creating a backup first.

A small syntax error can turn a recoverable problem into a bigger one.

3. A Plugin Conflict Has Broken the Website

Plugins are one of WordPress’s greatest strengths — and one of the most common sources of problems.

Your plugins don’t operate independently. They interact with:

  • WordPress core;
  • your theme;
  • PHP;
  • WooCommerce;
  • other plugins;
  • third-party APIs;
  • your hosting environment.

An update to any one of these components can expose a compatibility problem.

Common signs of a plugin conflict include:

  • features suddenly disappearing;
  • forms no longer submitting;
  • checkout problems;
  • JavaScript errors;
  • broken layouts;
  • admin pages failing to load;
  • critical errors.

If you can still access WordPress Admin, check whether the problem started immediately after a recent plugin update.

You can sometimes identify the cause by disabling suspected plugins one at a time and testing the affected feature again.

However, be especially careful when doing this on a live WooCommerce store. Deactivating payment, checkout, caching, security or other important plugins can affect customers currently using the site.

4. Your Website Broke After a WordPress, Theme or Plugin Update

A website that worked yesterday and broke immediately after an update gives you an important clue.

Updates can introduce:

  • compatibility conflicts;
  • deprecated functions;
  • PHP incompatibilities;
  • CSS changes;
  • JavaScript problems;
  • database changes.

The obvious temptation is to downgrade everything immediately.

That’s not always the best approach.

First determine what was updated and whether that update actually caused the problem.

Check WordPress update history, plugin versions and any recent changes made by administrators or developers.

If you have a recent backup or staging environment, it may be possible to test the suspected change without experimenting on the live website.

5. Your WordPress Website Has a 500 Internal Server Error

A 500 Internal Server Error tells you that something went wrong on the server, but the browser cannot provide a more specific explanation.

Possible causes include:

  • PHP errors;
  • corrupted .htaccess rules;
  • plugin problems;
  • theme errors;
  • exhausted PHP memory;
  • incorrect server configuration;
  • file permission problems.

If the error appeared after a specific change, start there.

Hosting error logs can also provide much more useful information than the generic 500 page shown in your browser.

Avoid making multiple unrelated changes at once. If you change five things and the site starts working, you won’t know what actually caused the problem — and it may return later.

6. WordPress Shows a White Screen or Blank Page

A completely white page is sometimes referred to as the WordPress White Screen of Death.

You may see:

  • an entirely blank page;
  • only part of the website;
  • a blank WordPress Admin page;
  • one particular page failing while others work.

Common causes include PHP errors, exhausted memory, theme problems and plugin conflicts.

The absence of an error message doesn’t mean there isn’t an error. Production websites often have PHP errors hidden from visitors for security and usability reasons.

Server logs or WordPress debugging can reveal what is actually happening behind the blank page.

7. WordPress Can't Connect to the Database

If you see:

“Error establishing a database connection”

WordPress cannot communicate correctly with its database.

The database contains much of your site’s important content and configuration, so WordPress cannot function normally without it.

Possible causes include:

  • incorrect database credentials;
  • database server downtime;
  • hosting problems;
  • a corrupted database;
  • configuration changes;
  • resource limits.

If you haven’t recently changed database settings, check your hosting provider’s service status before editing WordPress configuration files.

A temporary database server problem can sometimes produce the same error without anything being wrong with your WordPress installation.

8. The Website Loads, but the Layout Is Broken

Sometimes WordPress is technically online, but the website suddenly looks completely wrong.

You might see:

  • missing styling;
  • oversized images;
  • incorrect fonts;
  • elements in the wrong positions;
  • broken mobile layouts;
  • Elementor sections displaying incorrectly;
  • menus without formatting.

This often points towards CSS, caching, CDN or page-builder problems rather than WordPress itself being offline.

If you’re using Elementor, regenerating CSS and data may resolve certain styling problems. Clearing the relevant cache can also help when an old stylesheet is still being served.

But don’t repeatedly purge and change every optimisation setting at once. Determine whether the problem affects all visitors and whether it started after a particular update or configuration change.

9. Your WordPress Website Is Suddenly Very Slow

A website doesn’t have to be completely offline to be effectively broken.

If pages suddenly take 10 or 20 seconds to load, visitors may leave before seeing them.

A sudden slowdown can be caused by:

  • a problematic plugin;
  • excessive database queries;
  • hosting resource limits;
  • external API problems;
  • caching failures;
  • unusually high traffic;
  • bots;
  • malware;
  • scheduled tasks;
  • large or unoptimised database tables.

The important word here is suddenly.

If your site has always been slow, it may need broader performance optimisation. If it became slow overnight, look for something that recently changed.

10. WooCommerce Checkout Isn't Working

For an online store, this can be one of the most expensive WordPress problems.

The website may look perfectly normal while customers are unable to complete purchases.

Symptoms can include:

  • Add to Cart not working;
  • cart contents disappearing;
  • checkout endlessly loading;
  • payment errors;
  • shipping methods missing;
  • checkout fields behaving incorrectly;
  • orders failing after payment;
  • confirmation emails not being sent.

WooCommerce checkout depends on multiple systems working together: WooCommerce itself, payment gateways, shipping plugins, your theme, JavaScript, caching and sometimes external services.

Don’t assume WooCommerce itself is automatically the cause.

If possible, reproduce the problem using a test order and note the exact stage at which checkout fails.

A broken checkout should be treated as a priority because every failed transaction can mean a lost customer.

11. Contact Forms or WordPress Emails Have Stopped Working

Your website may appear to work perfectly while silently losing enquiries.

Common symptoms include:

  • contact forms submit but no email arrives;
  • WooCommerce order emails disappear;
  • password-reset emails aren’t delivered;
  • messages land in spam;
  • email delivery works intermittently.

WordPress email delivery can depend on your hosting environment, DNS configuration, SMTP provider and email authentication.

The first step is determining whether WordPress is failing to send the email or whether the email is being sent but rejected or filtered later.

For business websites, this problem deserves attention quickly. A contact form that silently fails can remain unnoticed for days while potential customers assume you’re ignoring them.

12. SSL, DNS or Hosting Problems Are Making the Site Unavailable

Not every broken WordPress website is actually a WordPress problem.

Your site also depends on infrastructure around WordPress.

Problems can include:

  • expired SSL certificates;
  • incorrect DNS records;
  • domain expiration;
  • hosting downtime;
  • server resource limits;
  • CDN configuration errors;
  • DNS changes that haven’t propagated correctly.

If WordPress itself hasn’t recently changed, check these external dependencies before modifying your website.

This is particularly important after:

  • changing hosting companies;
  • moving a website;
  • changing nameservers;
  • enabling a CDN;
  • changing DNS;
  • renewing or replacing SSL certificates.

Sometimes the correct fix isn’t inside WordPress at all.

What to Do When Your WordPress Website Is Not Working

If your WordPress website is not working, the most important thing is to identify the cause before making random changes. You can also refer to the official WordPress troubleshooting documentation for general troubleshooting guidance.

A better troubleshooting sequence is:

  1. Confirm the problem on another device or network.
  2. Record the exact error message or symptom.
  3. Check what changed recently.
  4. Check your hosting status.
  5. Create or confirm that you have a recent backup.
  6. Investigate the most likely cause first.
  7. Make one change at a time and test again.

This makes troubleshooting much safer.

It also gives you a way back if an attempted fix makes things worse.

When Should You Stop Troubleshooting It Yourself?

There is nothing wrong with fixing a straightforward WordPress problem yourself.

But there is a point where continued experimentation becomes risky.

Consider getting help if:

  • your business website is completely offline;
  • customers cannot complete WooCommerce orders;
  • you don’t have a reliable backup;
  • the problem involves the database;
  • you need to modify PHP or server configuration;
  • you don’t know what caused the problem;
  • every attempted fix creates another problem;
  • the website contains important customer or business data.

The cost of professional troubleshooting can be considerably lower than the cost of prolonged downtime or recovering from an unsuccessful repair attempt.

Need WordPress or Website Repair?

If your WordPress website is still not working, you don’t have to spend the rest of the day troubleshooting it.

Verto provides WordPress and website repair from €50.

We can investigate problems including WordPress errors, WooCommerce issues, plugin conflicts, failed updates, Elementor problems, broken layouts and other website faults.

First hour: €50

No maintenance contract required.

If the problem requires substantially more work, we’ll let you know before continuing.

GET HELP NOW

Frequently Asked Questions

Why has my WordPress website suddenly stopped working?

Common causes include plugin or theme conflicts, failed updates, PHP errors, hosting problems, database connection issues, caching problems and DNS or SSL configuration errors. Start by identifying exactly what changed and what error the website is displaying.

Can a WordPress plugin break an entire website?

Yes. A plugin can cause a fatal PHP error or conflict with WordPress, your theme or another plugin. This doesn't necessarily mean the plugin itself is badly made; sometimes an update exposes a compatibility issue elsewhere in the website.

Why did my WordPress website break after an update?

An updated plugin, theme or WordPress version may no longer be compatible with another component of the website. The update can also expose older code that is incompatible with your current PHP environment.

What does a WordPress critical error mean?

It generally means WordPress encountered a fatal PHP error that prevented part or all of the application from running. Plugins, themes, custom code, PHP compatibility and memory problems are common causes.

Should I restore a backup immediately?

Not necessarily. A backup can be extremely useful, but first establish what happened. Restoring an old backup without understanding the cause can remove recent orders, enquiries, content or other data, and the same problem may occur again.

How much does WordPress website repair cost?

Verto.rocks website repair starts from €50 for the first hour. If the issue requires additional work, the scope can be discussed before continuing.

Website Maintenance 2025 – Keep Your Site Secure & Fast

Lobile phone and upload sign. Website Maintenance 2025
Lobile phone and upload sign. Website Maintenance 2025

Website Maintenance: Why Your Site Needs It (and How Much It Really Costs)

Building a website is only the first step. The real challenge begins after launch: keeping your site fast, secure, and relevant. Yet many businesses underestimate this and fall into the trap of thinking their site is a one-time project. In reality, ignoring updates and regular maintenance can lead to technical problems, security risks, and unexpected repair costs.

That’s why website maintenance is more important than ever. In this article, we’ll explore why maintenance matters, what’s included, how much it costs, and what happens if you skip it.

Why Website Maintenance Matters

Websites are no longer static brochures. They are dynamic systems with plugins, databases, and integrations that need regular care. Without proper maintenance:

  • Security risks grow – outdated WordPress software, themes and plugins can contain known vulnerabilities.
  • Performance can decline – technical problems and outdated components can negatively affect the user experience.
  • SEO can suffer – technical issues, poor performance and downtime can negatively affect search visibility and user experience.
  • Problems can become more expensive to fix – regular maintenance can help identify issues before they develop into larger repairs.

What Website Maintenance Includes

A proper care plan isn’t just “clicking update” in WordPress. It’s a structured set of ongoing tasks:

1. Regular Updates

  • WordPress core

  • Themes

  • Plugins

    👉 Helps keep your website up to date, secure, and compatible.

gears for updates: Website Maintenance 2025

Depending on the maintenance plan and hosting setup, additional services may also include:

2. Backups & Restore Options

  • Daily or weekly backups
  • Cloud storage
  • Restore options in case of failure

3. Security Monitoring

  • Malware scans
  • Firewall configuration
  • Login protection
shield icon for security. Security Monitoring: Website Maintenance 2025

4. Speed & Performance Optimization

  • Database cleanup

  • Caching setup

  • Image optimization

5. SEO & Analytics Monitoring

  • Checking indexing errors

  • Reviewing analytics reports

  • Identifying technical SEO issues

6. Bug Fixes & Small Tasks

  • Fixing minor display issues

  • Small layout adjustments

  • Fixing broken links

cloud and checklist: Website Maintenance 2025

Website Maintenance Costs

So how much should businesses expect to pay for website maintenance? The cost depends on the type of website, the level of ongoing support, and the services included in the maintenance plan.

Verto Website Maintenance – €40/month

  • WordPress core, theme and plugin updates
  • Basic compatibility checks after updates
  • Website health monitoring
  • Minor maintenance related to routine updates
  • Covers one WordPress installation

The plan is suitable for small business websites and can also cover WooCommerce and multilingual websites when they are part of the same WordPress installation.

More extensive services such as performance optimization, advanced security work, SEO work, custom development or major troubleshooting can be handled separately when needed.

View our → Website Maintenance – Monthly Care Plan

Common Website Maintenance Mistakes

Many businesses still fall into traps when it comes to maintenance:

  • Doing it themselves – without backups or rollback options.

  • Updating too late – waiting months between updates can leave known vulnerabilities and compatibility issues unresolved.

  • Skipping monitoring – assuming “no news is good news.”

  • Not planning for maintenance – only dealing with website problems when something breaks.

What Happens If You Skip Maintenance?

Without regular maintenance, website problems can go unnoticed until they start affecting visitors or customers:

  • A plugin or integration stops working correctly.
  • A contact form or checkout develops a problem that isn’t noticed immediately.
  • Outdated software may expose the website to known security vulnerabilities.

👉 The result can be lost enquiries or sales, unexpected repair work, and unnecessary downtime.

How to Choose the Right Website Maintenance Plan

The right maintenance plan depends less on the size of your website and more on its technical setup and the level of ongoing support it requires.

  • Small business websites may only need regular WordPress, theme and plugin updates together with basic compatibility checks.
  • WooCommerce websites may require the same routine maintenance but can need additional troubleshooting if checkout, payment or other integrations are affected.
  • Multilingual websites can also be maintained under a standard plan when they are part of the same WordPress installation.
  • Complex or high-traffic websites may require additional monitoring, performance optimization, security work or custom technical support.

👉 Choose a maintenance plan based on what your website actually needs rather than simply its number of pages.

Benefits of Website Maintenance

  • Peace of mind – routine WordPress updates and maintenance are handled regularly.
  • Fewer compatibility problems – keeping WordPress, themes and plugins updated helps reduce issues caused by outdated software.
  • Better reliability – regular checks can help identify technical problems before they affect visitors or customers.
  • Lower risk of unexpected repairs – addressing smaller issues early can help prevent them from developing into larger problems.

Final Thoughts: Website Maintenance

Websites need ongoing care just like any other important business system. Regular updates and checks help keep WordPress websites compatible, reliable and easier to manage over time.

Website maintenance should not begin only when something breaks. A simple routine maintenance plan can help identify smaller issues early and keep your website running smoothly.

👉 Verto offers a monthly Website Maintenance plan for WordPress websites, including WooCommerce and multilingual websites running on a single WordPress installation.

View our → Website Maintenance – Monthly Care Plan

Recent Posts

Website Mistakes 2025 – Top Errors & How to Avoid Them

Website mistakes 2025
Website mistakes 2025

Website Mistakes 2025: 10 Errors That Can Kill Your Online Success

The online world moves fast, and 2025 is no exception. Businesses that want to stay competitive need more than just a “pretty” site — they need a functional, secure, and high-performing one. Unfortunately, many companies still struggle with website mistakes 2025 that hurt visibility, conversions, and trust.

In this guide, we’ll look at the 10 most common website mistakes in 2025, explain why they matter, and show you how to avoid them.

Why Website Mistakes 2025 Are So Costly

A website is your most important digital asset. When it’s built poorly, the hidden costs appear quickly:

  • Lost visibility – poor SEO means you won’t show up in search.

  • Lost conversions – slow or confusing websites frustrate users.

  • Lost trust – broken features make your brand look unprofessional.

  • Higher repair costs – fixing website mistakes in 2025 is more expensive than preventing them.

The 10 Most Common Website Mistakes in 2025

1. Ignoring Mobile Optimization

With over 60% of web traffic coming from mobile, failing to optimize for smartphones remains one of the biggest website mistakes 2025.

  • Text is too small

  • Buttons overlap

  • Layout breaks on smaller screens

👉 Fix: Use responsive design and test on multiple devices.

mobile-friendly vs broken mobile design

2. Slow Loading Speed

Visitors won’t wait. If your site takes more than 3 seconds to load, most will leave.

  • Oversized images

  • Too many plugins

  • Cheap hosting

👉 Fix: Optimize images, reduce scripts, and invest in fast hosting.

slow website speedometer.

3. Weak SEO Setup

A classic website mistake in 2025 is focusing only on design while ignoring SEO.

  • Missing meta descriptions

  • No keyword strategy

  • Poor heading structure

👉 Fix: Build SEO into the website from day one using tools like Yoast or RankMath.

4. Complicated Navigation

Confusing menus are still among the top website mistakes 2025. Users should reach information within 2–3 clicks.

  • Too many menu items

  • Hidden pages

  • No clear CTA

👉 Fix: Keep navigation simple and prioritize calls to action.

5. Skipping Security Basics

Cyber threats continue to rise. An insecure website can be blacklisted overnight.

  • No SSL certificate

  • Outdated plugins

  • Weak passwords

👉 Fix: Always enable SSL, update software, and set up monitoring.

broken padlock for security

6. Poor Content Quality

Even with great design, bad content will sink a website.

  • Endless walls of text

  • Generic stock photos

  • No clear messaging

👉 Fix: Write clear, customer-focused copy and use authentic visuals.

7. No Analytics Setup

Flying blind is a critical website mistake in 2025. Without analytics, you can’t improve.

  • No GA4 setup

  • No conversion tracking

  • No traffic source data

👉 Fix: Add Google Analytics and heatmaps from launch day.

8. Overcomplicated Design

Overloading your site with animations, sliders, and pop-ups may look modern but creates frustration.

  • Slows down loading speed

  • Distracts from the message

  • Hurts mobile experience

👉 Fix: Keep design clean and purposeful.

9. Neglecting Maintenance

One of the most expensive website mistakes 2025 is assuming a site is “done” at launch.

  • Plugins stop working

  • Links break

  • Security holes remain open

👉 Fix: Invest in a care plan (like our €40/month maintenance package). 

10. No Clear Call to Action

Every business website should lead visitors toward an action — but many don’t.

  • No visible contact button

  • CTAs hidden too low on the page

  • Confusing forms

👉 Fix: Place clear CTAs on every page, especially above the fold.

Real-Life Example: Why Fixing Mistakes Pays Off

One client came to us with a DIY site built cheaply. It looked fine but had multiple website mistakes 2025: slow speed, no SEO, and no tracking. After six months, they had gained only two leads.

We rebuilt the site for €1,200 with optimized speed, SEO, and clear calls to action. Within three months, their traffic tripled and qualified leads grew by 7x.

👉 Lesson: fixing mistakes early is far cheaper than trying to rescue a failing site later.

How to Avoid Website Mistakes 2025

  • Start with strategy – define goals and audiences before design.

  • Work with experts – professional development prevents costly errors.

  • Plan for the long-term – budget for SEO, hosting, and maintenance.

  • Measure everything – don’t just launch, track and optimize.

Final Thoughts

The digital landscape is evolving quickly, and avoiding website mistakes 2025 is critical if you want your site to succeed. The most common issues — slow loading, poor SEO, weak security, bad navigation, and no clear CTAs — all have one thing in common: they cost businesses real money.

The good news? Every mistake is preventable with the right planning and execution.

👉 At Verto.rocks, we help companies build websites that don’t just look good — they convert, perform, and last.
Contact us today to make sure your next website avoids the website mistakes 2025.

Recent Posts