14.7 sec in total
901 ms
13.7 sec
138 ms
Welcome to familytree.ru homepage info - get ready to check Family Tree best content for Russia right away, or after learning these important things about familytree.ru
soft,shareware,freeware,family tree of family,list imen,list family,dictionary name,dictionary familiy,история,программа,компьютер,архив,архивное дело,информация,информационные ресурсы,исторический ис...
Visit familytree.ruWe analyzed Familytree.ru page load time and found that the first response time was 901 ms and then it took 13.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
familytree.ru performance score
name
value
score
weighting
Value1.4 s
97/100
10%
Value10.3 s
0/100
25%
Value15.7 s
0/100
10%
Value2,200 ms
6/100
30%
Value0.018
100/100
15%
Value39.5 s
0/100
10%
901 ms
256 ms
805 ms
183 ms
810 ms
Our browser made a total of 289 requests to load all elements on the main page. We found that 86% of them (249 requests) were addressed to the original Familytree.ru, 2% (6 requests) were made to Mc.yandex.ru and 2% (5 requests) were made to Acint.net. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Familytree.ru.
Page size can be reduced by 232.6 kB (50%)
461.8 kB
229.2 kB
In fact, the total size of Familytree.ru main page is 461.8 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. Images take 223.6 kB which makes up the majority of the site volume.
Potential reduce by 49.9 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 11.6 kB, which is 19% 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 49.9 kB or 81% of the original size.
Potential reduce by 57.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. Obviously, Family Tree needs image optimization as it can save up to 57.8 kB or 26% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 124.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 124.8 kB or 71% of the original size.
Potential reduce by 93 B
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.ru needs all CSS files to be minified and compressed as it can save up to 93 B or 40% of the original size.
Number of requests can be reduced by 27 (10%)
280
253
The browser has sent 280 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Family Tree. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and as a result speed up the page load time.
familytree.ru
901 ms
style.css
256 ms
menu.js
805 ms
watch.js
183 ms
zp.js
810 ms
show_ads.js
8 ms
watch.js
444 ms
cycounter
259 ms
baner-new.jpg
605 ms
kgs2.gif
412 ms
flag-ru.png
259 ms
flag-en.png
259 ms
flag-de.png
268 ms
flag-fr.png
277 ms
flag-it.png
275 ms
flag-es.png
279 ms
flag-ro.png
514 ms
flag-ua.gif
529 ms
treeglob.gif
1180 ms
b_dvpt.gif
542 ms
bannerkoap.gif
670 ms
koapp.jpg
558 ms
bn88x31.jpg
771 ms
v_blue_on_white_ru.png
779 ms
sdk.js
71 ms
ad.jpg
765 ms
ae.jpg
782 ms
af.jpg
909 ms
ag.jpg
1034 ms
ai.jpg
1027 ms
al.jpg
1056 ms
am.jpg
1069 ms
an.jpg
1174 ms
ao.jpg
1295 ms
aq.jpg
1325 ms
ar.jpg
1314 ms
as.jpg
1346 ms
at.jpg
1417 ms
au.jpg
1444 ms
aw.jpg
1572 ms
az.jpg
1574 ms
ba.jpg
1604 ms
bb.jpg
1598 ms
bd.jpg
1666 ms
be.jpg
1711 ms
bf.jpg
1816 ms
bg.jpg
1826 ms
cnt
479 ms
hit
269 ms
51 ms
advert.gif
124 ms
paper.jpg
561 ms
zrt_lookup.html
29 ms
show_ads_impl.js
46 ms
ads
261 ms
aci.js
186 ms
xd_arbiter.php
67 ms
xd_arbiter.php
125 ms
osd.js
26 ms
bh.jpg
1632 ms
bi.jpg
1652 ms
bj.jpg
1697 ms
bm.jpg
1725 ms
bn.jpg
1822 ms
bo.jpg
1815 ms
like.php
92 ms
hit
131 ms
1
86 ms
vpc6VNjRPXV.js
132 ms
LVx-xkvaJ0b.png
141 ms
312419
111 ms
23414332
85 ms
94 ms
184 ms
u6986.72.spylog.com
370 ms
br.jpg
1678 ms
bs.jpg
1660 ms
bt.jpg
1687 ms
bv.jpg
1689 ms
263 ms
bw.jpg
1681 ms
by.jpg
1630 ms
bz.jpg
1676 ms
ca.jpg
1673 ms
cc.jpg
1684 ms
match
187 ms
cnt
239 ms
cf.jpg
1596 ms
counter2
158 ms
cg.jpg
1567 ms
ch.jpg
1619 ms
ck.jpg
1638 ms
cl.jpg
1627 ms
cm.jpg
1586 ms
cn.jpg
1581 ms
co.jpg
1559 ms
cr.jpg
1594 ms
cu.jpg
1622 ms
cv.jpg
1625 ms
cx.jpg
1592 ms
cy.jpg
1589 ms
cz.jpg
1547 ms
de.jpg
1605 ms
dj.jpg
1634 ms
dk.jpg
1626 ms
dm.jpg
1612 ms
do.jpg
1578 ms
dz.jpg
1546 ms
ec.jpg
1606 ms
ee.jpg
1624 ms
eg.jpg
1618 ms
eh.jpg
1622 ms
er.jpg
1579 ms
es.jpg
1541 ms
et.jpg
1626 ms
fi.jpg
1592 ms
fj.jpg
1595 ms
fk.jpg
1617 ms
fm.jpg
1604 ms
fr.jpg
1556 ms
ga.jpg
1585 ms
gd.jpg
1588 ms
ge.jpg
1607 ms
gf.jpg
1630 ms
gh.jpg
1594 ms
gi.jpg
1550 ms
gl.jpg
1590 ms
gm.jpg
1582 ms
gn.jpg
1601 ms
gp.jpg
1615 ms
gq.jpg
1604 ms
gr.jpg
1567 ms
gs.jpg
1597 ms
gt.jpg
1609 ms
gu.jpg
1588 ms
gw.jpg
1612 ms
gy.jpg
1593 ms
hk.jpg
1573 ms
hm.jpg
1575 ms
hn.jpg
1594 ms
hr.jpg
1593 ms
ht.jpg
1603 ms
hu.jpg
1595 ms
id.jpg
1589 ms
ie.jpg
1585 ms
il.jpg
1604 ms
in.jpg
1599 ms
io.jpg
1590 ms
iq.jpg
1584 ms
ir.jpg
1600 ms
is.jpg
1601 ms
it.jpg
1605 ms
jm.jpg
1593 ms
jo.jpg
1589 ms
jp.jpg
1597 ms
ke.jpg
1640 ms
kg.jpg
1636 ms
kh.jpg
1595 ms
ki.jpg
1594 ms
km.jpg
1620 ms
kn.jpg
1619 ms
kp.jpg
1672 ms
kr.jpg
1645 ms
kw.jpg
1599 ms
ky.jpg
1600 ms
kz.jpg
1612 ms
la.jpg
1617 ms
lb.jpg
1644 ms
lc.jpg
1630 ms
li.jpg
1587 ms
lk.jpg
1602 ms
lr.jpg
1603 ms
ls.jpg
1613 ms
lt.jpg
1640 ms
lu.jpg
1657 ms
lv.jpg
1589 ms
ly.jpg
1610 ms
ma.jpg
1638 ms
mc.jpg
1640 ms
md.jpg
1669 ms
mg.jpg
1647 ms
mh.jpg
1621 ms
mk.jpg
1627 ms
ml.jpg
1673 ms
mm.jpg
1671 ms
mn.jpg
1664 ms
mo.jpg
1612 ms
mp.jpg
1612 ms
mq.jpg
1629 ms
mr.jpg
1673 ms
ms.jpg
1686 ms
mt.jpg
1651 ms
mu.jpg
1575 ms
mv.jpg
1633 ms
mw.jpg
1638 ms
mx.jpg
1630 ms
my.jpg
1698 ms
mz.jpg
1619 ms
na.jpg
1568 ms
nc.jpg
1617 ms
ne.jpg
1631 ms
nf.jpg
1689 ms
ng.jpg
1694 ms
ni.jpg
1625 ms
nl.jpg
1613 ms
no.jpg
1646 ms
np.jpg
1636 ms
nr.jpg
1690 ms
nu.jpg
1719 ms
nz.jpg
1610 ms
om.jpg
1600 ms
pa.jpg
1642 ms
pe.jpg
1656 ms
pf.jpg
1659 ms
pg.jpg
1672 ms
ph.jpg
1604 ms
pk.jpg
1590 ms
pl.jpg
1654 ms
pn.jpg
1634 ms
pr.jpg
1620 ms
pt.jpg
1681 ms
pw.jpg
1596 ms
py.jpg
1632 ms
qa.jpg
1658 ms
ro.jpg
1649 ms
ru.jpg
1620 ms
rw.jpg
1612 ms
sa.jpg
1631 ms
sb.jpg
1637 ms
sc.jpg
1638 ms
sd.jpg
1636 ms
se.jpg
1618 ms
sg.jpg
1599 ms
sh.jpg
1641 ms
si.jpg
1679 ms
sj.jpg
1648 ms
sk.jpg
1649 ms
sl.jpg
1606 ms
sm.jpg
1750 ms
sn.jpg
1758 ms
so.jpg
1712 ms
sr.jpg
1655 ms
st.jpg
1668 ms
sv.jpg
1636 ms
sy.jpg
1736 ms
sz.jpg
1749 ms
tc.jpg
1716 ms
td.jpg
1683 ms
tf.jpg
1653 ms
tg.jpg
1666 ms
th.jpg
1745 ms
tj.jpg
1769 ms
tk.jpg
1721 ms
tm.jpg
1660 ms
tn.jpg
1669 ms
to.jpg
1707 ms
tp.jpg
1727 ms
tr.jpg
1742 ms
tt.jpg
1731 ms
tv.jpg
1669 ms
tw.jpg
1663 ms
tz.jpg
1701 ms
ua.jpg
1743 ms
ug.jpg
1727 ms
uk.jpg
1722 ms
um.jpg
1693 ms
us.jpg
1687 ms
uy.jpg
1692 ms
uz.jpg
1739 ms
va.jpg
1735 ms
vc.jpg
1703 ms
ve.jpg
1679 ms
vn.jpg
1699 ms
vu.jpg
1652 ms
wf.jpg
1656 ms
ws.jpg
1630 ms
ye.jpg
1653 ms
yt.jpg
1633 ms
za.jpg
1666 ms
zm.jpg
1624 ms
zw.jpg
1651 ms
paper.jpg
1632 ms
221 ms
impression.html
311 ms
sync
277 ms
extra.js
319 ms
pixel
23 ms
385 ms
match
87 ms
familytree.ru 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
Image elements do not have [alt] attributes
Links do not have a discernible name
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
familytree.ru best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Browser errors were logged to the console
familytree.ru 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
RU
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Familytree.ru can be misinterpreted by Google and other search engines. Our service has detected that Russian 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.ru 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.ru
Open Graph description is not detected on the main page of Family Tree. 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: