roxboroughmemorial.com website review

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

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

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

22 images could be 1.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 350 ms faster on a phone.

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

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

101 KiB could be saved by minifying JavaScript.

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

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

7 third-party services load with your homepage (Google Maps, steerhealth.io and userway.org and others), adding 773 KiB and 186 ms of main-thread time.

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

Polyfills for old browsers add 23 KiB JavaScript that modern phones do not need.

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

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

Your largest element takes 19.7 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 20.1 s. Good is under 3.8 s.

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

For real visitors the layout shifts by 0.18 (75th percentile). Good is under 0.1.

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

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

23 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-31, real Chrome visitors' tap response (inp) went from 81 ms to 96 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 3.9 s to 4.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 4.1 MB in 124 requests on a phone: images 2.6 MB (45), scripts 1,000 KiB (40) and fonts 341 KiB (9). Under 2 MB keeps phones on slow connections fast.

Corazon-Accreditation-Logo-2019.png weighs 538 KiB. On a phone connection a single image that size takes seconds.

3 images are downloaded at several times the size a phone draws them, for example Corazon-Accreditation-Logo-2019.png at 1,800 px wide, shown at 242 px. Resized copies would save about 873 KiB.

17 images (1.9 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.

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

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

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

There are 6 <h1> headlines (“FastTrackCare”, “MyChart Patient Portal Text Opt-In” and “Caring for the growing needs of our community.”). One clear main headline is easier for people and search engines.

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

Structured data found (AboutPage, Hospital, ImageObject and MedicalClinic) but with 1 problem, for example “WebSite: missing name”.

The homepage links to 143 pages on roxboroughmemorial.com and 17 external pages.

Your Organization JSON-LD is missing logo, sameAs (social profiles) and description. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

https://roxboroughmemorial.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://roxboroughmemorial.com/home all use the title “Roxborough Memorial Hospital | Philadelphia Community Hospital”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://roxboroughmemorial.com/our-services/school-of-nursing, https://roxboroughmemorial.com/your-bills-insurance, https://roxboroughmemorial.com/medical-records, https://roxboroughmemorial.com/my-chart-patient-portal and https://roxboroughmemorial.com/for-physicians have no meta description, so Google writes the search snippet from whatever text it finds.

https://roxboroughmemorial.com/find-a-provider and https://roxboroughmemorial.com/find-a-Provider use the same meta description. A description written for each page earns more clicks.

https://roxboroughmemorial.com/find-a-provider and https://roxboroughmemorial.com/find-a-Provider have no <h1> headline, so visitors and search engines get no clear main topic.

https://roxboroughmemorial.com/your-bills-insurance, https://roxboroughmemorial.com/carecredit, https://roxboroughmemorial.com/medical-records and https://roxboroughmemorial.com/for-physicians took over 3 s to send their HTML from our server.

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

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

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

Large scripts ship without source maps.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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