Tools & Wizards About Us
ourfamilyancestors.com screenshot

Report Summary

  • 95

    Performance

    Renders faster than
    93% of other websites

  • 46

    Accessibility

    Visual factors better than
    that of 19% of websites

  • 50

    Best Practices

    More advanced features
    available than in
    18% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

ourfamilyancestors.com

Our Family Ancestors - Helping You Discover Your Roots!

Page Load Speed

21.4 sec in total

First Response

211 ms

Resources Loaded

20.9 sec

Page Rendered

268 ms

ourfamilyancestors.com screenshot

About Website

Click here to check amazing Our Family Ancestors content. Otherwise, check out these important facts you probably never knew about ourfamilyancestors.com

Searchable genealogy database and family history site with 5,000+ surnames including Lisle, Mayo, Beardsley, Ferguson, Hamilton, Stallings, Winslett, and Walton. Includes historical articles, obituari...

Visit ourfamilyancestors.com

Key Findings

We analyzed Ourfamilyancestors.com page load time and found that the first response time was 211 ms and then it took 21.2 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number 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

ourfamilyancestors.com performance score

95

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.4 s

97/100

10%

LCP (Largest Contentful Paint)

Value2.8 s

82/100

25%

SI (Speed Index)

Value1.5 s

100/100

10%

TBT (Total Blocking Time)

Value20 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.037

100/100

15%

TTI (Time to Interactive)

Value2.4 s

99/100

10%

Network Requests Diagram

ourfamilyancestors.com

211 ms

ourfamilyancestors.com

273 ms

xaramenu.js

67 ms

mezzo2.js

131 ms

show_ads.js

70 ms

Our browser made a total of 75 requests to load all elements on the main page. We found that 43% of them (32 requests) were addressed to the original Ourfamilyancestors.com, 8% (6 requests) were made to Googleads.g.doubleclick.net and 5% (4 requests) were made to Yceml.net. The less responsive or slowest element that took the longest time to load (20.4 sec) relates to the external source Footnote.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 359.9 kB (56%)

Content Size

637.3 kB

After Optimization

277.5 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Ourfamilyancestors.com main page is 637.3 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. 20% of websites need less resources to load. Javascripts take 569.9 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 45.2 kB

  • Original 57.6 kB
  • After minification 53.8 kB
  • After compression 12.4 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 45.2 kB or 78% of the original size.

Image Optimization

-6%

Potential reduce by 564 B

  • Original 9.8 kB
  • After minification 9.2 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. Our Family Ancestors images are well optimized though.

JavaScript Optimization

-55%

Potential reduce by 314.1 kB

  • Original 569.9 kB
  • After minification 569.9 kB
  • After compression 255.8 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 314.1 kB or 55% of the original size.

Requests Breakdown

Number of requests can be reduced by 14 (25%)

Requests Now

55

After Optimization

41

  • AJAX
  • Images
  • JavaScript

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

Network Requests Diagram

ourfamilyancestors.com

ourfamilyancestors.com

211 ms

ourfamilyancestors.com

ourfamilyancestors.com

273 ms

xaramenu.js

xaramenu.js

67 ms

mezzo2.js

mezzo2.js

131 ms

show_ads.js

show_ads.js

70 ms

code.php

code.php

333 ms

image-2387487-10469560

image-2387487-10469560

59 ms

image-2387487-10376630

image-2387487-10376630

33 ms

Logo_25wht.gif

Logo_25wht.gif

9 ms

image-2387487-10470486

image-2387487-10470486

82 ms

tplimage

tplimage

116 ms

51046_blk_razr_120x60.jpg

51046_blk_razr_120x60.jpg

5 ms

image-2387487-9700744

image-2387487-9700744

27 ms

120x600_Download1.gif

120x600_Download1.gif

20398 ms

gentrack.asp

gentrack.asp

36 ms

urchin.js

urchin.js

8 ms

r6105jy1qwuFIJONKONFHGKMNMGP

r6105jy1qwuFIJONKONFHGKMNMGP

26 ms

n870z15u-yJMNSROSRJLKOPQSSP

n870z15u-yJMNSROSRJLKOPQSSP

57 ms

image-2387487-5042818

image-2387487-5042818

56 ms

banner

banner

115 ms

OFAResearch2.jpg

OFAResearch2.jpg

183 ms

JuneLisle_small.gif

JuneLisle_small.gif

189 ms

desperate.gif

desperate.gif

191 ms

SEGenealogy.gif

SEGenealogy.gif

191 ms

homsbanner41.gif

homsbanner41.gif

192 ms

BYDHbanner.gif

BYDHbanner.gif

205 ms

MAILBOX.GIF

MAILBOX.GIF

253 ms

Ancestor_Too.gif

Ancestor_Too.gif

254 ms

image-2384453-10469564

image-2384453-10469564

79 ms

image-2387487-10413110

image-2387487-10413110

80 ms

image-2387487-10428552

image-2387487-10428552

28 ms

10428552-1567794298541

10428552-1567794298541

46 ms

10376630-1639479607172

10376630-1639479607172

22 ms

www.ancestry.com

www.ancestry.com

70 ms

qassia88x31.gif

qassia88x31.gif

263 ms

5042818-1567790017004

5042818-1567790017004

9 ms

10413110-1567792035839

10413110-1567792035839

26 ms

adsbygoogle.js

adsbygoogle.js

119 ms

mezzo2_left.gif

mezzo2_left.gif

158 ms

mezzo2_b1_over.gif

mezzo2_b1_over.gif

159 ms

mezzo2_b1.gif

mezzo2_b1.gif

159 ms

mezzo2_b2_over.gif

mezzo2_b2_over.gif

160 ms

mezzo2_b2.gif

mezzo2_b2.gif

168 ms

mezzo2_b3_over.gif

mezzo2_b3_over.gif

181 ms

mezzo2_b3.gif

mezzo2_b3.gif

180 ms

mezzo2_b4_over.gif

mezzo2_b4_over.gif

181 ms

mezzo2_b4.gif

mezzo2_b4.gif

183 ms

mezzo2_b5_over.gif

mezzo2_b5_over.gif

197 ms

mezzo2_b5.gif

mezzo2_b5.gif

230 ms

mezzo2_b6_over.gif

mezzo2_b6_over.gif

244 ms

mezzo2_b6.gif

mezzo2_b6.gif

245 ms

mezzo2_b7_over.gif

mezzo2_b7_over.gif

243 ms

mezzo2_b7.gif

mezzo2_b7.gif

247 ms

mezzo2_b8_over.gif

mezzo2_b8_over.gif

261 ms

mezzo2_b8.gif

mezzo2_b8.gif

291 ms

mezzo2_b9_over.gif

mezzo2_b9_over.gif

307 ms

mezzo2_b9.gif

mezzo2_b9.gif

307 ms

mezzo2_right.gif

mezzo2_right.gif

309 ms

show_ads_impl.js

show_ads_impl.js

283 ms

zrt_lookup.html

zrt_lookup.html

19 ms

ads

ads

36 ms

ads

ads

38 ms

120_240_search.jpg

120_240_search.jpg

33 ms

search_sm.gif

search_sm.gif

28 ms

ads

ads

46 ms

tplimage

tplimage

103 ms

ads

ads

41 ms

gentrack.asp

gentrack.asp

23 ms

468_60_search.jpg

468_60_search.jpg

18 ms

search_sm.gif

search_sm.gif

17 ms

banner

banner

104 ms

ads

ads

82 ms

__utm.gif

__utm.gif

26 ms

qassia88x31.gif

qassia88x31.gif

16 ms

www.ancestry.com

www.ancestry.com

22 ms

Accessibility Review

ourfamilyancestors.com accessibility score

46

Accessibility Issues

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

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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

ourfamilyancestors.com best practices score

50

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

General

Impact

Issue

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

ourfamilyancestors.com SEO score

69

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

Image elements do not have [alt] attributes

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 Ourfamilyancestors.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 Ourfamilyancestors.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

ourfamilyancestors.com

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