826 ms in total
199 ms
417 ms
210 ms
Welcome to habitant.org homepage info - get ready to check Habitant best content right away, or after learning these important things about habitant.org
Various North American French genealogy topics.
Visit habitant.orgWe analyzed Habitant.org page load time and found that the first response time was 199 ms and then it took 627 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.
habitant.org performance score
name
value
score
weighting
Value0.7 s
100/100
10%
Value0.7 s
100/100
25%
Value0.7 s
100/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value0.7 s
100/100
10%
199 ms
71 ms
133 ms
134 ms
135 ms
Our browser made a total of 9 requests to load all elements on the main page. We found that all of those requests were addressed to Habitant.org and no external sources were called. The less responsive or slowest element that took the longest time to load (199 ms) belongs to the original domain Habitant.org.
Page size can be reduced by 13.5 kB (38%)
35.9 kB
22.4 kB
In fact, the total size of Habitant.org main page is 35.9 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. Only 5% of websites need less resources to load. Images take 18.4 kB which makes up the majority of the site volume.
Potential reduce by 13.5 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 2.8 kB, which is 16% 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 13.5 kB or 77% of the original size.
Potential reduce by 0 B
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. Habitant images are well optimized though.
We found no issues to fix!
8
8
The browser has sent 8 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Habitant. According to our analytics all requests are already optimized.
{{url}}
{{time}} ms
habitant.org accessibility score
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
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
habitant.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
habitant.org 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
Tap targets are not sized appropriately
![]()
EN
![]()
N/A
N/A
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Habitant.org can be misinterpreted by Google and other search engines. Our service has detected that English 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 Habitant.org main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
{{og_description}}
habitant.org
Open Graph description is not detected on the main page of Habitant. 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: