steinhospice.org website review

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

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

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

Your mobile performance score is 62 (desktop: 80). Pages that score under 90 lose visitors before the first paint.

5 third-party services load with your homepage (Google Tag Manager, Azure Web Services and Google Fonts and others), adding 369 KiB and 272 ms of main-thread time.

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

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

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

About 16 KiB of CSS is downloaded but never applied on this page.

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

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

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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.

Your largest element takes 16.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Man with bag, fist bumping man setting in chair.”.

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

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

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

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

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-10, real Chrome visitors' tap response (inp) went from 78 ms to 86 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 7.0 MB in 33 requests on a phone: images 6.5 MB (17), scripts 391 KiB (4) and fonts 68 KiB (2). Under 2 MB keeps phones on slow connections fast.

5 images weigh 3.2 MB together. On a phone connection a single image that size takes seconds.

5 images are downloaded at several times the size a phone draws them, for example DSC_8414_Hero_Desktop_1400x700.jpg at 1,400 px wide, shown at 350 px. Resized copies would save about 1.3 MB.

9 images (4.4 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.

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

14 tap targets are too small or too close together to hit reliably with a finger.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

There is no robots.txt at reserve-care.org/robots.txt, the first file search crawlers ask for.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 69 pages on steinhospice.org and 10 external pages.

There is no https://reserve-care.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://reserve-care.org/our-care-offerings/palliative-care and https://reserve-care.org/contact use the same meta description. A description written for each page earns more clicks.

https://reserve-care.org/healthcare-professionals, https://reserve-care.org/our-care-offerings, https://reserve-care.org/our-care-offerings/hospice-care, https://reserve-care.org/our-care-offerings/palliative-care, https://reserve-care.org/our-care-offerings/grief-support-services and https://reserve-care.org/contact and 2 others took over 3 s to send their HTML from our server.

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

Social proof on the homepage: 13 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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 688 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 3 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 8 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.