Website review, no card needed

adclinic.com logo

adclinic.com website review

Visit site (opens in a new tab)Reviewed 2 November 202640 issues · 88 checks

This review found 40 issues worth fixing on adclinic.com, 17 of them high impact, across 88 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
2.1 s2.0 sMay 16Oct 312.1 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.1 s
May 23, 20262.1 s
May 30, 20262.1 s
Jun 6, 20262.1 s
Jun 13, 20262.1 s
Jun 20, 20262.1 s
Jun 27, 20262.1 s
Jul 4, 20262.1 s
Jul 11, 20262.1 s
Jul 18, 20262.1 s
Jul 25, 20262.0 s
Aug 1, 20262.0 s
Aug 8, 20262.1 s
Aug 15, 20262.1 s
Aug 22, 20262.1 s
Aug 29, 20262.1 s
Sep 5, 20262.1 s
Sep 12, 20262.1 s
Sep 19, 20262.1 s
Sep 26, 20262.1 s
Oct 3, 20262.1 s
Oct 10, 20262.1 s
Oct 17, 20262.1 s
Oct 24, 20262.1 s
Oct 31, 20262.1 s
Real-visitor tap response (INP)75th percentile, phones
88 ms80 msMay 16Oct 3183 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202683 ms
May 23, 202684 ms
May 30, 202685 ms
Jun 6, 202685 ms
Jun 13, 202684 ms
Jun 20, 202683 ms
Jun 27, 202682 ms
Jul 4, 202684 ms
Jul 11, 202682 ms
Jul 18, 202681 ms
Jul 25, 202685 ms
Aug 1, 202683 ms
Aug 8, 202684 ms
Aug 15, 202687 ms
Aug 22, 202685 ms
Aug 29, 202684 ms
Sep 5, 202685 ms
Sep 12, 202682 ms
Sep 19, 202683 ms
Sep 26, 202684 ms
Oct 3, 202684 ms
Oct 10, 202684 ms
Oct 17, 202685 ms
Oct 24, 202685 ms
Oct 31, 202683 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 adclinic.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. adclinic.com at 0.7 s0.7 s
  2. adclinic.com at 1.3 s1.3 s
  3. adclinic.com at 2.0 s2.0 s
  4. adclinic.com at 2.7 s2.7 s
  5. adclinic.com at 3.3 s3.3 s
  6. adclinic.com at 4.0 s4.0 s
  7. adclinic.com at 4.7 s4.7 s
  8. adclinic.com at 5.4 s5.4 s

Speed

11 to fix28
  • Render-blocking requests

    5.5 s

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

  • Reduce unused JavaScript

    3.3 s · 668 KiB

    About 668 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.3 s faster on a phone.

  • Reduce unused CSS

    3.0 s · 489 KiB

    About 489 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 3.0 s faster on a phone.

  • Use efficient cache lifetimes

    2.7 s · 494 KiB

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

  • Mobile performance score: 28

    28/100

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

  • 3 third-party services on the page

    3 third-party services load with your homepage (ehc.com, Bing Ads and securiti.ai), adding 3.9 MB and 518 ms of main-thread time.

  • Legacy JavaScript

    600 ms · 77 KiB

    Polyfills for old browsers add 77 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 600 ms faster on a phone.

  • Minify CSS

    600 ms · 46 KiB

    46 KiB could be saved by minifying CSS.

  • ehc.com adds 305 ms

    305 ms

    ehc.com costs a phone 305 ms of main-thread work and 2.8 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.

  • Font display

    300 ms

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

  • Bing Ads adds 156 ms

    156 ms

    Bing Ads costs a phone 156 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.

  • Improve image delivery

    200 ms · 50 KiB

    3 images could be 50 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.

  • 5 long tasks on the main thread

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

  • Document request latency

    104 KiB

    The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

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

2 checks passed
  • Main-thread work: 1.7 s

    A phone's processor spends 1.7 s on main-thread work while loading, 1.1 s of it running JavaScript. That is comfortably low.

  • Server response: 383 ms

    383 ms

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

Core Web Vitals

12 to fix33
  • 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 CLS: 0.78

    0.78

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

  • Largest Contentful Paint: 21.3 s

    21.3 s

    Your largest element takes 21.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Please be advised that Pediatric Extended Care (ECC) will b…”.

  • Time to Interactive: 21.3 s

    21.3 s

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

  • First Contentful Paint: 6.5 s

    6.5 s

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

  • Speed Index: 11.2 s

    11.2 s

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

  • Cumulative Layout Shift: 0.577

    0.577

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

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

  • Real-user FCP: 2.2 s

    2.2 s

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

  • Real-user TTFB: 1.3 s

    1.3 s

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

  • Total Blocking Time: 278 ms

    278 ms

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

  • 9 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +1%

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

  • Largest content (LCP) held steady for real visitors

    +1%

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

1 checks passed
  • Real-user INP: 85 ms

    85 ms

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

Images and page weight

1 to fix70
  • Page weight: 4.3 MB in 133 requests

    4.3 MB

    Your homepage downloads 4.3 MB in 133 requests on a phone: fonts 1.4 MB (8), scripts 1.2 MB (25) and other files 683 KiB (57). Under 2 MB keeps phones on slow connections fast.

  • 1 image in older formats

    1 image (32 KiB) is JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

  • 2 images below the first screen load straight away

    2 images further down the page (55 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 1.2 g of CO₂ per visit

    1.20 g

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

1 checks passed
  • Images are sized for phones

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

Accessibility

5 to fixGoogle 9394
  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Positive tabindex

    1 element has a tabindex above 0, which scrambles the keyboard order.

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

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

  • Document should not have more than one banner landmark (1 element)

    Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

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

  • Headings skip levels

    Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.

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

    Elements with visible text labels do not have matching accessible names. (2 elements).

2 checks passed
  • Every image has alt text

    All 16 images in the HTML carry an alt attribute.

  • 50 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 6 failed. 3 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 (221 characters)

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

  • 6 links with vague text

    6 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 127 internal links, 10 external

    The homepage links to 127 pages on adclinic.com and 10 external pages.

7 checks passed
  • One H1 headline

    Your main headline reads: “About Austin Diagnostic Clinic”.

  • Title: 31 characters

    Your title is a healthy 31 characters: “Home | Austin Diagnostic Clinic”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: MedicalOrganization.

  • 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://adclinic.com/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://adclinic.com/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.

3 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 description; contact details would complete it.

  • Text is in the HTML

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

Other pages

3 to fix78
  • 1 page points its canonical at the homepage

    https://adclinic.com/home declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

  • 2 pages share a title

    / and https://adclinic.com/home all use the title “Home | Austin Diagnostic Clinic”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 11 pages without a meta description

    https://adclinic.com/patient-center/patient-portal.dot, https://adclinic.com/epay, https://adclinic.com/about/newsroom, https://adclinic.com/physicians, https://adclinic.com/patient-center and https://adclinic.com/patient-center/adc-celebrates-70th-anniversary.dot and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 7 pages slow to respond

    https://adclinic.com/home, https://adclinic.com/patient-center, https://adclinic.com/patient-center/adc-celebrates-70th-anniversary.dot, https://adclinic.com/patient-center/rsv-symptoms-treatment-and-prevention.dot, https://adclinic.com/patient-center/medicare-annual-wellness-visits.dot and https://adclinic.com/blog and 1 other took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

4 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • 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 9687
  • 11 small tap targets

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

  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Uncaught ReferenceError: hcaAnalyticsApiContextObj is not defined”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix69
  • 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.

  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • Thin social proof

    Social proof on the homepage: 12 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • No opening hours

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

  • 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 971 words of copy

    The homepage carries about 971 words of visible text.

4 checks passed
  • 5 calls to action

    The homepage has 5 calls to action, for example “Contact Us”, “Learn more” and “Book now”.

  • 5 short forms

    5 short forms (1 field at most) are right on the homepage.

  • Direct contact links

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

  • Phone number on the homepage

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

Privacy and tracking

  • 13 cookies set on arrival

    13

    Opening the homepage sets 13 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.

  • 6 other companies contacted

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

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 adclinic.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
jQuery
Hosting
Columbia Hca

Company

Founded
1952

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 40 issues on adclinic.com, including 23 speed issues, 2 SEO issues and 4 conversion gaps. 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