habausa.com website review

Your mobile performance score is 100. That is in Google's “good” band (90 and up).

A phone's processor spends 0.4 s on main-thread work while loading, 170 ms of it running JavaScript. That is comfortably low.

Your server sent the HTML in 7 ms, well inside Google's 600 ms guideline.

Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

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

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

For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.

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

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

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

Visually, the page fills in at 2.7 s (Speed Index), inside the 3.4 s “good” threshold.

The first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.

The layout barely moves while loading (CLS 0, good is under 0.1).

Your largest element renders in 1.1 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “HABA’s European-designed, sustainable kids toys and games o…”.

Scripts block the page for only 13 ms while loading. Good is under 200 ms.

Your homepage downloads 1.0 MB in 67 requests on a phone: scripts 559 KiB (29), images 301 KiB (24) and fonts 89 KiB (4). That is a lean page.

Every sizeable image is WebP, AVIF or SVG.

Images below the first screen wait until the visitor scrolls to them.

No image is downloaded at more than three times the size it is drawn on a phone.

axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 3 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

Your meta description is 154 characters: “Our extraordinary selection of kid's toys promotes learning and early development skills. Shop toys for kids that all a…”.

Your main headline reads: “HABA USA”.

Your title is a healthy 50 characters: “HABA Toys | Kid's Toys | Children's Toys– HABA USA”.

The canonical URL is https://www.habausa.com/.

Open Graph tags are complete, so shared links show a title, description and image.

robots.txt is in place and points crawlers to your sitemap.

Your XML sitemap is reachable at https://www.habausa.com/sitemap.xml.

Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

Your server sends the page's text in the HTML (1,819 words), so crawlers that don't run JavaScript still read it.

The site publishes /llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

All 15 pages we checked loaded without an error.

No page we checked hands its ranking to a different URL.

Every page we checked has its own title.

None of the pages we checked carries a noindex tag.

All 15 pages that loaded have a <title>.

No JavaScript errors were logged while the page loaded on a phone.

21 of 26 tappable elements near the top are at least 24 px.

The page declares a mobile viewport.

The homepage is served over HTTPS (habausa.com).

The certificate from Let's Encrypt · YE2 verifies for habausa.com and is valid for another 62 days.

X-Frame-Options or a frame-ancestors policy stops other sites framing yours.

A Content-Security-Policy is set, the main browser-side defence against injected scripts.

http://habausa.com redirects to the secure version.

The server speaks HTTP/2 and advertises HTTP/3, so browsers load many files over one connection.

All 47 links checked from your homepage (40 internal, 7 external) answered without errors.

habausa.com was registered in Jun 1999 through GoDaddy.com, LLC. An established domain carries more trust with email providers and search engines.

CAA records allow only globalsign.com, letsencrypt.org, pki.goog and ssl.com to issue certificates for habausa.com, so a mis-issued certificate from anyone else is refused.

habausa.com is registered until Jun 2027.

On a phone, the first screen shows a clear next step: “SHOP BEST SELLERS »”.

The homepage has 35 calls to action, for example “Shop Holiday”, “The Holiday Shop” and “Shop by Age”.

2 short forms (1 field at most) are right on the homepage.

Social proof on the homepage: 17 testimonial or review blocks and a star rating.

Analytics detected: Google Tag Manager.

Visitors can reach you directly: 1 phone link and 0 email links.

DMARC tells receivers to quarantine mail that fails authentication, and sends you reports.

An SPF record lists your sending servers and tells receivers to reject anything else: “v=spf1 include:spf.protection.outlook.com include:ebizcharge.net ip4:209.239.233.0/24 ip4:64.0.146.0/24 ip4:209.220.191…”.

A DKIM key is published (selector “k1”, “s1” and “s2”), so receivers can verify mail really came from you.

A consent management tool (Termly) loads with the page.