Website review, no card needed
aaobgyn.com website review
Visit site (opens in a new tab)Reviewed 20 October 202621 issues · 74 checks
This review found 21 issues worth fixing on aaobgyn.com, 5 of them high impact, across 74 checks. The most urgent: fails Core Web Vitals for real visitors. 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
84BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 852 ms |
| May 9, 2026 | 817 ms |
| May 16, 2026 | 788 ms |
| May 23, 2026 | 789 ms |
| May 30, 2026 | 831 ms |
| Jun 6, 2026 | 872 ms |
| Jun 13, 2026 | 868 ms |
| Jun 20, 2026 | 838 ms |
| Jun 27, 2026 | 830 ms |
| Jul 4, 2026 | 798 ms |
| Jul 11, 2026 | 825 ms |
| Jul 18, 2026 | 825 ms |
| Jul 25, 2026 | 838 ms |
| Aug 1, 2026 | 874 ms |
| Aug 8, 2026 | 866 ms |
| Aug 15, 2026 | 886 ms |
| Aug 22, 2026 | 898 ms |
| Aug 29, 2026 | 897 ms |
| Sep 5, 2026 | 908 ms |
| Sep 12, 2026 | 924 ms |
| Sep 19, 2026 | 924 ms |
| Sep 26, 2026 | 909 ms |
| Oct 3, 2026 | 924 ms |
| Oct 10, 2026 | 969 ms |
| Oct 17, 2026 | 969 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 75 ms |
| May 9, 2026 | 75 ms |
| May 16, 2026 | 75 ms |
| May 23, 2026 | 77 ms |
| May 30, 2026 | 79 ms |
| Jun 6, 2026 | 79 ms |
| Jun 13, 2026 | 79 ms |
| Jun 20, 2026 | 79 ms |
| Jun 27, 2026 | 78 ms |
| Jul 4, 2026 | 78 ms |
| Jul 11, 2026 | 79 ms |
| Jul 18, 2026 | 79 ms |
| Jul 25, 2026 | 79 ms |
| Aug 1, 2026 | 79 ms |
| Aug 8, 2026 | 78 ms |
| Aug 15, 2026 | 75 ms |
| Aug 22, 2026 | 73 ms |
| Aug 29, 2026 | 73 ms |
| Sep 5, 2026 | 74 ms |
| Sep 12, 2026 | 75 ms |
| Sep 19, 2026 | 77 ms |
| Sep 26, 2026 | 75 ms |
| Oct 3, 2026 | 74 ms |
| Oct 10, 2026 | 75 ms |
| Oct 17, 2026 | 75 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
Speed
Mobile performance score: 73
73/100Your mobile performance score is 73 (desktop: 98). Pages that score under 90 lose visitors before the first paint.
Improve image delivery
175 KiB1 image could be 175 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
1 long task on the main thread
1 long task block the main thread while loading, the longest for 52 ms. During a long task the page ignores taps.
Reduce unused CSS
21 KiBAbout 21 KiB of CSS is downloaded but never applied on this page.
Phones get a much slower page than desktops
Desktop scores 98 but mobile only 73. A gap that wide usually means heavy scripts and images that hit phones hardest.
2 third-party services on the page
2 third-party services load with your homepage (Google Fonts and Adobe TypeKit), adding 57 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.
2 checks passed
Main-thread work: 0.3 s
A phone's processor spends 0.3 s on main-thread work while loading, 56 ms of it running JavaScript. That is comfortably low.
Server response: 65 ms
65 msYour server sent the HTML in 65 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.
First Contentful Paint: 3.0 s
3.0 sThe first text or image appears after 3.0 s on a phone. Good is under 1.8 s.
Real-user CLS: 0.11
0.11For real visitors the layout shifts by 0.11 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 3.8 s
3.8 sYour largest element takes 3.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Caring for and Serving Women in Austin Texas Since 1960 Wel…”.
Cumulative Layout Shift: 0.211
0.211The layout shifts by 0.211 while loading, so content jumps under the reader's thumb. Good is under 0.1.
3 images without width and height
3 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
0%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 75 ms to 75 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 16% slower for real visitors
+16%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 0.9 s to 1.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 checks passed
Real-user LCP: 1.2 s
1.2 sReal visitors wait 1.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 79 ms
79 msReal visitors wait 79 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 0.8 s
0.8 sReal visitors see the first content after 0.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 629 ms
629 msReal visitors wait 629 ms for your server to start answering (75th percentile). Good is under 800 ms.
Speed Index: 3.4 s
3.4 sVisually, the page fills in at 3.4 s (Speed Index), inside the 3.4 s “good” threshold.
Time to Interactive: 3.8 s
3.8 sThe page is fully interactive after 3.8 s.
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
1 image far larger than shown
23 KiB1 image is downloaded at several times the size a phone draws it, for example practice-bg_mob.jpg at 1,242 px wide, shown at 390 px. Resized copies would save about 23 KiB.
1 image in older formats
1 image (208 KiB) is 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.
About 0.2 g of CO₂ per visit
0.18 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.18 g of CO₂e: 21.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Page weight: 645 KiB in 16 requests
645 KiBYour homepage downloads 645 KiB in 16 requests on a phone: images 379 KiB (6), fonts 204 KiB (7) and HTML 55 KiB (1). That is a lean page.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
45 text elements with low contrast
45 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
9 links without text
9 visible links have no text or label, so screen readers cannot say where they go.
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 (h4 → h6, h4 → h6 and h4 → h6), which makes the page harder to scan with a screen reader.
1 checks passed
30 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 34 WCAG 2.2 A/AA and best-practice rules on the phone render: 30 passed and 4 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
100 internal links, 42 external
The homepage links to 100 pages on aaobgyn.com and 42 external pages.
6 checks passed
Meta description: 118 characters
Your meta description is 118 characters: “Trusted OBGYN doctors in Austin TX offering pregnancy care, fertility treatment, and complete women’s health services.”.
Title: 57 characters
Your title is a healthy 57 characters: “OBGYN in Austin TX | Pregnancy & Fertility Care | AAOBGYN”.
Canonical URL set
The canonical URL is https://aaobgyn.com/.
Structured data in place
Structured data found: BreadcrumbList, WebPage and WebSite.
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://aaobgyn.com/sitemap_index.xml.
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,688 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://aaobgyn.com/llms.txt (4 KiB, 38 links), a plain-text guide to the site for AI tools.
Other pages
15 pages without a meta description
https://aaobgyn.com/about-us, https://aaobgyn.com/our-providers, https://aaobgyn.com/leadership, https://aaobgyn.com/classes, https://aaobgyn.com/resources and https://aaobgyn.com/services and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.
13 pages without an H1
https://aaobgyn.com/about-us, https://aaobgyn.com/our-providers, https://aaobgyn.com/leadership, https://aaobgyn.com/classes, https://aaobgyn.com/resources and https://aaobgyn.com/services and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 22 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.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Titles are unique
Every page we checked has its own title.
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
10 small tap targets
10 of 30 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
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: 8 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
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 602 words of copy
The homepage carries about 602 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: “Contact Us” and “Schedule Online”.
9 calls to action
The homepage has 9 calls to action, for example “Schedule Appt.”, “Contact Us” and “Schedule Online”.
1 short form
A short form (1 field at most) is right on the homepage.
Analytics in place
Analytics detected: Google Analytics.
Direct contact links
Visitors can reach you directly: 4 phone links and 0 email links.
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 aaobgyn.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 Analytics
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 21 issues on aaobgyn.com, including 7 speed issues, 2 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.