babysafe.co.id website review

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

14 images could be 2.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 5.9 s faster on a phone.

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

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

About 149 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 650 ms faster on a phone.

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

6 third-party services load with your homepage (Google Tag Manager, jQuery CDN and Google Fonts and others), adding 418 KiB and 421 ms of main-thread time.

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

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

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

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

5 KiB could be saved by minifying JavaScript.

3 KiB could be saved by minifying CSS.

Your largest element takes 41.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

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

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

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 8.2 MB in 60 requests on a phone: images 7.7 MB (42), scripts 389 KiB (5) and fonts 134 KiB (3). Under 2 MB keeps phones on slow connections fast.

1 image (178 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.

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

Links must have discernible text: 5 elements on the page fail this check, rated serious by axe-core.

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

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

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

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

No meta description, so Google writes its own snippet from whatever text it finds.

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

Your title is only 16 characters: “Home - Baby Safe”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

No XML sitemap at https://babysafe.co.id/sitemap.xml, so Google discovers your pages only by following links.

There is no robots.txt at babysafe.co.id/robots.txt, the first file search crawlers ask for.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 44 pages on babysafe.co.id and 1 external page.

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.

There is no https://babysafe.co.id/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.

/ and https://babysafe.co.id/id/home/index.html all use the title “Home - Baby Safe”. Search engines can't tell which page to show for a search, so each competes with the others.

https://babysafe.co.id/id/home/index.html, https://babysafe.co.id/id/appliances/index.html, https://babysafe.co.id/id/appliances/slow_cooker/index.html, https://babysafe.co.id/id/appliances/steam_cooker/index.html, https://babysafe.co.id/id/appliances/sterilizer/index.html and https://babysafe.co.id/id/appliances/milk_warmer/index.html and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://babysafe.co.id/id/home/index.html, https://babysafe.co.id/id/appliances/slow_cooker/index.html, https://babysafe.co.id/id/appliances/steam_cooker/index.html, https://babysafe.co.id/id/appliances/sterilizer/index.html, https://babysafe.co.id/id/appliances/milk_warmer/index.html and https://babysafe.co.id/id/appliances/warmer_jug/index.html and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://babysafe.co.id/id/feeding/index.html 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.

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

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

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

Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

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

The homepage has only about 118 words of visible text; thin pages give Google and first-time buyers little to go on.

There is no form on the homepage, so every lead has to click through to another page first.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

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.

Opening the homepage sets 3 cookies (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 8 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.