Website review, no card needed

americanhomewater.com logo

americanhomewater.com website review

Visit site (opens in a new tab)Reviewed 14 November 202644 issues · 95 checks

This review found 44 issues worth fixing on americanhomewater.com, 20 of them high impact, across 95 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
4.2 s3.2 sMay 23Nov 73.5 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20264.0 s
May 30, 20263.8 s
Jun 6, 20263.8 s
Jun 13, 20263.8 s
Jun 20, 20263.6 s
Jun 27, 20263.6 s
Jul 4, 20263.5 s
Jul 11, 20263.5 s
Jul 18, 20263.4 s
Jul 25, 20263.4 s
Aug 1, 20263.3 s
Aug 8, 20263.3 s
Aug 15, 20263.4 s
Aug 22, 20263.3 s
Aug 29, 20263.6 s
Sep 5, 20263.6 s
Sep 12, 20263.9 s
Sep 19, 20263.9 s
Sep 26, 20263.9 s
Oct 3, 20263.9 s
Oct 10, 20263.7 s
Oct 17, 20263.8 s
Oct 24, 20263.7 s
Oct 31, 20263.5 s
Nov 7, 20263.5 s
Real-visitor tap response (INP)75th percentile, phones
226 ms76 msMay 23Nov 7170 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026100 ms
May 30, 202695 ms
Jun 6, 202696 ms
Jun 13, 202693 ms
Jun 20, 2026104 ms
Jun 27, 2026107 ms
Jul 4, 2026104 ms
Jul 11, 2026104 ms
Jul 18, 2026109 ms
Jul 25, 2026117 ms
Aug 1, 2026114 ms
Aug 8, 2026117 ms
Aug 15, 2026137 ms
Aug 22, 2026145 ms
Aug 29, 2026157 ms
Sep 5, 2026161 ms
Sep 12, 2026176 ms
Sep 19, 2026185 ms
Sep 26, 2026194 ms
Oct 3, 2026209 ms
Oct 10, 2026202 ms
Oct 17, 2026208 ms
Oct 24, 2026208 ms
Oct 31, 2026154 ms
Nov 7, 2026170 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of americanhomewater.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. americanhomewater.com at 1.4 s1.4 s
  2. americanhomewater.com at 2.8 s2.8 s
  3. americanhomewater.com at 4.3 s4.3 s
  4. americanhomewater.com at 5.7 s5.7 s
  5. americanhomewater.com at 7.1 s7.1 s
  6. americanhomewater.com at 8.5 s8.5 s
  7. americanhomewater.com at 9.9 s9.9 s
  8. americanhomewater.com at 11.3 s11.3 s

Speed

15 to fix13
  • Render-blocking requests

    3.0 s

    40 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.0 s.

  • Google Tag Manager adds 1.0 s

    1.0 s

    Google Tag Manager costs a phone 1.0 s of main-thread work and 874 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Mobile performance score: 13

    13/100

    Your mobile performance score is 13. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Main-thread work: 8.7 s

    A phone's processor spends 8.7 s on main-thread work while loading, 4.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • 3,805 HTML elements

    The page has 3,805 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and leadconnectorhq.com and others), adding 2.9 MB and 2.5 s of main-thread time.

  • Use efficient cache lifetimes

    350 ms · 1.1 MB

    47 files are served with short cache lifetimes, so returning visitors download them again (1.1 MB).

  • Reduce unused JavaScript

    1.3 MB

    About 1.3 MB of JavaScript is downloaded but never used on this page.

  • Reduce unused CSS

    650 ms · 85 KiB

    About 85 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 650 ms faster on a phone.

  • Facebook adds 460 ms

    460 ms

    Facebook costs a phone 460 ms of main-thread work and 247 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Minify JavaScript

    350 ms · 107 KiB

    107 KiB could be saved by minifying JavaScript.

  • leadconnectorhq.com adds 338 ms

    338 ms

    leadconnectorhq.com costs a phone 338 ms of main-thread work and 1.1 MB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • 20 long tasks on the main thread

    20 long tasks block the main thread while loading, the longest for 420 ms. During a long task the page ignores taps.

  • Font display

    300 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 300 ms).

  • realworklabs.com adds 192 ms

    192 ms

    realworklabs.com costs a phone 192 ms of main-thread work and 319 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Improve image delivery

    200 ms · 44 KiB

    3 images could be 44 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 200 ms faster on a phone.

  • Legacy JavaScript

    50 KiB

    Polyfills for old browsers add 50 KiB JavaScript that modern phones do not need.

  • Chained critical requests

    Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

1 checks passed
  • Server response: 80 ms

    80 ms

    Your server sent the HTML in 80 ms, well inside Google's 600 ms guideline.

Core Web Vitals

12 to fix67
  • Fails Core Web Vitals for real visitors

    Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

  • Real-user FCP: 3.4 s

    3.4 s

    Real visitors see the first content after 3.4 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 2.3 s

    2.3 s

    Real visitors wait 2.3 s for your server to start answering (75th percentile). Good is under 800 ms.

  • Time to Interactive: 33.8 s

    33.8 s

    The page becomes fully interactive after 33.8 s. Good is under 3.8 s.

  • Speed Index: 12.2 s

    12.2 s

    Visually, the page fills in at 12.2 s (Speed Index). Good is under 3.4 s.

  • Total Blocking Time: 2.3 s

    2.3 s

    Scripts block taps and scrolling for 2.3 s in total while the page loads. Good is under 200 ms.

  • Cumulative Layout Shift: 0.75

    0.75

    The layout shifts by 0.75 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Largest Contentful Paint: 5.0 s

    5.0 s

    Your largest element takes 5.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “When comfort matters, Phoenix homeowners turn to American H…”. Most of its time is element render delay (4.4 s).

  • First Contentful Paint: 3.5 s

    3.5 s

    The first text or image appears after 3.5 s on a phone. Good is under 1.8 s.

  • Real-user LCP: 3.5 s

    3.5 s

    Real visitors wait 3.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Tap response (INP) got 66% slower for real visitors

    +66%

    Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 100 ms to 170 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • 8 images without width and height

    8 images have no width and height attributes, so the layout jumps as each one loads.

3 checks passed
  • Real-user INP: 162 ms

    162 ms

    Real visitors wait 162 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Largest content (LCP) got 11% faster for real visitors

    -11%

    Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 4.0 s to 3.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Images and page weight

1 to fix70
  • Page weight: 19.7 MB in 270 requests

    19.7 MB

    Your homepage downloads 19.7 MB in 270 requests on a phone: media 11.9 MB (1), scripts 3.3 MB (135) and other files 3.0 MB (55). Under 2 MB keeps phones on slow connections fast.

  • About 5.6 g of CO₂ per visit

    5.57 g

    By the Sustainable Web Design model, a visit to your homepage emits about 5.57 g of CO₂e: 668.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

9 to fixGoogle 8589
  • 9 tap targets too small

    9 tap targets are too small or too close together to hit reliably with a finger.

  • Links look like plain text

    5 links inside paragraphs rely on colour alone to stand out.

  • Scrollable region must have keyboard access (3 elements)

    Scrollable region must have keyboard access: 3 elements on the page fail this check, rated serious by axe-core.

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

  • All page content should be contained by landmarks (53 elements)

    All page content should be contained by landmarks: 53 elements on the page fail this check, rated moderate by axe-core.

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • 3 links without text

    3 visible links have no text or label, so screen readers cannot say where they go.

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • ARIA role should be appropriate for the element (5 elements)

    ARIA role should be appropriate for the element: 5 elements on the page fail this check, rated minor by axe-core.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

2 checks passed
  • Every image has alt text

    All 50 images in the HTML carry an alt attribute.

  • 47 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 8 failed. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 9293
  • Meta description is long (346 characters)

    Your meta description is 346 characters; Google truncates after about 160, so the end of your pitch is cut.

  • 2 links crawlers can't follow

    2 links have no real href, so search engines can't follow them.

  • 354 internal links, 28 external

    The homepage links to 354 pages on americanhomewater.com and 28 external pages.

7 checks passed
  • One H1 headline

    Your main headline reads: “Trusted Plumbing & AC Company in Phoenix”.

  • Title: 59 characters

    Your title is a healthy 59 characters: “American Home Water – AC Repair – Water Softeners – Phoenix”.

  • Canonical URL set

    The canonical URL is https://americanhomewater.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, FAQPage, HVACBusiness, ImageObject and Organization.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://americanhomewater.com/sitemap.xml.

AI search readiness

100
4 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Organization data: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (3,619 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://americanhomewater.com/llms.txt (195 KiB, 446 links), a plain-text guide to the site for AI tools.

Other pages

100
  • 9 pages slow to respond

    https://americanhomewater.com/ac-installation, https://americanhomewater.com/ac-repair-phoenix, https://americanhomewater.com/ductless-mini-splits, https://americanhomewater.com/air-conditioning-accessories-parts-phoenix, https://americanhomewater.com/air-duct-cleaning-phoenix and https://americanhomewater.com/phoenix-air-scrubbers and 3 others took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 79 found) and read each the way a search engine does.

7 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

3 to fixGoogle 7385
  • 7 small tap targets

    7 of 17 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 1 third-party cookie

    1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix89
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • About 2,409 words of copy

    The homepage carries about 2,409 words of visible text.

8 checks passed
  • 51 calls to action

    The homepage has 51 calls to action, for example “Drinking Water Pricing”, “Water Treatment Pricing” and “Contact A Water Specialist”.

  • Social proof on the page

    Social proof on the homepage: 12 testimonial or review blocks, a star rating, 2 trust badges and “over 50,000 satisfied customers”.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Cloudflare Web Analytics.

  • Direct contact links

    Visitors can reach you directly: 8 phone links and 0 email links.

  • Opening hours shown

    Your opening hours are on the homepage.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

  • 17 cookies set on arrival

    17

    Opening the homepage sets 17 cookies, 1 of them by other companies (measured from a US location before any click).

  • No consent tool detected

    No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

  • 31 other companies contacted

    Loading the homepage contacts 31 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at americanhomewater.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Analytics | Google Tag Manager
Hosting
Cloudflare

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 44 issues on americanhomewater.com, including 27 speed issues, 2 SEO issues and 1 conversion gap. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25