Tools & Wizards About Us
kindo.com screenshot

Report Summary

  • 51

    Performance

    Renders faster than
    69% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

kindo.com

Free Family Tree, Genealogy, Family History, and DNA Testing

Page Load Speed

2 sec in total

First Response

166 ms

Resources Loaded

1.5 sec

Page Rendered

356 ms

kindo.com screenshot

About Website

Visit kindo.com now to see the best up-to-date Kindo content and also check out these interesting facts you probably never knew about kindo.com

Create your family tree. Take a MyHeritage DNA test for ancestry and genetic testing. Access 41 billion historical records for genealogy research.

Visit kindo.com

Key Findings

We analyzed Kindo.com page load time and found that the first response time was 166 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

kindo.com performance score

51

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

46/100

10%

LCP (Largest Contentful Paint)

Value4.2 s

45/100

25%

SI (Speed Index)

Value6.2 s

43/100

10%

TBT (Total Blocking Time)

Value680 ms

44/100

30%

CLS (Cumulative Layout Shift)

Value0.028

100/100

15%

TTI (Time to Interactive)

Value10.6 s

23/100

10%

Network Requests Diagram

kindo.com

166 ms

kindo.com

277 ms

www.myheritage.com

186 ms

report-violation.php

66 ms

report-violation.php

68 ms

Our browser made a total of 91 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Kindo.com, 66% (60 requests) were made to Myheritage.com and 31% (28 requests) were made to Cf.mhcache.com. The less responsive or slowest element that took the longest time to load (821 ms) relates to the external source Myheritage-container.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 127.5 kB (63%)

Content Size

201.6 kB

After Optimization

74.1 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Kindo.com main page is 201.6 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 40% of websites need less resources to load. HTML takes 139.3 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 110.2 kB

  • Original 139.3 kB
  • After minification 136.5 kB
  • After compression 29.1 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 110.2 kB or 79% of the original size.

Image Optimization

-34%

Potential reduce by 17.2 kB

  • Original 50.2 kB
  • After minification 33.0 kB

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, Kindo needs image optimization as it can save up to 17.2 kB or 34% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-1%

Potential reduce by 80 B

  • Original 12.1 kB
  • After minification 12.1 kB
  • After compression 12.0 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. This website has mostly compressed JavaScripts.

Requests Breakdown

Number of requests can be reduced by 8 (28%)

Requests Now

29

After Optimization

21

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

kindo.com

kindo.com

166 ms

kindo.com

kindo.com

277 ms

www.myheritage.com

www.myheritage.com

186 ms

report-violation.php

report-violation.php

66 ms

report-violation.php

report-violation.php

68 ms

minimal-thin-base-responsive-without-footer_ltr_v1MVf0ff90126297d953055ed3c4483fff9co.css

minimal-thin-base-responsive-without-footer_ltr_v1MVf0ff90126297d953055ed3c4483fff9co.css

70 ms

TypographyComponents_bundle_ltr_v1MVa7d91d757d08fdfb5fbb5b2b74f4fe7ao.css

TypographyComponents_bundle_ltr_v1MVa7d91d757d08fdfb5fbb5b2b74f4fe7ao.css

80 ms

CompanyHomePageDesktop_bundle_ltr_v1MV5546d181ba37c8474f18e79a9caf4d66o.css

CompanyHomePageDesktop_bundle_ltr_v1MV5546d181ba37c8474f18e79a9caf4d66o.css

81 ms

Themes_bundle_ltr_v1MV508f72f03d1aa3e0986cf1d9e2ef4383o.css

Themes_bundle_ltr_v1MV508f72f03d1aa3e0986cf1d9e2ef4383o.css

80 ms

report-violation.php

report-violation.php

51 ms

report-violation.php

report-violation.php

59 ms

report-violation.php

report-violation.php

87 ms

report-violation.php

report-violation.php

85 ms

report-violation.php

report-violation.php

88 ms

report-violation.php

report-violation.php

86 ms

report-violation.php

report-violation.php

85 ms

report-violation.php

report-violation.php

124 ms

report-violation.php

report-violation.php

139 ms

report-violation.php

report-violation.php

144 ms

report-violation.php

report-violation.php

127 ms

report-violation.php

report-violation.php

136 ms

report-violation.php

report-violation.php

119 ms

report-violation.php

report-violation.php

149 ms

report-violation.php

report-violation.php

166 ms

report-violation.php

report-violation.php

159 ms

report-violation.php

report-violation.php

176 ms

report-violation.php

report-violation.php

239 ms

report-violation.php

report-violation.php

171 ms

report-violation.php

report-violation.php

140 ms

report-violation.php

report-violation.php

204 ms

report-violation.php

report-violation.php

204 ms

report-violation.php

report-violation.php

204 ms

report-violation.php

report-violation.php

205 ms

report-violation.php

report-violation.php

205 ms

report-violation.php

report-violation.php

222 ms

report-violation.php

report-violation.php

213 ms

report-violation.php

report-violation.php

231 ms

report-violation.php

report-violation.php

225 ms

report-violation.php

report-violation.php

231 ms

report-violation.php

report-violation.php

212 ms

report-violation.php

report-violation.php

242 ms

report-violation.php

report-violation.php

250 ms

report-violation.php

report-violation.php

252 ms

report-violation.php

report-violation.php

253 ms

report-violation.php

report-violation.php

262 ms

report-violation.php

report-violation.php

272 ms

report-violation.php

report-violation.php

269 ms

report-violation.php

report-violation.php

507 ms

report-violation.php

report-violation.php

283 ms

report-violation.php

report-violation.php

280 ms

report-violation.php

report-violation.php

292 ms

report-violation.php

report-violation.php

295 ms

report-violation.php

report-violation.php

302 ms

report-violation.php

report-violation.php

308 ms

report-violation.php

report-violation.php

312 ms

report-violation.php

report-violation.php

324 ms

report-violation.php

report-violation.php

337 ms

report-violation.php

report-violation.php

335 ms

report-violation.php

report-violation.php

356 ms

report-violation.php

report-violation.php

348 ms

report-violation.php

report-violation.php

361 ms

report-violation.php

report-violation.php

373 ms

report-violation.php

report-violation.php

362 ms

report-violation.php

report-violation.php

376 ms

report-violation.php

report-violation.php

382 ms

index.php

index.php

821 ms

report-violation.php

report-violation.php

389 ms

US-top-section-bg.webp

US-top-section-bg.webp

17 ms

myheritage_logo_inverse.svg

myheritage_logo_inverse.svg

14 ms

AccessibilityButtonInverse.svg

AccessibilityButtonInverse.svg

12 ms

logo.svg

logo.svg

16 ms

dna-genetic-groups-section-bg.webp

dna-genetic-groups-section-bg.webp

18 ms

ethnicity_card_face.webp

ethnicity_card_face.webp

18 ms

deep-nostalgia.webp

deep-nostalgia.webp

19 ms

discovery-bg.webp

discovery-bg.webp

19 ms

community.webp

community.webp

23 ms

devices-logo-desktop.webp

devices-logo-desktop.webp

22 ms

tablet.webp

tablet.webp

19 ms

mobile.webp

mobile.webp

20 ms

desktop.webp

desktop.webp

29 ms

Logos_US_1.png

Logos_US_1.png

23 ms

Logos_US_2.png

Logos_US_2.png

23 ms

Logos_US_3.png

Logos_US_3.png

24 ms

Logos_US_4.png

Logos_US_4.png

26 ms

Logos_US_1.png

Logos_US_1.png

24 ms

Logos_US_2.png

Logos_US_2.png

26 ms

Logos_US_3.png

Logos_US_3.png

25 ms

Logos_US_4.png

Logos_US_4.png

26 ms

companyhomequotesus_sprite.png

companyhomequotesus_sprite.png

27 ms

spacer.gif

spacer.gif

29 ms

GtmIframeLoaderBundled_vd7d622e4a031090f8d3bad13fe81b166.js

GtmIframeLoaderBundled_vd7d622e4a031090f8d3bad13fe81b166.js

3 ms

Accessibility Review

kindo.com accessibility score

90

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

[aria-*] attributes do not match their roles

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.

Best Practices

kindo.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

kindo.com SEO score

93

Search Engine Optimization Advices

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Kindo.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Kindo.com main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

kindo.com

Open Graph description is not detected on the main page of Kindo. 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: