umuch.org website review

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

Google Tag Manager costs a phone 1.0 s of main-thread work and 890 KiB 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 34 (desktop: 60). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

8 third-party services load with your homepage (Google Tag Manager, YouTube and perfalytics.com and others), adding 2.8 MB and 1.8 s of main-thread time.

YouTube costs a phone 660 ms of main-thread work and 1.7 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.

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 450 ms.

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

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

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

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

Desktop scores 60 but mobile only 34. A gap that wide usually means heavy scripts and images that hit phones hardest.

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

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

Your largest element takes 13.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Life Feels Better in Motion”.

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

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

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

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

Your homepage downloads 3.0 MB in 108 requests on a phone: scripts 2.5 MB (22), stylesheets 198 KiB (6) and HTML 154 KiB (5). Under 2 MB keeps phones on slow connections fast.

5 images (248 KiB) 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 (82 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.85 g of CO₂e: 101.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

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

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

The homepage links to 73 pages on umuch.org and 8 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

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

robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

https://www.umms.org/uch/giving and https://www.umms.org/uch/health-services/womens-services/breast-care have no meta description, so Google writes the search snippet from whatever text it finds.

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

5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

Chrome logged issues while loading the page (“Cookie”).

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 testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

The homepage has only about 198 words of visible text; thin pages give Google and first-time buyers little to go on.

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

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