Website review, no card needed

baby3d4d.com logo

baby3d4d.com website review

Visit site (opens in a new tab)Reviewed 17 November 202635 issues · 81 checks

This review found 35 issues worth fixing on baby3d4d.com, 8 of them high impact, across 81 checks. The most urgent: fails Core Web Vitals for real visitors. 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
875 ms531 msMay 30Nov 14623 ms
Show as table
DateReal-visitor load time (LCP)
May 30, 2026835 ms
Jun 6, 2026777 ms
Jun 13, 2026706 ms
Jun 20, 2026766 ms
Jun 27, 2026766 ms
Jul 4, 2026779 ms
Jul 11, 2026726 ms
Aug 22, 2026657 ms
Aug 29, 2026605 ms
Sep 5, 2026571 ms
Sep 12, 2026574 ms
Nov 14, 2026623 ms
Real-visitor tap response (INP)75th percentile, phones
101 ms85 msMay 30Sep 1295 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 202699 ms
Jun 6, 202696 ms
Jun 13, 202694 ms
Jun 20, 202695 ms
Jul 11, 202696 ms
Sep 5, 202687 ms
Sep 12, 202695 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 baby3d4d.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

7 to fix62
  • Mobile performance score: 62

    62/100

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

  • Improve image delivery

    872 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, leadconnectorhq.com and Facebook and others), adding 1.5 MB and 652 ms of main-thread time.

  • Reduce unused JavaScript

    580 KiB

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

  • Google Tag Manager adds 387 ms

    387 ms

    Google Tag Manager costs a phone 387 ms of main-thread work and 645 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.

  • Main-thread work: 2.3 s

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

  • leadconnectorhq.com adds 102 ms

    102 ms

    leadconnectorhq.com costs a phone 102 ms of main-thread work and 535 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.

  • 6 long tasks on the main thread

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

  • Use efficient cache lifetimes

    147 KiB

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

  • Reduce unused CSS

    32 KiB

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

  • Legacy JavaScript

    21 KiB

    Polyfills for old browsers add 21 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.

1 checks passed
  • Server response: 22 ms

    22 ms

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

Core Web Vitals

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

  • Time to Interactive: 15.8 s

    15.8 s

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

  • Cumulative Layout Shift: 0.456

    0.456

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

  • Largest Contentful Paint: 4.2 s

    4.2 s

    Your largest element takes 4.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

  • Real-user CLS: 0.11

    0.11

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

  • 6 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -7%

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

6 checks passed
  • Real-user LCP: 0.6 s

    0.6 s

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

  • Real-user FCP: 0.5 s

    0.5 s

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

  • Largest content (LCP) got 26% faster for real visitors

    -26%

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

  • Total Blocking Time: 194 ms

    194 ms

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

  • First Contentful Paint: 1.6 s

    1.6 s

    The first text or image appears after 1.6 s, inside the 1.8 s “good” threshold.

  • Speed Index: 3.0 s

    3.0 s

    Visually, the page fills in at 3.0 s (Speed Index), inside the 3.4 s “good” threshold.

Images and page weight

2 to fix81
  • Page weight: 3.1 MB in 104 requests

    3.1 MB

    Your homepage downloads 3.1 MB in 104 requests on a phone: images 1.4 MB (20), scripts 1.3 MB (56) and fonts 196 KiB (5). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    65ba8d5783daf26d2833db59.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • About 0.9 g of CO₂ per visit

    0.87 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

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

Accessibility

4 to fixGoogle 8793
  • 69 text elements with low contrast

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

  • Links must have discernible text (1 element)

    Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

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

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

  • 8 tap targets too small

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 24 images in the HTML carry an alt attribute.

  • 35 automated accessibility rules passed

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

SEO

5 to fixGoogle 10077
  • Title is short (19 characters)

    Your title is only 19 characters: “4D Special Delivery”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

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

  • 2 H1 headlines

    There are 2 <h1> headlines (“2D/3D/4D/HD Live Ultrasound” and “Heartwarming Teddies”). One clear main headline is easier for people and search engines.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • No social preview image

    No Open Graph image, 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.

  • 19 internal links, 5 external

    The homepage links to 19 pages on baby3d4d.com and 5 external pages.

3 checks passed
  • Meta description: 97 characters

    Your meta description is 97 characters: “Discover The Wonders Of Baby Ultrasounds And Connect With Your Baby In A World Of Magical Imaging”.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

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

AI search readiness

1 to fix88
  • 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://baby3d4d.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
  • 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 (1,135 words), so crawlers that don't run JavaScript still read it.

Other pages

5 to fix57
  • 1 linked page is broken

    Your homepage links to https://baby3d4d.com/privacy-policy, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 4 pages share a title

    /, https://baby3d4d.com/home, https://baby3d4d.com/locations and https://baby3d4d.com/3d-4d-ultrasound-palm-springs-prices all use the title “4D Special Delivery”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 1 page without a meta description

    https://baby3d4d.com/ultrasound-4d has no meta description, so Google writes the search snippet from whatever text it finds.

  • 5 pages share a meta description

    https://baby3d4d.com/home, https://baby3d4d.com/locations and https://baby3d4d.com/3d-4d-ultrasound-palm-springs-prices use the same meta description. A description written for each page earns more clicks.

  • 4 pages without an H1

    https://baby3d4d.com/faqs, https://baby3d4d.com/ultrasound, https://baby3d4d.com/ultrasound-4d and https://baby3d4d.com/hd-live-ultrasound 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 16 found) and read each the way a search engine does.

3 checks passed
  • Canonical URLs point to themselves

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

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 14 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9291
  • 1 small tap target

    1 of 5 tappable elements near the top of the page is smaller than 24 px, hard to hit with a thumb.

  • 4 distorted images

    4 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

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

3 to fix75
  • 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.

  • 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: 1 testimonial or review block. 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 1,123 words of copy

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

5 checks passed
  • 2 calls to action

    The homepage has 2 calls to action, for example “Book An Appointment!”.

  • Analytics in place

    Analytics detected: Google Tag Manager, Meta Pixel and Cloudflare Web Analytics.

  • Direct contact links

    Visitors can reach you directly: 3 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

  • 3 cookies set on arrival

    3

    Opening the homepage sets 3 cookies, 2 of them by other companies (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.

  • 5 other companies contacted

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

Upkeep, stack and company

Stack

Framework
Nuxt
Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 35 issues on baby3d4d.com, including 13 speed issues, 5 SEO issues and 3 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