6.3 sec in total
893 ms
5.1 sec
272 ms
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.jpWe analyzed Elmo.co.jp page load time and found that the first response time was 893 ms and then it took 5.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
elmo.co.jp performance score
name
value
score
weighting
Value4.7 s
12/100
10%
Value13.6 s
0/100
25%
Value10.2 s
9/100
10%
Value400 ms
68/100
30%
Value0.56
12/100
15%
Value12.8 s
13/100
10%
893 ms
336 ms
337 ms
338 ms
339 ms
Our browser made a total of 68 requests to load all elements on the main page. We found that 66% of them (45 requests) were addressed to the original Elmo.co.jp, 13% (9 requests) were made to Google.com and 6% (4 requests) were made to Elmoqbic.com. The less responsive or slowest element that took the longest time to load (2.3 sec) relates to the external source Elmoqbic.com.
Page size can be reduced by 140.6 kB (12%)
1.2 MB
1.0 MB
In fact, the total size of Elmo.co.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. 40% of websites need less resources to load. Images take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 39.2 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.6 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 39.2 kB or 78% of the original size.
Potential reduce by 58.8 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. Elmo images are well optimized though.
Potential reduce by 12.8 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 12.8 kB or 17% of the original size.
Potential reduce by 29.7 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 29.7 kB or 82% of the original size.
Number of requests can be reduced by 25 (38%)
65
40
The browser has sent 65 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 10 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
elmo.co.jp
893 ms
accordion.js
336 ms
base.css
337 ms
nav2.js
338 ms
search.css
339 ms
ex_attention.js
783 ms
style.css
168 ms
layout.css
371 ms
urchin.js
20 ms
jquery.min.js
93 ms
top_kv.jpg
519 ms
oshirase.jpg
363 ms
notice.gif
168 ms
onlinestore_banner.jpg
671 ms
BOXi_banner.jpg
673 ms
bnr_slimg_11_l.jpg
363 ms
bnr_slimg_01.jpg
504 ms
bnr_QBiC_MS1_PANO.jpg
502 ms
icon_new_products.gif
502 ms
icon_new.gif
669 ms
bnr_tit_pickup.gif
671 ms
bnr_slimg_02.jpg
837 ms
bnr_slimg_13.jpg
690 ms
bnr_slimg_10.jpg
836 ms
bnr_slimg_11.jpg
837 ms
bnr_slimg_03.jpg
837 ms
bnr_slimg_08.jpg
839 ms
bnr_slimg_05.jpg
862 ms
bnr_slimg_06.jpg
1169 ms
all.js
13 ms
bg_page.gif
997 ms
bg_header.gif
998 ms
header_logo.gif
999 ms
bt_usa.gif
1001 ms
bt_europe.gif
1030 ms
cse.js
80 ms
bt_report.gif
1154 ms
4bo4.jpg
1155 ms
4bo2.jpg
1156 ms
4bo1.jpg
1159 ms
bnr_slimg_12_sml.jpg
1191 ms
bg_gnav.jpg
1320 ms
gnav.jpg
1487 ms
bg_tit_newstopic.gif
1322 ms
bg_tit_event.gif
1322 ms
bg_tit_report.gif
1325 ms
bt_pagetop.gif
1363 ms
bnr_sltab.gif
1487 ms
__utm.gif
23 ms
cse.js
199 ms
39 ms
xd_arbiter.php
20 ms
xd_arbiter.php
26 ms
bg_bnr_jvc.gif
1340 ms
jsapi
26 ms
default+ja.css
3 ms
default.css
41 ms
default+ja.I.js
12 ms
default.css
39 ms
bg_footer.jpg
1147 ms
async-ads.js
60 ms
google_custom_search_watermark.gif
30 ms
small-logo.png
16 ms
search_box_icon.png
14 ms
clear.gif
16 ms
BNR_panoramaX_1400_314.png
1088 ms
BNR_MS-1X_1400_314.png
2263 ms
bnr_cloud_20150511.jpg
1400 ms
elmo.co.jp accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
elmo.co.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
elmo.co.jp SEO score
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
Document doesn't use legible font sizes
Tap targets are not sized appropriately
JA
N/A
SHIFT_JIS
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 neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Elmo.co.jp main page’s claimed encoding is shift_jis. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
elmo.co.jp
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: