misericordia.com website review

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

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

hcaptcha.com costs a phone 1.7 s of main-thread work and 1.2 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

8 third-party services load with your homepage (hcaptcha.com, Google Tag Manager and Shopify and others), adding 2.5 MB and 2.4 s of main-thread time.

6 files are served with short cache lifetimes, so returning visitors download them again (126 KiB).

13 files block the first paint until they finish downloading. Deferring or inlining them could save about 700 ms.

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

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

Shopify costs a phone 329 ms of main-thread work and 1,004 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.

Polyfills for old browsers add 66 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 350 ms faster on a phone.

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

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.

4 KiB could be saved by minifying JavaScript.

Your largest element takes 17.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Group of people wearing matching blue t-shirts with logos, …”.

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

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

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

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

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

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

Over the last 25 four-week periods to 2026-10-31, 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 4.9 MB in 323 requests on a phone: scripts 2.1 MB (178), images 1.3 MB (19) and other files 770 KiB (90). Under 2 MB keeps phones on slow connections fast.

Heartbreakers_FamilyFest_2024_v6.jpg weighs 747 KiB. On a phone connection a single image that size takes seconds.

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

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

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

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

1 visible link has no text or label, so screen readers cannot say where it goes.

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

Your title is only 27 characters: “Misericordia Heart of Mercy”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 3 <h1> headlines (“Living with Dignity, Challenge, and Respect”, “Compassionate Care with Dedicated Staff” and “Sharing Life's Journey Empowering Every Step”). One clear main headline is easier for people and search engines.

6 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 112 pages on misericordia.com and 15 external pages.

https://www.misericordia.com/pages/admissions, https://www.misericordia.com/pages/daf-donation-page and https://www.misericordia.com/pages/request-cards have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.misericordia.com/pages/admissions, https://www.misericordia.com/pages/contact-us, https://www.misericordia.com/pages/programs-and-services, https://www.misericordia.com/pages/give-now, https://www.misericordia.com/pages/daf-donation-page and https://www.misericordia.com/pages/heart-soil-composting have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

The page uses 1 deprecated browser API that will stop working in future browsers (“The Protected Audience API is deprecated and will be removed in a future release.”).

3 errors were logged to the browser console while the page loaded, for example “Refused to apply style from 'https://www.misericordia.com/cdn/shop/t/24/assets/search-overlay.css?v=10015' because its …”.

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

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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 576 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). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.

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

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