saintpetershcs.com website review

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

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

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

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

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

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

9 KiB could be saved by minifying CSS.

6 third-party services load with your homepage (Google CDN, Other Google APIs/SDKs and FontAwesome CDN and others), adding 306 KiB and 118 ms of main-thread time.

1 long task block the main thread while loading, the longest for 62 ms. During a long task the page ignores taps.

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

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.

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

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

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

Your largest element takes 3.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We use non-essential cookies to improve user experience and…”. Most of its time is element render delay (2.6 s).

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

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

april-2026-cover.png weighs 541 KiB. On a phone connection a single image that size takes seconds.

5 images (854 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.

1 image is downloaded at several times the size a phone draws it, for example Health-and-Wellness-Center-Blessing-19302.jpg at 1,051 px wide, shown at 146 px. Resized copies would save about 122 KiB.

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

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

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

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

7 form fields have no label, so screen readers announce an empty box and autofill guesses.

Alternative text of images should not be repeated as text: 7 elements on the page fail this check, rated minor by axe-core.

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

Your meta description is 161 characters; Google truncates after about 160, so the end of your pitch is cut.

No Open Graph image (also missing: og:title, og:description), 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.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 55 pages on saintpetershcs.com and 9 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

The HTML your server sends has 395 of the 692 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

There is no https://www.saintpetershcs.com/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.

https://www.saintpetershcs.com/Donate and https://www.saintpetershcs.com/donate all use the title “Donate”, 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://www.saintpetershcs.com/Donate and https://www.saintpetershcs.com/donate use the same meta description. A description written for each page earns more clicks.

https://www.saintpetershcs.com/Locations, https://www.saintpetershcs.com/Patients, https://www.saintpetershcs.com/Visitors and https://www.saintpetershcs.com/News have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.saintpetershcs.com/events has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

https://www.saintpetershcs.com/Donate, https://www.saintpetershcs.com/Find-a-Doctor, https://www.saintpetershcs.com/Services, https://www.saintpetershcs.com/Locations and https://www.saintpetershcs.com/Visitors took over 3 s to send their HTML from our server.

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

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

1 image is served at too low a resolution for sharp phone screens.

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 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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