Tools & Wizards About Us
familysources.com screenshot

Report Summary

  • 83

    Performance

    Renders faster than
    87% of other websites

  • 63

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 67

    SEO

    Google-friendlier than
    26% of websites

familysources.com

FamilySources.com >>> A Personal Genealogy Site

Page Load Speed

2.8 sec in total

First Response

80 ms

Resources Loaded

2.6 sec

Page Rendered

165 ms

familysources.com screenshot

About Website

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

FamilySources.com is a personal genealogy site including Adams, McCrave, and Nyenhuis families, as well as many others...

Visit familysources.com

Key Findings

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

Performance Metrics

familysources.com performance score

83

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.2 s

79/100

10%

LCP (Largest Contentful Paint)

Value4.2 s

44/100

25%

SI (Speed Index)

Value2.8 s

96/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value2.2 s

99/100

10%

Network Requests Diagram

familysources.com

80 ms

familysources.com

1872 ms

mytngstyle.css

148 ms

slideshow.js

117 ms

urchin.js

7 ms

Our browser made a total of 25 requests to load all elements on the main page. We found that 96% of them (24 requests) were addressed to the original Familysources.com, 4% (1 request) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Familysources.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 16.2 kB (12%)

Content Size

138.0 kB

After Optimization

121.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-66%

Potential reduce by 4.7 kB

  • Original 7.1 kB
  • After minification 7.0 kB
  • After compression 2.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 4.7 kB or 66% of the original size.

Image Optimization

-0%

Potential reduce by 315 B

  • Original 111.2 kB
  • After minification 110.8 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 Sources images are well optimized though.

JavaScript Optimization

-48%

Potential reduce by 6.9 kB

  • Original 14.3 kB
  • After minification 12.8 kB
  • After compression 7.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 6.9 kB or 48% of the original size.

CSS Optimization

-79%

Potential reduce by 4.3 kB

  • Original 5.4 kB
  • After minification 3.6 kB
  • After compression 1.1 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. Familysources.com needs all CSS files to be minified and compressed as it can save up to 4.3 kB or 79% of the original size.

Requests Breakdown

Number of requests can be reduced by 6 (26%)

Requests Now

23

After Optimization

17

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

familysources.com

familysources.com

80 ms

familysources.com

familysources.com

1872 ms

mytngstyle.css

mytngstyle.css

148 ms

slideshow.js

slideshow.js

117 ms

urchin.js

urchin.js

7 ms

surnamesearch.gif

surnamesearch.gif

201 ms

arrow.gif

arrow.gif

195 ms

nav_divider.jpg

nav_divider.jpg

323 ms

photo_left.gif

photo_left.gif

311 ms

photo_right4.jpg

photo_right4.jpg

285 ms

photo_right2.jpg

photo_right2.jpg

156 ms

photo_right3.jpg

photo_right3.jpg

318 ms

photo_right1.jpg

photo_right1.jpg

353 ms

unsolved_mysteries.gif

unsolved_mysteries.gif

306 ms

divider_ornament.gif

divider_ornament.gif

447 ms

latest_news.gif

latest_news.gif

412 ms

begin_your_search.gif

begin_your_search.gif

447 ms

records.gif

records.gif

427 ms

spacer.gif

spacer.gif

490 ms

button_search.gif

button_search.gif

474 ms

background_red.gif

background_red.gif

155 ms

bg_content.jpg

bg_content.jpg

119 ms

logo.jpg

logo.jpg

261 ms

background_content.gif

background_content.gif

131 ms

divider_content.gif

divider_content.gif

281 ms

Accessibility Review

familysources.com accessibility score

63

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

familysources.com best practices score

58

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

familysources.com SEO score

67

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

    N/A

  • Encoding

    UTF-8

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

familysources.com

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