Access enago.jp. 英文校正・英文校閲エナゴ | 1500以上の専門分野。英語論文の英文校正ならEnagoの英文添削・ネイティブチェック

name

value

score

weighting

FCP (First Contentful Paint)

Value5.2 s

8/100

10%

LCP (Largest Contentful Paint)

Value12.6 s

0/100

25%

SI (Speed Index)

Value11.2 s

5/100

10%

TBT (Total Blocking Time)

Value1,860 ms

9/100

30%

CLS (Cumulative Layout Shift)

Value0.262

47/100

15%

TTI (Time to Interactive)

Value17.8 s

4/100

10%

enago.jp

20 ms

www.enago.jp

32 ms

www.enago.jp

127 ms

8fbb3a.js

324 ms

bootstrap-new.css

45 ms

Our browser made a total of 114 requests to load all elements on the main page. We found that 73% of them (83 requests) were addressed to the original Enago.jp, 10% (11 requests) were made to Google.com and 3% (3 requests) were made to Cse.google.com. The less responsive or slowest element that took the longest time to load (965 ms) belongs to the original domain Enago.jp.

Content Size

1.2 MB

After Optimization

515.8 kB

In fact, the total size of Enago.jp main page is 1.2 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. 70% of websites need less resources to load. CSS take 535.5 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 66.5 kB

Original 84.4 kB
After minification 69.9 kB
After compression 17.9 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 14.5 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 66.5 kB or 79% of the original size.

Image Optimization

-0%

Potential reduce by 1.3 kB

Original 284.0 kB
After minification 282.7 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. Enago images are well optimized though.

JavaScript Optimization

-52%

Potential reduce by 147.2 kB

Original 281.6 kB
After minification 268.7 kB
After compression 134.4 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 147.2 kB or 52% of the original size.

CSS Optimization

-85%

Potential reduce by 454.7 kB

Original 535.5 kB
After minification 467.6 kB
After compression 80.8 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. Enago.jp needs all CSS files to be minified and compressed as it can save up to 454.7 kB or 85% of the original size.

Requests Now

106

After Optimization

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

Accessibility Issues

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.

High

[role] values are not valid

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 keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

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

High

Serves images with low resolution

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

Search Engine Optimization Advices

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

High

Links are not crawlable

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

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

EN
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Enago.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it does not match the claimed English language. Our system also found out that Enago.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

enago.jp

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

英文校正・英文校閲エナゴ | 1500以上の専門分野。英語論文の英文校正ならEnagoの英文添削・ネイティブチェック

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

enago.jp

www.enago.jp

www.enago.jp

8fbb3a.js

bootstrap-new.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

enago.jp

www.enago.jp

www.enago.jp

8fbb3a.js

bootstrap-new.css

index-style.css

modal.css

jquery-2.1.0.min.js

bootstrap.min.js

bootstrap-hover-dropdown.js

common-script.js

script.opentracker.net

conversion.js

main-logo.png

top-call-banner.jpg

transparent.gif

floatmenu.png

ps-banner.png

banner-text.png

strengths-bubble.png

cont-box-ps.png

cont-box-img-3.png

cont-box-img-1.png

cont-box-img-2.png

cont-box-img-4.png

cont-box-img-5.png

cont-box-img-6.png

cont-box-img-7.png

cont-box-img-8.png

beginner-img.png

ps-img.png

bottom-big-CTA.png

bottom-small-CTA1.png

bottom-small-CTA2.png

bottom-call-banner.jpg

ps-img.png

solutions-img.png

auto-quote-img.png

interview-img-1.png

interview-img-2.png

ulatus-banner.png

book-editing.png

academy-banner.png