24.7 sec in total
731 ms
23.7 sec
224 ms
Visit familytree.co.za now to see the best up-to-date Familytree content and also check out these interesting facts you probably never knew about familytree.co.za
I help many clients with challenging and problematic family history’s as well as difficulties in tracing their family trees. Using online and offline resource, my expertise will provide you with the a...
Visit familytree.co.zaWe analyzed Familytree.co.za page load time and found that the first response time was 731 ms and then it took 23.9 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.
familytree.co.za performance score
name
value
score
weighting
Value8.0 s
0/100
10%
Value8.4 s
2/100
25%
Value16.5 s
0/100
10%
Value1,900 ms
8/100
30%
Value0.174
69/100
15%
Value17.2 s
4/100
10%
731 ms
3127 ms
589 ms
779 ms
823 ms
Our browser made a total of 141 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Familytree.co.za, 1% (2 requests) were made to Cdn.jsdelivr.net and 1% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (3.1 sec) relates to the external source Ancestors.co.za.
Page size can be reduced by 142.2 kB (16%)
910.6 kB
768.4 kB
In fact, the total size of Familytree.co.za main page is 910.6 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. 50% of websites need less resources to load. Javascripts take 486.0 kB which makes up the majority of the site volume.
Potential reduce by 96.0 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 96.0 kB or 81% of the original size.
Potential reduce by 551 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. Familytree images are well optimized though.
Potential reduce by 38.1 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. This website has mostly compressed JavaScripts.
Potential reduce by 7.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.co.za has all CSS files already compressed.
Number of requests can be reduced by 129 (95%)
136
7
The browser has sent 136 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 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 82 to 1 for JavaScripts and from 49 to 1 for CSS and as a result speed up the page load time.
ancestors.co.za
731 ms
www.ancestors.co.za
3127 ms
dashicons.min.css
589 ms
jquery-ui-dialog.min.css
779 ms
style.css
823 ms
custom.css
792 ms
ngg-smart-image-search-public.css
863 ms
genericons.css
1059 ms
fancybox.css
34 ms
form-basic.css
891 ms
style.css
1093 ms
style.css
1105 ms
pum-site-styles.css
1177 ms
f0bd1feef983b97447056d0f1e58d444.min.css
2089 ms
min-shbp.min.css
1230 ms
min-768-max-1024-l.min.css
1424 ms
min-sh-cbp.min.css
1481 ms
jquery.min.js
1711 ms
jquery-migrate.min.js
1539 ms
lity.min.js
1559 ms
pressure.js
1741 ms
custom.js
1810 ms
ngg-smart-image-search-public.js
1847 ms
js
64 ms
style.min.css
1883 ms
core.min.js
2006 ms
mouse.min.js
2059 ms
resizable.min.js
2200 ms
draggable.min.js
2201 ms
controlgroup.min.js
2228 ms
checkboxradio.min.js
2324 ms
button.min.js
2362 ms
dialog.min.js
2412 ms
index.js
2416 ms
index.js
2471 ms
fancybox.umd.js
41 ms
fancyapps-fancybind-v-5-0.js
2520 ms
new-tab.js
2574 ms
pum-site-scripts.js
2706 ms
api.js
39 ms
wp-polyfill-inert.min.js
2735 ms
regenerator-runtime.min.js
2788 ms
wp-polyfill.min.js
2454 ms
index.js
2072 ms
modernizr.js
2118 ms
fusion-column-bg-image.js
2253 ms
cssua.js
2285 ms
fusion.js
2257 ms
bootstrap.transition.js
2089 ms
bootstrap.modal.js
2156 ms
jquery.waypoints.js
2273 ms
css
33 ms
jquery.requestAnimationFrame.js
2210 ms
jquery.easing.js
2189 ms
jquery.fitvids.js
1994 ms
jquery.flexslider.js
2019 ms
jquery.hoverintent.js
2016 ms
jquery.ilightbox.js
2186 ms
jquery.mousewheel.js
2009 ms
jquery.placeholder.js
2001 ms
jquery.fade.js
1949 ms
fusion-equal-heights.js
2001 ms
fusion-parallax.js
2002 ms
fusion-video-general.js
2030 ms
fusion-video-bg.js
1978 ms
fusion-waypoints.js
1864 ms
fusion-lightbox.js
1864 ms
js
57 ms
analytics.js
34 ms
jquery.sticky-kit.js
1911 ms
vimeoPlayer.js
1983 ms
collect
54 ms
collect
33 ms
lazysizes.js
2047 ms
avada-skip-link-focus-fix.js
1998 ms
avada-general-footer.js
1982 ms
avada-quantity.js
1981 ms
avada-crossfade-images.js
1956 ms
avada-select.js
1987 ms
avada-tabs-widget.js
2124 ms
recaptcha__it.js
28 ms
avada-contact-form-7.js
1981 ms
jquery.elasticslider.js
1971 ms
fusion-alert.js
1931 ms
fusion-animations.js
1918 ms
fusion-button.js
1918 ms
fusion-menu.js
1958 ms
fusion-flexslider.js
1957 ms
fusion-container.js
1935 ms
fusion-modal.js
1933 ms
avada-elastic-slider.js
1945 ms
avada-drop-down.js
1917 ms
avada-to-top.js
1953 ms
avada-custom-header.js
1929 ms
avada-sidebars.js
1963 ms
bootstrap.scrollspy.js
1964 ms
avada-scrollspy.js
1895 ms
fusion-responsive-typography.js
1938 ms
fusion-scroll-to-anchor.js
1884 ms
fusion-general-global.js
1887 ms
fusion-vertical-menu-widget.js
1928 ms
fusion-video.js
1921 ms
fusion-column.js
1848 ms
fa-solid-900.woff
2181 ms
fa-regular-400.woff
1849 ms
icomoon.woff
1895 ms
ancestors-hero-image.jpg
2175 ms
css.php
1910 ms
ancestors-logo-transparent-130x130.jpg
1606 ms
max-1c.min.css
288 ms
max-2c.min.css
298 ms
min-2c-max-3c.min.css
311 ms
min-3c-max-4c.min.css
314 ms
min-4c-max-5c.min.css
306 ms
min-5c-max-6c.min.css
277 ms
max-shbp.min.css
323 ms
max-sh-shbp.min.css
282 ms
min-768-max-1024-p.min.css
290 ms
max-sh-cbp.min.css
298 ms
max-sh-sbp.min.css
270 ms
max-sh-640.min.css
273 ms
max-shbp-18.min.css
283 ms
max-shbp-32.min.css
272 ms
max-640.min.css
277 ms
max-main.min.css
278 ms
max-cbp.min.css
281 ms
max-sh-cbp-cf7.min.css
291 ms
max-sh-cbp-eslider.min.css
284 ms
min-768-max-1024-p-social-sharing.min.css
276 ms
max-sh-640-social-sharing.min.css
270 ms
max-640-social-sharing.min.css
277 ms
max-sh-cbp-social-sharing.min.css
288 ms
max-sh-cbp.min.css
274 ms
min-768-max-1024-p.min.css
281 ms
max-640.min.css
267 ms
max-1c.css
269 ms
max-2c.css
276 ms
min-2c-max-3c.css
267 ms
min-3c-max-4c.css
286 ms
min-4c-max-5c.css
270 ms
min-5c-max-6c.css
270 ms
familytree.co.za accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Image elements do not have [alt] attributes
familytree.co.za best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
familytree.co.za SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
Tap targets are not sized appropriately
![]()
EN
![]()
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Familytree.co.za 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.co.za 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.
familytree.co.za
Open Graph data is detected on the main page of Familytree. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: