Tools & Wizards About Us
e-familytree.net screenshot

Report Summary

  • 70

    Performance

    Renders faster than
    81% of other websites

  • 67

    Accessibility

    Visual factors better than
    that of 32% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 62

    SEO

    Google-friendlier than
    23% of websites

e-familytree.net

The genealogy of 750,000 people connected to European Royalty

Page Load Speed

23.5 sec in total

First Response

460 ms

Resources Loaded

21.4 sec

Page Rendered

1.6 sec

e-familytree.net screenshot

About Website

Welcome to e-familytree.net homepage info - get ready to check E Familytree best content for United States right away, or after learning these important things about e-familytree.net

The Genealogy of 800000 people connected with European Royalty

Visit e-familytree.net

Key Findings

We analyzed E-familytree.net page load time and found that the first response time was 460 ms and then it took 23 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

e-familytree.net performance score

70

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0.8 s

100/100

10%

LCP (Largest Contentful Paint)

Value0.9 s

100/100

25%

SI (Speed Index)

Value2.1 s

99/100

10%

TBT (Total Blocking Time)

Value1,270 ms

18/100

30%

CLS (Cumulative Layout Shift)

Value0.064

97/100

15%

TTI (Time to Interactive)

Value6.7 s

56/100

10%

Network Requests Diagram

e-familytree.net

460 ms

plusone.js

247 ms

show_ads.js

134 ms

cb=gapi.loaded_0

96 ms

a1.gif

671 ms

Our browser made a total of 64 requests to load all elements on the main page. We found that 5% of them (3 requests) were addressed to the original E-familytree.net, 16% (10 requests) were made to A.disquscdn.com and 13% (8 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (19.7 sec) relates to the external source A4085.pagevisit.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 387.6 kB (67%)

Content Size

579.9 kB

After Optimization

192.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of E-familytree.net main page is 579.9 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. 65% of websites need less resources to load. Javascripts take 533.2 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 16.7 kB

  • Original 22.7 kB
  • After minification 20.6 kB
  • After compression 5.9 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 16.7 kB or 74% of the original size.

Image Optimization

-0%

Potential reduce by 30 B

  • Original 20.3 kB
  • After minification 20.3 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. E Familytree images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 367.9 kB

  • Original 533.2 kB
  • After minification 493.4 kB
  • After compression 165.4 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 367.9 kB or 69% of the original size.

CSS Optimization

-81%

Potential reduce by 3.0 kB

  • Original 3.7 kB
  • After minification 2.4 kB
  • After compression 683 B

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. E-familytree.net needs all CSS files to be minified and compressed as it can save up to 3.0 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 40 (69%)

Requests Now

58

After Optimization

18

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

e-familytree.net

e-familytree.net

460 ms

plusone.js

plusone.js

247 ms

show_ads.js

show_ads.js

134 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

96 ms

a1.gif

a1.gif

671 ms

logo.jpg

logo.jpg

666 ms

ca-pub-1380569340830635.js

ca-pub-1380569340830635.js

288 ms

zrt_lookup.html

zrt_lookup.html

946 ms

show_ads_impl.js

show_ads_impl.js

284 ms

88x31.png

88x31.png

545 ms

index.htm

index.htm

802 ms

embed.js

embed.js

668 ms

ga.js

ga.js

311 ms

ads

ads

659 ms

osd.js

osd.js

535 ms

ads

ads

559 ms

__utm.gif

__utm.gif

151 ms

form.css

form.css

273 ms

formNegCap.css

formNegCap.css

289 ms

prototype.js

prototype.js

2119 ms

form.js

form.js

624 ms

visitor.gif

visitor.gif

258 ms

ads

ads

439 ms

visitor.gif

visitor.gif

19724 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

431 ms

fastbutton

fastbutton

887 ms

collect

collect

508 ms

326 ms

m_js_controller.js

m_js_controller.js

476 ms

abg.js

abg.js

728 ms

lounge.load.d074862f091cd9585b295f3979a4eb15.js

lounge.load.d074862f091cd9585b295f3979a4eb15.js

247 ms

css

css

507 ms

postmessageRelay

postmessageRelay

678 ms

lounge.f668c82e65f78693a6a62a5c7d3e54b8.css

lounge.f668c82e65f78693a6a62a5c7d3e54b8.css

389 ms

favicon

favicon

1133 ms

favicon

favicon

648 ms

googlelogo_color_112x36dp.png

googlelogo_color_112x36dp.png

645 ms

mobile_unified_button_icon_white.png

mobile_unified_button_icon_white.png

188 ms

config.js

config.js

306 ms

common.bundle.2604ea86c00f3bcc98e8fdc57114c1cc.js

common.bundle.2604ea86c00f3bcc98e8fdc57114c1cc.js

612 ms

lounge.bundle.453d0281788b539960d8683df769dd95.js

lounge.bundle.453d0281788b539960d8683df769dd95.js

598 ms

x_button_blue2.png

x_button_blue2.png

459 ms

s

s

840 ms

1077434459-postmessagerelay.js

1077434459-postmessagerelay.js

1956 ms

rpc:shindig_random.js

rpc:shindig_random.js

900 ms

PuwvqkdbcqU-fCZ9Ed-b7S3USBnSvpkopQaUR-2r7iU.ttf

PuwvqkdbcqU-fCZ9Ed-b7S3USBnSvpkopQaUR-2r7iU.ttf

2261 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

844 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

1742 ms

W5F8_SL0XFawnjxHGsZjJA.ttf

W5F8_SL0XFawnjxHGsZjJA.ttf

2075 ms

j6SDDiQit5YY48GNgPpnCluJgoNCzbKlh5o6eVjReZI.js

j6SDDiQit5YY48GNgPpnCluJgoNCzbKlh5o6eVjReZI.js

102 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

21 ms

ga.js

ga.js

629 ms

activeview

activeview

377 ms

loader.5cc23909da9c4a9874500d7a85c4125f.gif

loader.5cc23909da9c4a9874500d7a85c4125f.gif

470 ms

discovery.449c10a436c997c3eee5afd5021da3a2.css

discovery.449c10a436c997c3eee5afd5021da3a2.css

309 ms

688 ms

sprite.06bad3144429d24544aa8b00ffd77160.png

sprite.06bad3144429d24544aa8b00ffd77160.png

244 ms

16

16

246 ms

icons.dcb5405f8abc9a80e5628869f735eaf0.woff

icons.dcb5405f8abc9a80e5628869f735eaf0.woff

379 ms

noavatar92.4549c5353ccf103d32a8b81a856576ed.png

noavatar92.4549c5353ccf103d32a8b81a856576ed.png

205 ms

discovery.bundle.188b7afdc0cb75bb665bca3eb0ce9ba7.js

discovery.bundle.188b7afdc0cb75bb665bca3eb0ce9ba7.js

316 ms

event.gif

event.gif

407 ms

16

16

284 ms

__utm.gif

__utm.gif

145 ms

Accessibility Review

e-familytree.net accessibility score

67

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.

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

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

High

Image elements do not have [alt] attributes

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

e-familytree.net 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

User Experience

Impact

Issue

High

Serves images with low resolution

SEO Factors

e-familytree.net SEO score

62

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

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise E-familytree.net can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that E-familytree.net 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

e-familytree.net

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