Repair or Rebuild a WordPress Website? How to Decide
Fix what is wrong or start again? A way to decide based on the actual problems, what the business needs now and what a rebuild puts at risk.
Read the articlePlain-English guides to common WordPress website problems: a site that is slow, breaks after updates, looks wrong on a phone or is not bringing in enquiries. Each one explains likely causes, what you can check yourself and when it is worth getting a developer involved.
Fix what is wrong or start again? A way to decide based on the actual problems, what the business needs now and what a rebuild puts at risk.
Read the articleFine on a laptop, awkward on a phone. How to see what visitors see, the usual causes of mobile layout problems and which fixes are quick.
Read the articleA white screen, a critical error or a broken layout after clicking Update. What to do first, what is safe to try yourself and what to leave to a developer.
Read the articleTraffic is arriving but the contact form is quiet. An ordered set of checks: broken forms, wrong visitors, unclear next steps and measurement gaps.
Read the articleBefore installing another speed plugin, work out what is actually slow and why. How to measure properly, the usual causes and when to bring in a developer.
Read the article
WordPress website problems usually have a handful of common causes. A slow site is often too many large images or plugins. A site that breaks after an update is usually a conflict between a plugin, the theme and the version of PHP. A page that looks wrong on a phone is a layout problem. Few enquiries can come from the way the page is written, not from the traffic.
Start with the problem you recognise, such as a slow page or a broken layout, and read that guide first. Each one lists the checks that are safe to do yourself, so you can rule out the common causes of WordPress website problems before spending money. If a guide solves it, you have saved time. If it does not, you will at least know what to tell a developer.
They are written for business owners and managers, not developers. Each guide explains the likely causes, what you can check yourself and when it makes sense to bring in a developer. Where an article relies on a source, such as the WordPress troubleshooting guide, it links to it so you can read it yourself.
Some WordPress website problems need hands-on work. If your site is down, or you are not comfortable changing settings on a live website, send me the details and I will tell you what I would check first. You can also see the services I offer, such as fixes and support, or how a project works from first message to launch. New guides are added as common questions come in, so the topics grow over time.
Send a few details about the site, what it needs to do and when you would like it live. I read every enquiry myself and reply with questions or next steps.