Tools & Wizards About Us
kokudo.or.jp screenshot

Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 63

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

kokudo.or.jp

公益財団法人国土地理協会 -TOP-

Page Load Speed

9.3 sec in total

First Response

1.3 sec

Resources Loaded

7.8 sec

Page Rendered

203 ms

kokudo.or.jp screenshot

About Website

Click here to check amazing Kokudo content for Japan. Otherwise, check out these important facts you probably never knew about kokudo.or.jp

地理・人口統計データと各種の地図を提供する財団法人。地名に関する最新情報を提供。

Visit kokudo.or.jp

Key Findings

We analyzed Kokudo.or.jp page load time and found that the first response time was 1.3 sec and then it took 8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

kokudo.or.jp performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

15/100

10%

LCP (Largest Contentful Paint)

Value84.4 s

0/100

25%

SI (Speed Index)

Value11.7 s

4/100

10%

TBT (Total Blocking Time)

Value2,710 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value84.2 s

0/100

10%

Network Requests Diagram

kokudo.or.jp

1255 ms

import.css

319 ms

jquery.1.7.2.js

1240 ms

jquery.easing.1.3.js

708 ms

script.js

703 ms

Our browser made a total of 99 requests to load all elements on the main page. We found that 98% of them (97 requests) were addressed to the original Kokudo.or.jp, 2% (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 Kokudo.or.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 192.6 kB (37%)

Content Size

519.1 kB

After Optimization

326.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Kokudo.or.jp main page is 519.1 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. 20% of websites need less resources to load. Images take 255.6 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 46.7 kB

  • Original 54.3 kB
  • After minification 44.6 kB
  • After compression 7.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 9.7 kB, which is 18% 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 46.7 kB or 86% of the original size.

Image Optimization

-0%

Potential reduce by 137 B

  • Original 255.6 kB
  • After minification 255.4 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. Kokudo images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 110.7 kB

  • Original 167.3 kB
  • After minification 160.4 kB
  • After compression 56.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 110.7 kB or 66% of the original size.

CSS Optimization

-84%

Potential reduce by 35.1 kB

  • Original 41.8 kB
  • After minification 33.3 kB
  • After compression 6.7 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. Kokudo.or.jp needs all CSS files to be minified and compressed as it can save up to 35.1 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 70 (73%)

Requests Now

96

After Optimization

26

  • Images
  • JavaScript
  • CSS

The browser has sent 96 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Kokudo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

kokudo.or.jp

kokudo.or.jp

1255 ms

import.css

import.css

319 ms

jquery.1.7.2.js

jquery.1.7.2.js

1240 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

708 ms

script.js

script.js

703 ms

jquery.cookie.js

jquery.cookie.js

716 ms

fontchange.js

fontchange.js

693 ms

nivo-slider.css

nivo-slider.css

873 ms

jquery.nivo.slider.pack.js

jquery.nivo.slider.pack.js

1035 ms

ga.js

ga.js

1026 ms

baseaa.css

baseaa.css

726 ms

base.css

base.css

1311 ms

ga.js

ga.js

100 ms

logo.gif

logo.gif

173 ms

bg_globalnavi.gif

bg_globalnavi.gif

330 ms

globalnavi01_rollover.gif

globalnavi01_rollover.gif

343 ms

globalnavi02.gif

globalnavi02.gif

341 ms

globalnavi03.gif

globalnavi03.gif

341 ms

globalnavi04.gif

globalnavi04.gif

351 ms

globalnavi05.gif

globalnavi05.gif

517 ms

globalnavi06.gif

globalnavi06.gif

671 ms

globalnavi07.gif

globalnavi07.gif

664 ms

globalnavi08.gif

globalnavi08.gif

679 ms

bg_gsubnavi.gif

bg_gsubnavi.gif

679 ms

gsubnavi01_1.gif

gsubnavi01_1.gif

713 ms

gsubnavi01_2.gif

gsubnavi01_2.gif

832 ms

gsubnavi01_3.gif

gsubnavi01_3.gif

1021 ms

gsubnavi01_4.gif

gsubnavi01_4.gif

1021 ms

gsubnavi01_5.gif

gsubnavi01_5.gif

1016 ms

globalnavi09.gif

globalnavi09.gif

1017 ms

globalnavi10.gif

globalnavi10.gif

1053 ms

globalnavi11.gif

globalnavi11.gif

1151 ms

utilnavi01.gif

utilnavi01.gif

1339 ms

utilnavi02.gif

utilnavi02.gif

1354 ms

utilnavi03.gif

utilnavi03.gif

1362 ms

utilnavi05.gif

utilnavi05.gif

1375 ms

headline_fontchange.gif

headline_fontchange.gif

1397 ms

btn_font_s.gif

btn_font_s.gif

1490 ms

btn_font_m.gif

btn_font_m.gif

1664 ms

btn_font_l.gif

btn_font_l.gif

1700 ms

headline_about.gif

headline_about.gif

1702 ms

mainimg.jpg

mainimg.jpg

2569 ms

headline_news.gif

headline_news.gif

1758 ms

icon_post.gif

icon_post.gif

1809 ms

icon_place.gif

icon_place.gif

2003 ms

icon_marge.gif

icon_marge.gif

2044 ms

icon_semminor.gif

icon_semminor.gif

2048 ms

icon_grant.gif

icon_grant.gif

2100 ms

icon_database.gif

icon_database.gif

2125 ms

__utm.gif

__utm.gif

11 ms

icon_service.gif

icon_service.gif

2210 ms

icon_about.gif

icon_about.gif

2066 ms

icon_books.gif

icon_books.gif

2081 ms

icon_master.gif

icon_master.gif

2120 ms

headline_place.gif

headline_place.gif

2140 ms

headline_post.gif

headline_post.gif

2352 ms

headline_master.gif

headline_master.gif

2211 ms

headline_database.gif

headline_database.gif

2118 ms

headline_service.gif

headline_service.gif

2130 ms

img_poplulation.jpg

img_poplulation.jpg

2484 ms

img_map.jpg

img_map.jpg

2543 ms

img_teijyu.jpg

img_teijyu.jpg

2849 ms

bg_merging_top.gif

bg_merging_top.gif

2259 ms

headline_merging.gif

headline_merging.gif

2084 ms

headline_merging_past.gif

headline_merging_past.gif

2100 ms

btn_search.gif

btn_search.gif

2395 ms

headline_books.gif

headline_books.gif

2424 ms

books_jinkou.jpg

books_jinkou.jpg

2412 ms

books_minzoku.jpg

books_minzoku.jpg

2349 ms

bg_seminar.jpg

bg_seminar.jpg

2357 ms

headline_seminar.gif

headline_seminar.gif

2378 ms

bg_library.jpg

bg_library.jpg

2559 ms

headline_library.gif

headline_library.gif

2459 ms

bg_newsletter.jpg

bg_newsletter.jpg

2582 ms

headline_newsletter.gif

headline_newsletter.gif

2420 ms

headline_distribution.gif

headline_distribution.gif

2376 ms

headline_population.gif

headline_population.gif

2351 ms

banner_teijyu.gif

banner_teijyu.gif

2481 ms

globalnavi02_rollover.gif

globalnavi02_rollover.gif

2497 ms

globalnavi03_rollover.gif

globalnavi03_rollover.gif

2453 ms

globalnavi04_rollover.gif

globalnavi04_rollover.gif

2318 ms

globalnavi05_rollover.gif

globalnavi05_rollover.gif

2336 ms

globalnavi06_rollover.gif

globalnavi06_rollover.gif

2345 ms

globalnavi07_rollover.gif

globalnavi07_rollover.gif

2403 ms

globalnavi08_rollover.gif

globalnavi08_rollover.gif

2448 ms

gsubnavi01_1_rollover.gif

gsubnavi01_1_rollover.gif

2238 ms

gsubnavi01_2_rollover.gif

gsubnavi01_2_rollover.gif

2287 ms

gsubnavi01_3_rollover.gif

gsubnavi01_3_rollover.gif

2313 ms

gsubnavi01_4_rollover.gif

gsubnavi01_4_rollover.gif

2312 ms

gsubnavi01_5_rollover.gif

gsubnavi01_5_rollover.gif

2379 ms

globalnavi09_rollover.gif

globalnavi09_rollover.gif

2334 ms

globalnavi10_rollover.gif

globalnavi10_rollover.gif

2255 ms

globalnavi11_rollover.gif

globalnavi11_rollover.gif

2302 ms

utilnavi01_rollover.gif

utilnavi01_rollover.gif

2270 ms

utilnavi02_rollover.gif

utilnavi02_rollover.gif

2315 ms

utilnavi03_rollover.gif

utilnavi03_rollover.gif

2083 ms

utilnavi05_rollover.gif

utilnavi05_rollover.gif

2137 ms

btn_font_m_act.gif

btn_font_m_act.gif

2193 ms

btn_font_m_act_act.gif

btn_font_m_act_act.gif

2190 ms

Accessibility Review

kokudo.or.jp accessibility score

63

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

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

High

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

High

Definition list items are not wrapped in <dl> elements

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

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

kokudo.or.jp best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

kokudo.or.jp SEO score

83

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

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

High

Document doesn't use legible font sizes

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Kokudo.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 Kokudo.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.

Social Sharing Optimization

kokudo.or.jp

Open Graph description is not detected on the main page of Kokudo. 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: