Website review, no card needed

hughchatham.org logo

hughchatham.org website review

Visit site (opens in a new tab)Reviewed 31 October 202618 issues · 78 checks

This review found 18 issues worth fixing on hughchatham.org, 3 of them high impact, across 78 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
1.5 s1.2 sMay 9Oct 241.2 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.4 s
May 16, 20261.4 s
May 23, 20261.4 s
May 30, 20261.4 s
Jun 6, 20261.4 s
Jun 13, 20261.4 s
Jun 20, 20261.4 s
Jun 27, 20261.4 s
Jul 4, 20261.3 s
Jul 11, 20261.3 s
Jul 18, 20261.3 s
Jul 25, 20261.3 s
Aug 1, 20261.2 s
Aug 8, 20261.2 s
Aug 15, 20261.2 s
Aug 22, 20261.2 s
Aug 29, 20261.3 s
Sep 5, 20261.3 s
Sep 12, 20261.3 s
Sep 19, 20261.4 s
Sep 26, 20261.4 s
Oct 3, 20261.4 s
Oct 10, 20261.3 s
Oct 17, 20261.3 s
Oct 24, 20261.2 s
Real-visitor tap response (INP)75th percentile, phones
71 ms61 msMay 9Oct 2463 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 202668 ms
May 16, 202670 ms
May 23, 202669 ms
May 30, 202666 ms
Jun 6, 202667 ms
Jun 13, 202669 ms
Jun 20, 202670 ms
Jun 27, 202670 ms
Jul 4, 202669 ms
Jul 11, 202667 ms
Jul 18, 202663 ms
Jul 25, 202663 ms
Aug 1, 202662 ms
Aug 8, 202662 ms
Aug 15, 202663 ms
Aug 22, 202664 ms
Aug 29, 202667 ms
Sep 5, 202669 ms
Sep 12, 202668 ms
Sep 19, 202669 ms
Sep 26, 202664 ms
Oct 3, 202664 ms
Oct 10, 202664 ms
Oct 17, 202663 ms
Oct 24, 202663 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 hughchatham.org (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. hughchatham.org at 0.4 s0.4 s
  2. hughchatham.org at 0.8 s0.8 s
  3. hughchatham.org at 1.1 s1.1 s
  4. hughchatham.org at 1.5 s1.5 s
  5. hughchatham.org at 1.9 s1.9 s
  6. hughchatham.org at 2.3 s2.3 s
  7. hughchatham.org at 2.6 s2.6 s
  8. hughchatham.org at 3.0 s3.0 s

Speed

3 to fix87
  • Render-blocking requests

    1.9 s

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

  • Mobile performance score: 87

    87/100

    Your mobile performance score is 87. Pages that score under 90 lose visitors before the first paint.

  • Improve image delivery

    578 KiB

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

  • Reduce unused JavaScript

    220 ms · 23 KiB

    About 23 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 220 ms faster on a phone.

  • Reduce unused CSS

    150 ms · 28 KiB

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

  • 2 long tasks on the main thread

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

  • Font display

    50 ms

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

  • 2 third-party services on the page

    2 third-party services load with your homepage (Google Fonts and FontAwesome CDN), adding 58 KiB and 0 ms of main-thread time.

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

  • Use efficient cache lifetimes

    3 KiB

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

2 checks passed
  • Main-thread work: 0.5 s

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

  • Server response: 33 ms

    33 ms

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

Core Web Vitals

6 to fix100
  • 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: 847 ms

    847 ms

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

  • Largest Contentful Paint: 3.6 s

    3.6 s

    Your largest element takes 3.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Hugh Chatham Health Main Entrance”. Most of its time is element render delay (1.9 s).

  • Speed Index: 4.5 s

    4.5 s

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

  • First Contentful Paint: 1.8 s

    1.8 s

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

  • 1 image without width and height

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

  • Tap response (INP) held steady for real visitors

    -9%

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

8 checks passed
  • Real-user LCP: 1.7 s

    1.7 s

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

  • Real-user INP: 67 ms

    67 ms

    Real visitors wait 67 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.

  • Real-user FCP: 1.5 s

    1.5 s

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

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

    -10%

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

  • Time to Interactive: 3.6 s

    3.6 s

    The page is fully interactive after 3.6 s.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

  • Total Blocking Time: 23 ms

    23 ms

    Scripts block the page for only 23 ms while loading. Good is under 200 ms.

Images and page weight

100
  • 2 images in older formats

    2 images (204 KiB) are 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.

  • About 0.2 g of CO₂ per visit

    0.25 g

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

3 checks passed
  • Page weight: 888 KiB in 37 requests

    888 KiB

    Your homepage downloads 888 KiB in 37 requests on a phone: images 680 KiB (23), scripts 88 KiB (5) and fonts 58 KiB (3). That is a lean page.

  • 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

2 to fixGoogle 9998
  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)

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

  • 2 links without text

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 37 images in the HTML carry an alt attribute.

  • 49 automated accessibility rules passed

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

SEO

3 to fixGoogle 9286
  • Title is short (26 characters)

    Your title is only 26 characters: “Home - Hugh Chatham Health”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 27 links with vague text

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

  • Meta description is long (367 characters)

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

  • 72 internal links, 6 external

    The homepage links to 72 pages on hughchatham.org and 6 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “Home”.

  • Canonical URL set

    The canonical URL is https://hughchatham.org/.

  • Structured data in place

    Structured data found: BreadcrumbList, Organization, WebPage and WebSite.

  • 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://hughchatham.org/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://hughchatham.org/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: 4 of 6 facts

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

  • Text is in the HTML

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

Other pages

1 to fix95
  • 3 pages without a meta description

    https://hughchatham.org/contact, https://hughchatham.org/find-a-service and https://hughchatham.org/find-a-provider have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

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

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

  • 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

Google 100100
3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    21 of 22 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix75
  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

  • 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 1,390 words of copy

    The homepage carries about 1,390 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Request An Appointment”.

  • 9 calls to action

    The homepage has 9 calls to action, for example “Contact”, “Request An Appointment” and “Request appointment”.

  • 2 short forms

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

  • Direct contact links

    Visitors can reach you directly: 1 phone link 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

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

  • 3 other companies contacted

    Loading the homepage contacts 3 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 hughchatham.org, 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
Hosting
Liquid Web

Company

Employees
944
Headquarters
Elkins

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 18 issues on hughchatham.org, including 9 speed issues, 3 SEO issues and 3 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