12.1 sec in total
866 ms
10.9 sec
334 ms
Visit unesco.or.jp now to see the best up-to-date Unesco content for Japan and also check out these interesting facts you probably never knew about unesco.or.jp
公益社団法人日本ユネスコ協会連盟の事業や活動内容をご紹介しています。世界寺子屋運動・世界遺産活動・未来遺産運動・東日本大震災子ども支援募金などの活動を行っています。
Visit unesco.or.jpWe analyzed Unesco.or.jp page load time and found that the first response time was 866 ms and then it took 11.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
unesco.or.jp performance score
name
value
score
weighting
Value7.9 s
0/100
10%
Value13.4 s
0/100
25%
Value18.8 s
0/100
10%
Value1,400 ms
16/100
30%
Value0
100/100
15%
Value26.7 s
0/100
10%
866 ms
320 ms
684 ms
348 ms
1272 ms
Our browser made a total of 150 requests to load all elements on the main page. We found that 89% of them (133 requests) were addressed to the original Unesco.or.jp, 6% (9 requests) were made to Google.com and 1% (2 requests) were made to Cse.google.com. The less responsive or slowest element that took the longest time to load (3.5 sec) belongs to the original domain Unesco.or.jp.
Page size can be reduced by 660.2 kB (33%)
2.0 MB
1.3 MB
In fact, the total size of Unesco.or.jp main page is 2.0 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. Images take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 28.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 7.3 kB, which is 19% 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 28.7 kB or 76% of the original size.
Potential reduce by 95.3 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. Unesco images are well optimized though.
Potential reduce by 211.3 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 211.3 kB or 54% of the original size.
Potential reduce by 324.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. Unesco.or.jp needs all CSS files to be minified and compressed as it can save up to 324.9 kB or 85% of the original size.
Number of requests can be reduced by 35 (24%)
148
113
The browser has sent 148 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Unesco. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
unesco.or.jp
866 ms
screen.css
320 ms
local.css
684 ms
libs.js
348 ms
jquery-1.6.1.min.js
1272 ms
search.js
398 ms
minmax.js
666 ms
mobilyslider.js
501 ms
init.js
527 ms
fontNav.js
588 ms
reset.css
721 ms
base.css
1412 ms
elements.css
1058 ms
form.css
939 ms
jsapi
16 ms
default.css
28 ms
default.css
70 ms
font_default.css
198 ms
ba_bg.gif
321 ms
main_bg.jpg
351 ms
banner_support_010_on.gif
354 ms
banner_support_010.gif
356 ms
header_link_010_on.gif
359 ms
header_link_010.gif
377 ms
header_link_020_on.gif
667 ms
header_link_020.gif
673 ms
hr_030.gif
681 ms
header_fsize_text.gif
702 ms
font_btn_normal.gif
705 ms
font_btn_large.gif
732 ms
3_20160219.jpg
863 ms
VmEPvjTnJf4
108 ms
2_20151130.png
2219 ms
0129.JPG
931 ms
font_btn_normal_on.gif
1008 ms
header_link_030_on.gif
1009 ms
header_link_030.gif
1040 ms
header_logo.gif
1043 ms
key_img_047.jpg
2162 ms
key_btn_020_on.png
1041 ms
key_main_btn_020.png
1381 ms
key_movie_btn_2.png
1408 ms
key_img_048.jpg
2568 ms
ba_bg_020.gif
1396 ms
contents_bg_head.jpg
1398 ms
ba_bg_bottom.gif
1752 ms
column_bg_010.gif
1779 ms
navi_btn_010_on.gif
1755 ms
navi_btn_010.gif
1958 ms
contents_img_010.jpg
2571 ms
news_btn_010_on.gif
2104 ms
news_btn_010.gif
2131 ms
navi_btn_020_on.gif
2314 ms
navi_btn_020.gif
2472 ms
contents_img_020.jpg
3059 ms
news_btn_020_on.gif
2533 ms
news_btn_020.gif
2650 ms
navi_btn_030_on.gif
2796 ms
14 ms
default+ja.css
2 ms
default+ja.I.js
8 ms
ga.js
30 ms
www-embed-player-vflZsBgOl.css
60 ms
www-embed-player.js
85 ms
__utm.gif
12 ms
6BOEML_YqI6cKINK5dmh8ZufcXg7sBa4jeB-I9gQ0xI.js
26 ms
ad_status.js
64 ms
navi_btn_030.gif
2589 ms
contents_img_030.jpg
3445 ms
news_btn_030_on.gif
2623 ms
news_btn_030.gif
2685 ms
banner_kodomo_020.jpg
3256 ms
banner_facebook_010.gif
2930 ms
banner_about_010.gif
2670 ms
banner_blog_010_on.jpg
2871 ms
banner_blog_010.jpg
2771 ms
banner_company_010_on.jpg
3125 ms
banner_company_010.jpg
3142 ms
title_unesco_010_on.gif
3090 ms
title_unesco_010.gif
2899 ms
title_topics_010.gif
3000 ms
btn_topics_010_on.gif
3126 ms
btn_topics_010.gif
3102 ms
arrow_middle_right.gif
3138 ms
link_icon_outside.gif
2855 ms
bg_hr_010.gif
2852 ms
topics_banner_040.jpg
2985 ms
topics_banner_030_on.jpg
3450 ms
topics_banner_030.jpg
3131 ms
topics_banner_060.jpg
2804 ms
topics_banner_100.jpg
2817 ms
topics_banner_010_on.jpg
2838 ms
topics_banner_010.jpg
2774 ms
topics_banner_020_on.jpg
2793 ms
topics_banner_020.jpg
2835 ms
topics_banner_140.gif
2878 ms
topics_banner_130.jpg
2701 ms
topics_banner_160.jpg
2682 ms
topics_banner_170.jpg
2663 ms
topics_banner_180.jpg
2731 ms
h2_bg_bottom_full.gif
2698 ms
h2_bg_top_full.gif
2732 ms
backtotop.gif
2670 ms
fcontents_bg_top.gif
2604 ms
fnav_hr_010.gif
2602 ms
footer_title_010.gif
2617 ms
footer_img_010.gif
2383 ms
footer_btn_access_on.gif
2562 ms
footer_btn_access.gif
2471 ms
footer_list_010.gif
2380 ms
footer_list_020.gif
2350 ms
footer_list_030.gif
2252 ms
footer_list_040.gif
2240 ms
footer_list_050.gif
2442 ms
footer_btn_contact.gif
2428 ms
footer_btn_download.gif
2396 ms
footer_title_support.gif
2332 ms
footer_text_support.gif
2250 ms
footer_support_link_010.gif
2238 ms
footer_support_text_010.gif
2425 ms
footer_support_link_030.gif
2384 ms
footer_support_link_040.gif
2410 ms
footer_support_link_050.gif
2303 ms
footer_support_link_060.gif
2182 ms
copyright.gif
2145 ms
footer_list_010_on.gif
2188 ms
footer_list_020_on.gif
2114 ms
footer_list_030_on.gif
2165 ms
footer_list_040_on.gif
2155 ms
footer_list_050_on.gif
2158 ms
footer_btn_contact_on.gif
2094 ms
footer_btn_download_on.gif
2164 ms
footer_support_bg.gif
2168 ms
footer_title_support_on.gif
2161 ms
footer_support_link_010_on.gif
2176 ms
footer_support_link_030_on.gif
2110 ms
footer_support_link_040_on.gif
2089 ms
footer_support_link_050_on.gif
2169 ms
footer_support_link_060_on.gif
2129 ms
fnav_bg_top.gif
2135 ms
fnav_hr_020.gif
2138 ms
arrow_small_right.gif
2104 ms
bullets.png
2089 ms
prev_next.png
2147 ms
print.css
180 ms
async-ads.js
56 ms
google_custom_search_watermark.gif
36 ms
small-logo.png
14 ms
clear.gif
15 ms
search_btn.gif
186 ms
unesco.or.jp 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
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
unesco.or.jp 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
Page has valid source maps
unesco.or.jp 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
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 Unesco.or.jp 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 Unesco.or.jp 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.
unesco.or.jp
Open Graph description is not detected on the main page of Unesco. 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: