Website review, no card needed
babyshop.com website review
Visit site (opens in a new tab)Reviewed 28 October 202638 issues · 85 checks
This review found 38 issues worth fixing on babyshop.com, 12 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.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
67DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 2.0 s |
| May 16, 2026 | 2.1 s |
| May 23, 2026 | 2.1 s |
| May 30, 2026 | 2.1 s |
| Jun 6, 2026 | 2.1 s |
| Jun 13, 2026 | 2.1 s |
| Jun 20, 2026 | 2.1 s |
| Jun 27, 2026 | 2.1 s |
| Jul 4, 2026 | 2.2 s |
| Jul 11, 2026 | 2.2 s |
| Jul 18, 2026 | 2.2 s |
| Jul 25, 2026 | 2.2 s |
| Aug 1, 2026 | 2.2 s |
| Aug 8, 2026 | 2.1 s |
| Aug 15, 2026 | 2.1 s |
| Aug 22, 2026 | 2.0 s |
| Aug 29, 2026 | 2.0 s |
| Sep 5, 2026 | 2.0 s |
| Sep 12, 2026 | 2.1 s |
| Sep 19, 2026 | 2.1 s |
| Sep 26, 2026 | 2.1 s |
| Oct 3, 2026 | 2.1 s |
| Oct 10, 2026 | 2.2 s |
| Oct 17, 2026 | 2.2 s |
| Oct 24, 2026 | 2.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 129 ms |
| May 16, 2026 | 128 ms |
| May 23, 2026 | 128 ms |
| May 30, 2026 | 128 ms |
| Jun 6, 2026 | 129 ms |
| Jun 13, 2026 | 129 ms |
| Jun 20, 2026 | 131 ms |
| Jun 27, 2026 | 136 ms |
| Jul 4, 2026 | 139 ms |
| Jul 11, 2026 | 144 ms |
| Jul 18, 2026 | 145 ms |
| Jul 25, 2026 | 146 ms |
| Aug 1, 2026 | 147 ms |
| Aug 8, 2026 | 147 ms |
| Aug 15, 2026 | 148 ms |
| Aug 22, 2026 | 149 ms |
| Aug 29, 2026 | 149 ms |
| Sep 5, 2026 | 148 ms |
| Sep 12, 2026 | 146 ms |
| Sep 19, 2026 | 145 ms |
| Sep 26, 2026 | 145 ms |
| Oct 3, 2026 | 146 ms |
| Oct 10, 2026 | 147 ms |
| Oct 17, 2026 | 147 ms |
| Oct 24, 2026 | 150 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
How it loaded on a phone
0.7 s
1.4 s
2.1 s
2.8 s
3.5 s
4.2 s
4.9 s
5.6 s
Speed
Render-blocking requests
1.6 s6 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.6 s.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and Hotjar and others), adding 1.6 MB and 951 ms of main-thread time.
Reduce unused JavaScript
300 ms · 773 KiBAbout 773 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.
Mobile performance score: 53
53/100Your mobile performance score is 53 (desktop: 66). Pages that score under 90 lose visitors before the first paint.
Google Tag Manager adds 347 ms
347 msGoogle Tag Manager costs a phone 347 ms of main-thread work and 524 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.
Use efficient cache lifetimes
389 KiB16 files are served with short cache lifetimes, so returning visitors download them again (389 KiB).
Main-thread work: 3.8 s
A phone's processor spends 3.8 s on main-thread work while loading, 2.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Legacy JavaScript
300 ms · 46 KiBPolyfills for old browsers add 46 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.
18 long tasks on the main thread
18 long tasks block the main thread while loading, the longest for 202 ms. During a long task the page ignores taps.
Reduce unused CSS
150 ms · 47 KiBAbout 47 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Duplicated JavaScript
11 KiB11 KiB JavaScript is shipped twice across bundles.
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.
Minify JavaScript
5 KiB5 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 6 ms
6 msYour server sent the HTML in 6 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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.34
0.34For real visitors the layout shifts by 0.34 (75th percentile). Good is under 0.1.
Time to Interactive: 21.0 s
21.0 sThe page becomes fully interactive after 21.0 s. Good is under 3.8 s.
Largest Contentful Paint: 6.6 s
6.6 sYour largest element takes 6.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We’re temporarily unable to ship to the United States due t…”.
Total Blocking Time: 857 ms
857 msScripts block taps and scrolling for 857 ms in total while the page loads. Good is under 200 ms.
First Contentful Paint: 2.4 s
2.4 sThe first text or image appears after 2.4 s on a phone. Good is under 1.8 s.
Tap response (INP) got 16% slower for real visitors
+16%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 129 ms to 150 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 11% slower for real visitors
+11%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.0 s to 2.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user LCP: 2.3 s
2.3 sReal visitors wait 2.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 149 ms
149 msReal visitors wait 149 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 1.1 s
1.1 sReal visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 367 ms
367 msReal visitors wait 367 ms for your server to start answering (75th percentile). Good is under 800 ms.
Speed Index: 2.8 s
2.8 sVisually, the page fills in at 2.8 s (Speed Index), inside the 3.4 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 2.6 MB in 122 requests
2.6 MBYour homepage downloads 2.6 MB in 122 requests on a phone: scripts 2.1 MB (67), fonts 306 KiB (8) and other files 104 KiB (23). Under 2 MB keeps phones on slow connections fast.
About 0.7 g of CO₂ per visit
0.74 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.74 g of CO₂e: 88.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
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
Elements must only use permitted ARIA attributes (2 elements)
Elements must only use permitted ARIA attributes: 2 elements on the page fail this check, rated serious by axe-core.
1 tap target too small
1 tap target is too small or too close together to hit reliably with a finger.
All page content should be contained by landmarks (15 elements)
All page content should be contained by landmarks: 15 elements on the page fail this check, rated moderate by axe-core.
Heading levels should only increase by one (1 element)
Heading levels should only increase by one: 1 element on the page fails 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.
4 form fields without a label
4 form fields have no label, so screen readers announce an empty box and autofill guesses.
3 links without text
3 visible links have no text or label, so screen readers cannot say where they go.
2 checks passed
Every image has alt text
All 6 images in the HTML carry an alt attribute.
43 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: 43 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
Page is set to noindex
The robots meta tag says “noindex, nofollow”: Google is told not to list this page at all.
Blocked from indexing
Google's crawler is blocked from indexing this page.
Title is long (87 characters)
Your title is 87 characters, so Google will cut it off around 60: “Market Closed | Babyshop - Shop premium children's clothes and baby gear - Babyshop.com”.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
Meta description is long (163 characters)
Your meta description is 163 characters; Google truncates after about 160, so the end of your pitch is cut.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
35 internal links, 6 external
The homepage links to 35 pages on babyshop.com and 6 external pages.
4 checks passed
One H1 headline
Your main headline reads: “We’ll be back soon”.
Canonical URL set
The canonical URL is https://www.babyshop.com/en-us.
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.babyshop.com/sitemap.xml.
AI search readiness
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.babyshop.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.
Opted out of AI training for 5 crawlers
robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and 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.
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 (263 words), so crawlers that don't run JavaScript still read it.
Other pages
14 linked pages hidden from search
https://www.babyshop.com/en-us/customer-service/contact-us, https://www.babyshop.com/en-us/offers/main-offer, https://www.babyshop.com/en-us/us, https://www.babyshop.com/en-us/news, https://www.babyshop.com/en-us/outerwear and https://www.babyshop.com/en-us/clothing and 8 others are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.
15 pages share a title
https://www.babyshop.com/en-us, https://www.babyshop.com/en-us/customer-service/contact-us, https://www.babyshop.com/en-us/offers/main-offer, https://www.babyshop.com/en-us/us, https://www.babyshop.com/en-us/news and https://www.babyshop.com/en-us/outerwear and 9 others all use the title “Market Closed | Babyshop - Shop premium children's clothes and baby g…”. Search engines can't tell which page to show for a search, so each competes with the others.
14 pages share a meta description
https://www.babyshop.com/en-us/customer-service/contact-us, https://www.babyshop.com/en-us/offers/main-offer, https://www.babyshop.com/en-us/us, https://www.babyshop.com/en-us/news, https://www.babyshop.com/en-us/outerwear and https://www.babyshop.com/en-us/clothing and 8 others use the same meta description. A description written for each page earns more clicks.
1 page slow to respond
https://www.babyshop.com/en-us/information/about-babyshop took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 21 found) and read each the way a search engine does.
5 checks passed
Linked pages load
14 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 14 pages that loaded have a meta description.
Every page has an H1
Each page we checked has a main headline.
Every page has a title
All 14 pages that loaded have a <title>.
Best practices
1 broken image
1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=5750944&Ver=2&mid=357d02cf-aba6-49e0-b41a-6d57ad3b215c&bo=1&sid=ba9075a0d29511f1b8b8638342ccb802&vid=ba90a460d29511f19fc1836b149f2287&vids=1&msclkid=N&pi=918639831&lg=.
12 small tap targets
12 of 25 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
6 JavaScript errors while loading
6 errors were 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
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 224 words
The homepage has only about 224 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Contact us” and “Sign up”.
5 calls to action
The homepage has 5 calls to action, for example “Contact us” and “Sign up”.
2 short forms
2 short forms (1 field at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Meta Pixel and 2 mores (measured from a US location before any click). A consent tool (Usercentrics) is installed; check it blocks these until visitors agree where the law requires it.
20 cookies set on arrival
20Opening the homepage sets 20 cookies (measured from a US location before any click).
33 other companies contacted
Loading the homepage contacts 33 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Usercentrics
A consent management tool (Usercentrics) 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 babyshop.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Hosting
- AWS
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 38 issues on babyshop.com, including 14 speed issues, 6 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.