Tools & Wizards About Us
familytree.com.au screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

familytree.com.au

Tracing Your Family History Made Easy with FamilyTree.com.au

Page Load Speed

3.6 sec in total

First Response

194 ms

Resources Loaded

3.2 sec

Page Rendered

258 ms

familytree.com.au screenshot

About Website

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

Explore and understand your family's history with the help of our advanced AI technology. Our comprehensive database of genealogy records and resources, interactive tools, and personalized recomm...

Visit familytree.com.au

Key Findings

We analyzed Familytree.com.au page load time and found that the first response time was 194 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

familytree.com.au performance score

0

Network Requests Diagram

familytree.com

194 ms

www.familytree.com

1181 ms

style.css

192 ms

slide-show.css

194 ms

jetpack.css

320 ms

Our browser made a total of 84 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Familytree.com.au, 14% (12 requests) were made to O.twimg.com and 12% (10 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Familytree.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 252.0 kB (21%)

Content Size

1.2 MB

After Optimization

946.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Familytree.com.au main page is 1.2 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. 60% of websites need less resources to load. Images take 896.8 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 38.1 kB

  • Original 47.9 kB
  • After minification 39.9 kB
  • After compression 9.8 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. This page needs HTML code to be minified as it can gain 7.9 kB, which is 17% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 38.1 kB or 80% of the original size.

Image Optimization

-6%

Potential reduce by 49.7 kB

  • Original 896.8 kB
  • After minification 847.1 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. Family Tree images are well optimized though.

JavaScript Optimization

-59%

Potential reduce by 107.7 kB

  • Original 183.2 kB
  • After minification 181.5 kB
  • After compression 75.5 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 107.7 kB or 59% of the original size.

CSS Optimization

-81%

Potential reduce by 56.6 kB

  • Original 70.3 kB
  • After minification 68.1 kB
  • After compression 13.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. Familytree.com.au needs all CSS files to be minified and compressed as it can save up to 56.6 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 37 (47%)

Requests Now

78

After Optimization

41

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

familytree.com

familytree.com

194 ms

www.familytree.com

www.familytree.com

1181 ms

style.css

style.css

192 ms

slide-show.css

slide-show.css

194 ms

jetpack.css

jetpack.css

320 ms

wp-paginate.css

wp-paginate.css

206 ms

jquery.js

jquery.js

440 ms

jquery-migrate.min.js

jquery-migrate.min.js

340 ms

B9333382.127099499;sz=300x250;ord=[timestamp];dc_lat=;dc_rdid=;tag_for_child_directed_treatment=

B9333382.127099499;sz=300x250;ord=[timestamp];dc_lat=;dc_rdid=;tag_for_child_directed_treatment=

52 ms

ga.js

ga.js

23 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

181 ms

__utm.gif

__utm.gif

20 ms

B9333382.127100863;sz=728x90;ord=[timestamp];dc_lat=;dc_rdid=;tag_for_child_directed_treatment=

B9333382.127100863;sz=728x90;ord=[timestamp];dc_lat=;dc_rdid=;tag_for_child_directed_treatment=

55 ms

quant.js

quant.js

75 ms

devicepx-jetpack.js

devicepx-jetpack.js

74 ms

e-201611.js

e-201611.js

76 ms

top-wrap-main.jpg

top-wrap-main.jpg

92 ms

logo.png

logo.png

350 ms

banner_bg.png

banner_bg.png

734 ms

img_homepage_beach-ads.jpg

img_homepage_beach-ads.jpg

504 ms

compare2.jpg

compare2.jpg

355 ms

surnames.png

surnames.png

503 ms

culture.png

culture.png

502 ms

heritage.png

heritage.png

761 ms

learn2.jpg

learn2.jpg

648 ms

research2.jpg

research2.jpg

712 ms

pinterest-button-300x150.jpg

pinterest-button-300x150.jpg

773 ms

modernizr_2.8.3_ec185bb44fe5e6bf7455d6e8ef37ed0e_no-classes.js

modernizr_2.8.3_ec185bb44fe5e6bf7455d6e8ef37ed0e_no-classes.js

153 ms

lidar.js

lidar.js

153 ms

likebox.php

likebox.php

253 ms

leftpan_bg.jpg

leftpan_bg.jpg

684 ms

right-pan_bg.jpg

right-pan_bg.jpg

807 ms

widgets.js

widgets.js

288 ms

__utm.gif

__utm.gif

63 ms

pixel;r=264923751;a=p-c3seWugRYFBGA;fpan=1;fpa=P0-7782892-1458271415654;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1458271415653;tzo=-180;ref=;url=https%3A%2F%2Fwww.familytree.com%2F;ogl=type.website%2Ctitle.Family%20Tree%2Cdescription.Genealogy%252C%20Ancestry%252C%20and%20Family%20Tree%20Research%2Curl.https%3A%2F%2Fwww%252Efamilytree%252Ecom%2F%2Csite_name.Family%20Tree%2Cimage.https%3A%2F%2Fs0%252Ewp%252Ecom%2Fi%2Fblank%252Ejpg%2Clocale.en_US

pixel;r=264923751;a=p-c3seWugRYFBGA;fpan=1;fpa=P0-7782892-1458271415654;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1458271415653;tzo=-180;ref=;url=https%3A%2F%2Fwww.familytree.com%2F;ogl=type.website%2Ctitle.Family%20Tree%2Cdescription.Genealogy%252C%20Ancestry%252C%20and%20Family%20Tree%20Research%2Curl.https%3A%2F%2Fwww%252Efamilytree%252Ecom%2F%2Csite_name.Family%20Tree%2Cimage.https%3A%2F%2Fs0%252Ewp%252Ecom%2Fi%2Fblank%252Ejpg%2Clocale.en_US

206 ms

g.gif

g.gif

158 ms

300x250.html

300x250.html

117 ms

728x90.html

728x90.html

67 ms

McLpmVM3wCm.css

McLpmVM3wCm.css

50 ms

VH4VPudaxfN.css

VH4VPudaxfN.css

72 ms

q68gy-v_YMF.js

q68gy-v_YMF.js

108 ms

FJmpeSpHpjS.js

FJmpeSpHpjS.js

108 ms

0wM5s1Khldu.js

0wM5s1Khldu.js

78 ms

1bNoFZUdlYZ.js

1bNoFZUdlYZ.js

107 ms

style.css

style.css

13 ms

css

css

195 ms

style.css

style.css

26 ms

timeline.d11f7a3b3287fb94220e8ee6d03cc772.js

timeline.d11f7a3b3287fb94220e8ee6d03cc772.js

139 ms

399122_324332214298054_64242432_n.jpg

399122_324332214298054_64242432_n.jpg

114 ms

548124_324334577631151_1236330705_n.jpg

548124_324334577631151_1236330705_n.jpg

90 ms

12821345_859454017496496_2937193375772444304_n.jpg

12821345_859454017496496_2937193375772444304_n.jpg

100 ms

9215_10206199387286273_3351253936256976467_n.jpg

9215_10206199387286273_3351253936256976467_n.jpg

101 ms

12705695_1687959654808987_7940540848032181856_n.jpg

12705695_1687959654808987_7940540848032181856_n.jpg

100 ms

12391971_10204125844301252_1958211906967228782_n.jpg

12391971_10204125844301252_1958211906967228782_n.jpg

99 ms

64739_10202918489749597_8952059066797049427_n.jpg

64739_10202918489749597_8952059066797049427_n.jpg

100 ms

10391861_539623349573683_1542518010821940032_n.jpg

10391861_539623349573683_1542518010821940032_n.jpg

104 ms

25215_111438992219937_650168_n.jpg

25215_111438992219937_650168_n.jpg

105 ms

wL6VQj7Ab77.png

wL6VQj7Ab77.png

26 ms

s7jcwEQH7Sx.png

s7jcwEQH7Sx.png

26 ms

image_728x90.jpg

image_728x90.jpg

37 ms

image_300x250.jpg

image_300x250.jpg

32 ms

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

73 ms

DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf

DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf

73 ms

MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf

MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf

110 ms

k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf

k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf

107 ms

syndication

syndication

147 ms

448184194611412992

448184194611412992

247 ms

I6-MnjEovm5.js

I6-MnjEovm5.js

46 ms

pQrUxxo5oQp.js

pQrUxxo5oQp.js

46 ms

proxy.jpg

proxy.jpg

31 ms

proxy.jpg

proxy.jpg

27 ms

proxy.jpg

proxy.jpg

32 ms

proxy.jpg

proxy.jpg

26 ms

proxy.jpg

proxy.jpg

33 ms

proxy.jpg

proxy.jpg

26 ms

proxy.jpg

proxy.jpg

36 ms

proxy.jpg

proxy.jpg

29 ms

proxy.jpg

proxy.jpg

29 ms

proxy.jpg

proxy.jpg

32 ms

proxy.jpg

proxy.jpg

36 ms

proxy.jpg

proxy.jpg

37 ms

timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css

timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css

45 ms

timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css

timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css

78 ms

pinit.js

pinit.js

51 ms

SEO Factors

familytree.com.au SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Familytree.com.au 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 Familytree.com.au 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

familytree.com.au

Open Graph data is detected on the main page of Family Tree. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: