Website review, no card needed

aquadocinc.com logo

aquadocinc.com website review

Visit site (opens in a new tab)Reviewed 25 October 202642 issues · 108 checks

This review found 42 issues worth fixing on aquadocinc.com, 11 of them high impact, across 108 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
3.5 s2.1 sMay 2Oct 173.3 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.3 s
May 9, 20262.4 s
May 16, 20262.4 s
May 23, 20262.4 s
May 30, 20262.4 s
Jun 6, 20262.4 s
Jun 13, 20262.3 s
Jun 20, 20262.2 s
Jun 27, 20262.3 s
Jul 4, 20262.3 s
Jul 11, 20262.4 s
Jul 18, 20262.5 s
Jul 25, 20262.5 s
Aug 1, 20262.5 s
Aug 8, 20262.5 s
Aug 15, 20262.5 s
Aug 22, 20262.5 s
Aug 29, 20262.6 s
Sep 5, 20262.5 s
Sep 12, 20262.6 s
Sep 19, 20262.9 s
Sep 26, 20263.0 s
Oct 3, 20263.1 s
Oct 10, 20263.3 s
Oct 17, 20263.3 s
Real-visitor tap response (INP)75th percentile, phones
152 ms98 msMay 2Oct 17133 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026105 ms
May 9, 2026111 ms
May 16, 2026108 ms
May 23, 2026110 ms
May 30, 2026111 ms
Jun 6, 2026104 ms
Jun 13, 2026109 ms
Jun 20, 2026105 ms
Jun 27, 2026107 ms
Jul 4, 2026112 ms
Jul 11, 2026112 ms
Jul 18, 2026115 ms
Jul 25, 2026113 ms
Aug 1, 2026114 ms
Aug 8, 2026113 ms
Aug 15, 2026112 ms
Aug 22, 2026114 ms
Aug 29, 2026114 ms
Sep 5, 2026119 ms
Sep 12, 2026129 ms
Sep 19, 2026137 ms
Sep 26, 2026146 ms
Oct 3, 2026141 ms
Oct 10, 2026137 ms
Oct 17, 2026133 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

Live view · interaction off

Speed

9 to fix48
  • Render-blocking requests

    3.3 s

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

  • Use efficient cache lifetimes

    1.2 s · 814 KiB

    38 files are served with short cache lifetimes, so returning visitors download them again (814 KiB).

  • Mobile performance score: 48

    48/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and Google CDN and others), adding 1.4 MB and 1.1 s of main-thread time.

  • Reduce unused CSS

    750 ms · 153 KiB

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

  • Reduce unused JavaScript

    817 KiB

    About 817 KiB of JavaScript is downloaded but never used on this page.

  • Google Tag Manager adds 633 ms

    633 ms

    Google Tag Manager costs a phone 633 ms of main-thread work and 1.0 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.

  • Facebook adds 370 ms

    370 ms

    Facebook costs a phone 370 ms of main-thread work and 253 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.

  • Main-thread work: 2.6 s

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

  • 13 long tasks on the main thread

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

  • Improve image delivery

    136 KiB

    2 images could be 136 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Font display

    50 ms

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

  • Legacy JavaScript

    30 KiB

    Polyfills for old browsers add 30 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: 23 ms

    23 ms

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

Core Web Vitals

13 to fix50
  • 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 TTFB: 2.5 s

    2.5 s

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

  • Time to Interactive: 17.9 s

    17.9 s

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

  • Speed Index: 7.7 s

    7.7 s

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

  • First Contentful Paint: 3.9 s

    3.9 s

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

  • Largest Contentful Paint: 4.9 s

    4.9 s

    Your largest element takes 4.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Working Full Time on Lake & Pond Management. So you don’t h…”. Most of its time is element render delay (3.2 s).

  • Real-user LCP: 3.0 s

    3.0 s

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

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

    +25%

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

  • Largest content (LCP) got 41% slower for real visitors

    +41%

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

  • Real-user FCP: 2.9 s

    2.9 s

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

  • Total Blocking Time: 579 ms

    579 ms

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

  • Cumulative Layout Shift: 0.123

    0.123

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

  • 8 images without width and height

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

1 checks passed
  • Real-user CLS: 0.05

    0.05

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

Images and page weight

2 to fix81
  • Page weight: 2.6 MB in 95 requests

    2.6 MB

    Your homepage downloads 2.6 MB in 95 requests on a phone: scripts 1.8 MB (34), images 376 KiB (18) and fonts 255 KiB (7). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    AquaDocLogo.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • About 0.7 g of CO₂ per visit

    0.74 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

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

Accessibility

4 to fixGoogle 9294
  • 16 tap targets too small

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

  • 4 text elements with low contrast

    4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • Headings skip levels

    Headings skip levels (h1 → h3, h1 → h3 and h1 → h3), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 17 images in the HTML carry an alt attribute.

  • 48 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 5 failed. 4 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
  • 6 H1 headlines

    There are 6 <h1> headlines (“Services & Solutions”, “See The Change in Effective Water Management” and “Visit the Pond Shoppe”). One clear main headline is easier for people and search engines.

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • 186 internal links, 12 external

    The homepage links to 186 pages on aquadocinc.com and 12 external pages.

7 checks passed
  • Meta description: 152 characters

    Your meta description is 152 characters: “Tired of your lake or pond looking like a swamp? Get professional lake and pond management solutions for your water fro…”.

  • Title: 48 characters

    Your title is a healthy 48 characters: “AQUA DOC - The Experts In Lake & Pond Management”.

  • Canonical URL set

    The canonical URL is https://www.aquadocinc.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, ImageObject, ProfessionalService, Store and WebPage.

  • 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.

  • XML sitemap found

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

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing url, logo and sameAs (social profiles). These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • No llms.txt

    There is no /llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

2 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.

  • Text is in the HTML

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

Other pages

3 to fix86
  • 7 pages share 2 titles

    /, /carolina-services, /georgia-pond-management-2, /pennsylvania-pond-management and /virginia-pond-management all use the title “AQUA DOC - The Experts In Lake & Pond Management”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 2 pages without a meta description

    /category/locations and /lake-monitoring-services have no meta description, so Google writes the search snippet from whatever text it finds.

  • 6 pages share a meta description

    /services/lake-pond-management and /services/commercial-management-lake-pond-management use the same meta description. A description written for each page earns more clicks.

  • 4 pages slow to respond

    /carolina-services, /pennsylvania-pond-management, /about-our-company/awards-and-accolades and /services/project-gallery took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

5 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 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

2 to fixGoogle 9287
  • 8 small tap targets

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

  • 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”.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Security and trust

3 to fix79
  • 1 broken external link

    1 link to other sites is dead, for example https://www.topratedlocal.com/aqua-doc-reviews (404).

  • No HSTS header

    No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

  • No Content-Security-Policy

    No Content-Security-Policy header, the main browser-side defence against injected scripts.

  • No clickjacking protection

    Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

  • No X-Content-Type-Options

    X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

  • 1 link through redirect chains

    1 link go through two or more redirects, for example https://g.page/r/CWlxQg98kCNAEB0/review.

  • No Referrer-Policy

    No Referrer-Policy header, so full URLs can leak to the sites you link to.

  • No Permissions-Policy

    No Permissions-Policy header to switch off camera, microphone and location for embedded content.

  • No security.txt

    There is no /.well-known/security.txt telling researchers how to report a security problem to you.

4 checks passed
  • Served over HTTPS

    The homepage is served over HTTPS (aquadocinc.com).

  • Valid certificate (44 days left)

    The certificate from Let's Encrypt · YR1 verifies for aquadocinc.com and is valid for another 44 days.

  • http:// redirects to https

    http://aquadocinc.com redirects to the secure version.

  • HTTP/2

    The server speaks HTTP/2, so browsers load many files over one connection.

Domain and trust

  • No CAA record

    aquadocinc.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

  • DNSSEC is off

    aquadocinc.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

2 checks passed
  • Domain is 25 years old

    25 years

    aquadocinc.com was registered in Jul 2001 through Domain.com - Network Solutions, LLC. An established domain carries more trust with email providers and search engines.

  • Registered until Jul 2027

    aquadocinc.com is registered until Jul 2027.

Content and conversion

1 to fix93
  • Thin social proof

    Social proof on the homepage: 16 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • No risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

  • About 2,036 words of copy

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

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “LEARN MORE”.

  • 4 calls to action

    The homepage has 4 calls to action, for example “Contact Us”, “learn more” and “Subscribe”.

  • 2 short forms

    2 short forms (4 fields at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

  • Phone number on the homepage

    Your phone number is on the homepage.

  • 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.

Email authentication

1 to fix75
  • DMARC is monitor-only (p=none)

    DMARC is set to p=none, so mail pretending to be aquadocinc.com is still delivered. Reports are on, so moving to quarantine is the next step.

  • Email authentication score: 75/100

    Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

2 checks passed
  • SPF with a strict ending (-all)

    An SPF record lists your sending servers and tells receivers to reject anything else: “v=spf1 include:spf.protection.outlook.com include:gateway.encrypttitan.io -all”.

  • DKIM signing found

    A DKIM key is published (selector “selector1”), so receivers can verify mail really came from you.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight 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.

  • 23 cookies set on arrival

    23

    Opening the homepage sets 23 cookies (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.

  • 23 other companies contacted

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

Upkeep, stack and company

  • 1 plugin is behind its latest release.woocommerce-google-adwords-conversion-tracking-tag 1.64.0 → 1.71.0

Stack

CMS
WordPress 7.1.3
Framework
jQuery
E-commerce
WooCommerce
Analytics
Google Analytics | Google Tag Manager

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 42 issues on aquadocinc.com, including 22 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