infanttech.com website review

About 774 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.6 s faster on a phone.

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

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

8 third-party services load with your homepage (reamaze.com, Shopify and Google Tag Manager and others), adding 1.2 MB and 346 ms of main-thread time.

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

Shopify costs a phone 55 ms of main-thread work and 596 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 32 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 140 ms faster on a phone.

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

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

3 images could be 22 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

Polyfills for old browsers add 9 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.

Your largest element takes 13.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Drive With Peace Of Mind The Only Car Baby Monitor Made For…”.

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

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

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

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 2.7 MB in 174 requests on a phone: scripts 1.2 MB (58), other files 762 KiB (92) and images 357 KiB (11). Under 2 MB keeps phones on slow connections fast.

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

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

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

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

ARIA input fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

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

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

Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

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

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

Headings skip levels (h2 → h5), which makes the page harder to scan with a screen reader.

Your title is 68 characters, so Google will cut it off around 60: “infanttech | zooby® baby monitor - Crash-Tested, Portable & Adorable”.

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

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

Your <h1> is empty.

The homepage links to 75 pages on infanttech.com and 12 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.

/products/zooby-baby-monitor-jordan-giraffe and /collections/main-shop/products/zooby-baby-monitor-jordan-giraffe all use the title “zooby® baby monitor | Jordan Giraffe – infanttech”. Search engines can't tell which page to show for a search, so each competes with the others.

/pages/zooby-love-collection has no meta description, so Google writes the search snippet from whatever text it finds.

/products/zooby-baby-monitor-jordan-giraffe and /collections/main-shop/products/zooby-baby-monitor-jordan-giraffe use the same meta description. A description written for each page earns more clicks.

Your homepage links to 6 pages by a URL that isn't their canonical one, for example /collections/main-shop/products/zooby-baby-monitor-jordan-giraffe, whose canonical is /products/zooby-baby-monitor-jordan-giraffe. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/pages/shop, /pages/zooby-love-collection, /pages/zooby, /pages/about-us, /products/zooby%C2%AE-mini-bailey-bunny and /products/zooby%C2%AE-mini-cooper-canine and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 image failed to load on a phone, for example https://hulkapps-wishlist.nyc3.digitaloceanspaces.com/assets/images/meta1.svg.svg.

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

1 error was logged to the browser console while the page loaded, for example “[Weglot] Cannot load Weglot because the project has been deleted”.

2 links from your homepage to your own site are broken, for example https://infanttech.com/pages/about-us-dev (404).

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

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.

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

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

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

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 540 words of visible text.

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, Klaviyo and Meta Pixel and 2 mores (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 15 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 34 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.