lrhc.org website review

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

17 images could be 2.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 5.8 s faster on a phone.

About 921 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.9 s faster on a phone.

About 732 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 3.8 s faster on a phone.

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

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

5 third-party services load with your homepage (Google Tag Manager, siteassist.biz and Google Fonts and others), adding 4.6 MB and 413 ms of main-thread time.

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

Cloudinary costs a phone 0 ms of main-thread work and 2.8 MB 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.

siteassist.biz costs a phone 10 ms of main-thread work and 1.4 MB 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.

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

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

6 KiB could be saved by minifying CSS.

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 28.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

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

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

3 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 94 ms to 104 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.4 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 6.5 MB in 46 requests on a phone: images 2.8 MB (18), scripts 1.5 MB (13) and fonts 1.3 MB (5). Under 2 MB keeps phones on slow connections fast.

2 images weigh 1.6 MB together. On a phone connection a single image that size takes seconds.

6 images are downloaded at several times the size a phone draws them, for example fullmer-joseph-cr.png at 2,539 px wide, shown at 274 px. Resized copies would save about 1.8 MB.

6 images (1.6 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.

3 images further down the page (1.3 MB) 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 1.84 g of CO₂e: 220.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

There are 3 <h1> headlines (“Lake Region Healthcare”, “The Future of Surgery Arrives” and “Evening Clinic”). One clear main headline is easier for people and search engines.

Your meta description is 217 characters; Google truncates after about 160, so the end of your pitch is cut.

Structured data found (MedicalOrganization and WebSite) but with 1 problem, for example “WebSite: missing name”.

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

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

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

The homepage links to 106 pages on lrhc.org and 10 external pages.

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

https://www.lrhc.org/provider-directory, https://www.lrhc.org/locations and https://www.lrhc.org/news have no meta description, so Google writes the search snippet from whatever text it finds.

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

Large scripts ship without source maps.

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.

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

There is no form on the homepage, so every lead has to click through to another page first.

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 476 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (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 5 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 7 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.