mynmchealth.org website review

Google Tag Manager costs a phone 1.2 s of main-thread work and 587 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 41. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

8 third-party services load with your homepage (Google Tag Manager, Hotjar and Facebook and others), adding 1,002 KiB and 2.1 s of main-thread time.

4 images could be 1.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 700 ms faster on a phone.

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

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

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

Hotjar costs a phone 409 ms of main-thread work and 65 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.

The page has 1,951 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

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

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

2 KiB could be saved by minifying JavaScript.

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.

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

Your largest element takes 14.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “nmc health digital award banner demonstrating award-winning…”.

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

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

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

Real visitors wait 3.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

Real visitors see the first content after 2.8 s (75th percentile). Good is under 1.8 s.

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

Your homepage downloads 4.5 MB in 111 requests on a phone: images 2.8 MB (22), scripts 1.4 MB (69) and fonts 122 KiB (3). Under 2 MB keeps phones on slow connections fast.

1 image further down the page (25 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.

5 form fields have no label, so screen readers announce an empty box and autofill guesses.

ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

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

Elements with visible text labels do not have matching accessible names. (1 element).

Structured data found (Article, ImageObject, MedicalOrganization and Organization) but with 1 problem, for example “Person: url is not an absolute URL ("#")”.

2 links have no real href, so search engines can't follow them.

The homepage links to 351 pages on mynmchealth.org and 25 external pages.

Your Organization JSON-LD is missing logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

https://www.mynmchealth.org/patients-and-visitors/pay-my-bill, https://www.mynmchealth.org/patients-and-visitors/surprise-billing-protection, https://www.mynmchealth.org/patients-and-visitors/request-medical-records, https://www.mynmchealth.org/patients-and-visitors/payment-information and https://www.mynmchealth.org/patients-and-visitors/health-library are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

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

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.

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

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