rmchospital.com website review

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

15 images could be 988 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.4 s faster on a phone.

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

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

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

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

3 third-party services load with your homepage (allaccessible.org, Facebook and fasthealth.com), adding 1.1 MB and 80 ms of main-thread time.

fasthealth.com costs a phone 0 ms of main-thread work and 897 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.

23 KiB could be saved by minifying CSS.

16 KiB could be saved by minifying JavaScript.

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

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Your largest element takes 9.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Riverside Medical Center”.

The layout shifts by 1.157 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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

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

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

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

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

4 images are downloaded at several times the size a phone draws them, for example 284927.jpg at 2,560 px wide, shown at 388 px. Resized copies would save about 586 KiB.

Your homepage downloads 2.4 MB in 55 requests on a phone: images 1.7 MB (34), scripts 360 KiB (9) and stylesheets 156 KiB (6). Under 2 MB keeps phones on slow connections fast.

13 images (1.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.

284927.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).

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

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

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

Some lists contain elements other than list items, which screen readers announce wrongly.

1 element hidden from screen readers can still receive keyboard focus.

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

All page content should be contained by landmarks: 24 elements on the page fail this check, rated moderate by axe-core.

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

Elements marked as presentational should be consistently ignored: 9 elements on the page fail this check, rated minor by axe-core.

Your title is only 24 characters: “Riverside Medical Center”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 4 <h1> headlines (“Welcome to Riverside Medical Center”, “View Events” and “Patients & Visitors”). One clear main headline is easier for people and search engines.

No XML sitemap at https://www.rmchospital.com/sitemap.xml, so Google discovers your pages only by following links.

The homepage links to 73 pages on rmchospital.com and 11 external pages.

There is no https://www.rmchospital.com/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.

Your homepage links to https://www.rmchospital.com/getpage.php, which answers with an error. Visitors hit a dead end and search engines drop it.

/, https://www.rmchospital.com/ecard and https://www.rmchospital.com/staff/bio.php all use the title “Riverside Medical Center”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.rmchospital.com/calendar, https://www.rmchospital.com/ecard and https://www.rmchospital.com/staff/bio.php have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://www.rmchospital.com/calendar, whose canonical is https://www.rmchospital.com/calendar/index.php?category=0. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

We fetched 4 pages linked from your homepage and read each the way a search engine does.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 401 ()”.

8 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

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

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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 analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 447 words of visible text.

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

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

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.

Loading the homepage contacts 4 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.