Access eigox.jp. 【公式】オンライン英会話のエイゴックス

name

value

score

weighting

FCP (First Contentful Paint)

Value7.5 s

1/100

10%

LCP (Largest Contentful Paint)

Value36.8 s

0/100

25%

SI (Speed Index)

Value16.9 s

0/100

10%

TBT (Total Blocking Time)

Value13,190 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.833

4/100

15%

TTI (Time to Interactive)

Value42.8 s

0/100

10%

eigox.jp

303 ms

eigox.jp

2032 ms

css

31 ms

roundedmplus1c.css

61 ms

css

52 ms

Our browser made a total of 95 requests to load all elements on the main page. We found that 35% of them (33 requests) were addressed to the original Eigox.jp, 15% (14 requests) were made to Youtube.com and 12% (11 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (2.8 sec) belongs to the original domain Eigox.jp.

Content Size

4.6 MB

After Optimization

2.5 MB

In fact, the total size of Eigox.jp main page is 4.6 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 2.7 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 1.3 MB

Original 1.5 MB
After minification 1.3 MB
After compression 217.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 164.2 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 1.3 MB or 85% of the original size.

Image Optimization

-31%

Potential reduce by 844.5 kB

Original 2.7 MB
After minification 1.9 MB

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, Eigox needs image optimization as it can save up to 844.5 kB or 31% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-11%

Potential reduce by 37.2 kB

Original 348.5 kB
After minification 335.1 kB
After compression 311.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 37.2 kB or 11% of the original size.

CSS Optimization

-0%

Potential reduce by 121 B

Original 121.5 kB
After minification 121.5 kB
After compression 121.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. Eigox.jp has all CSS files already compressed.

Requests Now

After Optimization

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

Accessibility Issues

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

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.

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

These items highlight common accessibility best practices.

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

Search Engine Optimization Advices

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

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/).

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

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

eigox.jp

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

Report Summary

Performance

Accessibility

Best Practices

SEO

【公式】オンライン英会話のエイゴックス｜ネイティブ100円〜

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

eigox.jp

eigox.jp

css

roundedmplus1c.css

css

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

eigox.jp

eigox.jp

css

roundedmplus1c.css

css

flag-icon.css

tafsales4.js

gtm.js

PWDAWpOhoUY

08EV236PSfs

5sTqVEscUqE

bY5BEUSVvbY

YlEQySeeU-0

m6d-rdE6YdA

page.php

dummyImg.png

yt_icon_rgb_ov.svg

yt_icon_rgb_df.svg

au.svg

ca.svg

bg-bnr_cvarea.jpg

icon_arrow_right.svg

za.svg

ph.svg

us.svg

gb.svg

in.svg

icon_crown_no1.svg

icon_crown_no2.svg

icon_crown_no3.svg

jp.svg

icon_human1_male.svg

icon_human1_female.svg

icon_arrow_right_ftr.svg

icon_blank_ftr.svg

rt.track.js

atm.js

font

font

Lobster12.ttf.woff

pMzIT5TYEYf.css

sGqMB8s6FJy.js

o1ndYS2og_B.js