Sample Audit

Chattanooga home-services company.
What a real audit finds.

We ran the public homepage of a local Chattanooga service business through the same lab tests we use in every audit (Google Lighthouse, mobile, October 2026). The business is not named and is not a client — this page shows how we read the numbers and what we would fix first.

Performance

52

out of 100

Accessibility

92

out of 100

Search (SEO)

85

out of 100

Best practices

100

out of 100

Speed on a mobile phone

First content visibleTarget under 1.8 s2.4 s
Main content visible (LCP)Target under 2.5 s4.4 s
Fully usable (TTI)Target under 3.8 s14.2 s
Page frozen by scripts (TBT)Target under 200 ms2,730 ms
Layout stability (CLS)Target under 0.10.021

Lab results vary from run to run and by device; they show direction and size of the problem, not an exact guarantee.

Prioritized recommendations

01 / Critical

Cut third-party and unused scripts

Outside scripts froze the page for about 2.3 seconds, and roughly 335 KB of code loads but is never used. On a phone, a visitor who taps “Call now” may get no response for several seconds. We would remove or delay non-essential widgets and trackers and load the rest only when needed.

02 / Critical

Make the main content appear in under 2.5 seconds

The largest element on screen took 4.4 seconds to show. Serving modern, correctly sized images (about 300 KB of savings found) and prioritizing the hero content brings this down sharply.

03 / High

Lighten the page structure

The homepage has over 1,000 page elements and needs 8.7 seconds of phone processing work. A leaner build means faster loads and lower hosting cost.

04 / High

Fix links search engines and screen readers can’t follow

Some links have no readable name, some aren’t crawlable, and the robots.txt file has an error. These quietly limit how well Google understands the site and how usable it is with assistive technology.

05 / Medium

Tidy heading order and ARIA attributes

Headings skip levels and some elements use ARIA attributes that aren’t allowed. Small fixes, but they move the site toward WCAG 2.2 AA standards.