3.2 sec in total
313 ms
2.3 sec
588 ms
Welcome to geneatique.com homepage info - get ready to check Geneatique best content for France right away, or after learning these important things about geneatique.com
logiciel de généalogie pour créer votre arbre généalogique. Idéal pour votre généalogie et partir à la recherche de vos ancêtres
Visit geneatique.comWe analyzed Geneatique.com page load time and found that the first response time was 313 ms 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.
geneatique.com performance score
name
value
score
weighting
Value4.7 s
13/100
10%
Value6.2 s
11/100
25%
Value8.6 s
17/100
10%
Value1,900 ms
8/100
30%
Value0.157
74/100
15%
Value18.7 s
3/100
10%
313 ms
752 ms
156 ms
233 ms
161 ms
Our browser made a total of 97 requests to load all elements on the main page. We found that 45% of them (44 requests) were addressed to the original Geneatique.com, 8% (8 requests) were made to Fonts.gstatic.com and 7% (7 requests) were made to Guide-genealogie.com. The less responsive or slowest element that took the longest time to load (800 ms) belongs to the original domain Geneatique.com.
Page size can be reduced by 723.7 kB (42%)
1.7 MB
998.5 kB
In fact, the total size of Geneatique.com main page is 1.7 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 791.2 kB which makes up the majority of the site volume.
Potential reduce by 99.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. 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 99.9 kB or 78% of the original size.
Potential reduce by 36.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. Geneatique images are well optimized though.
Potential reduce by 282.0 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 282.0 kB or 65% of the original size.
Potential reduce by 305.6 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. Geneatique.com needs all CSS files to be minified and compressed as it can save up to 305.6 kB or 83% of the original size.
Number of requests can be reduced by 40 (47%)
86
46
The browser has sent 86 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Geneatique. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.
geneatique.com
313 ms
www.geneatique.com
752 ms
stylesheet_combined_c6688c44224b7d6828a14d938a32e51b.css
156 ms
stylesheet_combined_81c464ba673920e4af24f97667674f9e.css
233 ms
stylesheet_combined_e91ed2fdcd46918f25f00953d70fbf46.css
161 ms
simplegrid.css
160 ms
font-awesome.min.css
235 ms
lightbox.css
226 ms
animations.css
237 ms
css
27 ms
jquery.min.js
9 ms
functions.min.js
254 ms
default.css
254 ms
nivo-slider.css
299 ms
Show_10.css
305 ms
Show_2.css
307 ms
jquery.nivo.slider.pack.js
305 ms
cookiechoices.js
500 ms
tinynav.min.js
538 ms
verifmail.js
538 ms
waypoints.min.js
537 ms
waypoints-sticky.min.js
536 ms
masonry.pkgd.min.js
610 ms
imagesloaded.pkgd.min.js
533 ms
lightbox.js
177 ms
CoverPop.css
519 ms
CoverPop.min.js
522 ms
css3-animate-it.js
176 ms
compatible-windows.png
351 ms
popup-geneatique-nexus.jpg
449 ms
popup-geneatique-google-play.png
354 ms
popup-geneatique-iPhone.png
447 ms
popup-geneatique-AppStore.png
352 ms
g2013-screenshot-383.jpg
446 ms
google-earth-export-246.jpg
520 ms
recherche-images.jpg
348 ms
separateur-media-246.jpg
346 ms
tablette-facilotab-220.jpg
346 ms
cassini-2015.thumbnail.jpg
351 ms
04-2015-boite-DVD-SS7-noir.thumbnail.png
480 ms
geneatique-2016-logo.jpg
96 ms
vu-a-la-tele-145.png
96 ms
slideshow-impression.jpg
346 ms
slideshow-document.jpg
480 ms
slideshow-saisie.jpg
441 ms
slideshow-mobile.jpg
312 ms
presentation-arbres-397.jpg
258 ms
presentation-arbres-jblaurent2-397.jpg
362 ms
presentation-arbres-mixte-397.jpg
442 ms
presentation-arbres-rouleau-397.jpg
440 ms
lesEchos.jpg
441 ms
citation-stephane-bern-419.png
477 ms
logiciel-genealogie-mac.jpg
647 ms
genealogie-synchronisation.jpg
800 ms
presentation-documents-fiche-familiale-170.png
515 ms
presentation-documents-liste-ascendante-170.png
491 ms
presentation-documents-livre-de-famille-170.jpg
615 ms
presentation-documents-notices-professions-170.jpg
616 ms
presentation-documents-statistiques-170.png
616 ms
g2015-icone-logiciel-180.png
617 ms
logo-cdip-orange.png
644 ms
gtm.js
46 ms
conversion_async.js
33 ms
analytics.js
7 ms
collect
11 ms
49 ms
76 ms
ga-audiences
62 ms
loading.gif
455 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
27 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
27 ms
EInbV5DfGHOiMmvb1Xr-honF5uFdDttMLvmWuJdhhgs.ttf
28 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
27 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
27 ms
xjAJXh38I15wypJXxuGMBp0EAVxt0G0biEntp43Qt6E.ttf
27 ms
gs_Hm9mvv5I
96 ms
fontawesome-webfont.woff
471 ms
platform.js
70 ms
sdk.js
19 ms
www-embed-player-vflfNyN_r.css
92 ms
www-embed-player.js
140 ms
base.js
177 ms
263 ms
xd_arbiter.php
111 ms
xd_arbiter.php
159 ms
detect.js
225 ms
bat.js
248 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
8 ms
ad_status.js
40 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
35 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
37 ms
stylesheet_combined_f6950e90217e69306a93c001383b12a4.css
79 ms
stylesheet_combined_7f818272c64f766807ae979353092c28.css
79 ms
pinit.js
18 ms
arrows.png
78 ms
bullets.png
78 ms
pinit_main.js
37 ms
geneatique.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.
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
Form elements do not have associated labels
Links do not have a discernible name
geneatique.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
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
geneatique.com 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
FR
FR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Geneatique.com can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and it matches the claimed language. Our system also found out that Geneatique.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.
geneatique.com
Open Graph description is not detected on the main page of Geneatique. 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: