8.7 sec in total
802 ms
5.7 sec
2.2 sec
Click here to check amazing HEREDIS content for France. Otherwise, check out these important facts you probably never knew about heredis.com
Téléchargez et essayez gratuitement le logiciel de généalogie HEREDIS, N°1 de la recherche généalogique en France et en Europe: votre arbre généalogique ici
Visit heredis.comWe analyzed Heredis.com page load time and found that the first response time was 802 ms and then it took 7.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
heredis.com performance score
name
value
score
weighting
Value4.5 s
15/100
10%
Value12.6 s
0/100
25%
Value11.4 s
5/100
10%
Value1,180 ms
21/100
30%
Value0.15
76/100
15%
Value14.1 s
9/100
10%
802 ms
90 ms
763 ms
698 ms
498 ms
Our browser made a total of 114 requests to load all elements on the main page. We found that 86% of them (98 requests) were addressed to the original Heredis.com, 4% (5 requests) were made to Fonts.gstatic.com and 3% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Heredis.com.
Page size can be reduced by 965.1 kB (14%)
6.8 MB
5.9 MB
In fact, the total size of Heredis.com main page is 6.8 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. 70% of websites need less resources to load. Images take 5.9 MB which makes up the majority of the site volume.
Potential reduce by 43.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 43.1 kB or 77% of the original size.
Potential reduce by 267.1 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. HEREDIS images are well optimized though.
Potential reduce by 372.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 372.1 kB or 63% of the original size.
Potential reduce by 282.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. Heredis.com needs all CSS files to be minified and compressed as it can save up to 282.8 kB or 86% of the original size.
Number of requests can be reduced by 37 (35%)
106
69
The browser has sent 106 CSS, Javascripts, AJAX and image requests in order to completely render the main page of HEREDIS. 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 14 to 1 for CSS and as a result speed up the page load time.
www.heredis.com
802 ms
90 ms
763 ms
language-selector.css
698 ms
reset.css
498 ms
style.css
870 ms
coda-slider-2.0.css
701 ms
jquery.fancybox-1.3.4.css
705 ms
css
25 ms
css
38 ms
css
45 ms
jquery.min.js
29 ms
modernizr.custom.94056.js
299 ms
jquery.tools.min.js
388 ms
jquery-ui-1.8.20.custom.min.js
760 ms
jquery.easing.1.3.js
592 ms
jquery.coda-slider-2.0.js
679 ms
waypoints.min.js
766 ms
jquery.hoverIntent.minified.js
781 ms
custom.js
785 ms
cookie-monster-public.css
792 ms
navigation.css
847 ms
cms-navigation-base.css
851 ms
cms-navigation.css
905 ms
jquery.js
1175 ms
jquery-migrate.min.js
906 ms
cookie-monster-public.js
732 ms
wp-embed.min.js
732 ms
sitepress.js
749 ms
ODelI1aHBYDBqgeIAH2zlNzbP97U9sKh0jjxbPbfOKg.ttf
29 ms
W72UZhum5Hw
153 ms
background.jpg
141 ms
header-bg.jpg
141 ms
header-promo.png
290 ms
light2.png
294 ms
logo.png
145 ms
logo-text.png
362 ms
onglet.png
427 ms
fr.png
176 ms
en.png
196 ms
facebook.png
274 ms
youtube.png
290 ms
twitter.png
363 ms
newsletter.png
371 ms
forum.png
378 ms
splash15-small-us.png
462 ms
archives-small.png
697 ms
identifier-small.png
888 ms
partager-small-us.png
881 ms
repartition-small2.png
992 ms
hol-small.png
763 ms
download-bg.png
547 ms
btn-demo-en.png
635 ms
black_arrow.png
722 ms
dl-icon.png
781 ms
btn-achat-en.png
808 ms
buy-icon.png
848 ms
bg-table.png
865 ms
blue-btn.png
893 ms
haut-EN.png
932 ms
prez-web-pc.png
1290 ms
new-us.png
960 ms
map-pc-us.png
1322 ms
Archives-en-lignebis-pc-us.png
1493 ms
intelligent.png
1103 ms
research-us2.png
1130 ms
ga.js
34 ms
research-bis.png
1134 ms
mnpfi9pxYH-Go5UiibESIqCWcynf_cDxXwCLxiixG1c.ttf
11 ms
IRFxB2matTxrjZt6a3FUnsQ6HWhO-urg7Zd40mHsFaI.ttf
30 ms
__utm.gif
45 ms
hol-web.png
1149 ms
www-embed-player-vflZsBgOl.css
65 ms
www-embed-player.js
87 ms
hol-web-photos.png
1173 ms
hol-publish.png
1208 ms
descendance-us.png
1369 ms
racine.png
1192 ms
1eJU4PjErWSV5LNTKFXcze5UHikZLg3viIH581vcHWA.js
39 ms
ad_status.js
44 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
67 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
77 ms
saisie-perso.png
1126 ms
illimite.png
1224 ms
sync.png
1150 ms
tree-pc.png
1182 ms
roue.png
1127 ms
arbres.png
1166 ms
panel-tree.png
1271 ms
outil-photo.png
1449 ms
bonus-us.png
1338 ms
liensBig.png
1221 ms
merge.png
1067 ms
indexes-windows.png
1160 ms
gedcom.png
1094 ms
livre.png
1005 ms
sheets.png
1008 ms
homepage-pc-us.png
1201 ms
personnalisation.png
1036 ms
haut.png
1011 ms
windows.png
1013 ms
footer-bg.jpg
1002 ms
ico-footer-presse.png
1022 ms
ico-footer-heredis-pc.png
1037 ms
ico-footer-droits.png
1015 ms
ico-footer-society.png
1004 ms
ico-footer-heredis-mac.png
977 ms
close.png
885 ms
ajax-loader.gif
884 ms
arrow-left.png
870 ms
arrow-right.png
773 ms
point.png
764 ms
point-select.png
760 ms
netbooks-tablets.css
90 ms
heredis.com 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
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
heredis.com 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
Browser errors were logged to the console
Page has valid source maps
heredis.com 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
FR
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Heredis.com can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and it does not match the claimed English language. Our system also found out that Heredis.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.
heredis.com
Open Graph description is not detected on the main page of HEREDIS. 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: