Tools & Wizards About Us
nittokyo.or.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

nittokyo.or.jp

公益社団法人日本糖尿病協会

Page Load Speed

6.5 sec in total

First Response

1.2 sec

Resources Loaded

4.8 sec

Page Rendered

428 ms

nittokyo.or.jp screenshot

About Website

Welcome to nittokyo.or.jp homepage info - get ready to check Nittokyo best content for Japan right away, or after learning these important things about nittokyo.or.jp

日本糖尿病協会は、糖尿病に関する知識の普及啓発、療養指導、調査研究等をその理念に掲げ、広く国民の健康増進に寄与することを目的に現在約10万人の会員を擁しています。日本糖尿病協会には、糖尿病患者とその家族、医師、看護師・栄養士・ 糖尿病療養指導士などの医療スタッフで作られた約1,600の糖尿病「友の会」があります。

Visit nittokyo.or.jp

Key Findings

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

Performance Metrics

nittokyo.or.jp performance score

0

Network Requests Diagram

nittokyo.or.jp

1197 ms

base.css

595 ms

skitter.styles2.css

788 ms

index.css

1171 ms

logo.gif

804 ms

Our browser made a total of 88 requests to load all elements on the main page. We found that 95% of them (84 requests) were addressed to the original Nittokyo.or.jp, 2% (2 requests) were made to Staticxx.facebook.com and 1% (1 request) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Nittokyo.or.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 313.0 kB (35%)

Content Size

888.5 kB

After Optimization

575.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-83%

Potential reduce by 41.3 kB

  • Original 49.7 kB
  • After minification 33.6 kB
  • After compression 8.3 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 16.1 kB, which is 32% 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 41.3 kB or 83% of the original size.

Image Optimization

-20%

Potential reduce by 125.8 kB

  • Original 641.5 kB
  • After minification 515.7 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. Obviously, Nittokyo needs image optimization as it can save up to 125.8 kB or 20% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-68%

Potential reduce by 94.9 kB

  • Original 140.2 kB
  • After minification 133.4 kB
  • After compression 45.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 94.9 kB or 68% of the original size.

CSS Optimization

-89%

Potential reduce by 51.0 kB

  • Original 57.1 kB
  • After minification 40.7 kB
  • After compression 6.2 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. Nittokyo.or.jp needs all CSS files to be minified and compressed as it can save up to 51.0 kB or 89% of the original size.

Requests Breakdown

Number of requests can be reduced by 20 (23%)

Requests Now

87

After Optimization

67

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

nittokyo.or.jp

nittokyo.or.jp

1197 ms

base.css

base.css

595 ms

skitter.styles2.css

skitter.styles2.css

788 ms

index.css

index.css

1171 ms

logo.gif

logo.gif

804 ms

address_off.png

address_off.png

810 ms

menu_beginner.png

menu_beginner.png

620 ms

menu_patient.png

menu_patient.png

784 ms

menu_doctor.png

menu_doctor.png

825 ms

menu_club.png

menu_club.png

975 ms

menu_event.png

menu_event.png

977 ms

menu_about.png

menu_about.png

1001 ms

visual_yuruchara.jpg

visual_yuruchara.jpg

1420 ms

visual_1st2.jpg

visual_1st2.jpg

1489 ms

visual_supporter.jpg

visual_supporter.jpg

1741 ms

visual_wddj.jpg

visual_wddj.jpg

1746 ms

title_patient3.png

title_patient3.png

1207 ms

title_doctor3.png

title_doctor3.png

1171 ms

new.gif

new.gif

1362 ms

title_beginner3.png

title_beginner3.png

1407 ms

title_event3.png

title_event3.png

1554 ms

title_club3.png

title_club3.png

1414 ms

title_about3.png

title_about3.png

1426 ms

title_emergency_patient3.png

title_emergency_patient3.png

1501 ms

pdficon_small.png

pdficon_small.png

1553 ms

title_emergency_doctor3.png

title_emergency_doctor3.png

1809 ms

title_news3.png

title_news3.png

1625 ms

jquery-1.6.3.min.js

jquery-1.6.3.min.js

1919 ms

jquery.skitter.min.js

jquery.skitter.min.js

1733 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

1548 ms

jquery.animate-colors-min.js

jquery.animate-colors-min.js

1548 ms

pagetop.js

pagetop.js

1630 ms

banner_wddj.png

banner_wddj.png

1738 ms

banner_meeting3.png

banner_meeting3.png

1739 ms

banner_db_edu.png

banner_db_edu.png

2048 ms

banner_db_den.png

banner_db_den.png

1830 ms

banner_db_club.png

banner_db_club.png

1958 ms

banner_ayumi.png

banner_ayumi.png

1949 ms

banner_iunite.png

banner_iunite.png

1924 ms

img_sakae3.png

img_sakae3.png

1847 ms

img_dme3.png

img_dme3.png

2328 ms

img_jadec_db.png

img_jadec_db.png

1908 ms

img_seminar.png

img_seminar.png

1903 ms

banner_ToothFairy_off.png

banner_ToothFairy_off.png

1891 ms

bnr_novo.gif

bnr_novo.gif

2012 ms

bnr_ono.gif

bnr_ono.gif

1837 ms

spacer.gif

spacer.gif

1897 ms

btn_to-page-top.gif

btn_to-page-top.gif

1661 ms

arrow_orange_off.gif

arrow_orange_off.gif

1547 ms

address_on.png

address_on.png

1616 ms

menu_bg.png

menu_bg.png

1539 ms

menu_beginner_on.png

menu_beginner_on.png

1493 ms

menu_patient_on.png

menu_patient_on.png

1491 ms

menu_doctor_on.png

menu_doctor_on.png

1508 ms

menu_club_on.png

menu_club_on.png

1470 ms

menu_event_on.png

menu_event_on.png

1485 ms

menu_about_on.png

menu_about_on.png

1474 ms

next.png

next.png

1408 ms

title_patient3_on.png

title_patient3_on.png

1388 ms

title_doctor3_on.png

title_doctor3_on.png

1451 ms

title_beginner3_on.png

title_beginner3_on.png

1481 ms

title_event3_on.png

title_event3_on.png

1463 ms

title_club3_on.png

title_club3_on.png

1348 ms

title_about3_on.png

title_about3_on.png

1355 ms

title_emergency_patient3_on.png

title_emergency_patient3_on.png

1329 ms

arrow_blue.gif

arrow_blue.gif

1375 ms

title_emergency_doctor3_on.png

title_emergency_doctor3_on.png

1304 ms

title_news3_on.png

title_news3_on.png

1346 ms

banner_wddj_on.png

banner_wddj_on.png

1346 ms

banner_meeting3_on.png

banner_meeting3_on.png

1264 ms

banner_db_edu_on.png

banner_db_edu_on.png

1190 ms

banner_db_den_on.png

banner_db_den_on.png

1242 ms

banner_db_club_on.png

banner_db_club_on.png

1275 ms

all.js

all.js

42 ms

banner_ayumi_on.png

banner_ayumi_on.png

1274 ms

banner_iunite_on.png

banner_iunite_on.png

1229 ms

168 ms

img_info_head.png

img_info_head.png

1214 ms

xd_arbiter.php

xd_arbiter.php

53 ms

xd_arbiter.php

xd_arbiter.php

72 ms

img_info_middle.png

img_info_middle.png

1223 ms

img_info_dash.png

img_info_dash.png

1274 ms

img_info_bottom.png

img_info_bottom.png

1303 ms

banner_ToothFairy_on.png

banner_ToothFairy_on.png

1236 ms

btn_to-page-top_ov.gif

btn_to-page-top_ov.gif

1153 ms

footer.jpg

footer.jpg

1161 ms

prev.png

prev.png

1231 ms

ajax-loader.gif

ajax-loader.gif

1197 ms

SEO Factors

nittokyo.or.jp SEO score

0

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 Nittokyo.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 Nittokyo.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

nittokyo.or.jp

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