6.8 sec in total
1.2 sec
5.4 sec
177 ms
Click here to check amazing Epco content for Japan. Otherwise, check out these important facts you probably never knew about epco.co.jp
株式会社 エプコの公式ホームページです。エプコのサービスや様々な取り組みの情報をお届けいたします。
Visit epco.co.jpWe analyzed Epco.co.jp page load time and found that the first response time was 1.2 sec and then it took 5.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
epco.co.jp performance score
name
value
score
weighting
Value9.8 s
0/100
10%
Value25.4 s
0/100
25%
Value21.5 s
0/100
10%
Value520 ms
56/100
30%
Value0.005
100/100
15%
Value25.7 s
0/100
10%
1207 ms
1331 ms
1534 ms
1784 ms
1381 ms
Our browser made a total of 53 requests to load all elements on the main page. We found that 89% of them (47 requests) were addressed to the original Epco.co.jp, 4% (2 requests) were made to Apis.google.com and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Epco.co.jp.
Page size can be reduced by 150.1 kB (9%)
1.7 MB
1.6 MB
In fact, the total size of Epco.co.jp main page is 1.7 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. 25% of websites need less resources to load. Images take 1.6 MB which makes up the majority of the site volume.
Potential reduce by 13.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 4.6 kB, which is 26% 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 13.9 kB or 79% of the original size.
Potential reduce by 30.6 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. Epco images are well optimized though.
Potential reduce by 70.1 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 70.1 kB or 53% of the original size.
Potential reduce by 35.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. Epco.co.jp needs all CSS files to be minified and compressed as it can save up to 35.5 kB or 83% of the original size.
Number of requests can be reduced by 17 (33%)
51
34
The browser has sent 51 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Epco. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
epco.co.jp
1207 ms
reset.css
1331 ms
base.css
1534 ms
layout.css
1784 ms
index.css
1381 ms
jsapi
27 ms
plusone.js
93 ms
jquery.colorbox.js
1914 ms
jquery.easing.1.3.js
563 ms
system.js
754 ms
index.js
946 ms
colorbox.css
1136 ms
jquery.min.js
31 ms
cb=gapi.loaded_0
16 ms
bg_animation.gif
384 ms
animation_dummy.jpg
982 ms
animation_1_img_1.jpg
1316 ms
animation_1_text_1.png
387 ms
animation_1_img_2.jpg
1375 ms
animation_1_img_3.jpg
2619 ms
animation_1_text_2.png
574 ms
animation_1_text_3.png
579 ms
animation_1_text_4.png
1145 ms
animation_1_text_5.png
772 ms
animation_1_text_6.png
966 ms
animation_1_text_7.png
1161 ms
animation_1_text_8.png
1178 ms
animation_2_img_1.jpg
1720 ms
animation_2_text_1.png
1353 ms
animation_2_img_2.jpg
1768 ms
animation_2_img_3.jpg
1678 ms
animation_2_text_2.png
1546 ms
animation_2_text_3.png
1571 ms
animation_2_text_4.png
1932 ms
animation_2_text_5.png
1768 ms
animation_2_text_6.png
1861 ms
animation_2_text_7.png
1910 ms
animation_2_text_8.png
1964 ms
bg_anavi.png
1965 ms
bg_anavi_off.png
2043 ms
anavi_1.png
2102 ms
anavi_2.png
2123 ms
anavi_3.png
2160 ms
anavi_4.png
2162 ms
anavi_5.png
2225 ms
anavi_6.png
2292 ms
index_arw.gif
2316 ms
index_bnr3.jpg
2357 ms
index_bnr4.jpg
2359 ms
analytics.js
19 ms
border.gif
2368 ms
collect
26 ms
controls.gif
2108 ms
epco.co.jp accessibility score
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
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>).
epco.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
Missing source maps for large first-party JavaScript
epco.co.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
JA
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Epco.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 Epco.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.
epco.co.jp
Open Graph description is not detected on the main page of Epco. 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: