Website review, no card needed

hchcares.org logo

hchcares.org website review

Visit site (opens in a new tab)Reviewed 2 November 202612 issues · 70 checks

This review found 12 issues worth fixing on hchcares.org, 2 of them high impact, across 70 checks. The most urgent: page weight: 5.4 MB in 67 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.0 s807 msMay 16Oct 31985 ms
Show as table
DateReal-visitor load time (LCP)
May 16, 2026830 ms
May 23, 2026856 ms
May 30, 2026870 ms
Jun 6, 2026874 ms
Jun 13, 2026892 ms
Jun 20, 2026879 ms
Jun 27, 2026908 ms
Jul 4, 2026918 ms
Jul 11, 2026918 ms
Jul 18, 2026925 ms
Jul 25, 2026915 ms
Aug 1, 2026915 ms
Aug 8, 2026940 ms
Aug 15, 2026956 ms
Aug 22, 2026963 ms
Aug 29, 2026974 ms
Sep 5, 2026971 ms
Sep 12, 2026968 ms
Sep 19, 2026979 ms
Sep 26, 2026962 ms
Oct 3, 2026965 ms
Oct 10, 2026973 ms
Oct 17, 2026974 ms
Oct 24, 2026981 ms
Oct 31, 2026985 ms
Real-visitor tap response (INP)75th percentile, phones
107 ms98 msMay 16Oct 31104 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026103 ms
May 23, 2026102 ms
May 30, 2026102 ms
Jun 6, 2026102 ms
Jun 13, 2026102 ms
Jun 20, 2026104 ms
Jun 27, 2026104 ms
Jul 4, 2026104 ms
Jul 11, 2026106 ms
Jul 18, 2026102 ms
Jul 25, 2026103 ms
Aug 1, 2026104 ms
Aug 8, 2026104 ms
Aug 15, 2026104 ms
Aug 22, 2026104 ms
Aug 29, 2026103 ms
Sep 5, 2026102 ms
Sep 12, 2026103 ms
Sep 19, 2026103 ms
Sep 26, 2026103 ms
Oct 3, 2026103 ms
Oct 10, 202699 ms
Oct 17, 2026103 ms
Oct 24, 2026103 ms
Oct 31, 2026104 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 hchcares.org (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

1 to fix94
  • Render-blocking requests

    300 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 300 ms.

  • 2 long tasks on the main thread

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

  • 2 third-party services on the page

    2 third-party services load with your homepage (perfalytics.com and CallRail), adding 130 KiB and 114 ms of main-thread time.

  • Use efficient cache lifetimes

    117 KiB

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

  • Improve image delivery

    116 KiB

    1 image could be 116 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Reduce unused JavaScript

    53 KiB

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

  • Reduce unused CSS

    16 KiB

    About 16 KiB of CSS is downloaded but never applied on this page.

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

3 checks passed
  • Mobile performance score: 94

    94/100

    Your mobile performance score is 94. That is in Google's “good” band (90 and up).

  • Main-thread work: 0.8 s

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

  • Server response: 2 ms

    2 ms

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

Core Web Vitals

3 to fix100
  • 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.

  • 17 images without width and height

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

  • Total Blocking Time: 219 ms

    219 ms

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

  • 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 103 ms to 104 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

    +17%

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

10 checks passed
  • Passes Core Web Vitals for real visitors

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

  • Real-user LCP: 1.0 s

    1.0 s

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

  • Real-user INP: 108 ms

    108 ms

    Real visitors wait 108 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: 0.9 s

    0.9 s

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

  • Real-user TTFB: 579 ms

    579 ms

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

  • Time to Interactive: 3.2 s

    3.2 s

    The page is fully interactive after 3.2 s.

  • Cumulative Layout Shift: 0

    0

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

  • First Contentful Paint: 0.9 s

    0.9 s

    The first text or image appears after 0.9 s, inside the 1.8 s “good” threshold.

  • Largest Contentful Paint: 0.9 s

    0.9 s

    Your largest element renders in 0.9 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “From caring staff and state-of-the-art technology, to excep…”.

Images and page weight

3 to fix53
  • Page weight: 5.4 MB in 67 requests

    5.4 MB

    Your homepage downloads 5.4 MB in 67 requests on a phone: media 4.2 MB (1), images 805 KiB (49) and fonts 342 KiB (1). Under 2 MB keeps phones on slow connections fast.

  • 3 images far larger than shown

    86 KiB

    3 images are downloaded at several times the size a phone draws them, for example CompetentciesBlog.jpg at 650 px wide, shown at 164 px. Resized copies would save about 86 KiB.

  • 5 images below the first screen load straight away

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

  • 5 images in older formats

    5 images (331 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 1.5 g of CO₂ per visit

    1.54 g

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

Accessibility

Google 100100
2 checks passed
  • Every image has alt text

    All 51 images in the HTML carry an alt attribute.

  • 42 automated accessibility rules passed

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

SEO

1 to fixGoogle 10097
  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 92 internal links, 15 external

    The homepage links to 92 pages on hchcares.org and 15 external pages.

7 checks passed
  • Meta description: 121 characters

    Your meta description is 121 characters: “From caring staff to outstanding facilities to exceptional care, Henry Community Health focuses on your whole well-bein…”.

  • One H1 headline

    Your main headline reads: “Your community. Your health.”.

  • Title: 30 characters

    Your title is a healthy 30 characters: “Welcome┃Henry Community Health”.

  • Canonical URL set

    The canonical URL is https://www.hchcares.org/.

  • Structured data in place

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

  • 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://www.hchcares.org/sitemap_index.xml.

AI search readiness

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

    Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. 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 https://www.hchcares.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.

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 (475 words), so crawlers that don't run JavaScript still read it.

Other pages

100
  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 61 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

1 to fixGoogle 10093
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

2 checks passed
  • Tap targets are thumb-sized

    19 of 20 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • No analytics detected

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

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

    The homepage carries about 357 words of visible text.

4 checks passed
  • Clear next step on the first screen

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

  • 2 calls to action

    The homepage has 2 calls to action, for example “Schedule an Appointment”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Direct contact links

    Visitors can reach you directly: 3 phone links and 1 email link.

Privacy and tracking

  • 6 cookies set on arrival

    6

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

  • 5 other companies contacted

    Loading the homepage contacts 5 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 hchcares.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
Hosting
WP Engine

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 12 issues on hchcares.org, including 4 speed issues, 1 SEO issue and 2 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