The page tells an old business story
Services change, locations change, prices change, and teams change. If the site promises something you no longer deliver, hides the service you want to sell, or shows years-old proof as current, a visual refresh will not solve the credibility problem. Start with a content inventory and a new priority order.
Keep pages that answer real questions. Remove or redirect pages that create false expectations.
Mobile visitors fight the layout
If text is tiny, buttons are hard to tap, forms are awkward, or important images push the offer below the fold, the site is charging a mobile tax. Test with a real phone, not only a resized desktop window.
Responsive design should preserve hierarchy and clarity—not shrink every desktop element until it technically fits.
Speed, access, or security is a known problem
Large images, blocking scripts, broken focus states, poor contrast, missing labels, outdated dependencies, and mixed-content warnings are product problems. Core Web Vitals and accessibility checks give useful signals, but the most important test is whether people can complete the task.
Keep backups, domain access, hosting access, analytics, and form delivery under business control before the old site is replaced.
- Measure real page speed and key tasks
- Keyboard-test forms and menus
- Update dependencies and certificates
- Confirm backups and recovery
The business cannot learn from the site
A redesign should not remove the ability to see which pages create calls, forms, bookings, or sales. Define events and privacy choices before launch. Connect Search Console, analytics, and the inbox or CRM that owns the lead.
If the current site is performing, migrate carefully: keep important URLs, map redirects, update the sitemap, and check indexing after release.