4.8 sec in total
572 ms
4.1 sec
161 ms
Click here to check amazing NANODAX content. Otherwise, check out these important facts you probably never knew about nanodax.jp
ナノダックス株式会社【nanodax】は世界初めてグラスウール(ガラス短繊維)を樹脂の高機能化フィラープラとして開発を行い製品化しています。環境性に優れた樹脂洗浄剤(パージ剤)・ナイロン製の釣糸など多くの製品を世界販売しています。
Visit nanodax.jpWe analyzed Nanodax.jp page load time and found that the first response time was 572 ms and then it took 4.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
nanodax.jp performance score
name
value
score
weighting
Value0.9 s
100/100
10%
Value0.9 s
100/100
25%
Value1.9 s
100/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value0.9 s
100/100
10%
572 ms
192 ms
344 ms
344 ms
356 ms
Our browser made a total of 103 requests to load all elements on the main page. We found that all of those requests were addressed to Nanodax.jp and no external sources were called. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Nanodax.jp.
Page size can be reduced by 42.1 kB (17%)
242.5 kB
200.4 kB
In fact, the total size of Nanodax.jp main page is 242.5 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. 35% of websites need less resources to load. Images take 203.1 kB which makes up the majority of the site volume.
Potential reduce by 30.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. 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 30.1 kB or 76% of the original size.
Potential reduce by 12.0 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. NANODAX images are well optimized though.
We found no issues to fix!
102
102
The browser has sent 102 CSS, Javascripts, AJAX and image requests in order to completely render the main page of NANODAX. According to our analytics all requests are already optimized.
nanodax.jp
572 ms
tenjikai_1.gif
192 ms
tenjikai_11.gif
344 ms
sinpo.gif
344 ms
sinpo1.gif
356 ms
next.gif
374 ms
next2.gif
385 ms
next_b.gif
381 ms
next_b2.gif
517 ms
g_mag1.gif
517 ms
g_mag11.gif
534 ms
banner20.gif
564 ms
banner201.gif
570 ms
banner18.gif
580 ms
banner181.gif
690 ms
proseleset160.gif
690 ms
proseleset1601.gif
713 ms
%E4%B8%96%E7%95%8C1.gif
938 ms
%E4%B8%96%E7%95%8C11.gif
762 ms
ronbun1.gif
774 ms
ronbun11.gif
862 ms
b_2.jpg
864 ms
b_22.jpg
890 ms
yano6.gif
952 ms
yano62.gif
970 ms
b_5.jpg
1035 ms
b_51.jpg
1041 ms
b_6.jpg
1069 ms
b_61.jpg
1124 ms
b_8.jpg
1141 ms
b_81.jpg
1163 ms
kiji_1.gif
1208 ms
kiji_11.gif
1213 ms
kouen.gif
1250 ms
kouen1.gif
1313 ms
catalgu.gif
1332 ms
catalgu2.gif
1358 ms
U_1.gif
1194 ms
U_11.gif
1046 ms
14.gif
1087 ms
141.gif
1151 ms
hibrid_b.gif
1153 ms
hibrid_b3.gif
1175 ms
yonex.jpg
1179 ms
yonex1.jpg
1215 ms
nanodax2.gif
1094 ms
nanodax22.gif
1160 ms
yumepuro.jpg
1153 ms
yumepuro2.jpg
1187 ms
sahashi_baner.jpg
1159 ms
sahashi_baner2.jpg
1274 ms
tokyo1.jpg
1192 ms
tokyo12.jpg
1192 ms
biclife1.jpg
1143 ms
biclife11.jpg
1136 ms
ipros.gif
1087 ms
ipros1.gif
1208 ms
yonex_1.gif
1204 ms
yonex_14.gif
1142 ms
hotfrog.gif
1131 ms
hotfrog1.gif
1174 ms
googl_1.gif
1107 ms
googl_13.gif
1220 ms
innovation.gif
1185 ms
innovation3.gif
1131 ms
yahoo_1.gif
1141 ms
yahoo_13.gif
1159 ms
amazon3D.gif
1130 ms
amazon3D3.gif
1212 ms
engineer.gif
1178 ms
engineer3.gif
1135 ms
rakuten.gif
1141 ms
rakuten3.gif
1143 ms
Zdnet.gif
1151 ms
Zdnet3.gif
1213 ms
seihinnabni.gif
1173 ms
seihinnabni3.gif
1135 ms
jtec.gif
1140 ms
jtec1.gif
1130 ms
youTube.gif
1166 ms
youTube1.gif
1164 ms
moukaru_2.gif
1088 ms
moukaru_21.gif
1116 ms
moukaru_3.gif
1126 ms
moukaru_31.gif
1127 ms
ecomaru_b1.jpg
1168 ms
ecomaru_b11.jpg
1073 ms
ecomaru_b2.gif
1052 ms
ecomaru_b21.gif
1115 ms
home.gif
1137 ms
home2.gif
1097 ms
b_9.jpg
1153 ms
b_91.jpg
1059 ms
jidousya.gif
1051 ms
jidousya2.gif
1125 ms
marcheur02.gif
1135 ms
creative1.jpg
1286 ms
anim.gif
1357 ms
b1.gif
1049 ms
company_annai.gif
1048 ms
line21.gif
1140 ms
image17.gif
1124 ms
44.gif
1159 ms
nanodax.jp accessibility score
nanodax.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
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
Browser errors were logged to the console
nanodax.jp SEO score
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nanodax.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 Nanodax.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.
nanodax.jp
Open Graph description is not detected on the main page of NANODAX. 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: