4 sec in total
1.1 sec
2.7 sec
165 ms
Click here to check amazing Familytree Zeem content for Saudi Arabia. Otherwise, check out these important facts you probably never knew about familytree.zeem.sa
Visit familytree.zeem.saWe analyzed Familytree.zeem.sa page load time and found that the first response time was 1.1 sec and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
familytree.zeem.sa performance score
name
value
score
weighting
Value1.9 s
87/100
10%
Value2.8 s
83/100
25%
Value2.4 s
98/100
10%
Value110 ms
98/100
30%
Value0.053
98/100
15%
Value2.6 s
98/100
10%
1126 ms
291 ms
205 ms
566 ms
293 ms
Our browser made a total of 49 requests to load all elements on the main page. We found that 98% of them (48 requests) were addressed to the original Familytree.zeem.sa, 2% (1 request) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Familytree.zeem.sa.
Page size can be reduced by 628.8 kB (24%)
2.6 MB
2.0 MB
In fact, the total size of Familytree.zeem.sa main page is 2.6 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. 40% of websites need less resources to load. Images take 1.8 MB which makes up the majority of the site volume.
Potential reduce by 20.6 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 4.6 kB, which is 18% 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 20.6 kB or 82% of the original size.
Potential reduce by 3.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. Familytree Zeem images are well optimized though.
Potential reduce by 227.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 227.6 kB or 70% of the original size.
Potential reduce by 376.8 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.zeem.sa needs all CSS files to be minified and compressed as it can save up to 376.8 kB or 85% of the original size.
Number of requests can be reduced by 37 (84%)
44
7
The browser has sent 44 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Familytree Zeem. 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 21 to 1 for CSS and as a result speed up the page load time.
familytree.zeem.sa
1126 ms
wp-emoji-release.min.js
291 ms
pagenavi-css.css
205 ms
bootstrap.min.css
566 ms
bootstrap-rtl.min.css
293 ms
font-awesome.min.css
299 ms
awesome-bootstrap-checkbox.css
202 ms
bootstrap-select.min.css
295 ms
uikit.almost-flat.min.css
671 ms
dotnav.almost-flat.min.css
374 ms
slidenav.almost-flat.min.css
376 ms
slideshow.almost-flat.min.css
378 ms
slider.almost-flat.min.css
387 ms
sticky.almost-flat.min.css
466 ms
accordion.almost-flat.min.css
467 ms
tooltip.almost-flat.min.css
468 ms
hover-min.css
770 ms
familytree.css
569 ms
responsive.css
568 ms
gform-edit.css
572 ms
treeapp.css
645 ms
style.css
649 ms
jquery-1.11.3.min.js
927 ms
js.js
599 ms
bootstrap.min.js
686 ms
bootstrap-select.min.js
780 ms
uikit.min.js
877 ms
slideshow.min.js
699 ms
slideset.min.js
778 ms
accordion.min.js
793 ms
tooltip.min.js
809 ms
pagination.min.js
868 ms
sticky.min.js
870 ms
lightbox.min.js
886 ms
gravityformedit.js
871 ms
masonry.pkgd.min.js
925 ms
imagesloaded.pkgd.min.js
17 ms
js.js
926 ms
wp-embed.min.js
832 ms
custom-fonts.css
455 ms
nav-trigger.png
179 ms
logo.png
178 ms
01.jpg
565 ms
04.jpg
645 ms
03.jpg
556 ms
Noor-Regular.woff
95 ms
Noor-Bold.woff
99 ms
fontawesome-webfont.woff
290 ms
fontawesome-webfont.woff
369 ms
familytree.zeem.sa 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.
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.zeem.sa best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
familytree.zeem.sa SEO score
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
AR
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Familytree.zeem.sa can be misinterpreted by Google and other search engines. Our service has detected that Arabic 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 Familytree.zeem.sa 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.zeem.sa
Open Graph description is not detected on the main page of Familytree Zeem. 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: