6.3 sec in total
1.1 sec
4.6 sec
551 ms
Welcome to habitatjp.org homepage info - get ready to check Habitatjp best content for Japan right away, or after learning these important things about habitatjp.org
ハビタット・フォー・ヒューマニティは、 世界70ヵ国以上で住まいの問題に取り組む国際NGOです。
Visit habitatjp.orgWe analyzed Habitatjp.org page load time and found that the first response time was 1.1 sec and then it took 5.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
habitatjp.org performance score
name
value
score
weighting
Value5.6 s
5/100
10%
Value16.5 s
0/100
25%
Value15.1 s
1/100
10%
Value810 ms
36/100
30%
Value0.538
14/100
15%
Value16.0 s
6/100
10%
1138 ms
389 ms
411 ms
620 ms
442 ms
Our browser made a total of 78 requests to load all elements on the main page. We found that 86% of them (67 requests) were addressed to the original Habitatjp.org, 4% (3 requests) were made to S.ytimg.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.8 sec) belongs to the original domain Habitatjp.org.
Page size can be reduced by 463.2 kB (47%)
990.3 kB
527.1 kB
In fact, the total size of Habitatjp.org main page is 990.3 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. 25% of websites need less resources to load. Images take 409.5 kB which makes up the majority of the site volume.
Potential reduce by 21.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. 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 21.7 kB or 83% of the original size.
Potential reduce by 30.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. Habitatjp images are well optimized though.
Potential reduce by 189.4 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 189.4 kB or 66% of the original size.
Potential reduce by 221.5 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. Habitatjp.org needs all CSS files to be minified and compressed as it can save up to 221.5 kB or 83% of the original size.
Number of requests can be reduced by 29 (43%)
67
38
The browser has sent 67 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Habitatjp. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
habitatjp.org
1138 ms
rollover.js
389 ms
tab.js
411 ms
levelsmenu.js
620 ms
levelsmenu-topbar.css
442 ms
levelsmenu-base.css
441 ms
levelsmenu-sidebar.css
575 ms
tab.css
605 ms
home_2.css
636 ms
design.css
638 ms
utf8.js
799 ms
img_random.js
414 ms
mbox1_h.gif
407 ms
mbox2_h.gif
408 ms
mbox3_h.gif
414 ms
w_js.php
390 ms
analytics.js
49 ms
logo.gif
426 ms
btn_search.gif
425 ms
blogger.gif
426 ms
facebook.gif
426 ms
btn_homeD.gif
427 ms
btn_englishD.gif
583 ms
menu01_D.gif
613 ms
menu02_D.gif
610 ms
menu03_D.gif
611 ms
menu04_D.gif
609 ms
menu05_D.gif
614 ms
menu06_D.gif
806 ms
NHK%20icon.jpg
2807 ms
facebook.gif
826 ms
menu_BG01.gif
220 ms
menu_G001D.gif
210 ms
menu_G002D.gif
220 ms
menu_G003D.gif
332 ms
menu_G004D.gif
322 ms
menu_G005D.gif
341 ms
menu_G006D.gif
452 ms
ab_d.jpg
701 ms
vo_d.jpg
695 ms
do_d.jpg
722 ms
bnr01d.jpg
1270 ms
OtakaraAid.jpg
785 ms
moreD.gif
679 ms
bottom_line01.gif
918 ms
bnr_facebook_180_60.gif
953 ms
blogspot.jpg
1766 ms
btn_policyD.gif
928 ms
btn_privacyD.gif
1021 ms
btn_sitemapD.gif
1148 ms
bottom_name.gif
1136 ms
bottom_copy.gif
1180 ms
collect
27 ms
collect
136 ms
menu_GBG_258.gif
914 ms
news.html
972 ms
catch_jp35.jpg
2810 ms
attention_top.gif
1014 ms
attention_mid.gif
1052 ms
attention_bot.gif
1078 ms
bottom_line02.gif
1159 ms
pxP6OBdD29A
256 ms
www-embed-player-vfl-z2BtK.css
314 ms
www-embed-player.js
429 ms
base.js
799 ms
home.css
397 ms
mbox1_h.gif
401 ms
mbox2_h.gif
399 ms
mbox3_h.gif
422 ms
tub_news01.gif
515 ms
tub_event02.gif
539 ms
news_line.gif
583 ms
news_sepa.gif
605 ms
fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js
229 ms
ad_status.js
225 ms
list_icon_top.gif
218 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
277 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
325 ms
habitatjp.org 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
[aria-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
ARIA toggle fields do not have accessible names
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
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
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
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.
habitatjp.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
Browser errors were logged to the console
habitatjp.org SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Habitatjp.org can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it matches the claimed language. Our system also found out that Habitatjp.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.
habitatjp.org
Open Graph description is not detected on the main page of Habitatjp. 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: