7.3 sec in total
558 ms
6.4 sec
333 ms
Click here to check amazing Dry Cabi content for Japan. Otherwise, check out these important facts you probably never knew about dry-cabi.co.jp
防湿庫業界の革新を牽引するトーリ・ハンのオフィシャルウェブサイト。防湿庫「ドライ・キャビ」・加湿庫「ウエット・キャビ」の製品案内、ご利用者様の声、納入先一覧などを掲載。
Visit dry-cabi.co.jpWe analyzed Dry-cabi.co.jp page load time and found that the first response time was 558 ms and then it took 6.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
dry-cabi.co.jp performance score
name
value
score
weighting
Value5.6 s
5/100
10%
Value9.0 s
1/100
25%
Value9.2 s
13/100
10%
Value1,090 ms
24/100
30%
Value0.022
100/100
15%
Value11.6 s
18/100
10%
558 ms
995 ms
336 ms
354 ms
691 ms
Our browser made a total of 122 requests to load all elements on the main page. We found that 79% of them (96 requests) were addressed to the original Dry-cabi.co.jp, 6% (7 requests) were made to Translate.googleapis.com and 3% (4 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Dry-cabi.co.jp.
Page size can be reduced by 253.1 kB (12%)
2.2 MB
1.9 MB
In fact, the total size of Dry-cabi.co.jp main page is 2.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. 45% of websites need less resources to load. Images take 1.9 MB which makes up the majority of the site volume.
Potential reduce by 18.3 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 18.3 kB or 72% of the original size.
Potential reduce by 110.3 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. Dry Cabi images are well optimized though.
Potential reduce by 63.2 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 63.2 kB or 30% of the original size.
Potential reduce by 61.2 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. Dry-cabi.co.jp needs all CSS files to be minified and compressed as it can save up to 61.2 kB or 81% of the original size.
Number of requests can be reduced by 35 (29%)
119
84
The browser has sent 119 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Dry Cabi. 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 13 to 1 for CSS and as a result speed up the page load time.
dry-cabi.co.jp
558 ms
www.dry-cabi.co.jp
995 ms
import.css
336 ms
top.css
354 ms
jquery.js
691 ms
rollover.min.js
357 ms
tiny.css
389 ms
element.js
34 ms
bookmark_button.js
400 ms
reset.css
206 ms
base.css
171 ms
category.css
214 ms
common.css
379 ms
fvn.css
249 ms
gallery.css
340 ms
add.css
400 ms
analytics.js
17 ms
button-only@2x.png
204 ms
header_logo_001.gif
213 ms
header_btn_001_off.gif
204 ms
english.png
202 ms
chinese.png
201 ms
no1.png
205 ms
gnav_img_001_off.gif
200 ms
gnav_img_002_off.gif
347 ms
gnav_img_003_off.gif
375 ms
gnav_img_004_off.gif
375 ms
gnav_img_005_off.gif
388 ms
gnav_img_007_off.gif
402 ms
key_txt_001.jpg
600 ms
key_txt_002.jpg
1098 ms
key_btn_001_off.jpg
1174 ms
key_btn_001-1_off.gif
569 ms
key_btn_002_off.jpg
1088 ms
index_h3_002.gif
623 ms
index_txt_001.jpg
922 ms
button_01_off.jpg
999 ms
index_txt_002.jpg
2544 ms
index_txt_006.gif
1112 ms
index_btn_001_off.jpg
1220 ms
index_btn_002_off.jpg
1281 ms
index_btn_003_off.jpg
1280 ms
fmail_bn_off.gif
1286 ms
gb_ba_off.jpg
1345 ms
glovebox2_b_off.jpg
1394 ms
b_center_off.jpg
1587 ms
food_off.jpg
1579 ms
campaign_ba_off.gif
1460 ms
side_btn_002_off.gif
1541 ms
snav_img_001.gif
1600 ms
side_txt_001_off.gif
1650 ms
side_txt_002.gif
1714 ms
side_txt_003.gif
1762 ms
translateelement.css
94 ms
main.js
99 ms
side_txt_002_off.jpg
1904 ms
collect
16 ms
205 ms
ga.js
4 ms
dry-cabi_co_jp
523 ms
__utm.gif
14 ms
element_main.js
40 ms
like.php
163 ms
banner_face.jpg
1602 ms
snav_img_002_off.gif
1638 ms
snav_img_003_off.gif
1701 ms
side_btn_003_off.jpg
1747 ms
wrap01_bg_001.gif
1820 ms
header_bg_001.gif
1823 ms
reset.css
13 ms
entry-button.css
13 ms
qeKvIRsJabD.js
488 ms
LVx-xkvaJ0b.png
554 ms
bbtn-l_v3.png
2 ms
header_bg_002.gif
1740 ms
key_bg_001.jpg
2502 ms
index_h3_001_2.gif
1764 ms
index_bg_001.gif
1855 ms
bgf1.gif
1810 ms
index_txt_004.jpg
2019 ms
index_txt_003.jpg
2264 ms
index_txt_005.jpg
2479 ms
sessionError.html
328 ms
index_mark_001.gif
1517 ms
index_mark_002.gif
1639 ms
side_bg_001.gif
1651 ms
side_ico_002.gif
1663 ms
side_line_001.gif
1723 ms
footer_bg_001.gif
1757 ms
translate_24dp.png
27 ms
l
39 ms
cleardot.gif
64 ms
googlelogo_color_68x28dp.png
6 ms
te_ctrl3.gif
11 ms
loading.gif
20 ms
te_bk.gif
11 ms
header_btn_001_on.gif
217 ms
gnav_img_001_on.gif
185 ms
gnav_img_002_on.gif
177 ms
gnav_img_003_on.gif
186 ms
gnav_img_004_on.gif
203 ms
gnav_img_005_on.gif
336 ms
gnav_img_007_on.gif
361 ms
key_btn_001_on.jpg
661 ms
key_btn_001-1_on.gif
375 ms
key_btn_002_on.jpg
960 ms
button_01_on.jpg
604 ms
index_btn_001_on.jpg
500 ms
index_btn_002_on.jpg
532 ms
index_btn_003_on.jpg
550 ms
fmail_bn_on.gif
670 ms
gb_ba_on.jpg
703 ms
glovebox2_b_on.jpg
728 ms
b_center_on.jpg
994 ms
food_on.jpg
840 ms
campaign_ba_on.gif
835 ms
side_btn_002_on.gif
899 ms
side_txt_001_on.gif
918 ms
side_txt_002_on.jpg
1159 ms
snav_img_002_on.gif
1032 ms
snav_img_003_on.gif
1083 ms
side_btn_003_on.jpg
1215 ms
dry-cabi.co.jp accessibility score
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
<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
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
dry-cabi.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
dry-cabi.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
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dry-cabi.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 Dry-cabi.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.
dry-cabi.co.jp
Open Graph description is not detected on the main page of Dry Cabi. 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: