Tools & Wizards About Us
johokan.jp screenshot

Report Summary

  • 49

    Performance

    Renders faster than
    67% of other websites

  • 64

    Accessibility

    Visual factors better than
    that of 29% of websites

  • 50

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 67

    SEO

    Google-friendlier than
    26% of websites

johokan.jp

オーストラリア留学、シドニー留学、ワーキングホリデーなら：ICNオーストラリア留学情報館

Page Load Speed

6.5 sec in total

First Response

526 ms

Resources Loaded

5.5 sec

Page Rendered

530 ms

johokan.jp screenshot

About Website

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

オーストラリア留学、オーストラリアワーキングホリデー、ACNTなどシドニー専門学校や語学留学、J-SHINE取得をお考えの方へ、口コミ80％のシドニー現地留学エージェントのICNオーストラリア留学情報館。

Visit johokan.jp

Key Findings

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

Performance Metrics

johokan.jp performance score

49

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

20/100

10%

LCP (Largest Contentful Paint)

Value4.2 s

45/100

25%

SI (Speed Index)

Value8.4 s

19/100

10%

TBT (Total Blocking Time)

Value510 ms

57/100

30%

CLS (Cumulative Layout Shift)

Value0.029

100/100

15%

TTI (Time to Interactive)

Value11.4 s

19/100

10%

Network Requests Diagram

johokan.jp

526 ms

johokan.jp

958 ms

style.css

178 ms

wrapper.js

355 ms

anzsco_widget.js

1050 ms

Our browser made a total of 118 requests to load all elements on the main page. We found that 75% of them (89 requests) were addressed to the original Johokan.jp, 15% (18 requests) were made to Platform.twitter.com and 3% (4 requests) were made to Searchmyanzsco.com.au. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Johokan.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 356.7 kB (53%)

Content Size

670.2 kB

After Optimization

313.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-85%

Potential reduce by 124.6 kB

  • Original 146.9 kB
  • After minification 121.8 kB
  • After compression 22.4 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 25.1 kB, which is 17% 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 124.6 kB or 85% of the original size.

Image Optimization

-45%

Potential reduce by 227.9 kB

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

JavaScript Optimization

-25%

Potential reduce by 4.0 kB

  • Original 16.2 kB
  • After minification 16.2 kB
  • After compression 12.2 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 4.0 kB or 25% of the original size.

CSS Optimization

-25%

Potential reduce by 209 B

  • Original 850 B
  • After minification 850 B
  • After compression 641 B

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. Johokan.jp needs all CSS files to be minified and compressed as it can save up to 209 B or 25% of the original size.

Requests Breakdown

Number of requests can be reduced by 51 (46%)

Requests Now

110

After Optimization

59

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

johokan.jp

johokan.jp

526 ms

johokan.jp

johokan.jp

958 ms

style.css

style.css

178 ms

wrapper.js

wrapper.js

355 ms

anzsco_widget.js

anzsco_widget.js

1050 ms

urchin.js

urchin.js

30 ms

widget_js_v

widget_js_v

1214 ms

top_bg.gif

top_bg.gif

370 ms

top_left.gif

top_left.gif

718 ms

en.png

en.png

326 ms

top_search.gif

top_search.gif

330 ms

top_pho.jpg

top_pho.jpg

568 ms

newstop.gif

newstop.gif

567 ms

bot1.gif

bot1.gif

750 ms

bot3.gif

bot3.gif

746 ms

bot2.gif

bot2.gif

746 ms

bot4.gif

bot4.gif

750 ms

bot5.gif

bot5.gif

750 ms

bot6.gif

bot6.gif

749 ms

bot8.gif

bot8.gif

953 ms

bot11.gif

bot11.gif

968 ms

bot9.gif

bot9.gif

965 ms

maru.gif

maru.gif

966 ms

top_siry.gif

top_siry.gif

965 ms

top_bg2.gif

top_bg2.gif

966 ms

main_side_left.gif

main_side_left.gif

1130 ms

main_side_right.gif

main_side_right.gif

1125 ms

gog_l3.gif

gog_l3.gif

1129 ms

jun_hirose103.jpg

jun_hirose103.jpg

1298 ms

skype_logo.png

skype_logo.png

1124 ms

line.gif

line.gif

1128 ms

Facebook_NEW.png

Facebook_NEW.png

1820 ms

instagram.jpg

instagram.jpg

1298 ms

bigtag3-blog.gif

bigtag3-blog.gif

1298 ms

free_support10.gif

free_support10.gif

1302 ms

insurance.gif

insurance.gif

1299 ms

bigtitle-riyosha2.gif

bigtitle-riyosha2.gif

1625 ms

new_2.gif

new_2.gif

1468 ms

aicon.gif

aicon.gif

1475 ms

more.gif

more.gif

1477 ms

bigtag_language.gif

bigtag_language.gif

1478 ms

bigtag_wh_1.gif

bigtag_wh_1.gif

1640 ms

bigtag3-naturopathy.gif

bigtag3-naturopathy.gif

1651 ms

purpose_separate.gif

purpose_separate.gif

1652 ms

bigtag3-beauty.gif

bigtag3-beauty.gif

1653 ms

top_center.gif

top_center.gif

666 ms

top_right.gif

top_right.gif

663 ms

spacer_gray.gif

spacer_gray.gif

663 ms

side_left_bg.gif

side_left_bg.gif

697 ms

l_syo.gif

l_syo.gif

1110 ms

l_oto.gif

l_oto.gif

1111 ms

l_sir.gif

l_sir.gif

1112 ms

l_mitu.gif

l_mitu.gif

1101 ms

widgets.js

widgets.js

294 ms

bigtag3-yoga.png

bigtag3-yoga.png

1684 ms

__utm.gif

__utm.gif

250 ms

bigtag3-fitness.png

bigtag3-fitness.png

1859 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

126 ms

settings

settings

198 ms

bigtag_childcare.gif

bigtag_childcare.gif

1296 ms

bigtag3-tesol.gif

bigtag3-tesol.gif

1294 ms

top_left.gif

top_left.gif

620 ms

spacer_gray.gif

spacer_gray.gif

635 ms

top_right.gif

top_right.gif

634 ms

top_center.gif

top_center.gif

619 ms

timeline.e108540dddc96e4b707f5cf259a582d7.js

timeline.e108540dddc96e4b707f5cf259a582d7.js

19 ms

side_left_bg.gif

side_left_bg.gif

768 ms

icnjapan_aus

icnjapan_aus

65 ms

bigtag3-tecsol.gif

bigtag3-tecsol.gif

1103 ms

bigtab3-cookery.gif

bigtab3-cookery.gif

1250 ms

side_right_bg.gif

side_right_bg.gif

783 ms

bigtag3-webdesign.gif

bigtag3-webdesign.gif

1290 ms

bigtag_tourism.gif

bigtag_tourism.gif

1285 ms

bigtag3-accountant.gif

bigtag3-accountant.gif

1286 ms

bigtag3-interior.gif

bigtag3-interior.gif

1415 ms

polyfills-a40ef1678bae11e696dba45124eadd70.js

polyfills-a40ef1678bae11e696dba45124eadd70.js

11 ms

runtime-b1c52fd0a13ead5fcf6b.js

runtime-b1c52fd0a13ead5fcf6b.js

77 ms

modules-96ebc7ac3ad66d681a3d.js

modules-96ebc7ac3ad66d681a3d.js

76 ms

main-babd9234dc048fb47339.js

main-babd9234dc048fb47339.js

69 ms

_app-a9c9f1a99e4414675fb1.js

_app-a9c9f1a99e4414675fb1.js

133 ms

%5BscreenName%5D-0517bdda27d5006a5a2d.js

%5BscreenName%5D-0517bdda27d5006a5a2d.js

146 ms

_buildManifest.js

_buildManifest.js

157 ms

_ssgManifest.js

_ssgManifest.js

158 ms

aicon.gif

aicon.gif

583 ms

gog_l3.gif

gog_l3.gif

584 ms

bigtag3-marketing.gif

bigtag3-marketing.gif

1202 ms

bigtag3-assistantnurse.png

bigtag3-assistantnurse.png

1424 ms

bigtag3-kangoprogram.png

bigtag3-kangoprogram.png

1599 ms

OET.jpg

OET.jpg

1248 ms

bigtag3-aromatherapy.gif

bigtag3-aromatherapy.gif

1371 ms

bigtag3-interpreter.gif

bigtag3-interpreter.gif

1370 ms

8526.0c32a8f0cfc5749221a3.js

8526.0c32a8f0cfc5749221a3.js

13 ms

1755.07a49c40b12af4f75780.js

1755.07a49c40b12af4f75780.js

12 ms

8283.f3e5048cca7cef5eed7f.js

8283.f3e5048cca7cef5eed7f.js

5 ms

3077.44bfeb00af01bc4020f6.js

3077.44bfeb00af01bc4020f6.js

9 ms

1362.42d432e02f7980bca032.js

1362.42d432e02f7980bca032.js

8 ms

4956.c4e51ef593974b9db0bb.js

4956.c4e51ef593974b9db0bb.js

29 ms

5893.d500bd2a89ded806aa73.js

5893.d500bd2a89ded806aa73.js

27 ms

bigtag_carrerup.gif

bigtag_carrerup.gif

1220 ms

purpose_bottom.gif

purpose_bottom.gif

1266 ms

monthly_cp.gif

monthly_cp.gif

1382 ms

t-language.gif

t-language.gif

1384 ms

t-jido.gif

t-jido.gif

1388 ms

anzsco_widget_inner.js

anzsco_widget_inner.js

206 ms

t-senmon.gif

t-senmon.gif

1266 ms

t-senmon_short.gif

t-senmon_short.gif

1254 ms

b-shikaku.gif

b-shikaku.gif

1369 ms

news_1.gif

news_1.gif

1371 ms

anaba.gif

anaba.gif

1373 ms

jquery-3.7.1.min

jquery-3.7.1.min

207 ms

authcompany

authcompany

1317 ms

visa.gif

visa.gif

1255 ms

purpose_title_left.gif

purpose_title_left.gif

1248 ms

purpose_title_center.gif

purpose_title_center.gif

1249 ms

purpose_title_right.gif

purpose_title_right.gif

1360 ms

page-not-found

page-not-found

989 ms

purpose_side_left.gif

purpose_side_left.gif

1257 ms

purpose_side_right.gif

purpose_side_right.gif

1206 ms

Accessibility Review

johokan.jp accessibility score

64

Accessibility Issues

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<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

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

johokan.jp best practices score

50

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

johokan.jp SEO score

67

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

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    EUC-JP

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Johokan.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Johokan.jp main page’s claimed encoding is euc-jp. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

johokan.jp

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