wfph.org website review

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

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

About 173 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.

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

3 images could be 132 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 750 ms faster on a phone.

3 third-party services load with your homepage (wpenginepowered.com, Vimeo and Google Fonts), adding 3.8 MB and 383 ms of main-thread time.

wpenginepowered.com costs a phone 307 ms of main-thread work and 2.6 MB 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.

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

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

Vimeo costs a phone 76 ms of main-thread work and 1.2 MB 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.

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

15 KiB could be saved by minifying JavaScript.

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

Desktop scores 88 but mobile only 47. 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.

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.

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

Your largest element takes 16.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Your Health. Your Hospital. Your Home.”.

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

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

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

Scripts block taps and scrolling for 376 ms in total while the page loads. Good is under 200 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-10, real Chrome visitors' tap response (inp) went from 86 ms to 86 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 3.8 MB in 127 requests on a phone: images 2.1 MB (26), scripts 1.4 MB (51) and stylesheets 281 KiB (29). Under 2 MB keeps phones on slow connections fast.

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

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

1 tap target is too small or too close together to hit reliably with a finger.

3 images have no alt text, which hurts accessibility and image search.

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

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

Structured data found (MedicalOrganization and SiteNavigationElement) but with 1 problem, for example “MedicalOrganization: sameAs is an empty list”.

The homepage links to 115 pages on wfph.org and 6 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 /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.

Your homepage links to 1 page by a URL that isn't its canonical one, for example /patients-visitors/patient-rights-and-responsibilities, whose canonical is /patient-rights-and-responsibilities. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

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

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

2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

1 error was logged to the browser console while the page loaded, for example “%c%d font-size:0;color:transparent NaN”.

Chrome logged issues while loading the page (“Cookie”).

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: 7 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.

The homepage shows no opening hours. If customers visit or call, show when.

There is no form on the homepage, so every lead has to click through to another page first.

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

Opening the homepage sets 9 cookies, 2 of them by other companies (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.