Website review, no card needed

babychakra.com logo

babychakra.com website review

Visit site (opens in a new tab)Reviewed 23 October 202628 issues · 78 checks

This review found 28 issues worth fixing on babychakra.com, 11 of them high impact, across 78 checks. The most urgent: page weight: 5.0 MB in 72 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
1.6 s1.2 sMay 2Oct 171.3 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20261.4 s
May 9, 20261.5 s
May 16, 20261.5 s
May 23, 20261.5 s
May 30, 20261.5 s
Jun 6, 20261.4 s
Jun 13, 20261.4 s
Jun 20, 20261.4 s
Jun 27, 20261.4 s
Jul 4, 20261.5 s
Jul 11, 20261.4 s
Jul 18, 20261.3 s
Jul 25, 20261.3 s
Aug 1, 20261.3 s
Aug 8, 20261.3 s
Aug 15, 20261.4 s
Aug 22, 20261.4 s
Aug 29, 20261.4 s
Sep 5, 20261.4 s
Sep 12, 20261.4 s
Sep 19, 20261.3 s
Sep 26, 20261.3 s
Oct 3, 20261.3 s
Oct 10, 20261.3 s
Oct 17, 20261.3 s
Real-visitor tap response (INP)75th percentile, phones
85 ms60 msMay 2Sep 2670 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 202671 ms
May 9, 202670 ms
May 16, 202673 ms
May 23, 202678 ms
May 30, 202681 ms
Jun 6, 202682 ms
Jun 13, 202676 ms
Jun 20, 202671 ms
Jun 27, 202664 ms
Jul 4, 202670 ms
Jul 11, 202670 ms
Jul 18, 202669 ms
Jul 25, 202673 ms
Aug 1, 202670 ms
Aug 8, 202674 ms
Aug 22, 202672 ms
Aug 29, 202663 ms
Sep 12, 202669 ms
Sep 19, 202674 ms
Sep 26, 202670 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 babychakra.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

2 to fix97
  • Improve image delivery

    4.5 MB

    11 images could be 4.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Use efficient cache lifetimes

    150 ms · 3.3 MB

    36 files are served with short cache lifetimes, so returning visitors download them again (3.3 MB).

  • Legacy JavaScript

    150 ms · 18 KiB

    Polyfills for old browsers add 18 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • Render-blocking requests

    150 ms

    4 files block the first paint until they finish downloading. Deferring or inlining them could save about 150 ms.

  • Reduce unused CSS

    110 ms · 28 KiB

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

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 59 ms. During a long task the page ignores taps.

  • Reduce unused JavaScript

    36 KiB

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

  • 1 third-party service on the page

    1 third-party service load with your homepage (Cloudflare), adding 10 KiB and 19 ms of main-thread time.

  • Minify JavaScript

    14 KiB

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

3 checks passed
  • Mobile performance score: 97

    97/100

    Your mobile performance score is 97 (desktop: 99). That is in Google's “good” band (90 and up).

  • Main-thread work: 0.8 s

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

  • Server response: 4 ms

    4 ms

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

Core Web Vitals

2 to fix100
  • 22 images without width and height

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

  • First Contentful Paint: 1.8 s

    1.8 s

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

  • Tap response (INP) held steady for real visitors

    +2%

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

  • Largest content (LCP) held steady for real visitors

    -9%

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

10 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.3 s

    1.3 s

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 1.3 s

    1.3 s

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

  • Real-user TTFB: 691 ms

    691 ms

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

  • Cumulative Layout Shift: 0.068

    0.068

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

  • Largest Contentful Paint: 2.0 s

    2.0 s

    Your largest element renders in 2.0 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “BabyChakra’s Bamboo Water Wipes with Bamboo Fiber, Aloe Ver…”.

  • Speed Index: 2.3 s

    2.3 s

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

  • Time to Interactive: 2.0 s

    2.0 s

    The page is fully interactive after 2.0 s.

  • Total Blocking Time: 0 ms

    0 ms

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

Images and page weight

5 to fix18
  • Page weight: 5.0 MB in 72 requests

    5.0 MB

    Your homepage downloads 5.0 MB in 72 requests on a phone: images 4.7 MB (23), scripts 149 KiB (38) and fonts 81 KiB (6). Under 2 MB keeps phones on slow connections fast.

  • 11 images far larger than shown

    3.8 MB

    11 images are downloaded at several times the size a phone draws them, for example 2240x614-(4).gif at 2,240 px wide, shown at 374 px. Resized copies would save about 3.8 MB.

  • 2 images over 500 KB

    2 images weigh 2.6 MB together. On a phone connection a single image that size takes seconds.

  • 11 images in older formats

    11 images (4.6 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.

  • 3 images below the first screen load straight away

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

  • About 1.4 g of CO₂ per visit

    1.41 g

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

Accessibility

7 to fixGoogle 8589
  • 2 buttons without a name

    2 buttons have 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.

  • <svg> elements with an img or image role must have alternative text (1 element)

    <svg> elements with an img or image role must have alternative text: 1 element on the page fails 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.

  • Zoom is disabled

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

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

2 checks passed
  • Every image has alt text

    All 22 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 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 6 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 10074
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is long (82 characters)

    Your title is 82 characters, so Google will cut it off around 60: “Parenting & BabyCare Tips by Experts, Shop Baby & Mom Products Online - BabyChakra”.

  • Meta description is long (204 characters)

    Your meta description is 204 characters; Google truncates after about 160, so the end of your pitch is cut.

  • Structured data has 2 problems

    Structured data found ((untyped) and WebSite) but with 2 problems, for example “untyped block: missing @context (expected "https://schema.org")”.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

  • 111 internal links, 7 external

    The homepage links to 111 pages on babychakra.com and 7 external pages.

4 checks passed
  • Canonical URL set

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

  • Open Graph tags complete

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

  • 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.babychakra.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://www.babychakra.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 (409 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix0
  • 15 linked pages are broken

    Your homepage links to https://www.babychakra.com/shopping-bag, https://www.babychakra.com/live-doctor-chat, https://www.babychakra.com/learn, https://www.babychakra.com/collection/view-all-products, https://www.babychakra.com/buy/baby-care/bath-body and https://www.babychakra.com/buy/baby-care/health-safety and 9 others, which answer with an error. Visitors hit a dead end and search engines drop them.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 84 found) and read each the way a search engine does.

Best practices

5 to fixGoogle 6962
  • 7 broken images

    7 images failed to load on a phone, for example https://www.babychakra.com/files-sub/site-images/original/new-bbc-logo.png.

  • Scrolls sideways on phones

    On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.

  • 8 small tap targets

    8 of 39 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Mixed content”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix83
  • 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 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 323 words of copy

    The homepage carries about 323 words of visible text.

5 checks passed
  • Clear next step on the first screen

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

  • 5 calls to action

    The homepage has 5 calls to action, for example “Shop”, “Shop From Categories” and “SIGN UP NOW”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager and Cloudflare Web Analytics.

  • Direct contact links

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

Privacy and tracking

  • 2 cookies set on arrival

    2

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

  • 3 other companies contacted

    Loading the homepage contacts 3 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 babychakra.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
Next.js

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 28 issues on babychakra.com, including 4 speed issues, 4 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