4.5 sec in total
1 sec
3.3 sec
146 ms
Visit gw.geneanet.org now to see the best up-to-date Gw Geneanet content for France and also check out these interesting facts you probably never knew about gw.geneanet.org
Log in or create a Geneanet account. Create your family tree, find your ancestors, search the collaborative database.
Visit gw.geneanet.orgWe analyzed Gw.geneanet.org page load time and found that the first response time was 1 sec and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
gw.geneanet.org performance score
name
value
score
weighting
Value7.7 s
0/100
10%
Value7.7 s
3/100
25%
Value9.5 s
12/100
10%
Value190 ms
91/100
30%
Value0
100/100
15%
Value8.4 s
39/100
10%
1013 ms
581 ms
618 ms
788 ms
863 ms
Our browser made a total of 35 requests to load all elements on the main page. We found that 11% of them (4 requests) were addressed to the original Gw.geneanet.org, 34% (12 requests) were made to Geneacdn.net and 20% (7 requests) were made to Static.geneanet.org. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Geneacdn.net.
Page size can be reduced by 1.7 MB (75%)
2.2 MB
560.0 kB
In fact, the total size of Gw.geneanet.org main page is 2.2 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. 50% of websites need less resources to load. CSS take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 27.7 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 6.2 kB, which is 17% 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 27.7 kB or 76% of the original size.
Potential reduce by 7.5 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. Gw Geneanet images are well optimized though.
Potential reduce by 721.6 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 721.6 kB or 74% of the original size.
Potential reduce by 918.1 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. Gw.geneanet.org needs all CSS files to be minified and compressed as it can save up to 918.1 kB or 87% of the original size.
Number of requests can be reduced by 24 (75%)
32
8
The browser has sent 32 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Gw Geneanet. 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 from 4 to 1 for CSS and as a result speed up the page load time.
gw.geneanet.org
1013 ms
style.css
581 ms
geneweb.css
618 ms
geneweb_bundle.css
788 ms
bbb2497.css
863 ms
jquery-1.7.2.js
744 ms
script.js
763 ms
script.js
764 ms
jquery.cookie.js
780 ms
config.js
166 ms
foundation_legacy.js
946 ms
script.js
894 ms
router.js
893 ms
routing
116 ms
visitor.js
894 ms
d926528.js
1105 ms
9b4a01b.js
1042 ms
d13e9df.js
1157 ms
smarttag.js
241 ms
smart.js
83 ms
all.js
290 ms
6408d3b03805f1d511e48f7435b0233f.js
289 ms
no_tree.png
938 ms
icon_notification_info_red.png
125 ms
logo_gw.png
84 ms
opacity_80.png
252 ms
ga.js
126 ms
api_write.proto
355 ms
__utm.gif
23 ms
186 ms
xd_arbiter.php
131 ms
xd_arbiter.php
263 ms
hit.xiti
300 ms
datacollect.php
214 ms
xd_arbiter.php
84 ms
gw.geneanet.org 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
Links do not have a discernible name
gw.geneanet.org 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
Missing source maps for large first-party JavaScript
gw.geneanet.org SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Page is blocked from indexing
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Gw.geneanet.org can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Gw.geneanet.org 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.
gw.geneanet.org
Open Graph description is not detected on the main page of Gw Geneanet. 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: