Website review, no card needed

allthebabynames.com logo

allthebabynames.com website review

Visit site (opens in a new tab)Reviewed 11 November 202637 issues · 87 checks

This review found 37 issues worth fixing on allthebabynames.com, 14 of them high impact, across 87 checks. The most urgent: improve image delivery. 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
5.0 s3.2 sMay 23Nov 73.7 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20264.2 s
May 30, 20263.9 s
Jun 6, 20263.9 s
Jun 13, 20264.0 s
Jun 20, 20264.0 s
Jun 27, 20264.1 s
Jul 4, 20264.3 s
Jul 11, 20264.0 s
Jul 18, 20264.2 s
Jul 25, 20263.7 s
Aug 1, 20263.6 s
Aug 8, 20263.5 s
Aug 15, 20263.4 s
Aug 22, 20263.7 s
Aug 29, 20264.0 s
Sep 5, 20264.2 s
Sep 12, 20264.2 s
Sep 19, 20264.6 s
Sep 26, 20264.3 s
Oct 3, 20264.8 s
Oct 10, 20264.2 s
Oct 17, 20263.5 s
Oct 24, 20263.5 s
Oct 31, 20263.5 s
Nov 7, 20263.7 s
Real-visitor tap response (INP)75th percentile, phones
235 ms114 msMay 23Nov 7128 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026145 ms
May 30, 2026134 ms
Jun 6, 2026134 ms
Jun 13, 2026134 ms
Jun 20, 2026135 ms
Jun 27, 2026177 ms
Jul 4, 2026177 ms
Jul 11, 2026195 ms
Jul 18, 2026195 ms
Jul 25, 2026168 ms
Aug 1, 2026153 ms
Aug 8, 2026147 ms
Aug 15, 2026144 ms
Aug 22, 2026143 ms
Aug 29, 2026152 ms
Sep 5, 2026146 ms
Sep 12, 2026164 ms
Sep 19, 2026212 ms
Sep 26, 2026217 ms
Oct 3, 2026221 ms
Oct 10, 2026168 ms
Oct 17, 2026155 ms
Oct 24, 2026141 ms
Oct 31, 2026130 ms
Nov 7, 2026128 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 allthebabynames.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. allthebabynames.com at 0.9 s0.9 s
  2. allthebabynames.com at 1.9 s1.9 s
  3. allthebabynames.com at 2.8 s2.8 s
  4. allthebabynames.com at 3.7 s3.7 s
  5. allthebabynames.com at 4.7 s4.7 s
  6. allthebabynames.com at 5.6 s5.6 s
  7. allthebabynames.com at 6.5 s6.5 s
  8. allthebabynames.com at 7.5 s7.5 s

Speed

9 to fix57
  • Improve image delivery

    2.3 s · 415 KiB

    2 images could be 415 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.3 s faster on a phone.

  • Reduce unused JavaScript

    1.8 s · 375 KiB

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

  • Use efficient cache lifetimes

    1.5 s · 286 KiB

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

  • Render-blocking requests

    1.4 s

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

  • Mobile performance score: 57

    57/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google/Doubleclick Ads, Google Tag Manager and Google CDN and others), adding 1.1 MB and 548 ms of main-thread time.

  • Reduce unused CSS

    450 ms · 111 KiB

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

  • Google/Doubleclick Ads adds 361 ms

    361 ms

    Google/Doubleclick Ads costs a phone 361 ms of main-thread work and 441 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.8 s

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

  • 4 long tasks on the main thread

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

  • Minify CSS

    12 KiB

    12 KiB could be saved by minifying CSS.

  • Minify JavaScript

    6 KiB

    6 KiB could be saved by minifying JavaScript.

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

1 checks passed
  • Server response: 114 ms

    114 ms

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

Core Web Vitals

9 to fix33
  • 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.

  • Real-user CLS: 0.40

    0.40

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

  • Real-user FCP: 3.0 s

    3.0 s

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

  • Largest Contentful Paint: 11.7 s

    11.7 s

    Your largest element takes 11.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Expecting parents smiling together while choosing a name fo…”.

  • First Contentful Paint: 5.1 s

    5.1 s

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

  • Speed Index: 9.7 s

    9.7 s

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

  • Time to Interactive: 12.2 s

    12.2 s

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

  • Real-user LCP: 3.6 s

    3.6 s

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

  • Real-user TTFB: 1.8 s

    1.8 s

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

  • Tap response (INP) held steady for real visitors

    -8%

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

4 checks passed
  • Real-user INP: 128 ms

    128 ms

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

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

    -12%

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

  • Cumulative Layout Shift: 0.021

    0.021

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

  • Total Blocking Time: 19 ms

    19 ms

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

Images and page weight

2 to fix75
  • Page weight: 3.0 MB in 105 requests

    3.0 MB

    Your homepage downloads 3.0 MB in 105 requests on a phone: media 1.1 MB (1), scripts 798 KiB (36) and images 468 KiB (10). Under 2 MB keeps phones on slow connections fast.

  • 2 images far larger than shown

    115 KiB

    2 images are downloaded at several times the size a phone draws them, for example all-the-baby-names.jpg at 1,200 px wide, shown at 387 px. Resized copies would save about 115 KiB.

  • 2 images in older formats

    2 images (450 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.9 g of CO₂ per visit

    0.86 g

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

1 checks passed
  • Images load when needed

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

Accessibility

8 to fixGoogle 8690
  • 1 button without a name

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

  • 4 text elements with low contrast

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

  • Inline text spacing must be adjustable with custom stylesheets (1 element)

    Inline text spacing must be adjustable with custom stylesheets: 1 element on the page fails this check, rated serious by axe-core.

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

    All page content should be contained by landmarks: 11 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 (3 elements)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 3 elements on the page fail this check, rated moderate by axe-core.

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • 5 links without text

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 5 images in the HTML carry an alt attribute.

  • 45 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: 45 passed and 8 failed. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 9295
  • No social preview image

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

  • 2 links crawlers can't follow

    2 links have no real href, so search engines can't follow them.

  • 181 internal links, 9 external

    The homepage links to 181 pages on allthebabynames.com and 9 external pages.

7 checks passed
  • Meta description: 114 characters

    Your meta description is 114 characters: “Discover the perfect baby name. Explore 10,000+ popular, unique, and religious names from 50+ cultures. 100% free.”.

  • One H1 headline

    Your main headline reads: “Find the perfect name for your baby”.

  • Title: 50 characters

    Your title is a healthy 50 characters: “All The Baby Names - Names with Meanings & Origins”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: Article, Organization, Person, 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://allthebabynames.com/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (2 of 6 facts)

    Your Organization JSON-LD is missing url, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • Opted out of AI training for 1 crawler

    robots.txt blocks CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

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 (1,061 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

1 to fix95
  • 3 pages without a meta description

    https://allthebabynames.com/popular-baby-names/baby-names-for-boys, https://allthebabynames.com/popular-baby-names/baby-names-for-girls and https://allthebabynames.com/unique-baby-names have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 41 found) 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

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • 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 direct contact details

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

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • 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 537 words of copy

    The homepage carries about 537 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “CONTACT US”.

  • 3 calls to action

    The homepage has 3 calls to action, for example “Contact us”.

  • 3 short forms

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

  • Analytics in place

    Analytics detected: Google Analytics.

Privacy and tracking

1 to fix
  • 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). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

  • 8 cookies set on arrival

    8

    Opening the homepage sets 8 cookies, 1 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.

  • 12 other companies contacted

    Loading the homepage contacts 12 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 allthebabynames.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
Hawk Host Inc.

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 allthebabynames.com, including 18 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