Website review, no card needed

communitymed.org logo

communitymed.org website review

Visit site (opens in a new tab)Reviewed 31 October 202632 issues · 86 checks

This review found 32 issues worth fixing on communitymed.org, 8 of them high impact, across 86 checks. The most urgent: improve image delivery. 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.9 s2.0 sMay 9Oct 242.4 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.1 s
May 16, 20262.1 s
May 23, 20262.1 s
May 30, 20262.1 s
Jun 6, 20262.2 s
Jun 13, 20262.2 s
Jun 20, 20262.3 s
Jun 27, 20262.4 s
Jul 4, 20262.4 s
Jul 11, 20262.4 s
Jul 18, 20262.3 s
Jul 25, 20262.4 s
Aug 1, 20262.5 s
Aug 8, 20262.5 s
Aug 15, 20262.5 s
Aug 22, 20262.6 s
Aug 29, 20262.5 s
Sep 5, 20262.4 s
Sep 12, 20262.5 s
Sep 19, 20262.6 s
Sep 26, 20262.7 s
Oct 3, 20262.8 s
Oct 10, 20262.7 s
Oct 17, 20262.5 s
Oct 24, 20262.4 s
Real-visitor tap response (INP)75th percentile, phones
84 ms76 msMay 9Oct 2482 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 202677 ms
May 16, 202677 ms
May 23, 202678 ms
May 30, 202678 ms
Jun 6, 202678 ms
Jun 13, 202678 ms
Jun 20, 202678 ms
Jun 27, 202678 ms
Jul 4, 202678 ms
Jul 11, 202679 ms
Jul 18, 202678 ms
Jul 25, 202679 ms
Aug 1, 202680 ms
Aug 8, 202679 ms
Aug 15, 202679 ms
Aug 22, 202679 ms
Aug 29, 202679 ms
Sep 5, 202681 ms
Sep 12, 202683 ms
Sep 19, 202682 ms
Sep 26, 202683 ms
Oct 3, 202683 ms
Oct 10, 202682 ms
Oct 17, 202681 ms
Oct 24, 202682 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 communitymed.org (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

6 to fix64
  • Improve image delivery

    3.6 s · 1.2 MB

    6 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 3.6 s faster on a phone.

  • Use efficient cache lifetimes

    1.1 s · 220 KiB

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

  • Reduce unused JavaScript

    900 ms · 138 KiB

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

  • Mobile performance score: 64

    64/100

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

  • Render-blocking requests

    950 ms

    5 files block the first paint until they finish downloading. Deferring or inlining them could save about 950 ms.

  • Reduce unused CSS

    300 ms · 88 KiB

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

  • 4 third-party services on the page

    4 third-party services load with your homepage (Google Tag Manager, Optanon and guideforproviders.net and others), adding 525 KiB and 174 ms of main-thread time.

  • Legacy JavaScript

    150 ms · 9 KiB

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

  • Minify JavaScript

    150 ms · 6 KiB

    6 KiB could be saved by minifying JavaScript.

  • Document request latency

    59 KiB

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

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 52 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).

  • Duplicated JavaScript

    7 KiB

    7 KiB JavaScript is shipped twice across bundles.

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

2 checks passed
  • Main-thread work: 0.5 s

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

  • Server response: 24 ms

    24 ms

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

Core Web Vitals

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

  • Largest Contentful Paint: 12.6 s

    12.6 s

    Your largest element takes 12.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “FIND A DOCTOR Find Specialties Schedule Appointment Find Lo…”.

  • Time to Interactive: 12.7 s

    12.7 s

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

  • Speed Index: 7.2 s

    7.2 s

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

  • Real-user FCP: 2.1 s

    2.1 s

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

  • Real-user TTFB: 1.4 s

    1.4 s

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

  • First Contentful Paint: 2.7 s

    2.7 s

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

  • 3 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +6%

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

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

    +18%

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

5 checks passed
  • Real-user LCP: 2.2 s

    2.2 s

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

  • Real-user INP: 87 ms

    87 ms

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

  • Cumulative Layout Shift: 0.052

    0.052

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

  • Total Blocking Time: 2 ms

    2 ms

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

Images and page weight

3 to fix68
  • Page weight: 2.1 MB in 51 requests

    2.1 MB

    Your homepage downloads 2.1 MB in 51 requests on a phone: images 1.4 MB (9), scripts 424 KiB (18) and fonts 150 KiB (5). Under 2 MB keeps phones on slow connections fast.

  • 3 images below the first screen load straight away

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

  • 1 image far larger than shown

    278 KiB

    1 image is downloaded at several times the size a phone draws it, for example communitymed_breastcancerawarenessmonth_2026.jpg at 2,425 px wide, shown at 326 px. Resized copies would save about 278 KiB.

  • 2 images in older formats

    2 images (438 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.6 g of CO₂ per visit

    0.61 g

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

Accessibility

2 to fixGoogle 9598
  • 4 links without text

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

  • 2 form fields without a label

    2 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Headings skip levels

    Headings skip levels (h2 → h5, h1 → h3 and h3 → h5), 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. (1 element).

2 checks passed
  • Every image has alt text

    All 7 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 44 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 2 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 9291
  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • No social preview image

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

  • 5 links with vague text

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

  • No X (Twitter) card tag

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

  • 92 internal links, 4 external

    The homepage links to 92 pages on communitymed.org and 4 external pages.

6 checks passed
  • Meta description: 138 characters

    Your meta description is 138 characters: “Community Medical Center is a leading healthcare system in Western Montana that offers a full range of health care serv…”.

  • One H1 headline

    Your main headline reads: “Welcome to Community Medical Center”.

  • Title: 48 characters

    Your title is a healthy 48 characters: “Community Medical Center | Missoula, MT Hospital”.

  • Canonical URL set

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

  • 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.communitymed.org/sitemap/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.communitymed.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 (508 words), so crawlers that don't run JavaScript still read it.

Other pages

4 to fix73
  • 1 page points its canonical at the homepage

    https://www.communitymed.org/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.

  • 4 pages share 2 titles

    / and https://www.communitymed.org/home all use the title “Community Medical Center | Missoula, MT Hospital”, 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

    https://www.communitymed.org/find-a-doctor/results and https://www.communitymed.org/find-a-doctor have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages without an H1

    https://www.communitymed.org/find-a-doctor/results and https://www.communitymed.org/find-a-doctor have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

3 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • 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

3 to fixGoogle 8185
  • 14 small tap targets

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

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Authorization will not be covered by the wildcard symbol (*) in CORS `Access-Control-Allow-Headers`…”).

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://cdn.prd.guideforproviders.net/v2/css/main.css' from origin 'https://www.communitym…”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix81
  • 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 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 342 words of copy

    The homepage carries about 342 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: “Try our find a doctor search” and “Schedule Appointment”.

  • 8 calls to action

    The homepage has 8 calls to action, for example “Schedule Appointment”, “Try our find a doctor search” and “LEARN MORE”.

  • 1 short form

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

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • 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

  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads Google Tag Manager (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

  • 2 cookies set on arrival

    2

    Opening the homepage sets 2 cookies (measured from a US location before any click).

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

1 checks passed
  • Consent tool: OneTrust

    A consent management tool (OneTrust) loads with the page.

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 communitymed.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
Tailwind CSS
Analytics
Google Tag Manager
Hosting
As11833 Leapfrog Interactive

Company

Founded
1922

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 32 issues on communitymed.org, including 14 speed issues, 3 SEO issues 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