Website Development
Troubleshooting Common Issues with Web Development Projects
We support live websites for small businesses and handle these issues every week. This guide is for owners facing a problem with a site in progress or a site already live. It covers build problems, live site problems and a method for reporting issues clearly. Use it before you contact your developer, so each problem is fixed quickly and fairly.
Problems during the build
Build problems usually show up as missed dates, unclear progress or work that does not match the brief. Most start with a gap in scope, content or communication. Spotting them early keeps the cost of fixing them low. These are the build problems we see most often.
- The timeline slips because content, logins or feedback arrived late.
- The design looks different from what you expected or approved.
- Features appear that you did not request, or requested features are missing.
- Pages look correct on a desktop but break on a phone.
- Progress updates stop and questions go unanswered for days.
Compare each problem against the written brief and the agreed design. Raise any gap as soon as you see it, not at the end. Our guide to common mistakes when working with web developers covers how to prevent most of these.
Problems on a live website
Live site problems cost enquiries every hour they stay unfixed. Some are obvious, such as an error page, while others stay hidden for weeks. A broken contact form often goes unnoticed until someone mentions it. Check for these problems regularly.
- Contact forms or bookings that stop sending to your inbox.
- Slow pages, especially on mobile connections.
- Error messages such as 404 page not found or 500 server error.
- A security warning in the browser because the SSL certificate has expired.
- Lost search rankings after a redesign because redirects were not set up.
Submit a test enquiry through your own forms once a month. Test page speed with Google PageSpeed Insights after every major change. Our SEO services page explains how we monitor rankings and technical health.
How to report a problem to your developer
A clear report gets a problem fixed faster and avoids paying for investigation time. Developers need to see the problem and repeat it on their own screen. Vague reports such as "the site is broken" slow everything down. Follow these steps for every issue you report.
- Write down the page address where the problem happens.
- Describe what you did, what you expected and what happened instead.
- Note the device, browser and time the problem occurred.
- Take a screenshot or a short screen recording.
- Say how urgent it is, such as lost sales or a cosmetic issue.
- Send everything in one message to your agreed support contact.
Check your support agreement for response times before you need them. A good agreement separates urgent fixes from routine changes. Our website maintenance cost guide explains what support plans usually cover.
Website health checklist
Run this checklist once a month on any live website. Each item catches a problem before it costs you enquiries. Keep a note of the date and result for each check.
- Test enquiry sent through every form and received
- Key pages loaded and checked on a phone
- Page speed tested on the homepage and main service page
- SSL certificate valid, with no browser warnings
- No new 404 errors in Google Search Console
- Plugins and software updated by your developer
- Backups confirmed as working
Good to know
Troubleshooting FAQs
What are the most common website problems?+
Broken forms, slow pages and missing redirects cause the most lost enquiries. Expired SSL certificates and outdated plugins cause many security warnings. Most of these problems show up in a simple monthly check. Fixing them early is far cheaper than fixing them after customers notice.
How do I fix a 404 error on my website?+
A 404 error means a page address no longer exists. Your developer fixes it by restoring the page or redirecting the old address to the closest live page. Google Search Console lists the 404 errors it finds on your site. Send that list to your developer with each monthly check.
Why is my website slow?+
Large images, too many plugins and basic hosting are the usual causes. Unoptimised code and slow third-party scripts add further delay. A page speed test shows which issues affect each page. Your developer can then compress images, remove unused scripts or upgrade hosting.
Who pays to fix problems after launch?+
That depends on your contract and support agreement. Defects in the original build are often fixed free within an agreed period. New features and routine changes are usually charged separately. Confirm these terms in writing before the project starts.
Keep this checklist and reporting method with your website logins. Share them with anyone who manages your site day to day. So you can catch problems early, report them clearly and keep your site bringing in enquiries.
Last updated