Website review, no card needed
usaobgyn.com website review
Visit site (opens in a new tab)Reviewed 18 October 202620 issues · 77 checks
This review found 20 issues worth fixing on usaobgyn.com, 3 of them high impact, across 77 checks. The most urgent: 1 button without a name. 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
91AClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 25, 2026 | 2.1 s |
| May 2, 2026 | 1.9 s |
| May 9, 2026 | 1.9 s |
| May 16, 2026 | 1.9 s |
| May 23, 2026 | 1.8 s |
| May 30, 2026 | 1.8 s |
| Jun 6, 2026 | 1.9 s |
| Jun 13, 2026 | 1.9 s |
| Jun 20, 2026 | 2.0 s |
| Jun 27, 2026 | 1.9 s |
| Jul 4, 2026 | 1.9 s |
| Jul 11, 2026 | 1.9 s |
| Jul 18, 2026 | 1.9 s |
| Jul 25, 2026 | 1.9 s |
| Aug 1, 2026 | 1.9 s |
| Aug 8, 2026 | 1.9 s |
| Aug 15, 2026 | 2.0 s |
| Aug 22, 2026 | 2.0 s |
| Aug 29, 2026 | 2.0 s |
| Sep 5, 2026 | 2.0 s |
| Sep 12, 2026 | 2.1 s |
| Sep 19, 2026 | 2.2 s |
| Sep 26, 2026 | 2.2 s |
| Oct 3, 2026 | 2.3 s |
| Oct 10, 2026 | 2.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 25, 2026 | 113 ms |
| May 2, 2026 | 111 ms |
| May 9, 2026 | 109 ms |
| May 16, 2026 | 109 ms |
| May 23, 2026 | 109 ms |
| May 30, 2026 | 111 ms |
| Jun 6, 2026 | 112 ms |
| Jun 13, 2026 | 115 ms |
| Jun 20, 2026 | 113 ms |
| Jun 27, 2026 | 111 ms |
| Jul 4, 2026 | 109 ms |
| Jul 11, 2026 | 105 ms |
| Jul 18, 2026 | 106 ms |
| Jul 25, 2026 | 106 ms |
| Aug 1, 2026 | 106 ms |
| Aug 8, 2026 | 105 ms |
| Aug 15, 2026 | 104 ms |
| Aug 22, 2026 | 105 ms |
| Aug 29, 2026 | 106 ms |
| Sep 5, 2026 | 110 ms |
| Sep 12, 2026 | 113 ms |
| Sep 19, 2026 | 112 ms |
| Sep 26, 2026 | 111 ms |
| Oct 3, 2026 | 112 ms |
| Oct 10, 2026 | 110 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.4 s
0.8 s
1.2 s
1.6 s
1.9 s
2.3 s
2.7 s
3.1 s
Speed
Improve image delivery
143 KiB1 image could be 143 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Reduce unused JavaScript
43 KiBAbout 43 KiB of JavaScript is downloaded but never used on this page.
Reduce unused CSS
12 KiBAbout 12 KiB of CSS is downloaded but never applied on this page.
2 third-party services on the page
2 third-party services load with your homepage (Google Fonts and Bootstrap CDN), adding 100 KiB and 0 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.
3 checks passed
Mobile performance score: 90
90/100Your mobile performance score is 90 (desktop: 84). That is in Google's “good” band (90 and up).
Main-thread work: 0.3 s
A phone's processor spends 0.3 s on main-thread work while loading, 62 ms of it running JavaScript. That is comfortably low.
Server response: 41 ms
41 msYour server sent the HTML in 41 ms, well inside Google's 600 ms guideline.
Core Web Vitals
First Contentful Paint: 2.4 s
2.4 sThe first text or image appears after 2.4 s on a phone. Good is under 1.8 s.
Speed Index: 4.6 s
4.6 sVisually, the page fills in at 4.6 s (Speed Index). Good is under 3.4 s.
Largest Contentful Paint: 2.7 s
2.7 sYour largest element takes 2.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Caring for the whole woman for over 25 years. Book Online N…”. Most of its time is resource load delay (2.4 s).
Tap response (INP) held steady for real visitors
-1%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' tap response (inp) went from 113 ms to 110 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 13% slower for real visitors
+13%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' largest content (lcp) went from 2.1 s to 2.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
9 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.1 s
1.1 sReal visitors wait 1.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 120 ms
120 msReal visitors wait 120 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.0 s
1.0 sReal visitors see the first content after 1.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 685 ms
685 msReal visitors wait 685 ms for your server to start answering (75th percentile). Good is under 800 ms.
Time to Interactive: 2.8 s
2.8 sThe page is fully interactive after 2.8 s.
Cumulative Layout Shift: 0.058
0.058The layout barely moves while loading (CLS 0.058, 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
2 images far larger than shown
81 KiB2 images are downloaded at several times the size a phone draws them, for example 1ef3239a26962fc4d02fc2c80bad79231.webp at 1,229 px wide, shown at 348 px. Resized copies would save about 81 KiB.
3 images in older formats
3 images (260 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.
4 images below the first screen load straight away
4 images further down the page (234 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 0.4 g of CO₂ per visit
0.43 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.43 g of CO₂e: 51.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Page weight: 1.5 MB in 23 requests
1.5 MBYour homepage downloads 1.5 MB in 23 requests on a phone: images 1.3 MB (13), fonts 99 KiB (2) and scripts 75 KiB (6). That is a lean page.
Accessibility
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
11 tap targets too small
11 tap targets are too small or too close together to hit reliably with a finger.
4 text elements with low contrast
4 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 (3 elements)
All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
38 links without text
38 visible links have no text or label, so screen readers cannot say where they go.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (2 elements).
2 checks passed
Every image has alt text
All 13 images in the HTML carry an alt attribute.
39 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 45 WCAG 2.2 A/AA and best-practice rules on the phone render: 39 passed and 6 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No XML sitemap
No XML sitemap at https://stg-advantiahealthcomnew-staging.kinsta.cloud/sitemap_index.xml, so Google discovers your pages only by following links.
3 links crawlers can't follow
3 links have no real href, so search engines can't follow them.
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.
112 internal links, 20 external
The homepage links to 112 pages on usaobgyn.com and 20 external pages.
7 checks passed
Meta description: 154 characters
Your meta description is 154 characters: “Discover expert OBGYN care at Heartland Women's Healthcare. Comprehensive services for women’s health needs in a suppor…”.
One H1 headline
Your main headline reads: “Caring for the whole woman for over 25 years.”.
Title: 58 characters
Your title is a healthy 58 characters: “Heartland Women's Healthcare of Advantia | Advantia Health”.
Canonical URL set
The canonical URL is https://www.advantiahealth.com/usaobgyn/.
Structured data in place
Structured data found: BreadcrumbList, ImageObject, WebPage and WebSite.
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.
AI search readiness
No Organization structured data
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.
3 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.
Text is in the HTML
Your server sends the page's text in the HTML (2,000 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.advantiahealth.com/llms.txt (15 KiB, 94 links), a plain-text guide to the site for AI tools.
Other pages
9 pages without a meta description
https://www.advantiahealth.com/usaobgyn/services, https://www.advantiahealth.com/usaobgyn/conditions, https://www.advantiahealth.com/usaobgyn/team, https://www.advantiahealth.com/usaobgyn/locations/heartland-womens-healthcare-of-advantia-carbondale, https://www.advantiahealth.com/usaobgyn/locations/heartland-womens-healthcare-of-advantia-centralia and https://www.advantiahealth.com/usaobgyn/locations/heartland-womens-healthcare-of-advantia-marion and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.
15 links to non-canonical URLs
Your homepage links to 15 pages by a URL that isn't their canonical one, for example https://www.advantiahealth.com/usaobgyn/womens-health-blog/tylenol-use-in-pregnancy, whose canonical is https://www.advantiahealth.com/womens-health-blog/tylenol-use-in-pregnancy. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 47 found) and read each the way a search engine does.
5 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
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
5 small tap targets
5 of 11 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “jQuery is not a function”.
1 checks passed
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: 2 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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 415 words of copy
The homepage carries about 415 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” and “Book Online Now!”.
17 calls to action
The homepage has 17 calls to action, for example “Learn More”, “Call Us Now!” and “Book Online Now!”.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 8 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
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.
3 other companies contacted
Loading the homepage contacts 3 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 usaobgyn.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
- The footer still says © 2024.
Stack
- CMS
- WordPress
- Framework
- jQuery
- Analytics
- Google Tag Manager
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 20 issues on usaobgyn.com, including 3 speed issues, 3 SEO issues and 2 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.