Tools & Wizards About Us
eikoh.co.jp screenshot

Report Summary

  • 37

    Performance

    Renders faster than
    57% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

eikoh.co.jp

栄光ゼミナール公式サイト ｜ 中学受験・高校受験・大学受験・個別指導の塾 | 中学受験・高校受験・大学受験・個別指導はお任せください。

Page Load Speed

3.5 sec in total

First Response

679 ms

Resources Loaded

2.7 sec

Page Rendered

133 ms

eikoh.co.jp screenshot

About Website

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

中学受験・高校受験・大学受験・個別指導の塾、栄光ゼミナール公式サイト。少人数グループ指導や個別指導など多様な指導で、一人ひとりの成績向上・志望校合格を実現します。

Visit eikoh.co.jp

Key Findings

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

Performance Metrics

eikoh.co.jp performance score

37

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.8 s

1/100

10%

LCP (Largest Contentful Paint)

Value14.3 s

0/100

25%

SI (Speed Index)

Value12.1 s

3/100

10%

TBT (Total Blocking Time)

Value410 ms

67/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value11.8 s

17/100

10%

Network Requests Diagram

eikoh.co.jp

679 ms

jquery-1.4.2.min.js

663 ms

jquery.cookie.js

334 ms

yuga.js

336 ms

thickbox.js

337 ms

Our browser made a total of 55 requests to load all elements on the main page. We found that all of those requests were addressed to Eikoh.co.jp and no external sources were called. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Eikoh.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 152.6 kB (44%)

Content Size

349.6 kB

After Optimization

197.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-83%

Potential reduce by 20.9 kB

  • Original 25.2 kB
  • After minification 16.5 kB
  • After compression 4.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 8.7 kB, which is 34% 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 20.9 kB or 83% of the original size.

Image Optimization

-21%

Potential reduce by 42.8 kB

  • Original 200.9 kB
  • After minification 158.2 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, Eikoh needs image optimization as it can save up to 42.8 kB or 21% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-71%

Potential reduce by 78.2 kB

  • Original 109.5 kB
  • After minification 92.4 kB
  • After compression 31.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 78.2 kB or 71% of the original size.

CSS Optimization

-76%

Potential reduce by 10.7 kB

  • Original 14.0 kB
  • After minification 10.9 kB
  • After compression 3.3 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. Eikoh.co.jp needs all CSS files to be minified and compressed as it can save up to 10.7 kB or 76% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (19%)

Requests Now

54

After Optimization

44

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

eikoh.co.jp

eikoh.co.jp

679 ms

jquery-1.4.2.min.js

jquery-1.4.2.min.js

663 ms

jquery.cookie.js

jquery.cookie.js

334 ms

yuga.js

yuga.js

336 ms

thickbox.js

thickbox.js

337 ms

common.js

common.js

338 ms

index.js

index.js

337 ms

reset.css

reset.css

500 ms

layout.css

layout.css

501 ms

wysiwyg.css

wysiwyg.css

502 ms

common.css

common.css

503 ms

index.css

index.css

503 ms

s_code.js

s_code.js

546 ms

logo_img_01.png

logo_img_01.png

168 ms

header_home.png

header_home.png

167 ms

header_sitemap.png

header_sitemap.png

167 ms

header_inquary.png

header_inquary.png

168 ms

fontsize_img_01.png

fontsize_img_01.png

169 ms

fontsize_img_02.png

fontsize_img_02.png

170 ms

fontsize_img_03.png

fontsize_img_03.png

333 ms

header_search_img_01.png

header_search_img_01.png

333 ms

gnavi_bg_01.png

gnavi_bg_01.png

333 ms

gnavi_img_01.png

gnavi_img_01.png

335 ms

gnavi_img_04.png

gnavi_img_04.png

334 ms

gnavi_img_05.png

gnavi_img_05.png

336 ms

gnavi_img_06.png

gnavi_img_06.png

496 ms

index_img_01.png

index_img_01.png

497 ms

icon_rss.png

icon_rss.png

497 ms

icon_viewall.png

icon_viewall.png

498 ms

news_icon_publicity.png

news_icon_publicity.png

498 ms

index_img_04.png

index_img_04.png

498 ms

index_img_05.png

index_img_05.png

826 ms

index_img_06.png

index_img_06.png

661 ms

ISOmark.jpg

ISOmark.jpg

828 ms

index_img_07.png

index_img_07.png

663 ms

index_img_08.png

index_img_08.png

663 ms

footer_img_01.png

footer_img_01.png

664 ms

footer_gotop_01.png

footer_gotop_01.png

827 ms

arrow_01.png

arrow_01.png

829 ms

top.xml

top.xml

793 ms

header_home_on.png

header_home_on.png

800 ms

header_sitemap_on.png

header_sitemap_on.png

952 ms

header_inquary_on.png

header_inquary_on.png

953 ms

fontsize_img_02_on.png

fontsize_img_02_on.png

954 ms

fontsize_img_03_on.png

fontsize_img_03_on.png

956 ms

header_search_img_01_on.png

header_search_img_01_on.png

956 ms

gnavi_img_01_on.png

gnavi_img_01_on.png

956 ms

gnavi_img_04_on.png

gnavi_img_04_on.png

1117 ms

gnavi_img_05_on.png

gnavi_img_05_on.png

1115 ms

gnavi_img_06_on.png

gnavi_img_06_on.png

997 ms

index_img_04_on.png

index_img_04_on.png

997 ms

index_img_06_on.png

index_img_06_on.png

997 ms

loadingAnimation.gif

loadingAnimation.gif

997 ms

img1.png

img1.png

651 ms

img2.png

img2.png

653 ms

Accessibility Review

eikoh.co.jp accessibility score

81

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-hidden="true"] elements contain focusable descendents

High

ARIA IDs are not unique

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

High

Links do not have a discernible name

Best Practices

eikoh.co.jp best practices score

67

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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

eikoh.co.jp SEO score

79

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

robots.txt is not valid

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 Eikoh.co.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 Eikoh.co.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

eikoh.co.jp

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