FaultFound

Home What we find

The checks are chosen by one test: can a customer still do business with you?

FaultFound is not a general website audit. It looks for a specific class of problem — the kind that quietly stops someone buying, booking or getting in touch, while the website itself looks perfectly healthy.

Checking scope

Six categories of customer-impacting fault.

Severity labels below show the typical weighting for that class of fault. The score on a real finding depends on where it sits in your journey and how reliably we could reproduce it.

Buying

Everything between finding a product and completing a purchase.

  • Checkout failures Critical
  • Cart and basket errors Critical
  • Payment step errors Critical
  • Broken product pages High
  • Category pages that fail to load High
  • Delivery and postage steps that error Critical

Contacting

The routes a prospective customer uses to reach a human being.

  • Enquiry forms that fail High
  • Missing or broken contact pages High
  • Quote request routes High
  • Form endpoints returning errors High
  • Dead mailto and tel links Medium
  • Live chat that never loads Medium

Booking

Appointment, table, room, class and reservation journeys.

  • Booking systems returning errors Critical
  • Reservation links that 404 High
  • Appointment flows that stall High
  • Retired third-party booking providers High
  • Calendar widgets failing to render Medium
  • Booking buttons pointing nowhere High

Reliability

Server and delivery faults on commercially important pages.

  • Persistent HTTP 500 errors Critical
  • Persistent HTTP 503 errors Critical
  • 404s on important commercial pages High
  • Redirect loops and dead ends Medium
  • Certificate and HTTPS faults High
  • Mixed-content blocking Medium

Customer journey

Structural problems that strand a visitor part-way through.

  • Broken primary navigation High
  • Commercially important pages missing High
  • Broken commercial links Medium
  • Old URLs still publicly reachable Medium
  • Search returning errors Medium
  • Journeys that loop back on themselves Medium

Scripts & integrations

Front-end failures that block an action the customer needs to take.

  • JavaScript errors blocking key actions High
  • Buttons that do nothing when clicked High
  • Embedded forms that never submit High
  • Third-party widgets failing to load Medium
  • Payment widgets failing to initialise Critical
  • Consent walls that block the whole site High

Out of scope, on purpose

What we ignore matters as much as what we check.

Most automated audits pad their reports with anything they can measure. That is how a report ends up with ninety findings and no priority. We exclude these by design.

Never reported as a fault

  • Cosmetic and styling trivia. A slightly misaligned button is not a lost sale.
  • Analytics and tracking-tag failures. Annoying for reporting, invisible to customers.
  • Bot protection and rate limiting. Blocking us is your firewall working correctly.
  • One-off, transient server errors. Cleared on the re-check, discarded silently.
  • Branch and store-locator artefacts. Generated pages for locations that never existed.
  • Console warnings with no user impact. Deprecation notices are not faults.
  • Ad and consent scripts. Third-party noise you did not write and cannot control.
  • Anything behind a login. We never go there, so we never report on it.

What makes something reportable

  • It sits on a route a customer would realistically use.
  • It stops, blocks or derails an action with commercial value.
  • It reproduced on a separate, later check.
  • It was independently confirmed in a real browser.
  • It is not explained by bot protection or rate limiting.
  • It can be pinned to a specific, nameable URL.
  • There is a practical repair someone could actually carry out.
  • We can describe it without exaggerating what we know.

Platforms

The checks are platform-agnostic. The repair guidance isn't.

Because we test the way a customer browses, what your site is built on makes no difference to whether we can find a fault. It makes a great deal of difference to how we explain the repair.

WordPress & WooCommerce

Theme, plugin and template faults, plus the checkout and cart routes WooCommerce generates.

Shopify

Product, collection and checkout journeys, along with app-driven routes and embedded widgets.

Custom and bespoke builds

Anything that serves HTML over HTTP can be checked. Repair guidance is written from the evidence.

Site builders

Wix, Squarespace and similar platforms, where faults often come from an integration rather than the site.

Third-party booking systems

Where the journey leaves your website entirely and the failure happens at the provider.

Anything else

If a customer can reach it in a browser, we can check it. If we can't, we say so rather than guessing.

An honest limitation: we can tell you precisely what failed and where. On a platform we cannot see the source of, we describe the likely cause and the checks to run rather than pretending to know the exact line of code. Your report always distinguishes between what we observed and what we infer.

Want to see how a finding is written up?

The sample report shows the full structure: evidence, severity, confidence, plain-English explanation and repair direction.

Open the sample report Worked examples