1.3 sec in total
335 ms
866 ms
134 ms
Click here to check amazing Whosyerdad E content. Otherwise, check out these important facts you probably never knew about whosyerdad-e.com
Collaboratively create, edit and view your family history online using the latest genealogy software.
Visit whosyerdad-e.comWe analyzed Whosyerdad-e.com page load time and found that the first response time was 335 ms and then it took 1000 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.
whosyerdad-e.com performance score
name
value
score
weighting
Value2.4 s
69/100
10%
Value9.0 s
1/100
25%
Value4.9 s
64/100
10%
Value550 ms
54/100
30%
Value0.301
39/100
15%
Value9.6 s
29/100
10%
335 ms
61 ms
115 ms
33 ms
81 ms
Our browser made a total of 51 requests to load all elements on the main page. We found that 39% of them (20 requests) were addressed to the original Whosyerdad-e.com, 14% (7 requests) were made to Apis.google.com and 10% (5 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (335 ms) belongs to the original domain Whosyerdad-e.com.
Page size can be reduced by 495.0 kB (53%)
938.6 kB
443.6 kB
In fact, the total size of Whosyerdad-e.com main page is 938.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. 55% of websites need less resources to load. Javascripts take 739.5 kB which makes up the majority of the site volume.
Potential reduce by 19.1 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 19.1 kB or 65% of the original size.
Potential reduce by 6.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. Whosyerdad E images are well optimized though.
Potential reduce by 454.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 454.8 kB or 61% of the original size.
Potential reduce by 14.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. Whosyerdad-e.com needs all CSS files to be minified and compressed as it can save up to 14.9 kB or 89% of the original size.
Number of requests can be reduced by 24 (48%)
50
26
The browser has sent 50 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Whosyerdad E. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and as a result speed up the page load time.
whosyerdad-e.com
335 ms
styles.css
61 ms
swfobject.js
115 ms
all.js
33 ms
plusone.js
81 ms
show_ads.js
32 ms
brand
25 ms
dc.js
97 ms
get_flash_player.gif
258 ms
horizontal_solution_PP.gif
238 ms
googlelogo_lightgrey_46x16dp.png
182 ms
cb=gapi.loaded_0
79 ms
ca-pub-1157176502839981.js
189 ms
zrt_lookup.html
168 ms
show_ads_impl.js
102 ms
cb=gapi.loaded_1
126 ms
fastbutton
140 ms
background.jpg
119 ms
toplineblu.jpg
90 ms
logo.jpg
172 ms
lines_m.jpg
156 ms
btn_home.jpg
154 ms
btn_aboutus.jpg
155 ms
btn_register.jpg
143 ms
btn_sitemap.jpg
154 ms
btn_emailus.jpg
218 ms
main_back.jpg
317 ms
h_welcome.jpg
218 ms
arrow1.jpg
217 ms
h_latestnews.jpg
217 ms
arrow2.jpg
218 ms
h_genealogyresearch.jpg
277 ms
group.jpg
278 ms
h_registernow.jpg
276 ms
pixel.gif
115 ms
x-click-but21.gif
135 ms
148 ms
0sTQzbapM8j.js
108 ms
0sTQzbapM8j.js
144 ms
__utm.gif
44 ms
like.php
203 ms
rum.js
68 ms
ads
206 ms
osd.js
54 ms
postmessageRelay
67 ms
rs=AGLTcCOnDxwX8-LbpDmaxOBIoHm7W_kGNA
19 ms
971028622-postmessagerelay.js
49 ms
rpc:shindig_random.js
26 ms
4qFiRLLPSF7.js
25 ms
lH1ibRl5GKq.png
17 ms
cb=gapi.loaded_0
5 ms
whosyerdad-e.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
whosyerdad-e.com 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
whosyerdad-e.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Whosyerdad-e.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 Whosyerdad-e.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.
whosyerdad-e.com
Open Graph description is not detected on the main page of Whosyerdad E. 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: