Reporting and Upkeep

Prioritizing Fixes by Effort and Impact

A simple way to order website audit findings by how much they matter and how hard they are to fix, with a worked example and common pitfalls to avoid.

On this page
  1. The problem with a long list
  2. Impact: how much could this matter?
  3. Effort: how hard is it?
  4. Place each finding on a grid
  5. A worked example (hypothetical)
  6. Add a few tie-breakers
  7. Common mistakes
  8. Keep the result visible

The problem with a long list

An audit rarely ends with three tidy problems. More often it ends with dozens of items of very different weight: a handful of broken links, hundreds of images without descriptions, a slow template, some thin pages, a missing policy page. Treating everything as equally urgent leads to one of two outcomes: you freeze, or you start at the top of the list and spend a week on something trivial.

A simple ordering method fixes this. Rate each finding on two questions, how much it matters and how hard it is, and let the combination suggest the sequence.

Impact: how much could this matter?

Impact is a judgment, not a measurement, so keep the scale coarse: low, medium or high. Useful questions include:

  • Does it block visitors or search engines? Pages that cannot be reached, forms that fail, or important content kept out of search results are usually high impact.
  • How many pages or visitors does it touch? A problem in a template affects every page that uses it. A problem on one old page affects one.
  • How important are the affected pages? An issue on a page that brings inquiries or sales matters more than the same issue on an archive page.
  • Is there a risk? Security warnings and insecure resources, such as mixed content, deserve extra weight.
  • Does it affect people’s ability to use the site? Problems that make reading, tapping or navigating difficult are worth fixing even when the search effect is unclear.

Be honest about the uncertainty. Nobody can promise that a given fix will raise visibility. Weigh impact by how directly the problem hurts visitors and how plausible the harm to search performance is.

Effort: how hard is it?

Effort covers time, skill, cost and risk. Again, use low, medium or high.

  • Low: a few minutes to an hour, done by you, with little chance of breaking anything. Editing a title or fixing a link are typical.
  • Medium: a few hours or a day, may need some technical comfort, and may need testing.
  • High: requires a developer, a redesign, a migration or a long content effort.

Remember hidden costs. A change that touches many pages needs testing and a backup beforehand, and anything affecting URLs raises the risk of damage if done carelessly.

Place each finding on a grid

Put the two ratings together into four groups:

  • High impact, low effort (do first): the quick wins. Fix these immediately.
  • High impact, high effort (plan): major projects. Schedule them, break them into steps, and consider help.
  • Low impact, low effort (fill gaps): do these when you have spare time or are already editing the page.
  • Low impact, high effort (probably skip): write them down, but do not spend energy on them unless something changes.

The aim is not precision. It is to move attention away from the bottom-right corner and toward the top-left one.

A worked example (hypothetical)

Imagine a small local business site with these audit findings:

  1. The contact form fails to send mail on one browser. Impact: high. Effort: low to medium.
  2. Twelve pages have missing page descriptions. Impact: low. Effort: low.
  3. The home page loads slowly because of one oversized image. Impact: medium to high. Effort: low.
  4. The whole site uses an outdated layout that is hard to use on phones. Impact: high. Effort: high.
  5. A few old blog posts are thin and outdated. Impact: low to medium. Effort: medium.
  6. Alt text is missing from decorative images. Impact: low. Effort: medium.

The order that follows: first the form (item 1), then the oversized image (3), which are both cheap and valuable. Next, plan item 4 as a project with a budget and a timeline. Meanwhile, fix the descriptions (2) in a spare half hour. Items 5 and 6 go on a later list, with the thin posts reviewed as part of a wider look at content pruning.

The numbers on such a list are not to be taken as measurements; they are your best judgment at the time.

Add a few tie-breakers

When two items look alike, these can help decide:

  • Dependencies: some fixes must come first. Fixing the site’s redirect setup before cleaning up links, for example, avoids repeated work.
  • Risk of delay: security and site-down problems go first no matter what.
  • Fit with goals: prefer fixes that support your main conversion or your most important pages.
  • Momentum: a visible early win makes it easier to keep going.

Common mistakes

  • Fixing what is easy to find, not what matters. Tools flag thousands of minor warnings. Volume is not importance.
  • Treating tool severity labels as the final word. They are generic, and know nothing about your site’s purpose.
  • Overloading a sprint. Choose a realistic number for the period, such as three to five items, and finish them.
  • Making many changes at once. If you change ten things, you will not know which one helped or hurt. Group changes carefully and record them.
  • Never revisiting the list. Priorities shift as the site changes. Review the list at each monthly or quarterly check.

Keep the result visible

Record the final order in a simple table: finding, impact, effort, owner, target date and status. Reading it takes a minute, and it doubles as the action section of a report. When you finish an item, mark the date, so later results can be matched to the work.

A priority list does not guarantee results. It only helps you spend limited time on the things most likely to help.

The complete guide to reporting and upkeep

Reporting and Ongoing Site Maintenance
Read the guide

Keep exploring

Guides from other topics

All topics →