Website Operations
What a Website Audit Cannot See
A website score is a useful starting point, but it cannot prove every page, interaction, or customer journey works. Here is how to use an audit without asking it to do more than it can.
During our September–October 2026 website work, we kept coming back to a simple question: what can a website check actually tell us? A score can point you toward a problem. It cannot tell you that every visitor can finish the job they came to do. That distinction matters when you are deciding what to fix first or whether a change is ready to go live.
Our scoring methodology states the limits of our own free audit. It examines the HTML a server returns, checks one page at a time, and looks at a limited security surface. It does not run every interaction in a browser or inspect the private systems behind a site. That is useful information, but it is not a complete verdict.
Start by asking what was measured
Imagine an audit flags a missing page description. You can inspect the page, correct the text, and run the check again. That is a good use of an automated result: the problem is specific and the follow-up is clear.
Now imagine the audit reports no obvious problem with a contact page. Can someone open the menu on a phone, reach the form with a keyboard, understand an error message, and know whether the message was delivered? A server response alone cannot answer those questions. A customer experiences the rendered page and its behavior, not just the file the server sent.
The same distinction applies to contrast. A checker that reads colors from code may miss text over a photograph, a hover state, or a notice that only appears after a failed request. The right next step is to inspect the actual screen in the states people will see.
Build a short second pass
You do not need a giant testing department to get beyond a score. Pick the page or journey that matters most this week and run a few deliberate checks:
- Open it on a phone and a desktop screen. Look for clipped text and sideways scrolling.
- Use the keyboard. Can you see where focus is, open the menu, and reach the main action?
- Follow the action to its end. If it is a form, what does success or failure say? Do not submit a real inquiry just to test; use an approved test route or safe fixture.
- Visit the bottom. Footers, final calls to action, and content revealed on scroll are easy to overlook.
- Compare the result with a second tool or a manual review when the issue is consequential.
This is also how we approached the site-wide theme work in October. A stylesheet could say the right colors were present while one page still rendered unreadable text. We checked real pages in both themes and at different widths because those were the states visitors would actually use.
What if the audit score is good?
Keep the good result, but give it the right name. It means the checks that ran did not find a problem. It does not certify the whole website, promise legal compliance, or guarantee more sales. If a high score and a frustrated customer disagree, listen to the customer and investigate the journey.
The practical decision is to pair an audit with one real task. For a service business, that might be finding a service and making contact. For a nonprofit, it might be finding the right program and a way to ask for help. If the task is awkward, that is work worth considering even when the score looks healthy.
If you have an audit result and cannot tell what to do next, send us the page and the problem you are trying to solve. We can help separate a measurable defect from a wider usability question and choose a sensible first check.