wvukids.com website review

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

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

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

Your mobile performance score is 60 (desktop: 90). Pages that score under 90 lose visitors before the first paint.

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

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

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

2 third-party services load with your homepage (JSDelivr CDN and Google Fonts), adding 212 KiB and 59 ms of main-thread time.

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

Desktop scores 90 but mobile only 60. 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.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

4 KiB could be saved by minifying JavaScript.

Your largest element takes 10.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “WVU MEDICINE GOLISANO CHILDREN'S Where lives are changed & …”.

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

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

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

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

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

Your homepage downloads 3.4 MB in 99 requests on a phone: images 2.5 MB (18), scripts 424 KiB (32) and fonts 260 KiB (4). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example 01-Best-Hospitals.jpg at 400 px wide, shown at 130 px. Resized copies would save about 3 KiB.

6 images (378 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.

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

Some lists contain elements other than list items, which screen readers announce wrongly.

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

Links must have discernible text: 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.

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

There are 3 <h1> headlines (“Where lives are changed & miracles happen”, “WVU Medicine Golisano Children's Hospital” and “WVU Medicine Golisano Children's provides special…”). 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.

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

The homepage links to 113 pages on wvukids.com and 12 external pages.

https://wvumedicine.org/our-care/institutes/childrens/our-care/units/nicu has no meta description, so Google writes the search snippet from whatever text it finds.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

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.

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.

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

Opening the homepage sets 1 cookie (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 3 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.