vwhs.org website review

85 files are served with short cache lifetimes, so returning visitors download them again (6.0 MB).

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

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

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

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

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

4 third-party services load with your homepage (Google Tag Manager, Accessibe Accessibility Overlay and Google Fonts and others), adding 591 KiB and 743 ms of main-thread time.

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

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

Accessibe Accessibility Overlay costs a phone 366 ms of main-thread work and 243 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.

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

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

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

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 18.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Your Health Our Priority! Valley-Wide Health Systems, Inc. …”.

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

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

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

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

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

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

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

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

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

Your homepage downloads 6.9 MB in 103 requests on a phone: images 5.3 MB (22), scripts 840 KiB (28) and other files 306 KiB (12). Under 2 MB keeps phones on slow connections fast.

9 images are downloaded at several times the size a phone draws them, for example 2024-OSV-Badge-Fin.png at 2,292 px wide, shown at 122 px. Resized copies would save about 3.8 MB.

2024-OSV-Badge-Fin.png weighs 2.2 MB. On a phone connection a single image that size takes seconds.

11 images (4.1 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.

10 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 1.95 g of CO₂e: 234.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Images must have alternative text: 8 elements on the page fail this check, rated critical by axe-core.

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

Elements must only use permitted ARIA attributes: 8 elements on the page fail this check, rated serious by axe-core.

3 links inside paragraphs rely on colour alone to stand out.

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

3 visible links have no text or label, so screen readers cannot say where they go.

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

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

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

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

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

The homepage links to 276 pages on vwhs.org and 19 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://valley-widehealth.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.

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

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

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.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

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