Website review, no card needed

bmsi.org logo

bmsi.org website review

Visit site (opens in a new tab)Reviewed 29 October 202635 issues · 91 checks

This review found 35 issues worth fixing on bmsi.org, 13 of them high impact, across 91 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
8.2 s3.8 sMay 9Oct 245.0 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20267.2 s
May 16, 20267.6 s
May 23, 20267.7 s
May 30, 20267.5 s
Jun 6, 20267.6 s
Jun 13, 20267.7 s
Jun 20, 20267.3 s
Jun 27, 20267.0 s
Jul 4, 20266.8 s
Jul 11, 20266.3 s
Jul 18, 20265.9 s
Jul 25, 20265.3 s
Aug 1, 20264.5 s
Aug 8, 20264.7 s
Aug 15, 20264.7 s
Aug 22, 20264.4 s
Aug 29, 20264.3 s
Sep 5, 20264.5 s
Sep 12, 20264.7 s
Sep 19, 20264.8 s
Sep 26, 20264.8 s
Oct 3, 20264.9 s
Oct 10, 20264.8 s
Oct 17, 20265.0 s
Oct 24, 20265.0 s
Real-visitor tap response (INP)75th percentile, phones
137 ms94 msMay 9Oct 24111 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 202699 ms
May 16, 2026118 ms
May 23, 2026127 ms
May 30, 2026131 ms
Jun 6, 2026132 ms
Jun 13, 2026125 ms
Jun 20, 2026121 ms
Jun 27, 2026122 ms
Jul 4, 2026122 ms
Jul 11, 2026119 ms
Jul 18, 2026110 ms
Jul 25, 2026111 ms
Aug 1, 2026109 ms
Aug 8, 2026116 ms
Aug 15, 2026119 ms
Aug 22, 2026118 ms
Aug 29, 2026122 ms
Sep 5, 2026117 ms
Sep 12, 2026117 ms
Sep 19, 2026126 ms
Sep 26, 2026121 ms
Oct 3, 2026125 ms
Oct 10, 2026121 ms
Oct 17, 2026114 ms
Oct 24, 2026111 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 bmsi.org (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. bmsi.org at 2.6 s2.6 s
  2. bmsi.org at 5.3 s5.3 s
  3. bmsi.org at 7.9 s7.9 s
  4. bmsi.org at 10.5 s10.5 s
  5. bmsi.org at 13.1 s13.1 s
  6. bmsi.org at 15.8 s15.8 s
  7. bmsi.org at 18.4 s18.4 s
  8. bmsi.org at 21.0 s21.0 s

Speed

11 to fix46
  • Render-blocking requests

    3.0 s

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

  • Mobile performance score: 46

    46/100

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

  • Main-thread work: 5.7 s

    A phone's processor spends 5.7 s on main-thread work while loading, 3.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • Reduce unused JavaScript

    600 ms · 1.4 MB

    About 1.4 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google CDN, YouTube and Google Tag Manager and others), adding 3.1 MB and 1.5 s of main-thread time.

  • Use efficient cache lifetimes

    300 ms · 1.0 MB

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

  • Reduce unused CSS

    300 ms · 208 KiB

    About 208 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.

  • YouTube adds 396 ms

    396 ms

    YouTube costs a phone 396 ms of main-thread work and 991 KiB 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.

  • Google CDN adds 410 ms

    410 ms

    Google CDN costs a phone 410 ms of main-thread work and 742 KiB 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.

  • Google Tag Manager adds 394 ms

    394 ms

    Google Tag Manager costs a phone 394 ms of main-thread work and 668 KiB 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.

  • Facebook adds 275 ms

    275 ms

    Facebook costs a phone 275 ms of main-thread work and 370 KiB 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.

  • 17 long tasks on the main thread

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

  • Font display

    100 ms

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

  • Legacy JavaScript

    47 KiB

    Polyfills for old browsers add 47 KiB JavaScript that modern phones do not need.

  • Improve image delivery

    38 KiB

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

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

  • Minify CSS

    4 KiB

    4 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 3 ms

    3 ms

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

Core Web Vitals

10 to fix67
  • 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 LCP: 6.3 s

    6.3 s

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

  • Real-user FCP: 5.8 s

    5.8 s

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

  • Real-user TTFB: 5.2 s

    5.2 s

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

  • Speed Index: 22.5 s

    22.5 s

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

  • Time to Interactive: 26.3 s

    26.3 s

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

  • Largest Contentful Paint: 6.9 s

    6.9 s

    Your largest element takes 6.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Nurse showing patient charts.”. Most of its time is resource load delay (8.5 s).

  • Total Blocking Time: 699 ms

    699 ms

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

  • First Contentful Paint: 2.4 s

    2.4 s

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

  • 2 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +4%

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

4 checks passed
  • Real-user INP: 103 ms

    103 ms

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

  • Real-user CLS: 0.03

    0.03

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

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

    -32%

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

  • Cumulative Layout Shift: 0.024

    0.024

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

Images and page weight

2 to fix69
  • Page weight: 5.0 MB in 188 requests

    5.0 MB

    Your homepage downloads 5.0 MB in 188 requests on a phone: scripts 3.1 MB (62), images 724 KiB (24) and fonts 396 KiB (16). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    photo_nurse_and_woman-1-768x859.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • 3 images in older formats

    3 images (133 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.

  • 1 image below the first screen load straight away

    1 image further down the page (47 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 1.4 g of CO₂ per visit

    1.40 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.40 g of CO₂e: 168.4 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

6 to fix77
  • Invalid ARIA attributes

    1 element use ARIA attributes their role does not allow, which confuses screen readers.

  • 19 text elements with low contrast

    19 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 4 form fields without a label

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

  • Elements use prohibited ARIA attributes

    Elements use prohibited ARIA attributes (1 element).

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

  • Links look like plain text

    1 link inside paragraphs relies on colour alone to stand out.

  • Headings skip levels

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

1 checks passed
  • Every image has alt text

    All 17 images in the HTML carry an alt attribute.

SEO

1 to fixGoogle 8597
  • No social preview image

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

  • 57 internal links, 18 external

    The homepage links to 57 pages on bmsi.org and 18 external pages.

7 checks passed
  • Meta description: 159 characters

    Your meta description is 159 characters: “Baltimore Medical System is an independent, community healthcare non-profit. The care we provide goes far beyond what y…”.

  • One H1 headline

    Your main headline reads: “Our goal is to provide high quality care to people who need it the most”.

  • Title: 55 characters

    Your title is a healthy 55 characters: “Baltimore Medical System | Quality Community Healthcare”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, LocalBusiness, 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://bmsi.org/news-sitemap.xml.

AI search readiness

100
  • No llms.txt

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

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

  • Text is in the HTML

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

Other pages

100
  • 9 pages slow to respond

    https://bmsi.org/our-centers, https://bmsi.org/for-patients, https://bmsi.org/our-pharmacies, https://bmsi.org/our-programs, https://bmsi.org/who-we-are and https://bmsi.org/who-we-are/donate and 3 others took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

7 checks passed
  • Linked pages load

    11 pages of 15 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 11 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 11 pages that loaded have a <title>.

Best practices

3 to fixGoogle 6985
  • 10 small tap targets

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

  • 5 third-party cookies

    5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Unexpected token ';'”.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix94
  • Thin social proof

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

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

    The homepage carries about 645 words of visible text.

8 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “CONTACT US” and “CLICK HERE TO LEARN MORE”.

  • 6 calls to action

    The homepage has 6 calls to action, for example “Contact Us”, “Call for an Appointment” and “CLICK HERE TO LEARN MORE”.

  • 3 short forms

    3 short forms (2 fields at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Meta Pixel.

  • Direct contact links

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

  • Opening hours shown

    Your opening hours are on the homepage.

  • Phone number on the homepage

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

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and The Trade Desk and 1 more (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.

  • 2 cookies set on arrival

    2

    Opening the homepage sets 2 cookies, 1 of them by other companies (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.

  • 23 other companies contacted

    Loading the homepage contacts 23 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 bmsi.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
Analytics
Google Analytics | Google Tag Manager
Hosting
DigitalOcean

Company

Employees
332

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 35 issues on bmsi.org, including 21 speed issues, 1 SEO issue and 1 conversion gap. 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