Website review, no card needed

yourbabyscan.com logo

yourbabyscan.com website review

Visit site (opens in a new tab)Reviewed 13 November 202637 issues · 85 checks

This review found 37 issues worth fixing on yourbabyscan.com, 18 of them high impact, across 85 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
2.9 s1.5 sMay 23Nov 72.8 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20261.9 s
May 30, 20261.9 s
Jun 6, 20262.0 s
Jun 13, 20261.9 s
Jun 20, 20262.0 s
Jun 27, 20262.0 s
Jul 4, 20261.8 s
Jul 11, 20261.8 s
Jul 18, 20261.7 s
Jul 25, 20261.6 s
Aug 1, 20261.7 s
Aug 8, 20261.9 s
Aug 15, 20262.0 s
Aug 22, 20262.3 s
Aug 29, 20262.2 s
Sep 5, 20261.9 s
Sep 12, 20261.9 s
Sep 19, 20261.7 s
Sep 26, 20261.7 s
Oct 3, 20261.7 s
Oct 10, 20261.8 s
Oct 17, 20261.9 s
Oct 24, 20262.3 s
Oct 31, 20262.6 s
Nov 7, 20262.8 s
Real-visitor tap response (INP)75th percentile, phones
106 ms90 msMay 23Nov 796 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 202697 ms
May 30, 202697 ms
Jun 6, 202695 ms
Jun 13, 202695 ms
Jun 20, 202699 ms
Jun 27, 2026100 ms
Jul 4, 202695 ms
Jul 11, 202695 ms
Jul 18, 202692 ms
Jul 25, 202692 ms
Aug 1, 202697 ms
Aug 8, 202697 ms
Aug 15, 202699 ms
Aug 22, 2026104 ms
Aug 29, 2026102 ms
Sep 5, 202698 ms
Sep 12, 202699 ms
Sep 19, 202696 ms
Sep 26, 202696 ms
Oct 3, 202697 ms
Oct 10, 202697 ms
Oct 17, 2026101 ms
Oct 24, 202698 ms
Oct 31, 202696 ms
Nov 7, 202696 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 yourbabyscan.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. yourbabyscan.com at 0.5 s0.5 s
  2. yourbabyscan.com at 1.0 s1.0 s
  3. yourbabyscan.com at 1.5 s1.5 s
  4. yourbabyscan.com at 2.0 s2.0 s
  5. yourbabyscan.com at 2.5 s2.5 s
  6. yourbabyscan.com at 3.0 s3.0 s
  7. yourbabyscan.com at 3.5 s3.5 s
  8. yourbabyscan.com at 4.0 s4.0 s

Speed

8 to fix33
  • Render-blocking requests

    2.3 s

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

  • Use efficient cache lifetimes

    1.9 s · 293 KiB

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

  • Reduce unused JavaScript

    1.4 s · 296 KiB

    About 296 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.4 s faster on a phone.

  • Reduce unused CSS

    1.1 s · 336 KiB

    About 336 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.

  • Mobile performance score: 33

    33/100

    Your mobile performance score is 33. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Improve image delivery

    850 ms · 146 KiB

    5 images could be 146 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 850 ms faster on a phone.

  • 8 third-party services on the page

    8 third-party services load with your homepage (cloudfront.net, tailwindcss.com and Google Tag Manager and others), adding 729 KiB and 546 ms of main-thread time.

  • Main-thread work: 2.6 s

    A phone's processor spends 2.6 s on main-thread work while loading, 1.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • 8 long tasks on the main thread

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

  • Legacy JavaScript

    10 KiB

    Polyfills for old browsers add 10 KiB JavaScript that modern phones do not need.

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

    2 KiB

    2 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 42 ms

    42 ms

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

Core Web Vitals

8 to fix100
  • Largest Contentful Paint: 23.9 s

    23.9 s

    Your largest element takes 23.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Making Memories We believe that pregnancy is an amazing and…”.

  • Time to Interactive: 24.8 s

    24.8 s

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

  • First Contentful Paint: 5.0 s

    5.0 s

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

  • Speed Index: 9.2 s

    9.2 s

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

  • Cumulative Layout Shift: 0.4

    0.4

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

  • Largest content (LCP) got 44% slower for real visitors

    +44%

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

  • Total Blocking Time: 285 ms

    285 ms

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

  • 18 images without width and height

    18 images have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) held steady for real visitors

    -1%

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

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

    1.8 s

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

  • Real-user INP: 111 ms

    111 ms

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

  • Real-user CLS: 0.03

    0.03

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

  • Real-user FCP: 1.2 s

    1.2 s

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

  • Real-user TTFB: 352 ms

    352 ms

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

Images and page weight

5 to fix18
  • Page weight: 7.3 MB in 123 requests

    7.3 MB

    Your homepage downloads 7.3 MB in 123 requests on a phone: images 5.8 MB (34), scripts 1.1 MB (45) and stylesheets 236 KiB (21). Under 2 MB keeps phones on slow connections fast.

  • 5 images far larger than shown

    1.8 MB

    5 images are downloaded at several times the size a phone draws them, for example woman-in-grass-2023-11-27-05-07-06-utc-scaled-1.jpg at 2,560 px wide, shown at 312 px. Resized copies would save about 1.8 MB.

  • 1 image over 500 KB

    woman-in-grass-2023-11-27-05-07-06-utc-scaled-1.jpg weighs 1.0 MB. On a phone connection a single image that size takes seconds.

  • 7 images in older formats

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

  • 8 images below the first screen load straight away

    8 images further down the page (2.2 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 2.1 g of CO₂ per visit

    2.06 g

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

Accessibility

8 to fixGoogle 7889
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

    All page content should be contained by landmarks: 13 elements on the page fail this check, rated moderate by axe-core.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 16 tap targets too small

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

  • 2 links without text

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

  • Headings should not be empty (9 elements)

    Headings should not be empty: 9 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

    Headings skip levels (h1 → h3, h3 → h6 and h3 → h6), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 26 images in the HTML carry an alt attribute.

  • 42 automated accessibility rules passed

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

SEO

3 to fixGoogle 10088
  • Structured data has 1 problem

    Structured data found (ImageObject, MedicalClinic, MedicalOrganization and Organization) but with 1 problem, for example “MedicalOrganization: sameAs is an empty list”.

  • No XML sitemap

    No XML sitemap at https://www.yourbabyscan.com/sitemap.xml, so Google discovers your pages only by following links.

  • No robots.txt

    There is no robots.txt at yourbabyscan.com/robots.txt, the first file search crawlers ask for.

  • 69 internal links, 12 external

    The homepage links to 69 pages on yourbabyscan.com and 12 external pages.

5 checks passed
  • Meta description: 152 characters

    Your meta description is 152 characters: “Award-winning private baby scans in Widnes and Crewe, Cheshire. Early pregnancy, gender and 4D scans by HCPC registered…”.

  • One H1 headline

    Your main headline reads: “Ultrasound scans for every stage of pregnancy | Your Baby Scan”.

  • Title: 53 characters

    Your title is a healthy 53 characters: “Private Baby Scans in Widnes & Crewe | Your Baby Scan”.

  • Canonical URL set

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

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

AI search readiness

100
  • No llms.txt

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

2 checks passed
  • 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 (2,743 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 1 page without an H1

    https://www.yourbabyscan.com/contact has 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 43 found) and read each the way a search engine does.

6 checks passed
  • Linked pages load

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

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 3 pages that loaded have a meta description.

  • 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 3 pages that loaded have a <title>.

Best practices

3 to fixGoogle 9671
  • 1 broken image

    1 image failed to load on a phone, for example https://www.yourbabyscan.com/wp-content/uploads/2025/07/Cheshire-Bloods-Clinic-Logo-768x280.webp.

  • 4 small tap targets

    4 of 13 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 “Failed to load resource: the server responded with a status of 403 ()”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix88
  • 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 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 2,666 words of copy

    The homepage carries about 2,666 words of visible text.

7 checks passed
  • 3 calls to action

    The homepage has 3 calls to action, for example “Contact”, “Book now” and “Book now 5”.

  • 2 short forms

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

  • Social proof on the page

    Social proof on the homepage: 9 testimonial or review blocks and 2 trust badges.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 1 email link.

  • 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

  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (measured from a US location before any click). A consent tool (Termly) is installed; check it blocks these until visitors agree where the law requires it.

  • 4 cookies set on arrival

    4

    Opening the homepage sets 4 cookies (measured from a US location before any click).

  • 15 other companies contacted

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

1 checks passed
  • Consent tool: Termly

    A consent management tool (Termly) loads with the page.

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 yourbabyscan.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 Analytics
Hosting
20i Limited

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 yourbabyscan.com, including 16 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