kidsmadehere.com website review

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

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

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

8 third-party services load with your homepage (Google CDN, vtexassets.com and Google Tag Manager and others), adding 4.8 MB and 2.3 s of main-thread time.

Google CDN costs a phone 818 ms of main-thread work and 2.8 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.

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

vtexassets.com costs a phone 463 ms of main-thread work and 961 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.

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

Facebook costs a phone 289 ms of main-thread work and 311 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.

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

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

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

About 59 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.

Desktop scores 66 but mobile only 24. A gap that wide usually means heavy scripts and images that hit phones hardest.

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

1 image could be 5 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Your homepage downloads 4.2 MB in 135 requests on a phone: scripts 3.0 MB (71), other files 724 KiB (39) and HTML 189 KiB (4). Under 2 MB keeps phones on slow connections fast.

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

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

5 elements hidden from screen readers can still receive keyboard focus.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

All page content should be contained by landmarks: 2 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 form fields have no label, so screen readers announce an empty box and autofill guesses.

2 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 meta description is 228 characters; Google truncates after about 160, so the end of your pitch is cut.

Structured data found (WebSite) but with 1 problem, for example “WebSite: missing name”.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

No XML sitemap at https://www.MiTienda.com.br/sitemap.xml, so Google discovers your pages only by following links.

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

The homepage links to 10 pages on kidsmadehere.com and 0 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.

There is no https://www.kidsmadehere.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.kidsmadehere.com/onlineonly, https://www.kidsmadehere.com/halloween-outfits, https://www.kidsmadehere.com/sets-of-the-week, https://www.kidsmadehere.com/nuevos-ingresos, https://www.kidsmadehere.com/rebajas and https://www.kidsmadehere.com/accesorios use the same meta description. A description written for each page earns more clicks.

https://www.kidsmadehere.com/onlineonly, https://www.kidsmadehere.com/halloween-outfits, https://www.kidsmadehere.com/sets-of-the-week, https://www.kidsmadehere.com/nuevos-ingresos, https://www.kidsmadehere.com/ropa and https://www.kidsmadehere.com/ropa/tops/polos and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.kidsmadehere.com/nuevos-ingresos, https://www.kidsmadehere.com/ropa and https://www.kidsmadehere.com/accesorios took over 3 s to send their HTML from our server.

We fetched 8 pages linked from your homepage and read each the way a search engine does.

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

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

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

The homepage has only about 10 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, Google Tag Manager, Hotjar and Meta Pixel and 1 more (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 22 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 31 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.