How to Audit a Small Business Website Before Paying for a Redesign

A website can look dated without actually needing to be rebuilt. The opposite is also true: a site can look reasonably modern while hiding navigation, mobile, performance, content, or maintenance problems that make a redesign worthwhile.

Before paying for a redesign, audit the current website around the jobs it needs to do. The goal is not to collect a long list of cosmetic complaints. It is to separate problems that can be repaired from structural problems that a redesign should solve.

Start with the visitor path, not the visual style

Open the website as if you have never seen the business before. Within the first few moments, a visitor should be able to understand what the business offers, who the site is for, and where to go next.

Check the homepage, main service pages, contact path, and any location or supporting pages that matter to the business. Look for vague headings, competing calls to action, buried services, menus that require too much interpretation, and pages that do not lead anywhere useful.

If the main problem is wording or a few misplaced links, a full redesign may be unnecessary. If the entire site hierarchy makes important information difficult to find, the problem is more structural.

Audit the site in six separate layers

A useful audit becomes easier when you stop treating “the website” as one problem. Review these layers independently, then look at how they affect one another.

1. Content clarity

Read each important page without judging its colors or imagery. Does the page answer the question implied by its title? Does it explain the service clearly enough for a prospective customer to decide what to do next?

Watch for pages that repeat the same general sales language, sections that exist only to make the page longer, outdated details, duplicate information, and important questions that are never answered.

2. Navigation and information architecture

Count how many decisions a visitor must make to reach an important service or contact option. Menu labels should describe destinations clearly. Related pages should connect naturally instead of forcing visitors to return to the main menu after every page.

If this is a recurring problem, compare your findings with the guide on website navigation that has become too complicated.

Modern office desks and chairs beside large windows

3. Mobile usability

Do not evaluate mobile by shrinking a desktop browser and assuming that is enough. Use an actual phone or a reliable responsive preview and move through the same tasks a customer would perform.

Check whether the menu is easy to operate, headings wrap cleanly, buttons are easy to tap, images stay proportional, forms fit the screen, and columns stack in a sensible order. A site that technically fits on a phone can still be frustrating to use.

651 Web Design’s mobile-friendly website design guidance provides a useful next step when mobile layout is one of the problems the audit uncovers.

4. Performance

Separate measured performance problems from the feeling that a site is “slow.” Test important page types and look for repeatable issues. Large images, excessive scripts, plugin overhead, caching problems, and slow server responses can all contribute, but they require different fixes.

A redesign does not automatically make a website fast. If performance is the main complaint, diagnose it before rebuilding everything. The existing website speed troubleshooting guide explains how to prioritize likely causes.

5. Technical reliability

Test the pieces that visitors depend on rather than assuming they work because the pages load. Submit contact forms, follow important internal links, check redirects, verify HTTPS behavior, and look for obvious browser errors.

Also note how difficult routine WordPress work has become. If a simple text edit risks breaking a layout, plugins overlap heavily, or nobody understands why certain workarounds exist, maintainability belongs in the redesign decision.

Web developer working on code across dual computer monitors

6. Search and page structure

Check whether important pages have distinct purposes and whether their visible headings match those purposes. Look for missing or duplicated page titles, thin pages competing for the same topic, broken internal links, and important pages that are difficult to reach through the site structure.

This is not a promise that changing a few fields will improve rankings. It is a way to identify structural confusion before carrying it into a new website.

Label every finding: repair, redesign, or retire

Once the audit is complete, sort each finding into one of three decisions.

  • Repair: The underlying page or system is sound and the issue can be corrected without rebuilding the site.
  • Redesign: The problem is tied to the page structure, site hierarchy, mobile layout, or technical setup strongly enough that rebuilding is the cleaner path.
  • Retire: The page, feature, plugin, or content no longer serves a useful purpose and should not be carried into the new site.

This prevents a redesign from becoming a visual reskin of the same problems. It also keeps a repair project from expanding into a rebuild when a smaller fix would solve the real issue.

Write the redesign requirements from the audit

If the evidence points toward a redesign, turn the findings into requirements. Instead of asking for a “modern website,” document what the new site needs to accomplish.

For example, a useful requirement might be that visitors can reach every primary service from the main navigation, that the contact form works comfortably on a phone, or that routine content edits can be made without rebuilding page sections. These are testable goals. “Make it look better” is not.

The earlier guide on deciding between a website redesign and targeted repairs can help when the audit produces a mixed result.

Preserve what already works

A redesign should not automatically discard every existing asset. Identify useful copy, working URLs, strong page topics, effective forms, imagery worth keeping, and any content visitors already rely on.

Record important URLs before changing the structure. If a useful published URL must change, the migration plan should account for where it needs to lead afterward. Rebuilding first and inventorying later creates avoidable cleanup.

Audit again after the redesign

The pre-redesign audit creates a baseline. After the new site is built, repeat the important checks against the actual rendered website on desktop and mobile. Verify the visitor paths, forms, links, images, headings, performance, and page structure rather than assuming the new design solved them.

A redesign is successful when it fixes the problems that justified the project without introducing a new set of them. If you need help turning an audit into a practical rebuild plan, 651 Web Design works on WordPress website design, troubleshooting, performance, and site structure for small businesses.