6.1 sec in total
498 ms
5.4 sec
190 ms
Visit janic.org now to see the best up-to-date JANIC content for Japan and also check out these interesting facts you probably never knew about janic.org
国際協力NGOを支援するNGO。日本有数のネットワーク型NGO。オンライン寄付サイト「NGOサポート募金」、やNGOの情報庫「NGOダイレクトリー」「NGO市民情報センター」などを運営している。
Visit janic.orgWe analyzed Janic.org page load time and found that the first response time was 498 ms and then it took 5.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
janic.org performance score
name
value
score
weighting
Value3.8 s
28/100
10%
Value6.4 s
10/100
25%
Value10.8 s
6/100
10%
Value670 ms
45/100
30%
Value0.022
100/100
15%
Value17.5 s
4/100
10%
498 ms
712 ms
852 ms
1157 ms
733 ms
Our browser made a total of 142 requests to load all elements on the main page. We found that 85% of them (121 requests) were addressed to the original Janic.org, 7% (10 requests) were made to Static.xx.fbcdn.net and 5% (7 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (3.1 sec) belongs to the original domain Janic.org.
Page size can be reduced by 239.1 kB (12%)
1.9 MB
1.7 MB
In fact, the total size of Janic.org main page is 1.9 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. 45% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.
Potential reduce by 23.0 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 3.6 kB, which is 12% 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 23.0 kB or 76% of the original size.
Potential reduce by 49.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. JANIC images are well optimized though.
Potential reduce by 85.7 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 85.7 kB or 60% of the original size.
Potential reduce by 80.9 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. Janic.org needs all CSS files to be minified and compressed as it can save up to 80.9 kB or 87% of the original size.
Number of requests can be reduced by 77 (55%)
141
64
The browser has sent 141 CSS, Javascripts, AJAX and image requests in order to completely render the main page of JANIC. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
janic.org
498 ms
import.css
712 ms
mt.js
852 ms
jquery.js
1157 ms
yuga.js
733 ms
fontsize.js
753 ms
format.css
163 ms
contents.css
187 ms
directry.css
303 ms
home.css
324 ms
contents_mdgs.css
343 ms
ga.js
78 ms
janic.gif
162 ms
get_flash_player.gif
64 ms
bk.gif
206 ms
hd_btn_english.gif
225 ms
hd_btn_donation.gif
244 ms
hd_btn_sitemap.gif
261 ms
hd_btn_contact.gif
163 ms
hd_btn_login.gif
182 ms
hd_btn_search.gif
341 ms
side_books_bk.jpg
444 ms
No.166-thumb-65xauto-4088.jpg
463 ms
No.165-thumb-65xauto-4062.jpg
484 ms
line_green.gif
503 ms
line_gray.gif
521 ms
label_news.gif
564 ms
label_event.gif
682 ms
line_gray_shade.gif
700 ms
label_event.gif
722 ms
label_seiki.gif
742 ms
label_keiyaku.gif
760 ms
label_study.gif
801 ms
label_books.gif
921 ms
label_josei.gif
939 ms
ft_navi_hd.gif
961 ms
hd_btn_english_on.gif
982 ms
hd_btn_donation_on.gif
998 ms
hd_btn_sitemap_on.gif
1041 ms
hd_btn_contact_on.gif
1127 ms
hd_btn_login_on.gif
1145 ms
logo.gif
278 ms
hd_btn_voice.gif
337 ms
hd_btn_size.gif
427 ms
hd_btn_size_big.gif
427 ms
hd_btn_size_defo.gif
429 ms
hd_btn_size_small.gif
429 ms
hd_btn_search.gif
539 ms
hd_gn_01.gif
577 ms
hd_gn_02.gif
595 ms
hd_gn_03.gif
616 ms
hd_gn_04.gif
635 ms
hd_gn_05.gif
656 ms
hd_gn_06.gif
776 ms
hd_gn_07.gif
814 ms
side_navi_monthly131118.jpg
993 ms
side_navi_01.jpg
854 ms
side_navi_02.jpg
874 ms
side_navi_04.jpg
1054 ms
side_navi_05.jpg
1015 ms
side_navi_06.jpg
1052 ms
side_navi_08.jpg
1073 ms
side_navi_09.jpg
1092 ms
bnr_youtube.png
1153 ms
twitter.gif
1175 ms
side_navi_rss.gif
1211 ms
side_navi_link.gif
1231 ms
main_new_ttl.gif
1251 ms
btn_rss.gif
1273 ms
btn_all.gif
1310 ms
ngo_bbs_ttl.gif
1336 ms
ngo_bbs_02.gif
1370 ms
ngo_bbs_03.gif
1392 ms
ngo_bbs_04.gif
1411 ms
ngo_bbs_05.gif
1433 ms
ngo_bbs_06.gif
1468 ms
likebox.php
173 ms
__utm.gif
22 ms
top_bb_event.gif
1409 ms
hDvwL1_H7g-.css
91 ms
udqjbTyb5Ue.css
111 ms
q68gy-v_YMF.js
149 ms
FJmpeSpHpjS.js
180 ms
0wM5s1Khldu.js
166 ms
1bNoFZUdlYZ.js
166 ms
top_bb_jinzai.gif
1252 ms
top_bb_study.gif
1224 ms
12249942_1072790079428247_8764500960170254587_n.jpg
98 ms
45579_546559692051291_1304000057_n.jpg
58 ms
10574362_909513335794695_4208344610817871836_n.jpg
60 ms
10590663_550074205115265_6371792133888433736_n.jpg
60 ms
1934261_1003621113041326_7345101270973991234_n.jpg
56 ms
10801861_1654341721459490_4494928548929270588_n.jpg
79 ms
12661939_1681671552106244_5356477038889473439_n.jpg
68 ms
wL6VQj7Ab77.png
19 ms
s7jcwEQH7Sx.png
18 ms
top_bb_books.gif
1152 ms
top_bb_josei.gif
1174 ms
bnr_plaza3.jpg
1206 ms
bnr_plazablog7.jpg
1236 ms
I6-MnjEovm5.js
19 ms
pQrUxxo5oQp.js
35 ms
simoblogbanner.jpg
1314 ms
bnr_koko.jpg
1145 ms
bnr_asc2012.jpg
2738 ms
bnr_hap.jpg
3084 ms
bnr_nanpro_new.jpg
1317 ms
bnr_ugokuugokasu.gif
1170 ms
bnr_beyondmdgs.jpg
1106 ms
bn_150326.jpg
1334 ms
btn_pagetop.gif
1156 ms
ft_navi_ttl.gif
1168 ms
ft_navi_01.gif
1117 ms
ft_navi_02.gif
1154 ms
ft_navi_03.gif
1150 ms
ft_navi_04.gif
1215 ms
ft_btn_about.gif
1235 ms
ft_btn_privacy.gif
1236 ms
ft_btn_tokutei.gif
1213 ms
ft_address.gif
1253 ms
ft_btn_map.gif
1258 ms
ft_telfax.gif
1256 ms
ft_copyright.gif
1275 ms
hd_btn_voice_on.gif
1313 ms
hd_gn_01_on.gif
1320 ms
hd_gn_02_on.gif
1312 ms
hd_gn_03_on.gif
1317 ms
hd_gn_04_on.gif
1352 ms
hd_gn_05_on.gif
1378 ms
hd_gn_06_on.gif
1375 ms
hd_gn_07_on.gif
1379 ms
side_navi_monthly131118_on.jpg
1565 ms
side_navi_01_on.jpg
1424 ms
side_navi_02_on.jpg
1416 ms
side_navi_04_on.jpg
1436 ms
side_navi_06_on.jpg
1518 ms
side_navi_08_on.jpg
1503 ms
side_navi_09_on.jpg
1512 ms
ft_navi_01_on.gif
1507 ms
ft_navi_02_on.gif
1455 ms
ft_navi_03_on.gif
1446 ms
ft_navi_04_on.gif
1455 ms
janic.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.
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
Links do not have a discernible name
janic.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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
janic.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
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 doesn't use 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 Janic.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 Janic.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.
janic.org
Open Graph description is not detected on the main page of JANIC. 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: