softsensbaby.com website review

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

The page has 4,756 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

About 3.0 MB of JavaScript is downloaded but never used on this page.

8 third-party services load with your homepage (shiprocket.in, Google Tag Manager and pickrr.com and others), adding 3.2 MB and 1.7 s of main-thread time.

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

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

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

shiprocket.in costs a phone 468 ms of main-thread work and 120 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.

23 images could be 322 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

pickrr.com costs a phone 309 ms of main-thread work and 1.3 MB 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.

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

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 300 ms).

Shopify costs a phone 152 ms of main-thread work and 640 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.

autoketing.org costs a phone 52 ms of main-thread work and 297 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.

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

54 KiB could be saved by minifying JavaScript.

Polyfills for old browsers add 6 KiB JavaScript that modern phones do not need.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

2 KiB could be saved by minifying CSS.

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.

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

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

Scripts block taps and scrolling for 772 ms in total while the page loads. Good is under 200 ms.

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

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

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

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

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

Your homepage downloads 12.2 MB in 290 requests on a phone: fonts 6.1 MB (9), scripts 2.8 MB (90) and images 1.7 MB (84). Under 2 MB keeps phones on slow connections fast.

Kids-soaps-mobile-2.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).

1 image is downloaded at several times the size a phone draws it, for example placeholder.webp at 1,920 px wide, shown at 386 px. Resized copies would save about 35 KiB.

1 image (54 KiB) is 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 further down the page (109 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

2 buttons have no accessible name, so screen readers announce just “button”.

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

Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.

Documents must have <title> element to aid in navigation: 1 element on the page fails this check, rated serious by axe-core.

Some lists contain elements other than list items, which screen readers announce wrongly.

137 images have no alt text, which hurts accessibility and image search.

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

4 form fields have no label, so screen readers announce an empty box and autofill guesses.

1 element hidden from screen readers can still receive keyboard focus.

Some list items are not inside a list.

Alternative text of images should not be repeated as text: 6 elements on the page fail this check, rated minor by axe-core.

Headings should not be empty: 5 elements on the page fail this check, rated minor by axe-core.

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

Elements with visible text labels do not have matching accessible names. (1 element).

Your page has no <title>, so Google has to invent the blue link in search results.

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

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

There are 3 <h1> headlines (“”, “” and “Excellence or Nothing”). One clear main headline is easier for people and search engines.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 371 pages on softsensbaby.com and 100 external pages.

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.

/collections/shop-all, /collections/all-baby-care, /collections/baby-combos, /collections/baby-care-new-arrivals, /collections/baby-bestseller and /collections/baby-soap-wash and 8 others have no <title>, so Google invents the link text in results.

/collections/shop-all, /collections/all-baby-care, /collections/baby-combos, /collections/baby-care-new-arrivals, /collections/baby-bestseller and /collections/baby-soap-wash and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

/collections/shop-all, /collections/all-baby-care, /collections/baby-combos, /collections/baby-care-new-arrivals, /collections/baby-bestseller and /collections/baby-soap-wash and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

/collections/dry-hair-or-scalp took over 3 s to send its HTML from our server.

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

5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

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

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

2 images are served at too low a resolution for sharp phone screens.

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

HSTS is set, but max-age is 91 days; one year is the recommended minimum.

6 links go through two or more redirects, for example https://www.facebook.com/sharer.php?u=https://softsensbaby.com//blogs/all-blogs/the-skin-barrier-explained-your-baby-s-invisible-superpower.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

softsensbaby.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

softsensbaby.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

DMARC is set to p=none, so mail pretending to be softsensbaby.com is still delivered. Reports are on, so moving to quarantine is the next step.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity (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.

Opening the homepage sets 16 cookies, 1 of them by other companies (measured from a US location before any click).

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.

Loading the homepage contacts 31 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.