Tools & Wizards About Us
kidy.com.br screenshot

Report Summary

  • 13

    Performance

    Renders faster than
    25% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 74

    SEO

    Google-friendlier than
    31% of websites

kidy.com.br

Page Load Speed

3.8 sec in total

First Response

458 ms

Resources Loaded

2.8 sec

Page Rendered

577 ms

kidy.com.br screenshot

About Website

Welcome to kidy.com.br homepage info - get ready to check Kidy best content for Brazil right away, or after learning these important things about kidy.com.br

Visit kidy.com.br

Key Findings

We analyzed Kidy.com.br page load time and found that the first response time was 458 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

kidy.com.br performance score

13

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.1 s

1/100

10%

LCP (Largest Contentful Paint)

Value8.2 s

2/100

25%

SI (Speed Index)

Value12.2 s

3/100

10%

TBT (Total Blocking Time)

Value2,840 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.155

74/100

15%

TTI (Time to Interactive)

Value19.1 s

3/100

10%

Network Requests Diagram

kidy.com.br

458 ms

www.kidy.com.br

232 ms

js

83 ms

js

115 ms

gtm.js

137 ms

Our browser made a total of 61 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Kidy.com.br, 41% (25 requests) were made to Kidy.fbitsstatic.net and 20% (12 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (912 ms) relates to the external source Kidy.fbitsstatic.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 544.7 kB (29%)

Content Size

1.9 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Kidy.com.br main page is 1.9 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 70% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 330.4 kB

  • Original 429.4 kB
  • After minification 429.4 kB
  • After compression 99.0 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 330.4 kB or 77% of the original size.

Image Optimization

-14%

Potential reduce by 205.5 kB

  • Original 1.4 MB
  • After minification 1.2 MB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Obviously, Kidy needs image optimization as it can save up to 205.5 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-23%

Potential reduce by 3.2 kB

  • Original 13.5 kB
  • After minification 13.5 kB
  • After compression 10.3 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 3.2 kB or 23% of the original size.

CSS Optimization

-78%

Potential reduce by 5.7 kB

  • Original 7.3 kB
  • After minification 7.3 kB
  • After compression 1.6 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Kidy.com.br needs all CSS files to be minified and compressed as it can save up to 5.7 kB or 78% of the original size.

Requests Breakdown

Number of requests can be reduced by 19 (42%)

Requests Now

45

After Optimization

26

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 45 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Kidy. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

kidy.com.br

kidy.com.br

458 ms

www.kidy.com.br

www.kidy.com.br

232 ms

js

js

83 ms

js

js

115 ms

gtm.js

gtm.js

137 ms

bootstrap.min.css

bootstrap.min.css

22 ms

207 ms

alertacookie.css

alertacookie.css

720 ms

alertacookie.js

alertacookie.js

166 ms

css2

css2

49 ms

css2

css2

80 ms

injector.js

injector.js

102 ms

9a8f5d1c-baa9-4a10-a878-fbc6c80f7600-loader.js

9a8f5d1c-baa9-4a10-a878-fbc6c80f7600-loader.js

760 ms

bundle.js

bundle.js

98 ms

js

js

71 ms

storefront-sdk.min.js

storefront-sdk.min.js

69 ms

142 ms

183 ms

logo-kidy.png

logo-kidy.png

177 ms

placeholder.svg

placeholder.svg

89 ms

c3f1b17f-9e0c-4992-9225-11b937eedd77.png

c3f1b17f-9e0c-4992-9225-11b937eedd77.png

388 ms

2621451e-28d6-44a4-89ed-2eb8ee1a2ad2.png

2621451e-28d6-44a4-89ed-2eb8ee1a2ad2.png

317 ms

e5c79878-340e-4802-b858-1bdb9d8f4cbc.png

e5c79878-340e-4802-b858-1bdb9d8f4cbc.png

305 ms

menino.png

menino.png

230 ms

menina.png

menina.png

230 ms

beb%C3%AA.png

beb%C3%AA.png

897 ms

fase1.png

fase1.png

303 ms

fase-pe-1.png

fase-pe-1.png

444 ms

fase2.png

fase2.png

305 ms

fase-pe-2.png

fase-pe-2.png

597 ms

fase3.png

fase3.png

699 ms

fase-pe-3.png

fase-pe-3.png

558 ms

fase4.png

fase4.png

410 ms

fase-pe-4-v2.png

fase-pe-4-v2.png

674 ms

home_idade_1.png

home_idade_1.png

496 ms

home_idade_2.png

home_idade_2.png

912 ms

home_idade_3.png

home_idade_3.png

901 ms

2.png

2.png

621 ms

1.png

1.png

644 ms

pxiByp8kv8JHgFVrLDz8V1g.woff

pxiByp8kv8JHgFVrLDz8V1g.woff

89 ms

pxiByp8kv8JHgFVrLFj_V1g.woff

pxiByp8kv8JHgFVrLFj_V1g.woff

140 ms

pxiGyp8kv8JHgFVrLPTedA.woff

pxiGyp8kv8JHgFVrLPTedA.woff

165 ms

pxiEyp8kv8JHgFVrFJM.woff

pxiEyp8kv8JHgFVrFJM.woff

166 ms

pxiByp8kv8JHgFVrLGT9V1g.woff

pxiByp8kv8JHgFVrLGT9V1g.woff

164 ms

pxiByp8kv8JHgFVrLEj6V1g.woff

pxiByp8kv8JHgFVrLEj6V1g.woff

163 ms

pxiByp8kv8JHgFVrLCz7V1g.woff

pxiByp8kv8JHgFVrLCz7V1g.woff

165 ms

pxiByp8kv8JHgFVrLDD4V1g.woff

pxiByp8kv8JHgFVrLDD4V1g.woff

163 ms

pxiByp8kv8JHgFVrLBT5V1g.woff

pxiByp8kv8JHgFVrLBT5V1g.woff

166 ms

Valken.woff

Valken.woff

585 ms

lead-tracking.min.js

lead-tracking.min.js

39 ms

traffic-source-cookie.min.js

traffic-source-cookie.min.js

40 ms

OTQzNjpraWR5LWNhbGNhZG9zLWluZmFudGlz

OTQzNjpraWR5LWNhbGNhZG9zLWluZmFudGlz

292 ms

styles.css

styles.css

20 ms

otimo.svg

otimo.svg

23 ms

reclame-aqui-logo.svg

reclame-aqui-logo.svg

29 ms

css

css

17 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVQ.woff

5 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQ.woff

4 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVQ.woff

26 ms

rdstation-popup.min.js

rdstation-popup.min.js

46 ms

rd-js-integration.min.js

rd-js-integration.min.js

45 ms

Accessibility Review

kidy.com.br accessibility score

76

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Document doesn't have a <title> element

High

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

kidy.com.br best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

kidy.com.br SEO score

74

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Document doesn't have a <title> element

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    PT

  • Language Claimed

    PT

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Kidy.com.br can be misinterpreted by Google and other search engines. Our service has detected that Portuguese is used on the page, and it matches the claimed language. Our system also found out that Kidy.com.br main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

kidy.com.br

Open Graph description is not detected on the main page of Kidy. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: