Tools & Wizards About Us
kateinoigaku.ne.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

kateinoigaku.ne.jp

株式会社保健同人社｜HOKENDOHJINSHA INC.

Page Load Speed

4.7 sec in total

First Response

580 ms

Resources Loaded

3.9 sec

Page Rendered

168 ms

kateinoigaku.ne.jp screenshot

About Website

Visit kateinoigaku.ne.jp now to see the best up-to-date Kateinoigaku content for Japan and also check out these interesting facts you probably never knew about kateinoigaku.ne.jp

暮らしを、職場を、社会を、「Well-being」に。株式会社保健同人社のコーポレートサイトです。

Visit kateinoigaku.ne.jp

Key Findings

We analyzed Kateinoigaku.ne.jp page load time and found that the first response time was 580 ms and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

kateinoigaku.ne.jp performance score

0

Network Requests Diagram

kateinoigaku.ne.jp

580 ms

www.hokendohjin.co.jp

877 ms

reset.css

329 ms

base.css

328 ms

prototype.css

326 ms

Our browser made a total of 68 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Kateinoigaku.ne.jp, 87% (59 requests) were made to Hokendohjin.co.jp and 4% (3 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Hokendohjin.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 175.2 kB (49%)

Content Size

360.3 kB

After Optimization

185.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Kateinoigaku.ne.jp main page is 360.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. 30% of websites need less resources to load. Javascripts take 133.6 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 17.0 kB

  • Original 22.7 kB
  • After minification 20.3 kB
  • After compression 5.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 2.4 kB, which is 11% 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 17.0 kB or 75% of the original size.

Image Optimization

-0%

Potential reduce by 56 B

  • Original 115.5 kB
  • After minification 115.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. Kateinoigaku images are well optimized though.

JavaScript Optimization

-61%

Potential reduce by 81.1 kB

  • Original 133.6 kB
  • After minification 121.7 kB
  • After compression 52.5 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 81.1 kB or 61% of the original size.

CSS Optimization

-87%

Potential reduce by 77.1 kB

  • Original 88.5 kB
  • After minification 54.5 kB
  • After compression 11.4 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. Kateinoigaku.ne.jp needs all CSS files to be minified and compressed as it can save up to 77.1 kB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 42 (64%)

Requests Now

66

After Optimization

24

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

kateinoigaku.ne.jp

kateinoigaku.ne.jp

580 ms

www.hokendohjin.co.jp

www.hokendohjin.co.jp

877 ms

reset.css

reset.css

329 ms

base.css

base.css

328 ms

prototype.css

prototype.css

326 ms

class.css

class.css

985 ms

main.css

main.css

714 ms

layout.css

layout.css

458 ms

jquery-1.4.1.min.js

jquery-1.4.1.min.js

1136 ms

common.js

common.js

490 ms

heightLine.js

heightLine.js

487 ms

img_hover.js

img_hover.js

611 ms

faq_open_close.js

faq_open_close.js

649 ms

jquery.cookie.js

jquery.cookie.js

651 ms

jquery.textresizer.js

jquery.textresizer.js

763 ms

textresizedetector.js

textresizedetector.js

811 ms

utility_navigation_hover.js

utility_navigation_hover.js

812 ms

search_open_close.js

search_open_close.js

890 ms

books_detail_tab.js

books_detail_tab.js

914 ms

jquery.lightbox-0.5.min.js

jquery.lightbox-0.5.min.js

1149 ms

swfobject.js

swfobject.js

1150 ms

jquery.lightbox-0.5.css

jquery.lightbox-0.5.css

1068 ms

ga.js

ga.js

35 ms

yjlogo_type4.gif

yjlogo_type4.gif

577 ms

fCGcZ1x3Za5Wql_HjmIj17NGiZfUaJqlLEuu4YAFtg--.gif

fCGcZ1x3Za5Wql_HjmIj17NGiZfUaJqlLEuu4YAFtg--.gif

608 ms

logo.gif

logo.gif

157 ms

arrow_red.gif

arrow_red.gif

182 ms

dotted_gray.gif

dotted_gray.gif

163 ms

site_fontsize_small.gif

site_fontsize_small.gif

169 ms

site_fontsize_medium.gif

site_fontsize_medium.gif

164 ms

site_fontsize_large.gif

site_fontsize_large.gif

167 ms

key_visual_toppage_201309.jpg

key_visual_toppage_201309.jpg

805 ms

visitor_navi_soudan_off.gif

visitor_navi_soudan_off.gif

325 ms

visitor_navi_web_off.gif

visitor_navi_web_off.gif

328 ms

visitor_navi_shuppan_off.gif

visitor_navi_shuppan_off.gif

325 ms

visitor_navi_teams_off.gif

visitor_navi_teams_off.gif

329 ms

pamphlet_off.jpg

pamphlet_off.jpg

538 ms

pmark_75.gif

pmark_75.gif

487 ms

kurumin_75.gif

kurumin_75.gif

487 ms

top_pickup_teams.gif

top_pickup_teams.gif

649 ms

top_pickup_kenshu.gif

top_pickup_kenshu.gif

491 ms

top_pickup_5258.gif

top_pickup_5258.gif

648 ms

top_pickup_5257_2.gif

top_pickup_5257_2.gif

648 ms

top_pickup_5239.gif

top_pickup_5239.gif

656 ms

top_pickup_kenkofile.gif

top_pickup_kenkofile.gif

714 ms

site_balloon_arrow.gif

site_balloon_arrow.gif

794 ms

site_fontsize.gif

site_fontsize.gif

794 ms

site_fontsize_small_on.gif

site_fontsize_small_on.gif

794 ms

site_fontsize_medium_on.gif

site_fontsize_medium_on.gif

802 ms

site_fontsize_large_on.gif

site_fontsize_large_on.gif

874 ms

square_gray.gif

square_gray.gif

937 ms

h3.gif

h3.gif

953 ms

page_next.gif

page_next.gif

954 ms

arrow_box.gif

arrow_box.gif

954 ms

footer.gif

footer.gif

964 ms

widgets.js

widgets.js

33 ms

__utm.gif

__utm.gif

20 ms

copyright.gif

copyright.gif

1003 ms

arrow_gray.gif

arrow_gray.gif

1040 ms

visitor_navi_soudan_on.gif

visitor_navi_soudan_on.gif

1065 ms

visitor_navi_web_on.gif

visitor_navi_web_on.gif

1066 ms

visitor_navi_shuppan_on.gif

visitor_navi_shuppan_on.gif

1068 ms

visitor_navi_teams_on.gif

visitor_navi_teams_on.gif

1080 ms

button.831500944bc3eb7ea5276ccdc3f71d2e.js

button.831500944bc3eb7ea5276ccdc3f71d2e.js

30 ms

follow_button.6a78875565a912489e9aef879c881358.ja.html

follow_button.6a78875565a912489e9aef879c881358.ja.html

14 ms

pamphlet_on.jpg

pamphlet_on.jpg

1274 ms

jot

jot

78 ms

print.css

print.css

155 ms

SEO Factors

kateinoigaku.ne.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 Kateinoigaku.ne.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 Kateinoigaku.ne.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

kateinoigaku.ne.jp

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