4.6 sec in total
869 ms
3.6 sec
172 ms
Click here to check amazing EIDAI content for Japan. Otherwise, check out these important facts you probably never knew about eidai.com
新築からリフォームまで、住宅の内装のことなら永大産業株式会社へ。フローリング、室内ドア、収納、システムキッチン、洗面化粧台、システムバスなど様々な製品を取り扱っております。
Visit eidai.comWe analyzed Eidai.com page load time and found that the first response time was 869 ms and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
eidai.com performance score
name
value
score
weighting
Value8.1 s
0/100
10%
Value19.4 s
0/100
25%
Value13.0 s
2/100
10%
Value380 ms
70/100
30%
Value0.142
78/100
15%
Value13.4 s
11/100
10%
869 ms
323 ms
672 ms
503 ms
700 ms
Our browser made a total of 80 requests to load all elements on the main page. We found that 98% of them (78 requests) were addressed to the original Eidai.com, 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Eidai.com.
Page size can be reduced by 171.6 kB (23%)
751.7 kB
580.1 kB
In fact, the total size of Eidai.com main page is 751.7 kB. 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 589.3 kB which makes up the majority of the site volume.
Potential reduce by 14.1 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 2.9 kB, which is 15% 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 14.1 kB or 75% of the original size.
Potential reduce by 39.4 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. EIDAI images are well optimized though.
Potential reduce by 22.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 22.1 kB or 63% of the original size.
Potential reduce by 96.0 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. Eidai.com needs all CSS files to be minified and compressed as it can save up to 96.0 kB or 89% of the original size.
Number of requests can be reduced by 30 (39%)
77
47
The browser has sent 77 CSS, Javascripts, AJAX and image requests in order to completely render the main page of EIDAI. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for CSS and as a result speed up the page load time.
eidai.com
869 ms
import.css
323 ms
common.js
672 ms
top.css
503 ms
index.css
700 ms
swfobject.js
549 ms
sidearea.css
162 ms
common.css
173 ms
header.css
478 ms
header_new.css
340 ms
footer.css
512 ms
text.css
409 ms
winie6.css
506 ms
winie7.css
515 ms
landing.css
550 ms
urchin.js
23 ms
seach_icon_02.gif
518 ms
eidai_logo.jpg
674 ms
bg_body.jpg
169 ms
bodyline.gif
170 ms
topspbanner_27.gif
185 ms
topspbanner_28.jpg
177 ms
topspbanner_26.jpg
669 ms
topspbanner_17.jpg
162 ms
topspbanner_30.jpg
320 ms
topspbanner_29.jpg
334 ms
bg_line_length.gif
337 ms
bg_line_bottom.gif
352 ms
h2_title_01.jpg
367 ms
icon_product_01.jpg
480 ms
icon_product_05.jpg
501 ms
icon_product_03.jpg
504 ms
icon_product_06.jpg
525 ms
icon_product_04.jpg
550 ms
h2_title_02.jpg
639 ms
icon_company_01.jpg
668 ms
icon_company_02.jpg
672 ms
icon_company_03.jpg
700 ms
icon_company_04.jpg
733 ms
h2_title_03.jpg
798 ms
icon_building_01.jpg
1334 ms
icon_building_02.jpg
834 ms
icon_building_03.jpg
840 ms
icon_building_04.jpg
875 ms
icon_building_05.jpg
916 ms
h2_title_04.jpg
956 ms
icon_support_01.jpg
1000 ms
icon_support_02.jpg
1009 ms
icon_support_03.jpg
1049 ms
icon_support_04.jpg
1098 ms
icon_support_05.jpg
1115 ms
line_center.gif
1167 ms
h2_title_short.jpg
1175 ms
__utm.gif
11 ms
title_update.jpg
1193 ms
rss.jpg
1127 ms
line_01.gif
1115 ms
ic_01.gif
1171 ms
h2_title_long.jpg
1174 ms
title_new_info.jpg
1222 ms
list.gif
1121 ms
title_info.jpg
1137 ms
fl_alt2.jpg
1170 ms
fl_alt_download.jpg
1156 ms
safecareplusbanner.jpg
1151 ms
link_sitemap_02.gif
1101 ms
linl_seach_02.gif
1101 ms
g_menu2.jpg
1332 ms
scd_menubase.gif
1145 ms
footer_navul.gif
1123 ms
footer_navli.gif
1046 ms
footer_comnavli.gif
1089 ms
link_parties.gif
1091 ms
link_contacts.gif
1165 ms
link_faq.gif
1139 ms
link_sitemap.gif
1120 ms
foot_yaji.gif
1131 ms
index.html
161 ms
index.html
161 ms
print.css
170 ms
eidai.com accessibility score
ARIA
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.
Impact
Issue
[aria-*] attributes do not match their roles
[aria-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
ARIA toggle fields do not have accessible names
[aria-*] attributes do not have valid values
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
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>).
eidai.com 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
Page has valid source maps
eidai.com 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
Tap targets are not sized appropriately
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Eidai.com 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 Eidai.com 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.
eidai.com
Open Graph description is not detected on the main page of EIDAI. 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: