Website review, no card needed

sihf.org logo

sihf.org website review

Visit site (opens in a new tab)Reviewed 19 November 202631 issues · 82 checks

This review found 31 issues worth fixing on sihf.org, 8 of them high impact, across 82 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.4 s1.2 sMay 30Nov 141.2 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20261.3 s
Jun 6, 20261.3 s
Jun 13, 20261.3 s
Jun 20, 20261.2 s
Jun 27, 20261.2 s
Jul 4, 20261.3 s
Jul 11, 20261.3 s
Jul 18, 20261.3 s
Jul 25, 20261.2 s
Aug 1, 20261.2 s
Aug 8, 20261.2 s
Aug 15, 20261.3 s
Aug 22, 20261.3 s
Aug 29, 20261.3 s
Sep 5, 20261.3 s
Sep 12, 20261.3 s
Sep 19, 20261.2 s
Sep 26, 20261.3 s
Oct 3, 20261.2 s
Oct 10, 20261.2 s
Oct 17, 20261.2 s
Oct 24, 20261.2 s
Oct 31, 20261.2 s
Nov 7, 20261.2 s
Nov 14, 20261.2 s
Real-visitor tap response (INP)75th percentile, phones
76 ms65 msMay 30Nov 1469 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 202672 ms
Jun 6, 202671 ms
Jun 13, 202671 ms
Jun 20, 202670 ms
Jun 27, 202670 ms
Jul 4, 202670 ms
Jul 11, 202670 ms
Jul 18, 202671 ms
Jul 25, 202672 ms
Aug 1, 202672 ms
Aug 8, 202675 ms
Aug 15, 202674 ms
Aug 22, 202672 ms
Aug 29, 202674 ms
Sep 5, 202672 ms
Sep 12, 202671 ms
Sep 19, 202670 ms
Sep 26, 202670 ms
Oct 3, 202669 ms
Oct 10, 202669 ms
Oct 17, 202669 ms
Oct 24, 202668 ms
Oct 31, 202667 ms
Nov 7, 202666 ms
Nov 14, 202669 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 sihf.org (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. sihf.org at 0.6 s0.6 s
  2. sihf.org at 1.3 s1.3 s
  3. sihf.org at 1.9 s1.9 s
  4. sihf.org at 2.5 s2.5 s
  5. sihf.org at 3.1 s3.1 s
  6. sihf.org at 3.8 s3.8 s
  7. sihf.org at 4.4 s4.4 s
  8. sihf.org at 5.0 s5.0 s

Speed

4 to fix72
  • Render-blocking requests

    1.5 s

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

  • Use efficient cache lifetimes

    950 ms · 1.4 MB

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

  • Improve image delivery

    600 ms · 1.2 MB

    11 images could be 1.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 600 ms faster on a phone.

  • Mobile performance score: 72

    72/100

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

  • Reduce unused CSS

    110 ms · 15 KiB

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

  • 5 third-party services on the page

    5 third-party services load with your homepage (Cloudflare CDN, Mixpanel and StackAdapt and others), adding 205 KiB and 74 ms of main-thread time.

  • Font display

    50 ms

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

  • 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: 0.3 s

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

  • Server response: 1 ms

    1 ms

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

Core Web Vitals

5 to fix100
  • Speed Index: 8.4 s

    8.4 s

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

  • 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 image. Most of its time is element render delay (4.3 s).

  • Time to Interactive: 5.1 s

    5.1 s

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

  • 18 images without width and height

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

  • First Contentful Paint: 2.0 s

    2.0 s

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

  • Tap response (INP) held steady for real visitors

    -6%

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

  • Largest content (LCP) held steady for real visitors

    -3%

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

8 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.3 s

    1.3 s

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

  • Real-user INP: 83 ms

    83 ms

    Real visitors wait 83 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.3 s

    1.3 s

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

  • Real-user TTFB: 575 ms

    575 ms

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

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 0 ms

    0 ms

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

Images and page weight

4 to fix48
  • 1 image over 500 KB

    705-1664976130.png weighs 595 KiB. On a phone connection a single image that size takes seconds.

  • 2 images far larger than shown

    586 KiB

    2 images are downloaded at several times the size a phone draws them, for example 705-1664976130.png at 1,200 px wide, shown at 120 px. Resized copies would save about 586 KiB.

  • 11 images in older formats

    11 images (1.4 MB) 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.

  • 9 images below the first screen load straight away

    9 images further down the page (1.2 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 0.5 g of CO₂ per visit

    0.47 g

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

1 checks passed
  • Page weight: 1.7 MB in 54 requests

    1.7 MB

    Your homepage downloads 1.7 MB in 54 requests on a phone: images 1.4 MB (18), scripts 114 KiB (12) and stylesheets 59 KiB (16). That is a lean page.

Accessibility

6 to fixGoogle 9590
  • Form elements should have a visible label (6 elements)

    Form elements should have a visible label: 6 elements on the page fail this check, rated serious by axe-core.

  • Hidden but focusable

    2 elements hidden from screen readers can still receive keyboard focus.

  • 2 images without alt text

    2 images have no alt text, which hurts accessibility and image search.

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

    All page content should be contained by landmarks: 14 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.

  • 2 links without text

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

1 checks passed
  • 40 automated accessibility rules passed

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

SEO

4 to fixGoogle 10081
  • Title is short (15 characters)

    Your title is only 15 characters: “SIHF Healthcare”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • One H1 headline

    Your <h1> is empty.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 76 internal links, 9 external

    The homepage links to 76 pages on sihf.org and 9 external pages.

4 checks passed
  • Meta description: 150 characters

    Your meta description is 150 characters: “SIHF Healthcare in Southern Illinois is changing the face of healthcare by welcoming you and your loved ones with open …”.

  • Structured data in place

    Structured data found: Hospital.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.sihf.org/sitemap.xml.

AI search readiness

1 to fix88
  • No Organization structured data

    There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

  • No llms.txt

    There is no https://www.sihf.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 (596 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix98
  • 2 pages share a meta description

    https://www.sihf.org/patient-care-services/cardiology and https://www.sihf.org/patient-care-services/cardiology/pediatric-cardiology use the same meta description. A description written for each page earns more clicks.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 54 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 9297
  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

  • 3 low-resolution images

    3 images are served at too low a resolution for sharp phone screens.

3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

    77 of 84 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix75
  • 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 phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • Thin social proof

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

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

    The homepage carries about 337 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: “HEALTHY START” and “CHILD & ADOLESCENT VACCINATION SCHEDULE”.

  • 7 calls to action

    The homepage has 7 calls to action, for example “Healthy Start”, “Child & Adolescent Vaccination Schedule” and “Adult Vaccination Schedule”.

  • 3 short forms

    3 short forms (4 fields at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Mixpanel.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads Mixpanel (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.

  • 4 cookies set on arrival

    4

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

  • 7 other companies contacted

    Loading the homepage contacts 7 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 sihf.org, 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
Analytics
Google Analytics | Google Tag Manager | Mixpanel
Hosting
AWS

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 31 issues on sihf.org, including 9 speed issues, 4 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