Website review, no card needed
monroehospital.com website review
Visit site (opens in a new tab)Reviewed 29 October 202634 issues · 82 checks
This review found 34 issues worth fixing on monroehospital.com, 17 of them high impact, across 82 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
78CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 2.7 s |
| May 16, 2026 | 2.6 s |
| May 23, 2026 | 2.7 s |
| May 30, 2026 | 2.8 s |
| Jun 6, 2026 | 3.1 s |
| Jun 13, 2026 | 3.4 s |
| Jun 20, 2026 | 3.6 s |
| Jun 27, 2026 | 3.7 s |
| Jul 4, 2026 | 3.7 s |
| Jul 11, 2026 | 3.5 s |
| Jul 18, 2026 | 3.3 s |
| Jul 25, 2026 | 3.0 s |
| Aug 1, 2026 | 2.9 s |
| Aug 8, 2026 | 2.8 s |
| Aug 15, 2026 | 2.9 s |
| Aug 22, 2026 | 3.2 s |
| Aug 29, 2026 | 3.4 s |
| Sep 5, 2026 | 3.8 s |
| Sep 12, 2026 | 4.3 s |
| Sep 19, 2026 | 4.3 s |
| Sep 26, 2026 | 4.4 s |
| Oct 3, 2026 | 4.4 s |
| Oct 10, 2026 | 4.2 s |
| Oct 17, 2026 | 4.1 s |
| Oct 24, 2026 | 3.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 203 ms |
| May 16, 2026 | 239 ms |
| May 23, 2026 | 267 ms |
| May 30, 2026 | 262 ms |
| Jun 6, 2026 | 171 ms |
| Jun 13, 2026 | 142 ms |
| Jun 20, 2026 | 120 ms |
| Jun 27, 2026 | 137 ms |
| Jul 4, 2026 | 135 ms |
| Jul 11, 2026 | 126 ms |
| Jul 18, 2026 | 111 ms |
| Jul 25, 2026 | 103 ms |
| Aug 1, 2026 | 105 ms |
| Aug 8, 2026 | 136 ms |
| Aug 15, 2026 | 137 ms |
| Aug 22, 2026 | 147 ms |
| Aug 29, 2026 | 135 ms |
| Sep 5, 2026 | 108 ms |
| Sep 12, 2026 | 94 ms |
| Sep 19, 2026 | 88 ms |
| Sep 26, 2026 | 88 ms |
| Oct 3, 2026 | 87 ms |
| Oct 10, 2026 | 86 ms |
| Oct 17, 2026 | 87 ms |
| Oct 24, 2026 | 86 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
How it loaded on a phone
0.5 s
1.0 s
1.5 s
2.0 s
2.5 s
3.0 s
3.5 s
4.1 s
Speed
Use efficient cache lifetimes
4.3 s · 9.1 MB99 files are served with short cache lifetimes, so returning visitors download them again (9.1 MB).
Improve image delivery
2.9 s · 3.6 MB17 images could be 3.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.9 s faster on a phone.
Render-blocking requests
2.5 s28 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.5 s.
Reduce unused JavaScript
900 ms · 160 KiBAbout 160 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: 59
59/100Your mobile performance score is 59. Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
300 ms · 84 KiBAbout 84 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.
Legacy JavaScript
200 ms · 18 KiBPolyfills for old browsers add 18 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.
Font display
200 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 200 ms).
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 164 ms. During a long task the page ignores taps.
Minify CSS
150 ms · 5 KiB5 KiB could be saved by minifying CSS.
6 third-party services on the page
6 third-party services load with your homepage (steerhealth.io, userway.org and trustindex.io and others), adding 481 KiB and 72 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.
2 checks passed
Main-thread work: 1.5 s
A phone's processor spends 1.5 s on main-thread work while loading, 378 ms of it running JavaScript. That is comfortably low.
Server response: 58 ms
58 msYour server sent the HTML in 58 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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: 5.0 s
5.0 sReal visitors wait 5.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 3.3 s
3.3 sReal visitors see the first content after 3.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 2.9 s
2.9 sReal visitors wait 2.9 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 31.4 s
31.4 sYour largest element takes 31.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “FastTrackCareReserve Your ER Arrival…”.
Time to Interactive: 33.1 s
33.1 sThe page becomes fully interactive after 33.1 s. Good is under 3.8 s.
Speed Index: 12.4 s
12.4 sVisually, the page fills in at 12.4 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.2 s
3.2 sThe first text or image appears after 3.2 s on a phone. Good is under 1.8 s.
Largest content (LCP) got 52% slower for real visitors
+52%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.7 s to 3.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
16 images without width and height
16 images have no width and height attributes, so the layout jumps as each one loads.
5 checks passed
Real-user INP: 84 ms
84 msReal visitors wait 84 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Tap response (INP) got 61% faster for real visitors
-61%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 203 ms to 86 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 124 ms
124 msScripts block the page for only 124 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 23.0 MB in 122 requests
23.0 MBYour homepage downloads 23.0 MB in 122 requests on a phone: media 13.9 MB (4), images 8.2 MB (44) and scripts 465 KiB (34). Under 2 MB keeps phones on slow connections fast.
5 images over 500 KB
5 images weigh 5.3 MB together. On a phone connection a single image that size takes seconds.
9 images far larger than shown
2.4 MB9 images are downloaded at several times the size a phone draws them, for example VAS5STAR.jpg at 1,800 px wide, shown at 116 px. Resized copies would save about 2.4 MB.
17 images in older formats
17 images (7.2 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.
13 images below the first screen load straight away
13 images further down the page (3.0 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 6.5 g of CO₂ per visit
6.53 gBy the Sustainable Web Design model, a visit to your homepage emits about 6.53 g of CO₂e: 783.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
4 text elements with low contrast
4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
3 tap targets too small
3 tap targets are too small or too close together to hit reliably with a finger.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
2 checks passed
Every image has alt text
All 95 images in the HTML carry an alt attribute.
50 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 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
7 H1 headlines
There are 7 <h1> headlines (“FastTrackCare”, “Fast ER Care!” and “Care begins with a safe place”). One clear main headline is easier for people and search engines.
24 links with vague text
24 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
Structured data has 1 problem
Structured data found (AboutPage, Hospital, ImageObject and MedicalClinic) but with 1 problem, for example “WebSite: missing name”.
2 links crawlers can't follow
2 links have no real href, so search engines can't follow them.
102 internal links, 20 external
The homepage links to 102 pages on monroehospital.com and 20 external pages.
6 checks passed
Meta description: 139 characters
Your meta description is 139 characters: “Monroe Hospital in Bloomington, IN provides award-winning emergency care, diagnostic imaging, wound management, and mor…”.
Title: 46 characters
Your title is a healthy 46 characters: “Trusted Bloomington Hospital | Monroe Hospital”.
Canonical URL set
The canonical URL is https://monroehospital.com/.
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://monroehospital.com/sitemap_index.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing logo, sameAs (social profiles) and description. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
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 (1,476 words), so crawlers that don't run JavaScript still read it.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 43 found) and read each the way a search engine does.
7 checks passed
Linked pages load
1 page 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 1 page 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 1 page that loaded have a <title>.
Best practices
5 small tap targets
5 of 22 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
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 distorted images
2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
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 1,024 words of copy
The homepage carries about 1,024 words of visible text.
7 checks passed
23 calls to action
The homepage has 23 calls to action, for example “Learn More”, “Contact Us” and “Call Us”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 32 testimonial or review blocks and 59 trust badges.
Direct contact links
Visitors can reach you directly: 2 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
3 cookies set on arrival
3Opening the homepage sets 3 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.
9 other companies contacted
Loading the homepage contacts 9 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 monroehospital.com, 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
- Sucuri
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 34 issues on monroehospital.com, including 16 speed issues, 4 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.