ANCESTRY.COM Ancestry® | Genealogy, Family Trees & Family History Records

ancestry.com Website Information

Daily Unique Visits: 1,213,269

Daily Page Views: 9,706,152

Income Per Day: $9,706

Estimated Value: $10,482,480

This website is located in United States and is using following IP address 66.43.22.183. See the complete list of popular websites hosted in United States.

ancestry.com is registered under .COM top-level domain. Please check other sites in .COM zone.

Website ancestry.com is using the following name servers:

  • ns-1136.awsdns-14.org
  • ns-737.awsdns-28.net
  • ns-1865.awsdns-41.co.uk
  • ns-238.awsdns-29.com
  • ns-568.awsdns-07.net
  • ns-415.awsdns-51.com
  • ns-1996.awsdns-57.co.uk
  • ns-1429.awsdns-50.org

and is probably hosted by MYFAM-DC1 - Myfamily.com, Inc., US. See the full list of other websites hosted by MYFAM-DC1 - Myfamily.com, Inc., US.

The highest website ancestry.com position in Alexa rank database was 403 and the lowest rank position was 2467. Current position of ancestry.com in Alexa rank database is 1256.

Desktop speed score of ancestry.com (83/100) is better than the results of 79.34% of other sites and shows that the page is performing great on desktop computers.

Mobile usability score of ancestry.com (98/100) is better than the results of 68.65% of other sites and means that the page is mobile-friendly.

Mobile speed score of ancestry.com (59/100) is better than the results of 52.08% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.

Advertisement

ancestry.com Alexa Rank

The traffic rank is based on three months of aggregated historical traffic data from millions of Alexa Toolbar users and is a combined measure of page views and users.


ancestry.com whois

WHOIS gives you the ability to lookup any generic domains to find out the registered domain holder. WHOIS database are provided for information purposes only. It allows the public to check whether a specific domain name is still available or not and to obtain information related to the registration records of existing domain names.


Domain Name: ANCESTRY.COM
Registry Domain ID: 4417943_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.markmonitor.com
Registrar URL: http://www.markmonitor.com
Updated Date: 2017-09-27T00:45:10Z
Creation Date: 1995-05-16T04:00:00Z
Registry Expiry Date: 2019-05-17T04:00:00Z
Registrar: MarkMonitor Inc.
Registrar IANA ID: 292
Registrar Abuse Contact Email: abusecomplaints@markmonitor.com
Registrar Abuse Contact Phone: +1.2083895740
Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
Name Server: NS-1429.AWSDNS-50.ORG
Name Server: NS-1996.AWSDNS-57.CO.UK
Name Server: NS-415.AWSDNS-51.COM
Name Server: NS-737.AWSDNS-28.NET
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2018-06-29T12:23:55Z

ancestry.com server information

Servers Location

ancestry.com desktop page speed rank

Last tested: 2016-06-12


Desktop Speed Medium
83/100

ancestry.com Desktop Speed Test Quick Summary


priority - 16 Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 2 blocking script resources and 3 blocking CSS resources. This causes a delay in rendering your page.

Remove render-blocking JavaScript:

http://c.mfcreative.com/lib/tgn/combo.ashx?14/lib/…nager.js&14/js/mbox.js
http://myfamilycominc.tt.omtrdc.net/m2/myfamilycom…ferrer=&mboxVersion=57

Optimize CSS Delivery of the following:

http://c.mfcreative.com/lib/tgn/combo.ashx?14//css…s&14//css/v3/modal.css
https://c.mfcreative.com//SSS_FTB/1.1.163/CDN/css/v1.css
http://c.mfcreative.com/lib/tgn/combo.ashx?x/css/v…css&x/css/v3/modal.css

priority - 2 Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

http://atemda.com/UserMatch.ashx?bidderid=43&bidde…4b00-b30b-a1084ee7ae8d (1 second)
http://tags.tiqcdn.com/utag/ancestry/main/prod/utag.js (5 minutes)
http://connect.facebook.net/en_US/fbevents.js (20 minutes)
http://tags.tiqcdn.com/utag/tiqapp/utag.v.js?a=anc…01718&cb=1465687366680 (30 minutes)
http://stats.g.doubleclick.net/dc.js (2 hours)

priority - 0 Enable compression

Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.

Enable compression for the following resources to reduce their transfer size by 3.5KiB (57% reduction).

Compressing http://c.mfcreative.com/i/logo/ancestry.svg could save 2.9KiB (59% reduction).
Compressing http://pixel.mathtag.com/event/js?mt_id=471677&mt_…&s1=&s2=&s3=&mt_lim=10 could save 569B (49% reduction).

ancestry.com Desktop Resource Breakdown

Total Resources109
Number of Hosts40
Static Resources53
JavaScript Resources36
CSS Resources4

ancestry.com mobile page speed rank

Last tested: 2016-06-12


Mobile Speed Bad
59/100

ancestry.com Mobile Speed Test Quick Summary


priority - 64 Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 4 blocking script resources and 3 blocking CSS resources. This causes a delay in rendering your page.

Remove render-blocking JavaScript:

http://c.mfcreative.com/lib/tgn/combo.ashx?14/lib/…nager.js&14/js/mbox.js
http://myfamilycominc.tt.omtrdc.net/m2/myfamilycom…ferrer=&mboxVersion=57
http://c.mfcreative.com/js/v1/callout.js
http://myfamilycominc.tt.omtrdc.net/m2/myfamilycom…ferrer=&mboxVersion=57

Optimize CSS Delivery of the following:

http://c.mfcreative.com/lib/tgn/combo.ashx?14//css…s&14//css/v3/modal.css
https://c.mfcreative.com//SSS_FTB/1.1.163/CDN/css/v1.css
http://c.mfcreative.com/lib/tgn/combo.ashx?x/css/v…css&x/css/v3/modal.css

priority - 8 Prioritize visible content

Your page requires additional network round trips to render the above-the-fold content. For best performance, reduce the amount of HTML needed to render above-the-fold content.

The entire HTML response was not sufficient to render the above-the-fold content. This usually indicates that additional resources, loaded after HTML parsing, were required to render above-the-fold content. Prioritize visible content that is needed for rendering above-the-fold by including it directly in the HTML response.

Only about 47% of the final above-the-fold content could be rendered with the full HTML response.

priority - 3 Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

http://tags.tiqcdn.com/utag/ancestry/main/prod/utag.js (5 minutes)
http://connect.facebook.net/en_US/fbevents.js (20 minutes)
http://tags.tiqcdn.com/utag/tiqapp/utag.v.js?a=anc…01718&cb=1465687362467 (30 minutes)
http://stats.g.doubleclick.net/dc.js (2 hours)

priority - 0 Enable compression

Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.

Enable compression for the following resources to reduce their transfer size by 569B (49% reduction).

Compressing http://pixel.mathtag.com/event/js?mt_id=471677&mt_…&s1=&s2=&s3=&mt_lim=10 could save 569B (49% reduction).

ancestry.com Mobile Resource Breakdown

Total Resources103
Number of Hosts42
Static Resources42
JavaScript Resources37
CSS Resources4

ancestry.com mobile page usability

Last tested: 2016-06-12


Mobile Usability Good
98/100

ancestry.com Mobile Usability Test Quick Summary


priority - 1 Size tap targets appropriately

Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.

The following tap targets are close to other nearby tap targets and may need additional spacing around them.

The tap target <a id="Ftr_TL_SupportCenter_Link" href="http://help.ancestry.com/">Support Center</a> is close to 1 other tap targets.

The tap target <a id="Ftr_TL_Blog_Link" href="http://blogs.a….com/ancestry/" class="footerLink">Ancestry Blog</a> and 2 others are close to other tap targets.

ancestry.com Mobile Resource Breakdown

Total Resources103
Number of Hosts42
Static Resources42
JavaScript Resources37
CSS Resources4

ancestry.com HTML validation

Errors

Saw “<” when expecting an attribute name. Probable cause: Missing “>” immediately before.

Line: 5 Column: - 1
"... lang="en-US" <head> <met..."

Attribute “<head” not allowed on element “html” at this point.

Line: 5 Column: 16 - 6
"...TYPE html> <html class="r" lang="en-US" <head> <..."

A document must not include more than one “meta” element with a “charset” attribute.

Line: 8 Column: 2 - 25
"...tart --> <meta charset="utf-8" /> <!--..."

Bad value “text/xhtml;charset=utf-8” for attribute “content” on element “meta”: The legacy encoding declaration did not start with “text/html;”.

Line: 15 Column: 2 - 70
"....0" /> <meta http-equiv="Content-Type" content="text/xhtml;charset=utf-8" /> <!--..."

A document must not include both a “meta” element with an “http-equiv” attribute whose value is “content-type”, and a “meta” element with a “charset” attribute.

Line: 15 Column: 2 - 70
"....0" /> <meta http-equiv="Content-Type" content="text/xhtml;charset=utf-8" /> <!--..."

Element “style” not allowed as child of element “body” in this context. (Suppressing further errors from this subtree.)

Line: 124 Column: 1 - 7
"...</script> <style> ...." Line: 135 Column: 1 - 7
"...sheet" /> <style> /..." Line: 200 Column: 1 - 7
"...ction --> <style> /* ta..." Line: 333 Column: 1 - 7
"...ction --> <style> ...." Line: 462 Column: 1 - 7
"...ction --> <style> #..." Line: 507 Column: 1 - 7
"...ction --> <style> ...." Line: 543 Column: 1 - 7
".../section> <style> .coco..." Line: 593 Column: 1 - 7
"...ction --> <style> ...." Line: 780 Column: 1 - 7
"...ction --> <style> ...." Line: 845 Column: 1 - 7
"...ction --> <style> ...." Line: 863 Column: 1 - 7
"...ction --> <style> #..."

Duplicate attribute “id”.

Line: 194 Column: - 197
"... navAccount" id="navAccount" d..."

An “img” element must have an “alt” attribute, except under certain conditions. For details, consult guidance on providing text alternatives for images.

Line: 582 Column: 13 - 136
"... <img class="cocoCopy" src="https://www.ancestrycdn.com/mars/landing/landing-pages/2017/us/coco/us-2957-pg-disney-pixar.png"> ..."

Warnings

Attribute “<head” is not serializable as XML 1.0.

Line: 5 Column: 16 - 6
"...TYPE html> <html class="r" lang="en-US" <head> <..."

Section lacks heading. Consider using “h2”-“h6” elements to add identifying headings to all sections.

Line: 577 Column: 1 - 31
"... </style> <section class="cocoBladeWrap"> <..."

The “contentinfo” role is unnecessary for element “footer”.

Line: 951 Column: 68 - 130
"...08:45Z --><footer class="footer clearfix" id="footer" role="contentinfo"> <div..."

ancestry.com similar domains

Similar domains:
www.ancestry.com
www.ancestry.net
www.ancestry.org
www.ancestry.info
www.ancestry.biz
www.ancestry.us
www.ancestry.mobi
www.ncestry.com
www.ancestry.com
www.qncestry.com
www.aqncestry.com
www.qancestry.com
www.wncestry.com
www.awncestry.com
www.wancestry.com
www.sncestry.com
www.asncestry.com
www.sancestry.com
www.zncestry.com
www.azncestry.com
www.zancestry.com
www.acestry.com
www.abcestry.com
www.anbcestry.com
www.abncestry.com
www.ahcestry.com
www.anhcestry.com
www.ahncestry.com
www.ajcestry.com
www.anjcestry.com
www.ajncestry.com
www.amcestry.com
www.anmcestry.com
www.amncestry.com
www.anestry.com
www.anxestry.com
www.ancxestry.com
www.anxcestry.com
www.andestry.com
www.ancdestry.com
www.andcestry.com
www.anfestry.com
www.ancfestry.com
www.anfcestry.com
www.anvestry.com
www.ancvestry.com
www.anvcestry.com
www.ancstry.com
www.ancwstry.com
www.ancewstry.com
www.ancwestry.com
www.ancsstry.com
www.ancesstry.com
www.ancsestry.com
www.ancdstry.com
www.ancedstry.com
www.ancrstry.com
www.ancerstry.com
www.ancrestry.com
www.ancetry.com
www.ancewtry.com
www.anceswtry.com
www.anceetry.com
www.ancesetry.com
www.anceestry.com
www.ancedtry.com
www.ancesdtry.com
www.anceztry.com
www.ancesztry.com
www.ancezstry.com
www.ancextry.com
www.ancesxtry.com
www.ancexstry.com
www.anceatry.com
www.ancesatry.com
www.anceastry.com
www.ancesry.com
www.ancesrry.com
www.ancestrry.com
www.ancesrtry.com
www.ancesfry.com
www.ancestfry.com
www.ancesftry.com
www.ancesgry.com
www.ancestgry.com
www.ancesgtry.com
www.ancesyry.com
www.ancestyry.com
www.ancesytry.com
www.ancesty.com
www.ancestey.com
www.ancestrey.com
www.ancestery.com
www.ancestdy.com
www.ancestrdy.com
www.ancestdry.com
www.ancestfy.com
www.ancestrfy.com
www.ancestty.com
www.ancestrty.com
www.ancesttry.com
www.ancestr.com
www.ancestrt.com
www.ancestryt.com
www.ancestrg.com
www.ancestryg.com
www.ancestrgy.com
www.ancestrh.com
www.ancestryh.com
www.ancestrhy.com
www.ancestru.com
www.ancestryu.com
www.ancestruy.com
www.ancestry.con

ancestry.com Ping

Ping is a computer network administration software utility used to test the reachability of a host on an Internet Protocol (IP) network. It measures the round-trip time for messages sent from the originating host to a destination computer that are echoed back to the source.


ancestry.com TRACEROUTE

Traceroute is a computer network diagnostic tool for displaying the route (path) and measuring transit delays of packets across an Internet Protocol (IP) network. The history of the route is recorded as the round-trip times of the packets received from each successive host (remote node) in the route (path); the sum of the mean times in each hop is a measure of the total time spent to establish the connection. Traceroute proceeds unless all (three) sent packets are lost more than twice, then the connection is lost and the route cannot be evaluated.