Website review, no card needed
babyforest.in website review
Visit site (opens in a new tab)Reviewed 8 November 202632 issues · 84 checks
This review found 32 issues worth fixing on babyforest.in, 9 of them high impact, across 84 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
79C- #56,263 of 126,333 reviewed websitesbeats 50%
- #36,691 of 70,435 online storesbeats 42%
- #35,123 of 63,941 Shopify storesbeats 39%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 3.1 s |
| May 23, 2026 | 3.1 s |
| May 30, 2026 | 3.2 s |
| Jun 6, 2026 | 3.4 s |
| Jun 13, 2026 | 3.5 s |
| Jun 20, 2026 | 3.5 s |
| Jun 27, 2026 | 3.5 s |
| Jul 4, 2026 | 3.5 s |
| Jul 11, 2026 | 3.6 s |
| Jul 18, 2026 | 3.7 s |
| Jul 25, 2026 | 4.0 s |
| Aug 1, 2026 | 4.0 s |
| Aug 8, 2026 | 4.0 s |
| Aug 15, 2026 | 4.1 s |
| Aug 22, 2026 | 4.1 s |
| Aug 29, 2026 | 4.2 s |
| Sep 5, 2026 | 4.3 s |
| Sep 12, 2026 | 4.2 s |
| Sep 19, 2026 | 4.3 s |
| Sep 26, 2026 | 4.3 s |
| Oct 3, 2026 | 4.3 s |
| Oct 10, 2026 | 4.2 s |
| Oct 17, 2026 | 4.1 s |
| Oct 24, 2026 | 3.9 s |
| Oct 31, 2026 | 3.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 199 ms |
| May 23, 2026 | 200 ms |
| May 30, 2026 | 203 ms |
| Jun 6, 2026 | 210 ms |
| Jun 13, 2026 | 212 ms |
| Jun 20, 2026 | 213 ms |
| Jun 27, 2026 | 212 ms |
| Jul 4, 2026 | 223 ms |
| Jul 11, 2026 | 234 ms |
| Jul 18, 2026 | 242 ms |
| Jul 25, 2026 | 269 ms |
| Aug 1, 2026 | 272 ms |
| Aug 8, 2026 | 272 ms |
| Aug 15, 2026 | 274 ms |
| Aug 22, 2026 | 257 ms |
| Aug 29, 2026 | 249 ms |
| Sep 5, 2026 | 251 ms |
| Sep 12, 2026 | 260 ms |
| Sep 19, 2026 | 271 ms |
| Sep 26, 2026 | 283 ms |
| Oct 3, 2026 | 293 ms |
| Oct 10, 2026 | 291 ms |
| Oct 17, 2026 | 280 ms |
| Oct 24, 2026 | 261 ms |
| Oct 31, 2026 | 232 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.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Render-blocking requests
1.4 s10 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.
Mobile performance score: 78
78/100Your mobile performance score is 78. Pages that score under 90 lose visitors before the first paint.
Improve image delivery
300 ms · 290 KiB8 images could be 290 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.
Use efficient cache lifetimes
300 ms · 65 KiB8 files are served with short cache lifetimes, so returning visitors download them again (65 KiB).
Reduce unused CSS
300 ms · 53 KiBAbout 53 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
2,389 HTML elements
The page has 2,389 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Shopify adds 0 ms
0 msShopify costs a phone 0 ms of main-thread work and 655 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.
7 third-party services on the page
7 third-party services load with your homepage (lively.li, trackier.com and Shopify and others), adding 871 KiB and 3 ms of main-thread time.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Minify CSS
8 KiB8 KiB could be saved by minifying CSS.
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.
2 checks passed
Main-thread work: 0.4 s
A phone's processor spends 0.4 s on main-thread work while loading, 36 ms of it running JavaScript. That is comfortably low.
Server response: 13 ms
13 msYour server sent the HTML in 13 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.
Largest Contentful Paint: 6.2 s
6.2 sYour largest element takes 6.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Real-user LCP: 3.1 s
3.1 sReal visitors wait 3.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 214 ms
214 msReal visitors wait 214 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 24% slower for real visitors
+24%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 199 ms to 232 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 20% slower for real visitors
+20%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 3.1 s to 3.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Time to Interactive: 6.2 s
6.2 sThe page becomes fully interactive after 6.2 s. Good is under 3.8 s.
7 images without width and height
7 images have no width and height attributes, so the layout jumps as each one loads.
7 checks passed
Real-user CLS: 0.05
0.05For real visitors the layout shifts by 0.05 (75th percentile). Good is under 0.1.
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: 544 ms
544 msReal visitors wait 544 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 1.4 s
1.4 sThe first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Speed Index: 1.7 s
1.7 sVisually, the page fills in at 1.7 s (Speed Index), inside the 3.4 s “good” threshold.
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 5.2 MB in 85 requests
5.2 MBYour homepage downloads 5.2 MB in 85 requests on a phone: images 3.9 MB (42), media 574 KiB (1) and scripts 396 KiB (30). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
Pehli_dawat_M_04_11_800x800.webp 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).
1 image far larger than shown
41 KiB1 image is downloaded at several times the size a phone draws it, for example nanhe_704x704_b0490717-a802-424d-a25c-f88b85818f0f.webp at 390 px wide, shown at 69 px. Resized copies would save about 41 KiB.
5 images in older formats
5 images (468 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 1.5 g of CO₂ per visit
1.49 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.49 g of CO₂e: 178.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
4 buttons without a name
4 buttons have no accessible name, so screen readers announce just “button”.
62 text elements with low contrast
62 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Elements must only use permitted ARIA attributes (5 elements)
Elements must only use permitted ARIA attributes: 5 elements on the page fail this check, rated serious by axe-core.
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.
14 images without alt text
14 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (2 elements)
All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.
5 links without text
5 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has 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.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
1 checks passed
46 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 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
Title is long (70 characters)
Your title is 70 characters, so Google will cut it off around 60: “Shop Premium Ayurvedic Newborn Baby Care Products Online | Baby Forest”.
262 internal links, 5 external
The homepage links to 262 pages on babyforest.in and 5 external pages.
7 checks passed
Meta description: 155 characters
Your meta description is 155 characters: “Explore Baby Forest's range of organic baby care products made with Ayurvedic ingredients. From skincare to feeding ess…”.
One H1 headline
Your main headline reads: “Baby Forest”.
Canonical URL set
The canonical URL is https://www.babyforest.in/.
Structured data in place
Structured data found: BreadcrumbList, Corporation, Organization, VideoObject and WebSite.
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.babyforest.in/sitemap.xml.
AI search readiness
No llms.txt
There is no https://www.babyforest.in/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.
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.
Organization data: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and description; contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,270 words), so crawlers that don't run JavaScript still read it.
Other pages
3 pages without an H1
https://www.babyforest.in/collections/shop-all, https://www.babyforest.in/collections/bestsellers and https://www.babyforest.in/collections/combo have no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://www.babyforest.in/collections/combo has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
1 page slow to respond
https://www.babyforest.in/collections/combo took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 97 found) and read each the way a search engine does.
6 checks passed
Linked pages load
4 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 4 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 4 pages that loaded have a <title>.
Best practices
28 small tap targets
28 of 52 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”.
3 distorted images
3 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 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 941 words of copy
The homepage carries about 941 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 All” and “SHOP”.
17 calls to action
The homepage has 17 calls to action, for example “Shop All”, “Track Order” and “SHOP NOW”.
41 short forms
41 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 94 testimonial or review blocks and 3 trust badges.
Analytics in place
Analytics detected: Google Tag Manager and Microsoft Clarity.
Privacy and tracking
5 cookies set on arrival
5Opening the homepage sets 5 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.
4 other companies contacted
Loading the homepage contacts 4 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 babyforest.in, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Go beyond the website
What your $25 Growth Playbook adds
This review found 32 issues on babyforest.in, including 15 speed issues, 1 SEO issue 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.