Report Summary

  • 9

    Performance

    Renders faster than
    23% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

elmo.co.jp

エルモは教育ICTを基盤として様々な映像情報コミュニケーション価値を創造します。

Page Load Speed

13.5 sec in total

First Response

2.2 sec

Resources Loaded

9.6 sec

Page Rendered

1.7 sec

elmo.co.jp screenshot

About Website

Visit elmo.co.jp now to see the best up-to-date Elmo content for Japan and also check out these interesting facts you probably never knew about elmo.co.jp

創業1921年のエルモは、映像情報コミュニケーションの世界と未来を見据え、先進テクノロジーの研究・開発にさらに研鑽を重ね、新しい価値を創造するとともに、教育と企業の発展によりウェルビーイングな社会の実現に貢献していきたいと考えます。

Visit elmo.co.jp

Key Findings

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

Performance Metrics

elmo.co.jp performance score

9

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.9 s

4/100

10%

LCP (Largest Contentful Paint)

Value22.8 s

0/100

25%

SI (Speed Index)

Value20.0 s

0/100

10%

TBT (Total Blocking Time)

Value1,280 ms

18/100

30%

CLS (Cumulative Layout Shift)

Value0.476

18/100

15%

TTI (Time to Interactive)

Value20.5 s

2/100

10%

Network Requests Diagram

www.elmo.co.jp

2223 ms

jquery.min.js

91 ms

search-filter-build.min.js

348 ms

chosen.jquery.min.js

690 ms

jquery-migrate.min.js

140 ms

Our browser made a total of 93 requests to load all elements on the main page. We found that 81% of them (75 requests) were addressed to the original Elmo.co.jp, 4% (4 requests) were made to Googletagmanager.com and 3% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (5 sec) relates to the external source Googletagmanager.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 375.6 kB (9%)

Content Size

4.3 MB

After Optimization

4.0 MB

In fact, the total size of Elmo.co.jp main page is 4.3 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. Only a small number of websites need less resources to load. Images take 3.9 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 59.0 kB

  • Original 70.9 kB
  • After minification 66.7 kB
  • After compression 11.8 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 59.0 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 5.4 kB

  • Original 3.9 MB
  • After minification 3.8 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. Elmo images are well optimized though.

JavaScript Optimization

-62%

Potential reduce by 169.9 kB

  • Original 275.3 kB
  • After minification 275.3 kB
  • After compression 105.5 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 169.9 kB or 62% of the original size.

CSS Optimization

-95%

Potential reduce by 141.2 kB

  • Original 148.8 kB
  • After minification 42.9 kB
  • After compression 7.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. Elmo.co.jp needs all CSS files to be minified and compressed as it can save up to 141.2 kB or 95% of the original size.

Requests Breakdown

Number of requests can be reduced by 27 (30%)

Requests Now

89

After Optimization

62

The browser has sent 89 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Elmo. 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 4 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

elmo.co.jp accessibility score

94

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

Links do not have a discernible name

Tables and lists

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

Impact

Issue

High

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

Best Practices

elmo.co.jp 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

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

elmo.co.jp SEO score

91

Search Engine Optimization Advices

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 doesn't use 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 Elmo.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 Elmo.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

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