Website review, no card needed
mercymedcenter.com website review
Visit site (opens in a new tab)Reviewed 27 October 202637 issues · 83 checks
This review found 37 issues worth fixing on mercymedcenter.com, 15 of them high impact, across 83 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
76CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 3.3 s |
| May 16, 2026 | 3.2 s |
| May 23, 2026 | 3.1 s |
| May 30, 2026 | 3.2 s |
| Jun 6, 2026 | 3.6 s |
| Jun 13, 2026 | 3.8 s |
| Jun 20, 2026 | 4.0 s |
| Jun 27, 2026 | 3.8 s |
| Jul 4, 2026 | 3.6 s |
| Jul 11, 2026 | 3.6 s |
| Jul 18, 2026 | 3.5 s |
| Jul 25, 2026 | 3.7 s |
| Aug 1, 2026 | 3.6 s |
| Aug 8, 2026 | 3.7 s |
| Aug 15, 2026 | 3.6 s |
| Aug 22, 2026 | 3.4 s |
| Aug 29, 2026 | 3.5 s |
| Sep 5, 2026 | 3.2 s |
| Sep 12, 2026 | 3.4 s |
| Sep 19, 2026 | 3.2 s |
| Sep 26, 2026 | 3.3 s |
| Oct 3, 2026 | 3.3 s |
| Oct 10, 2026 | 3.4 s |
| Oct 17, 2026 | 3.6 s |
| Oct 24, 2026 | 3.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 154 ms |
| May 16, 2026 | 154 ms |
| May 23, 2026 | 150 ms |
| May 30, 2026 | 153 ms |
| Jun 6, 2026 | 148 ms |
| Jun 13, 2026 | 144 ms |
| Jun 20, 2026 | 129 ms |
| Jun 27, 2026 | 95 ms |
| Jul 4, 2026 | 79 ms |
| Jul 11, 2026 | 79 ms |
| Jul 18, 2026 | 80 ms |
| Jul 25, 2026 | 85 ms |
| Aug 1, 2026 | 84 ms |
| Aug 8, 2026 | 84 ms |
| Aug 15, 2026 | 90 ms |
| Aug 22, 2026 | 87 ms |
| Aug 29, 2026 | 93 ms |
| Sep 5, 2026 | 91 ms |
| Sep 12, 2026 | 82 ms |
| Sep 19, 2026 | 81 ms |
| Sep 26, 2026 | 79 ms |
| Oct 3, 2026 | 78 ms |
| Oct 10, 2026 | 79 ms |
| Oct 17, 2026 | 78 ms |
| Oct 24, 2026 | 82 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
How it loaded on a phone
0.5 s
0.9 s
1.4 s
1.8 s
2.3 s
2.7 s
3.2 s
3.6 s
Speed
Use efficient cache lifetimes
5.4 s · 2.2 MB104 files are served with short cache lifetimes, so returning visitors download them again (2.2 MB).
Improve image delivery
5.0 s · 2.1 MB17 images could be 2.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 5.0 s faster on a phone.
Render-blocking requests
5.0 s31 files block the first paint until they finish downloading. Deferring or inlining them could save about 5.0 s.
Reduce unused JavaScript
900 ms · 158 KiBAbout 158 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.
Mobile performance score: 57
57/100Your mobile performance score is 57 (desktop: 80). Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
750 ms · 138 KiBAbout 138 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 750 ms faster on a phone.
Legacy JavaScript
350 ms · 25 KiBPolyfills for old browsers add 25 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 350 ms faster on a phone.
Font display
350 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 350 ms).
6 third-party services on the page
6 third-party services load with your homepage (steerhealth.io, userway.org and Google Fonts and others), adding 449 KiB and 45 ms of main-thread time.
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
2 checks passed
Main-thread work: 0.9 s
A phone's processor spends 0.9 s on main-thread work while loading, 339 ms of it running JavaScript. That is comfortably low.
Server response: 18 ms
18 msYour server sent the HTML in 18 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
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-user LCP: 4.2 s
4.2 sReal visitors wait 4.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user TTFB: 1.9 s
1.9 sReal visitors wait 1.9 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 22.0 s
22.0 sYour largest element takes 22.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Start at 40. Stay on schedule. A scr…”.
Time to Interactive: 22.4 s
22.4 sThe page becomes fully interactive after 22.4 s. Good is under 3.8 s.
First Contentful Paint: 6.6 s
6.6 sThe first text or image appears after 6.6 s on a phone. Good is under 1.8 s.
Speed Index: 7.9 s
7.9 sVisually, the page fills in at 7.9 s (Speed Index). Good is under 3.4 s.
Real-user FCP: 2.8 s
2.8 sReal visitors see the first content after 2.8 s (75th percentile). Good is under 1.8 s.
16 images without width and height
16 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) got 12% slower for real visitors
+12%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 3.3 s to 3.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user INP: 84 ms
84 msReal visitors wait 84 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Tap response (INP) got 48% faster for real visitors
-48%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 154 ms to 82 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 5.7 MB in 121 requests
5.7 MBYour homepage downloads 5.7 MB in 121 requests on a phone: images 4.7 MB (37), fonts 412 KiB (8) and scripts 411 KiB (49). Under 2 MB keeps phones on slow connections fast.
7 images far larger than shown
615 KiB7 images are downloaded at several times the size a phone draws them, for example Truven_15TOP-2013_Color-Corrected.jpg at 1,500 px wide, shown at 242 px. Resized copies would save about 615 KiB.
18 images in older formats
18 images (2.2 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.
17 images below the first screen load straight away
17 images further down the page (1.5 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.6 g of CO₂ per visit
1.62 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.62 g of CO₂e: 194.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
29 tap targets too small
29 tap targets are too small or too close together to hit reliably with a finger.
5 text elements with low contrast
5 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
4 links without text
4 visible links have no text or label, so screen readers cannot say where they go.
ARIA toggle fields do not have accessible names
ARIA toggle fields do not have accessible names (1 element).
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h1 → h3, h1 → h3 and h1 → h3), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 31 images in the HTML carry an alt attribute.
47 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 5 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
13 H1 headlines
There are 13 <h1> headlines (“Start at 40. Stay on schedule.”, “FastTrackCare” and “Emergency Department Accreditation”). One clear main headline is easier for people and search engines.
3 links with vague text
3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
55 internal links, 19 external
The homepage links to 55 pages on mercymedcenter.com and 19 external pages.
7 checks passed
Meta description: 143 characters
Your meta description is 143 characters: “Mercy Medical Center in Aurora, IL offers expert medical care with comprehensive services. Trust us for your health and…”.
Title: 47 characters
Your title is a healthy 47 characters: “Top Hospital Near Aurora - Mercy Medical Center”.
Canonical URL set
The canonical URL is https://mercymedcenter.com/.
Structured data in place
Structured data found: Hospital, ImageObject, Organization, Place and WebPage.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://mercymedcenter.com/sitemap_index.xml.
AI search readiness
4 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Organization data: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,056 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://mercymedcenter.com/llms.txt (21 KiB, 60 links, though it should open with a “# Title” line), a plain-text guide to the site for AI tools.
Other pages
1 page points its canonical at the homepage
https://mercymedcenter.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.
2 pages share a title
/ and https://mercymedcenter.com/home all use the title “Top Hospital Near Aurora - Mercy Medical Center”. Search engines can't tell which page to show for a search, so each competes with the others.
1 page without a meta description
https://mercymedcenter.com/mammogram has no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://mercymedcenter.com/birthing-center has no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://mercymedcenter.com/find-a-provider 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.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 30 found) and read each the way a search engine does.
3 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
13 small tap targets
13 of 26 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
8 distorted images
8 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Local business without LocalBusiness data
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.
Thin social proof
Social proof on the homepage: 7 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
About 514 words of copy
The homepage carries about 514 words of visible text.
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Learn More”.
5 calls to action
The homepage has 5 calls to action, for example “Learn More”, “Contact Us” and “Call Us”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Direct contact links
Visitors can reach you directly: 2 phone links and 0 email links.
Opening hours shown
Your opening hours are on the homepage.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
3 cookies set on arrival
3Opening the homepage sets 3 cookies (measured from a US location before any click).
No consent tool detected
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.
8 other companies contacted
Loading the homepage contacts 8 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at mercymedcenter.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Hosting
- Sucuri
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 37 issues on mercymedcenter.com, including 17 speed issues, 2 SEO issues and 3 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.