Website review, no card needed

txfertility.com logo

txfertility.com website review

Visit site (opens in a new tab)Reviewed 20 October 202632 issues · 88 checks

This review found 32 issues worth fixing on txfertility.com, 8 of them high impact, across 88 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
3.0 s2.7 sMay 2Oct 172.8 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.8 s
May 9, 20262.9 s
May 16, 20262.9 s
May 23, 20263.0 s
May 30, 20262.9 s
Jun 6, 20262.8 s
Jun 13, 20262.8 s
Jun 20, 20262.8 s
Jun 27, 20262.9 s
Jul 4, 20262.9 s
Jul 11, 20262.9 s
Jul 18, 20262.8 s
Jul 25, 20262.7 s
Aug 1, 20262.8 s
Aug 8, 20262.8 s
Aug 15, 20262.8 s
Aug 22, 20262.8 s
Aug 29, 20262.7 s
Sep 5, 20262.7 s
Sep 12, 20262.8 s
Sep 19, 20262.8 s
Sep 26, 20262.7 s
Oct 3, 20262.8 s
Oct 10, 20262.7 s
Oct 17, 20262.8 s
Real-visitor tap response (INP)75th percentile, phones
87 ms74 msMay 2Oct 1780 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 202679 ms
May 9, 202679 ms
May 16, 202679 ms
May 23, 202680 ms
May 30, 202679 ms
Jun 6, 202677 ms
Jun 13, 202675 ms
Jun 20, 202677 ms
Jun 27, 202679 ms
Jul 4, 202679 ms
Jul 11, 202680 ms
Jul 18, 202679 ms
Jul 25, 202679 ms
Aug 1, 202679 ms
Aug 8, 202679 ms
Aug 15, 202679 ms
Aug 22, 202680 ms
Aug 29, 202680 ms
Sep 5, 202680 ms
Sep 12, 202681 ms
Sep 19, 202681 ms
Sep 26, 202681 ms
Oct 3, 202685 ms
Oct 10, 202682 ms
Oct 17, 202680 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

Full-page screenshot of txfertility.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. txfertility.com at 0.4 s0.4 s
  2. txfertility.com at 0.8 s0.8 s
  3. txfertility.com at 1.1 s1.1 s
  4. txfertility.com at 1.5 s1.5 s
  5. txfertility.com at 1.9 s1.9 s
  6. txfertility.com at 2.3 s2.3 s
  7. txfertility.com at 2.6 s2.6 s
  8. txfertility.com at 3.0 s3.0 s

Speed

8 to fix59
  • Render-blocking requests

    2.3 s

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

  • Reduce unused JavaScript

    980 ms · 201 KiB

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

  • Mobile performance score: 59

    59/100

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

  • Improve image delivery

    510 KiB

    9 images could be 510 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Reduce unused CSS

    300 ms · 152 KiB

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

  • Google Tag Manager adds 260 ms

    260 ms

    Google Tag Manager costs a phone 260 ms of main-thread work and 319 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • 1,580 HTML elements

    The page has 1,580 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • FontAwesome CDN adds 24 ms

    24 ms

    FontAwesome CDN costs a phone 24 ms of main-thread work and 332 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • 7 third-party services on the page

    7 third-party services load with your homepage (Google Tag Manager, Hotjar and JSDelivr CDN and others), adding 977 KiB and 402 ms of main-thread time.

  • 5 long tasks on the main thread

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

  • Use efficient cache lifetimes

    100 ms · 21 KiB

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

  • Font display

    50 ms

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

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

  • Minify CSS

    5 KiB

    5 KiB could be saved by minifying CSS.

2 checks passed
  • Main-thread work: 1.7 s

    A phone's processor spends 1.7 s on main-thread work while loading, 562 ms of it running JavaScript. That is comfortably low.

  • Server response: 8 ms

    8 ms

    Your server sent the HTML in 8 ms, well inside Google's 600 ms guideline.

Core Web Vitals

6 to fix100
  • 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.

  • Largest Contentful Paint: 12.2 s

    12.2 s

    Your largest element takes 12.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Life’s Little Miracles Happen Here At Texas Fertility Cente…”.

  • First Contentful Paint: 5.3 s

    5.3 s

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

  • Time to Interactive: 12.3 s

    12.3 s

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

  • Speed Index: 6.1 s

    6.1 s

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

  • Real-user TTFB: 851 ms

    851 ms

    Real visitors wait 851 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Tap response (INP) held steady for real visitors

    +3%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 79 ms to 80 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) held steady for real visitors

    -2%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.8 s to 2.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

6 checks passed
  • Real-user LCP: 1.7 s

    1.7 s

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

  • Real-user INP: 64 ms

    64 ms

    Real visitors wait 64 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.04

    0.04

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

  • Real-user FCP: 1.5 s

    1.5 s

    Real visitors see the first content after 1.5 s (75th percentile). Good is under 1.8 s.

  • Total Blocking Time: 139 ms

    139 ms

    Scripts block the page for only 139 ms while loading. Good is under 200 ms.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

1 to fix85
  • Page weight: 2.2 MB in 81 requests

    2.2 MB

    Your homepage downloads 2.2 MB in 81 requests on a phone: images 1.0 MB (19), scripts 554 KiB (20) and fonts 407 KiB (18). Under 2 MB keeps phones on slow connections fast.

  • 3 images in older formats

    3 images (143 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.

  • About 0.6 g of CO₂ per visit

    0.63 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.63 g of CO₂e: 75.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

2 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

7 to fixGoogle 8892
  • 36 text elements with low contrast

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

  • 28 tap targets too small

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

  • All page content should be contained by landmarks (21 elements)

    All page content should be contained by landmarks: 21 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.

  • 18 links without text

    18 visible links have no text or label, so screen readers cannot say where they go.

  • 2 form fields without a label

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

  • ARIA role should be appropriate for the element (8 elements)

    ARIA role should be appropriate for the element: 8 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

    Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 60 images in the HTML carry an alt attribute.

  • 46 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 7 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 9288
  • Title is long (75 characters)

    Your title is 75 characters, so Google will cut it off around 60: “Austin Fertility Center - Male & Female Infertility - Central & South Texas”.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • 386 internal links, 25 external

    The homepage links to 386 pages on txfertility.com and 25 external pages.

6 checks passed
  • Meta description: 141 characters

    Your meta description is 141 characters: “Our Austin Fertility Center serves the Men and Women of Central Texas and South Texas. Voted Best Doctors in America fo…”.

  • One H1 headline

    Your main headline reads: “Dreams of Parenthood Come True at Our Texas Fertility Centers”.

  • Canonical URL set

    The canonical URL is https://txfertility.com/.

  • Structured data in place

    Structured data found: Article, ImageObject, MedicalClinic, Organization and Person.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://txfertility.com/sitemap.xml.

AI search readiness

100
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: 6 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,953 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://txfertility.com/llms.txt (54 KiB, 106 links, though it should open with a “# Title” line), a plain-text guide to the site for AI tools.

Other pages

4 to fix81
  • 2 pages share a title

    https://txfertility.com/getting-started-with-fertility-treatment and https://txfertility.com/getting-started all use the title “Getting Started with Fertility Treatment - Finding the Right Plan”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 2 pages share a meta description

    https://txfertility.com/getting-started-with-fertility-treatment and https://txfertility.com/getting-started use the same meta description. A description written for each page earns more clicks.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://txfertility.com/getting-started, whose canonical is https://txfertility.com/getting-started-with-fertility-treatment. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 4 pages without an H1

    https://txfertility.com/about-tfc/maps-directions, https://txfertility.com/fertility-blog, https://txfertility.com/videos and https://txfertility.com/trying-to-conceive have no <h1> headline, so visitors and search engines get no clear main topic.

  • 7 pages slow to respond

    https://txfertility.com/fertility-research, https://txfertility.com/make-payment, https://txfertility.com/getting-started-with-fertility-treatment, https://txfertility.com/getting-started-with-fertility-treatment/new-patient-registration-process, https://txfertility.com/videos and https://txfertility.com/getting-started and 1 other took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

4 checks passed
  • Linked pages load

    13 pages of 15 loaded without an error (the rest turned automated requests away).

  • Every page has a meta description

    All 13 pages that loaded have a meta description.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 13 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 27 small tap targets

    27 of 44 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

1 to fix94
  • Thin social proof

    Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

  • 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 1,084 words of copy

    The homepage carries about 1,084 words of visible text.

8 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Contact” and “Get Started Today!”.

  • 17 calls to action

    The homepage has 17 calls to action, for example “Contact”, “Get Started Today” and “Ovarian Reserve Testing”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

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

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Hotjar (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

  • 7 cookies set on arrival

    7

    Opening the homepage sets 7 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.

  • 11 other companies contacted

    Loading the homepage contacts 11 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

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 txfertility.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
Framework
jQuery
Analytics
Google Tag Manager

Company

Founded
1980

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 32 issues on txfertility.com, including 14 speed issues, 3 SEO issues and 1 conversion gap. 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25