kidy.com.br website review

16 images could be 718 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.3 s faster on a phone.

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

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

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

Your mobile performance score is 58 (desktop: 83). Pages that score under 90 lose visitors before the first paint.

8 third-party services load with your homepage (Google Tag Manager, Shopify and RD Station and others), adding 1.0 MB and 616 ms of main-thread time.

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

Google Tag Manager costs a phone 267 ms of main-thread work and 330 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 298 KiB of JavaScript is downloaded but never used on this page.

About 11 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 180 ms faster on a phone.

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

11 KiB could be saved by minifying JavaScript.

Desktop scores 83 but mobile only 58. 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.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

2 KiB could be saved by minifying CSS.

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 11.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

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

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

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

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

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

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

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

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

Your homepage downloads 4.3 MB in 262 requests on a phone: images 2.3 MB (98), scripts 1,023 KiB (65) and other files 659 KiB (57). Under 2 MB keeps phones on slow connections fast.

VELOZ.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

10 images further down the page (736 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

2 images are downloaded at several times the size a phone draws them, for example 99b50ed2-bec6-47a1-80d9-78ae2942697f at 1,024 px wide, shown at 33 px. Resized copies would save about 232 KiB.

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

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

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

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

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

Elements with visible text labels do not have matching accessible names. (4 elements).

Your title is 79 characters, so Google will cut it off around 60: “Calçados Infantis Kidy | Conforto e Tecnologia para os Pequenos – Kidy Calçados”.

Your meta description is 320 characters; Google truncates after about 160, so the end of your pitch is cut.

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

Your <h1> is empty.

The homepage links to 614 pages on kidy.com.br and 24 external pages.

https://www.kidy.com.br/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://www.kidy.com.br/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://www.kidy.com.br/collections/menino/6-meses-a-1-ano, https://www.kidy.com.br/collections/menino/1-a-4-anos, https://www.kidy.com.br/collections/menino/Acima-de-5-anos, https://www.kidy.com.br/collections/menino/6-meses-a-1-ano+1-a-4-anos+Acima-de-5-anos and https://www.kidy.com.br/collections/menino all use the title “Calçados Infantis Menino Kidy Cuidando de Cada Passo – Kidy Calçados”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.kidy.com.br/collections/all and https://www.kidy.com.br/customer_authentication/redirect have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.kidy.com.br/collections/menino/6-meses-a-1-ano, https://www.kidy.com.br/collections/menino/1-a-4-anos, https://www.kidy.com.br/collections/menino/Acima-de-5-anos, https://www.kidy.com.br/collections/menino/6-meses-a-1-ano+1-a-4-anos+Acima-de-5-anos and https://www.kidy.com.br/collections/menino use the same meta description. A description written for each page earns more clicks.

Your homepage links to 8 pages by a URL that isn't their canonical one, for example https://www.kidy.com.br/collections/menino/6-meses-a-1-ano, whose canonical is https://www.kidy.com.br/collections/menino. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.kidy.com.br/customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.

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

2 errors were logged to the browser console while the page loaded, for example “[splide] Invalid JSON Et (https://www.kidy.com.br/cdn/shop/t/19/assets/store-DOiTbFE6.js:10:2887)”.

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.

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

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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 1,106 words of visible text.

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