nems.org website review

About 2.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 11.9 s faster on a phone.

Google CDN costs a phone 1.8 s of main-thread work and 4.1 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.

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

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

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

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

7 third-party services load with your homepage (Google CDN, Other Google APIs/SDKs and jotform.com and others), adding 5.3 MB and 2.3 s of main-thread time.

About 141 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 610 ms faster on a phone.

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

jotform.com costs a phone 154 ms of main-thread work and 469 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.

Google Fonts costs a phone 0 ms of main-thread work and 346 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.

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

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

38 KiB could be saved by minifying CSS.

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

15 KiB could be saved by minifying JavaScript.

Polyfills for old browsers add 10 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.

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

Your largest element takes 58.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Medical”.

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

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

The layout shifts by 1.208 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 23.8 MB in 225 requests on a phone: images 16.2 MB (88), scripts 4.3 MB (55) and other files 1.7 MB (17). Under 2 MB keeps phones on slow connections fast.

6 images weigh 8.5 MB together. On a phone connection a single image that size takes seconds.

4 images are downloaded at several times the size a phone draws them, for example Mobile_San-Bruno-Clinic-Exterior-Night-View.jpeg at 8,684 px wide, shown at 390 px. Resized copies would save about 4.6 MB.

22 images (7.7 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.

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

7 buttons have no accessible name, so screen readers announce just “button”.

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

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

1 element hidden from screen readers can still receive keyboard focus.

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

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

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

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

Alternative text of images should not be repeated as text: 5 elements on the page fail this check, rated minor by axe-core.

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

Your title is only 18 characters: “Home - NEMS : NEMS”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

There are 7 <h1> headlines (“Get Medi-Cal and Stay Covered Regardless of Your …”, “Skip the line! Check in using our new Welcome Kio…” and “MyChart – A new way for NEMS members to access he…”). One clear main headline is easier for people and search engines.

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

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

The homepage links to 155 pages on nems.org and 27 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://nems.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://nems.org/provider-search, https://nems.org/services/behavioral-health, https://nems.org/services/integrative-medicine, https://nems.org/covid-19, https://nems.org/programs and https://nems.org/programs/internal-medicine-residency-program use the same meta description. A description written for each page earns more clicks.

https://nems.org/provider-search has no <h1> headline, so visitors and search engines get no clear main topic.

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

1 image failed to load on a phone, for example https://nems.org/95,%2095,%20homeabout-sm,%20homeabout-sm.jpg,%2045358,%20https://www.nems.org/wp-content/uploads/homeabout-sm.jpg,%20https://www.nems.org/home/homeabout-sm/,%20,%203,%20,%20,%20homeab.

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

2 errors were logged to the browser console while the page loaded, for example “Invalid site key or not loaded in api.js: 6LcZA3gqAAAAAIMbnl9oHnmiq27F2_2NXiK_zNwi”.

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.

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

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

Your longest form asks for 8 fields (7 required). Every extra field lowers completion.

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 1,567 words of visible text.

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.