mihs.org website review

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

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

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

9 images could be 1.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

Your mobile performance score is 59. Pages that score under 90 lose visitors before the first paint.

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

8 third-party services load with your homepage (jQuery CDN, FontAwesome CDN and Google Maps and others), adding 1.0 MB and 422 ms of main-thread time.

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

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

heyzine.com costs a phone 16 ms of main-thread work and 371 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 71 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

35 KiB could be saved by minifying JavaScript.

1 long task block the main thread while loading, the longest for 100 ms. During a long task the page ignores taps.

21 KiB could be saved by minifying CSS.

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 17.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “You’re More to Us Whether you need a routine checkup, speci…”.

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

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

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

Real visitors wait 869 ms for your server to start answering (75th percentile). Good is under 800 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-31, real Chrome visitors' tap response (inp) went from 104 ms to 112 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 3.9 MB in 172 requests on a phone: images 1.9 MB (26), scripts 1.5 MB (67) and stylesheets 307 KiB (50). Under 2 MB keeps phones on slow connections fast.

4 images (715 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.

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

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

1 image has no alt text, which hurts accessibility and image search.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

The skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.

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

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

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

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 163 pages on mihs.org and 18 external pages.

Your Organization JSON-LD is missing 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.

There is no https://valleywisehealth.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://valleywisehealth.org/es, https://valleywisehealth.org/fr, https://valleywisehealth.org/ar, https://valleywisehealth.org/sw, https://valleywisehealth.org/my and https://valleywisehealth.org/fa and 1 other all use the title “Valleywise Health”. Search engines can't tell which page to show for a search, so each competes with the others.

https://valleywisehealth.org/fr, https://valleywisehealth.org/ar, https://valleywisehealth.org/sw, https://valleywisehealth.org/my, https://valleywisehealth.org/fa and https://valleywisehealth.org/rw and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.

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

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

1 error was logged to the browser console while the page loaded, for example “Error with Permissions-Policy header: Parse of permissions policy failed because of errors reported by structured heade…”.

1 image is served at too low a resolution for sharp phone screens.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

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

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

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