779 ms in total
54 ms
644 ms
81 ms
Click here to check amazing Forums Family Search content for United States. Otherwise, check out these important facts you probably never knew about forums.familysearch.org
Discover your family history. Explore the world’s largest collection of free family trees, genealogy records and resources.
Visit forums.familysearch.orgWe analyzed Forums.familysearch.org page load time and found that the first response time was 54 ms and then it took 725 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.
forums.familysearch.org performance score
54 ms
205 ms
210 ms
216 ms
211 ms
Our browser made a total of 28 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Forums.familysearch.org, 4% (1 request) were made to Familysearch.org and 4% (1 request) were made to Consent.truste.com. The less responsive or slowest element that took the longest time to load (329 ms) relates to the external source Consent.truste.com.
Page size can be reduced by 407.1 kB (70%)
578.1 kB
171.1 kB
In fact, the total size of Forums.familysearch.org main page is 578.1 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. Javascripts take 371.4 kB which makes up the majority of the site volume.
Potential reduce by 30.5 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 5.7 kB, which is 14% 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 30.5 kB or 77% of the original size.
Potential reduce by 0 B
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. Forums Family Search images are well optimized though.
Potential reduce by 248.6 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 248.6 kB or 67% of the original size.
Potential reduce by 127.9 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. Forums.familysearch.org needs all CSS files to be minified and compressed as it can save up to 127.9 kB or 79% of the original size.
Number of requests can be reduced by 22 (85%)
26
4
The browser has sent 26 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Forums Family Search. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
54 ms
promise-428cb7815950deaef1f709031b7b10b6.js
205 ms
fetch-a0e2d5a1dec47fc320392f29334708a3.js
210 ms
usertiming-19176478921f925ed60496e825b1aa11.js
216 ms
clientManifest-cd156822b74036e17eb324c429a838df.js
211 ms
fs-31fa943df75b3afb78ad79ce3e166524.js
234 ms
familysearch-styles-c984c46f0de719c07bc34b101327b94e.css
217 ms
hf-308a9a8026eefd59225aa22ecf614b61.css
230 ms
hf-responsive-1e24d8acf4b16a84384ed69bbaba263c.css
243 ms
new_pages_new-94e65436134b982fc36702a857dff02c.css
245 ms
main-ad8f547ccfa4ea0ec34c6630e7c3191f.css
247 ms
inject-09b08fbbe21ff7e5aba4b511586ad1cf.js
254 ms
hf-585f3e05824b8e9451e15473b04649c1.js
263 ms
jquery-4637e41d8f0500d0cd40baad7ba2bae3.js
286 ms
angular.min-fa01f26d0b1419bb939f5d6401517f3e.js
287 ms
angular-route.min-02d70e660e425bca3477477b76dc240a.js
263 ms
xml2json-14e18c61520e999d6b2edfe9735ea963.js
281 ms
main-7a67d40319b54c8f72af071c9914e709.js
281 ms
bootstrap-4f96eb7a4efcdc2ca66ddcfd6d50e361.js
284 ms
notice
329 ms
tree-logotype-0x-3d2b7e16bde9d86e31d3503fd3d2c13e.png
32 ms
museo_slab_500-webfont-ec7fff86c753ba5b0c00df24d1f94a7f.woff
68 ms
lds-logo_en-e9a2bcbd46d8885b58dd4a26f387b5f1.png
31 ms
utag.js
66 ms
NewPages-69c6bdf3c6ebbfff083d8216abc98573.js
29 ms
Feedback-64c1a1c0e8d7f4bc4c17fbb8fe0d78ca.js
28 ms
get
60 ms
Feedback-731054d18a22fc55c241cefdcc8cd720.css
35 ms
forums.familysearch.org SEO score
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Forums.familysearch.org can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Forums.familysearch.org 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.
forums.familysearch.org
Open Graph description is not detected on the main page of Forums Family Search. 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: