Tools & Wizards About Us
kyo-shoku.net screenshot

Report Summary

  • 56

    Performance

    Renders faster than
    74% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 86

    SEO

    Google-friendlier than
    61% of websites

kyo-shoku.net

福分堂　教職ネットマガジン | 先生と、先生を目指す方のためのデジタル教育雑誌

Page Load Speed

9.6 sec in total

First Response

472 ms

Resources Loaded

8.8 sec

Page Rendered

263 ms

kyo-shoku.net screenshot

About Website

Welcome to kyo-shoku.net homepage info - get ready to check Kyo Shoku best content for Japan right away, or after learning these important things about kyo-shoku.net

先生と、先生を目指す方のためのデジタル教育雑誌

Visit kyo-shoku.net

Key Findings

We analyzed Kyo-shoku.net page load time and found that the first response time was 472 ms and then it took 9.1 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

kyo-shoku.net performance score

56

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

22/100

10%

LCP (Largest Contentful Paint)

Value6.5 s

8/100

25%

SI (Speed Index)

Value9.4 s

12/100

10%

TBT (Total Blocking Time)

Value40 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value6.5 s

59/100

10%

Network Requests Diagram

kyo-shoku.net

472 ms

kyo-shoku.net

1666 ms

reset.css

534 ms

common.css

539 ms

layout.css

546 ms

Our browser made a total of 106 requests to load all elements on the main page. We found that 66% of them (70 requests) were addressed to the original Kyo-shoku.net, 8% (8 requests) were made to Platform.twitter.com and 8% (8 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (3.8 sec) belongs to the original domain Kyo-shoku.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 255.2 kB (39%)

Content Size

650.6 kB

After Optimization

395.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Kyo-shoku.net main page is 650.6 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. 55% of websites need less resources to load. Images take 341.5 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 59.1 kB

  • Original 71.8 kB
  • After minification 62.5 kB
  • After compression 12.6 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.3 kB, which is 13% 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 59.1 kB or 82% of the original size.

Image Optimization

-9%

Potential reduce by 30.0 kB

  • Original 341.5 kB
  • After minification 311.5 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. Kyo Shoku images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 105.8 kB

  • Original 164.6 kB
  • After minification 140.7 kB
  • After compression 58.7 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 105.8 kB or 64% of the original size.

CSS Optimization

-83%

Potential reduce by 60.3 kB

  • Original 72.8 kB
  • After minification 58.5 kB
  • After compression 12.5 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. Kyo-shoku.net needs all CSS files to be minified and compressed as it can save up to 60.3 kB or 83% of the original size.

Requests Breakdown

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

Requests Now

104

After Optimization

37

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

kyo-shoku.net

kyo-shoku.net

472 ms

kyo-shoku.net

kyo-shoku.net

1666 ms

reset.css

reset.css

534 ms

common.css

common.css

539 ms

layout.css

layout.css

546 ms

style.css

style.css

992 ms

easy_table_creator.css

easy_table_creator.css

644 ms

style.css

style.css

995 ms

ui.tabs.css

ui.tabs.css

1086 ms

theme-my-login.css

theme-my-login.css

1099 ms

styles.css

styles.css

1134 ms

pagenavi-css.css

pagenavi-css.css

1186 ms

jquery.min.js

jquery.min.js

18 ms

i-like-this.js

i-like-this.js

1526 ms

easy_table_creator.js

easy_table_creator.js

1554 ms

jquery.tablesorter.min.js

jquery.tablesorter.min.js

1824 ms

i-like-this.css

i-like-this.css

1647 ms

lemmon-slider.js

lemmon-slider.js

1687 ms

jquery.tile.js

jquery.tile.js

1699 ms

slideshow.js

slideshow.js

2092 ms

smoothScroll.js

smoothScroll.js

2304 ms

textCut.js

textCut.js

2248 ms

echo.js

echo.js

2228 ms

jquery.fs.boxer.js

jquery.fs.boxer.js

2428 ms

jquery.fs.boxer.css

jquery.fs.boxer.css

2368 ms

common.js

common.js

2668 ms

core.min.js

core.min.js

2319 ms

widget.min.js

widget.min.js

2324 ms

tabs.min.js

tabs.min.js

2426 ms

jquery.form.min.js

jquery.form.min.js

2524 ms

scripts.js

scripts.js

2546 ms

ga.js

ga.js

18 ms

__utm.gif

__utm.gif

11 ms

header_bg.png

header_bg.png

523 ms

header_logo.png

header_logo.png

600 ms

header_login_btn.png

header_login_btn.png

636 ms

header_reg_btn.png

header_reg_btn.png

838 ms

header_reg_balloon.png

header_reg_balloon.png

948 ms

bullet01.png

bullet01.png

966 ms

search_block_btn.png

search_block_btn.png

1128 ms

header_content_select.png

header_content_select.png

1133 ms

gnavi_slider_arrow.png

gnavi_slider_arrow.png

1236 ms

sotsugyo_syousyo.png

sotsugyo_syousyo.png

1862 ms

today_pickup_title_in.png

today_pickup_title_in.png

1508 ms

icon_free_l.png

icon_free_l.png

1566 ms

1e2b9f10d06080a8fa340dc31ccc50cf1-212x300.png

1e2b9f10d06080a8fa340dc31ccc50cf1-212x300.png

2181 ms

icon_member_l.png

icon_member_l.png

1764 ms

3304ae3a5776f8a9879f282ab27339ac.jpg

3304ae3a5776f8a9879f282ab27339ac.jpg

2093 ms

icon_free_s.png

icon_free_s.png

2077 ms

icon_member_s.png

icon_member_s.png

2129 ms

monthly_title.png

monthly_title.png

2326 ms

border_line_dot.png

border_line_dot.png

2372 ms

loading.gif

loading.gif

2659 ms

more_read_bullet.png

more_read_bullet.png

2658 ms

b6bd1e8e3a2639b098fdde9b4b1de093.jpg

b6bd1e8e3a2639b098fdde9b4b1de093.jpg

2881 ms

bfce80ac2d40c7908e4ee01c37d9248e.jpg

bfce80ac2d40c7908e4ee01c37d9248e.jpg

2709 ms

ffb86f0d8a28f5ac4a88490faeaa3c51.jpg

ffb86f0d8a28f5ac4a88490faeaa3c51.jpg

2892 ms

monthly_more_btn.png

monthly_more_btn.png

2928 ms

monthly_book_title.png

monthly_book_title.png

3202 ms

monthly_book_more_btn.png

monthly_book_more_btn.png

3220 ms

recommend_area_title.png

recommend_area_title.png

3333 ms

1515574ad09ebb8417cc65d0daf6ac92.jpg

1515574ad09ebb8417cc65d0daf6ac92.jpg

3463 ms

c4d43450a8ee665d0fddba46467e7199.jpg

c4d43450a8ee665d0fddba46467e7199.jpg

3646 ms

widgets.js

widgets.js

193 ms

recommend_more_btn.png

recommend_more_btn.png

3475 ms

sdk.js

sdk.js

33 ms

platform.js

platform.js

60 ms

subcol_about_bnr.png

subcol_about_bnr.png

3693 ms

icon_important.png

icon_important.png

3729 ms

253 ms

xd_arbiter.php

xd_arbiter.php

69 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

30 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

58 ms

fastbutton

fastbutton

81 ms

subcol_info_title.png

subcol_info_title.png

3722 ms

postmessageRelay

postmessageRelay

62 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

18 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

17 ms

3193398744-postmessagerelay.js

3193398744-postmessagerelay.js

33 ms

rpc:shindig_random.js

rpc:shindig_random.js

35 ms

subcol_keyword_title.png

subcol_keyword_title.png

3762 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

61 ms

button.0308b81ff1714e446f674b5b9793f2cd.js

button.0308b81ff1714e446f674b5b9793f2cd.js

33 ms

timeline.d11f7a3b3287fb94220e8ee6d03cc772.js

timeline.d11f7a3b3287fb94220e8ee6d03cc772.js

62 ms

like.php

like.php

221 ms

subcol_tw_title.png

subcol_tw_title.png

3702 ms

syndication

syndication

91 ms

552698487431647233

552698487431647233

168 ms

follow_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html

follow_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html

40 ms

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html

56 ms

footer_logo.png

footer_logo.png

3664 ms

wy1X4hBW7e7.js

wy1X4hBW7e7.js

38 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

15 ms

timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css

timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css

28 ms

timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css

timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css

238 ms

footer_company_logo.png

footer_company_logo.png

3713 ms

224f2a1a39d1ea0f95da599b3e8157af_normal.jpeg

224f2a1a39d1ea0f95da599b3e8157af_normal.jpeg

228 ms

hfKRegkr_normal.png

hfKRegkr_normal.png

233 ms

ff_normal.gif

ff_normal.gif

233 ms

tirbuqxkn06i5m9qy8vp_normal.jpeg

tirbuqxkn06i5m9qy8vp_normal.jpeg

238 ms

Cd-jQqtUAAEpIS3.jpg:small

Cd-jQqtUAAEpIS3.jpg:small

241 ms

CcbCR6rWIAEoeb4.jpg:small

CcbCR6rWIAEoeb4.jpg:small

239 ms

CcbCm_RXEAAYaDW.jpg:small

CcbCm_RXEAAYaDW.jpg:small

238 ms

backtotop.png

backtotop.png

3653 ms

footer_bg.png

footer_bg.png

3602 ms

jot.html

jot.html

26 ms

Accessibility Review

kyo-shoku.net accessibility score

77

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.

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

Best Practices

kyo-shoku.net best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

kyo-shoku.net SEO score

86

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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 uses 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 Kyo-shoku.net 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 Kyo-shoku.net 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

kyo-shoku.net

Open Graph data is detected on the main page of Kyo Shoku. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: