Website review, no card needed

pregnancychoicesdirectory.com logo

pregnancychoicesdirectory.com website review

Visit site (opens in a new tab)Reviewed 11 November 202619 issues · 60 checks

This review found 19 issues worth fixing on pregnancychoicesdirectory.com, 3 of them high impact, across 60 checks. The most urgent: no call to action on the first screen. 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

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

How it loaded on a phone

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

Speed

4 to fix59
  • Mobile performance score: 59

    59/100

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

  • 4 third-party services on the page

    4 third-party services load with your homepage (Google Tag Manager, Clarity and JSDelivr CDN and others), adding 337 KiB and 765 ms of main-thread time.

  • Google Tag Manager adds 569 ms

    569 ms

    Google Tag Manager costs a phone 569 ms of main-thread work and 287 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 long tasks on the main thread

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

  • Reduce unused JavaScript

    139 KiB

    About 139 KiB of JavaScript is downloaded but never used on this page.

  • Reduce unused CSS

    32 KiB

    About 32 KiB of CSS is downloaded but never applied on this page.

  • Use efficient cache lifetimes

    13 KiB

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

  • Minify CSS

    7 KiB

    7 KiB could be saved by minifying CSS.

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

  • Document request latency

    5 KiB

    The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

  • 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: 1.3 s

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

  • Server response: 1 ms

    1 ms

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

Core Web Vitals

6 to fix57
  • Cumulative Layout Shift: 0.366

    0.366

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

  • Total Blocking Time: 512 ms

    512 ms

    Scripts block taps and scrolling for 512 ms in total while the page loads. Good is under 200 ms.

  • First Contentful Paint: 2.8 s

    2.8 s

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

  • Time to Interactive: 5.1 s

    5.1 s

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

  • Speed Index: 4.2 s

    4.2 s

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

  • Largest Contentful Paint: 2.8 s

    2.8 s

    Your largest element takes 2.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Stories and experiences of unplanned pregnancy, abortion, m…”. Most of its time is element render delay (2.2 s).

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Images and page weight

100
  • About 0.1 g of CO₂ per visit

    0.11 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.11 g of CO₂e: 12.6 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: 380 KiB in 13 requests

    380 KiB

    Your homepage downloads 380 KiB in 13 requests on a phone: scripts 334 KiB (5), stylesheets 34 KiB (1) and HTML 8 KiB (1). That is a lean page.

Accessibility

Google 100100
1 checks passed
  • 37 automated accessibility rules passed

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

SEO

2 to fixGoogle 10093
  • No structured data

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

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No X (Twitter) card tag

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

  • 20 internal links, 0 external

    The homepage links to 20 pages on pregnancychoicesdirectory.com and 0 external pages.

6 checks passed
  • Meta description: 152 characters

    Your meta description is 152 characters: “Experiencing difficulty around unplanned pregnancy, pre- or post-abortion, miscarriage or baby loss? Get free and confi…”.

  • One H1 headline

    Your main headline reads: “Stories and experiences of unplanned pregnancy, abortion, miscarriage and baby-loss”.

  • Title: 62 characters

    Your title is a healthy 62 characters: “Pregnancy Choices Directory - free help & counselling near you”.

  • Canonical URL set

    The canonical URL is https://www.pregnancychoicesdirectory.com/.

  • 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://www.pregnancychoicesdirectory.com/sitemap.xml.

AI search readiness

1 to fix83
  • 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.

  • No llms.txt

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

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

Other pages

1 to fix95
  • 9 pages without a meta description

    https://www.pregnancychoicesdirectory.com/peoplesstories/tags, https://www.pregnancychoicesdirectory.com/peoplesstories/abortion, https://www.pregnancychoicesdirectory.com/peoplesstories/adoption, https://www.pregnancychoicesdirectory.com/peoplesstories/babyloss, https://www.pregnancychoicesdirectory.com/peoplesstories/crisispregnancy and https://www.pregnancychoicesdirectory.com/peoplesstories/keepingmybaby and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 4 pages with very little text

    https://www.pregnancychoicesdirectory.com/peoplesstories, https://www.pregnancychoicesdirectory.com/info, https://www.pregnancychoicesdirectory.com/about and https://www.pregnancychoicesdirectory.com/contact have 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 and read each the way a search engine does.

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

  • 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

Google 100100
3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    17 of 17 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix50
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • Only about 95 words

    The homepage has only about 95 words of visible text; thin pages give Google and first-time buyers little to go on.

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

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

2 checks passed
  • 1 call to action

    The homepage has 1 call to action, for example “Contact Admin”.

  • Analytics in place

    Analytics detected: Google Analytics and Microsoft Clarity.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager and Microsoft Clarity (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.

  • 4 cookies set on arrival

    4

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

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 pregnancychoicesdirectory.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Analytics
Google Analytics | Microsoft Clarity
Hosting
Iomart As Iomart Cloud Services Limited

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 19 issues on pregnancychoicesdirectory.com, including 10 speed issues, 2 SEO issues and 4 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

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