baby-pet.com website review

About 2.7 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 8.8 s faster on a phone.

19 files block the first paint until they finish downloading. Deferring or inlining them could save about 5.8 s.

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

cybassets.com costs a phone 1.3 s of main-thread work and 4.8 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

Your mobile performance score is 22. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

6 third-party services load with your homepage (cybassets.com, Google Tag Manager and Facebook and others), adding 6.3 MB and 2.0 s of main-thread time.

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

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

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

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

Facebook costs a phone 166 ms of main-thread work and 316 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 51 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.

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

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.

4 KiB could be saved by minifying JavaScript.

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.

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

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

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

The layout shifts by 1.013 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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

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

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

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

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

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

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

Your homepage downloads 6.4 MB in 94 requests on a phone: scripts 3.3 MB (43), images 2.9 MB (20) and HTML 87 KiB (1). Under 2 MB keeps phones on slow connections fast.

W1siZiIsIjIzODczL2F0dGFjaGVkX3Bob3Rvcy8xNjcyMzg5OTQyXzEwMDE1 weighs 963 KiB. On a phone connection a single image that size takes seconds.

10 images are downloaded at several times the size a phone draws them, for example W1siZiIsIjIzODczL2F0dGFjaGVkX3Bob3Rvcy8xNzYxMTE3NzM3X-a7v-mh at 1,920 px wide, shown at 390 px. Resized copies would save about 1.0 MB.

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

4 images further down the page (853 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 1.80 g of CO₂e: 216.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

115 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

ARIA attributes must conform to valid values: 8 elements on the page fail this check, rated critical by axe-core.

Images must have alternative text: 6 elements on the page fail this check, rated critical by axe-core.

1 button has no accessible name, so screen readers announce just “button”.

Interactive controls must not be nested: 8 elements on the page fail this check, rated serious by axe-core.

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

1 frame has no title, so screen-reader users cannot tell what it contains.

All page content should be contained by landmarks: 129 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.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

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

13 visible links have no text or label, so screen readers cannot say where they go.

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

Your title is only 12 characters: “babypet 小犬布屋”. Between 30 and 65 characters leaves room to say what you do and for whom.

Your meta description is only 26 characters: “小犬布屋提供各式多樣化及優惠竉物食品,貓狗用品,零食”. 70 to 160 characters is enough to sell the click.

Structured data found (Organization and WebSite) but with 2 problems, for example “Organization: missing name”.

1 link has no real href, so search engines can't follow it.

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

The homepage links to 578 pages on baby-pet.com and 11 external pages.

Your Organization JSON-LD is missing name, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

There is no https://www.baby-pet.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.

https://www.baby-pet.com/pages/%E6%9A%96%E5%BF%83%E5%A5%BD%E7%B3%A7 has no meta description, so Google writes the search snippet from whatever text it finds.

https://www.baby-pet.com/collections/new%E7%86%B1%E9%8A%B7%E6%96%B0%E4%B8%8A%E5%B8%82, https://www.baby-pet.com/collections/%E5%84%AA%E6%83%A0%E6%8E%A8%E8%96%A6, https://www.baby-pet.com/collections/dog%E7%B3%BB%E5%88%97, https://www.baby-pet.com/collections/cat%E7%B3%BB%E5%88%97, https://www.baby-pet.com/collections/mix%E7%B3%BB%E5%88%97 and https://www.baby-pet.com/collections/%E9%BC%A0%E5%85%94%E7%B3%BB%E5%88%97 and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.baby-pet.com/collections/new%E7%86%B1%E9%8A%B7%E6%96%B0%E4%B8%8A%E5%B8%82, https://www.baby-pet.com/collections/%E5%84%AA%E6%83%A0%E6%8E%A8%E8%96%A6, https://www.baby-pet.com/collections/dog%E7%B3%BB%E5%88%97, https://www.baby-pet.com/collections/cat%E7%B3%BB%E5%88%97, https://www.baby-pet.com/collections/mix%E7%B3%BB%E5%88%97 and https://www.baby-pet.com/collections/%E9%BC%A0%E5%85%94%E7%B3%BB%E5%88%97 and 7 others took over 3 s to send their HTML from our server.

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

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

6 errors were logged to the browser console while the page loaded, for example “Request timed out”.

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

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

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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

The homepage carries about 253 words of visible text.

The page uses urgency cues (a countdown or limited-time wording).

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (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 11 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 11 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.