providencekc.com website review

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

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

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

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

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

About 160 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 750 ms faster on a phone.

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

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

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

7 third-party services load with your homepage (steerhealth.io, userway.org and trustindex.io and others), adding 777 KiB and 205 ms of main-thread time.

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

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.

5 KiB could be saved by minifying CSS.

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.

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

Your largest element takes 32.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “FastTrackCareReserve Your ER Arrival…”.

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

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

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

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

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

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

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

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

Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 88 ms to 92 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 3.8 s to 3.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 7.7 MB in 125 requests on a phone: images 6.6 MB (55), fonts 485 KiB (10) and scripts 417 KiB (30). Under 2 MB keeps phones on slow connections fast.

16 images are downloaded at several times the size a phone draws them, for example Award-Seals-CPMI-PAA_PLATINUM.png at 1,500 px wide, shown at 242 px. Resized copies would save about 1.9 MB.

25 images (3.5 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.

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

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

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

There are 10 <h1> headlines (“FastTrackCare”, “MyChart Patient Portal Text Opt-In” and “Changing Lives through Hearts and Minds – Togethe…”). One clear main headline is easier for people and search engines.

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

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

The homepage links to 118 pages on providencekc.com and 23 external pages.

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

Your homepage links to https://providencekc.com/referral, which answers with an error. Visitors hit a dead end and search engines drop it.

https://providencekc.com/home declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

/ and https://providencekc.com/home all use the title “Best Hospital in Kansas | ER 24/7-Providence Medical Center”. Search engines can't tell which page to show for a search, so each competes with the others.

https://providencekc.com/our-services, https://providencekc.com/patients-visitors, https://providencekc.com/careers, https://providencekc.com/billing-insurance-information, https://providencekc.com/carecredit and https://providencekc.com/medical-records and 2 others took over 3 s to send their HTML from our server.

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

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

8 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

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.

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

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 885 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 10 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.