7.5 sec in total
728 ms
6.5 sec
285 ms
Click here to check amazing NANODAX content. Otherwise, check out these important facts you probably never knew about nanodax.jp
ナノダックス株式会社【nanodax】は世界初めてグラスウール繊維を樹脂の高機能化フィラープラとして製品化しています。環境性に優れた樹脂洗浄剤(パージ剤)・3Dプリンターフィラメントなど多くの製品を世界に供給しています。
Visit nanodax.jpWe analyzed Nanodax.jp page load time and found that the first response time was 728 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.
nanodax.jp performance score
name
value
score
weighting
Value1.9 s
86/100
10%
Value2.2 s
95/100
25%
Value5.5 s
54/100
10%
Value500 ms
58/100
30%
Value0
100/100
15%
Value10.8 s
22/100
10%
728 ms
148 ms
1626 ms
1627 ms
1629 ms
Our browser made a total of 180 requests to load all elements on the main page. We found that 92% of them (166 requests) were addressed to the original Nanodax.jp, 4% (7 requests) were made to Youtube.com and 1% (2 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Nanodax.jp.
Page size can be reduced by 395.1 kB (58%)
678.7 kB
283.6 kB
In fact, the total size of Nanodax.jp main page is 678.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. 55% of websites need less resources to load. CSS take 368.5 kB which makes up the majority of the site volume.
Potential reduce by 48.6 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 48.6 kB or 78% of the original size.
Potential reduce by 10.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. NANODAX images are well optimized though.
Potential reduce by 24.3 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 24.3 kB or 47% of the original size.
Potential reduce by 311.4 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. Nanodax.jp needs all CSS files to be minified and compressed as it can save up to 311.4 kB or 85% of the original size.
Number of requests can be reduced by 5 (3%)
177
172
The browser has sent 177 CSS, Javascripts, AJAX and image requests in order to completely render the main page of NANODAX. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and as a result speed up the page load time.
nanodax.jp
728 ms
DlUqh1tziwM
148 ms
tenjikai_1.gif
1626 ms
tenjikai_11.gif
1627 ms
sinpo.gif
1629 ms
sinpo1.gif
1622 ms
home.gif
1630 ms
home2.gif
1628 ms
next.gif
1630 ms
next2.gif
1631 ms
next_b.gif
1632 ms
next_b2.gif
1631 ms
143.gif
1634 ms
141.gif
1642 ms
g_mag1.gif
1643 ms
g_mag11.gif
1696 ms
banner20.gif
1698 ms
banner201.gif
1698 ms
banner18.gif
1701 ms
banner181.gif
1693 ms
banner17.gif
1692 ms
banner171.gif
1695 ms
ronbun1.gif
1694 ms
ronbun11.gif
1697 ms
yamagata_b.gif
1697 ms
yamagata_b4.gif
1698 ms
ronbun3.gif
1699 ms
ronbun31.gif
1701 ms
VIP1.gif
1701 ms
VIP12.gif
1702 ms
sahashi_1.gif
1703 ms
sahashi_11.gif
1703 ms
nss1.gif
1704 ms
nss11.gif
1706 ms
yasukawa_1.gif
1704 ms
yasukawa_14.gif
1709 ms
thisuu_1.gif
1707 ms
thisuu_11.gif
1644 ms
www-player.css
58 ms
www-embed-player.js
628 ms
base.js
788 ms
fetch-polyfill.js
22 ms
sahashi1.gif
429 ms
sahashi11.gif
429 ms
puro1.gif
426 ms
puro11.gif
424 ms
24.gif
422 ms
241.gif
421 ms
NSS_1.gif
558 ms
NSS_11.gif
561 ms
b_5.jpg
559 ms
b_51.jpg
558 ms
b_6.jpg
524 ms
b_61.jpg
545 ms
ad_status.js
388 ms
b_8.jpg
656 ms
b_81.jpg
693 ms
b_9.jpg
692 ms
b_91.jpg
694 ms
kiji_1.gif
691 ms
kiji_11.gif
693 ms
jidousya.gif
798 ms
jidousya2.gif
813 ms
kouen.gif
810 ms
kouen1.gif
815 ms
yumepuro.jpg
820 ms
yumepuro2.jpg
824 ms
ecomaru_b.gif
962 ms
ecomaru_b1.gif
976 ms
3D_p.gif
982 ms
3D_p1.gif
980 ms
biclife2.gif
991 ms
biclife21.gif
1014 ms
U_1.gif
1126 ms
U_11.gif
1146 ms
tokyo2.jpg
1147 ms
tokyo22.jpg
1160 ms
catalgu.gif
1162 ms
Y-zeT9jJ33tCNYTX0Kw8-3I-ogsAM9wZgys9W8554e8.js
381 ms
embed.js
146 ms
catalgu3.gif
910 ms
id
127 ms
ecomaru_b1.jpg
964 ms
ecomaru_b11.jpg
989 ms
ecomaru_b2.gif
992 ms
ecomaru_b21.gif
1004 ms
hibrid_b.gif
1012 ms
hibrid_b1.gif
1048 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
185 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
186 ms
3D_B.gif
997 ms
3D_B1.gif
1043 ms
yonex.jpg
1030 ms
yonex1.jpg
1208 ms
proseleset160.gif
1050 ms
Create
137 ms
proseleset1601.gif
1085 ms
npo_set200.gif
990 ms
npo_set2001.gif
1002 ms
sahashi_baner.jpg
1011 ms
sahashi_baner2.jpg
1201 ms
%E4%B8%96%E7%95%8C1.gif
1254 ms
%E4%B8%96%E7%95%8C11.gif
1308 ms
opera_1.gif
1066 ms
opera_11.gif
1059 ms
tokyo1.jpg
1061 ms
tokyo12.jpg
1217 ms
ikegai1.gif
1220 ms
ikegai11.gif
1224 ms
GenerateIT
17 ms
yamagata_a.gif
1111 ms
yamagata_a2.gif
1150 ms
rikadai_1.gif
1196 ms
rikadai_11.gif
1219 ms
yonex1.gif
1216 ms
yonex11.gif
1201 ms
ipros.gif
1109 ms
ipros1.gif
1155 ms
hotfrog.gif
1193 ms
hotfrog1.gif
1205 ms
aperza.gif
1211 ms
aperza3.gif
1195 ms
googl_1.gif
1117 ms
googl_13.gif
1163 ms
engineer.gif
1193 ms
engineer3.gif
1204 ms
Zdnet.gif
1206 ms
Zdnet3.gif
1182 ms
yahoo_1.gif
1127 ms
yahoo_13.gif
1168 ms
amazon3D.gif
1175 ms
amazon3D3.gif
1191 ms
covestoro.gif
1160 ms
covestoro3.gif
1076 ms
innovation.gif
1095 ms
innovation3.gif
1174 ms
china2018.gif
1172 ms
china20181.gif
1041 ms
rakuten.gif
1044 ms
rakuten3.gif
1049 ms
yonex_1.gif
1072 ms
yonex_14.gif
1108 ms
koshida1.gif
1030 ms
koshida11.gif
1041 ms
gaitassist1.gif
1045 ms
gaitassist11.gif
1076 ms
koshida.gif
1063 ms
koshida2.gif
1077 ms
NCI.gif
1053 ms
NCI1.gif
1045 ms
kisokogyu.gif
1043 ms
kisokogyu1.gif
1078 ms
woald.gif
1071 ms
woald1.gif
1068 ms
gaitassit.gif
1069 ms
gaitassit1.gif
1077 ms
tyuugai.gif
1045 ms
tyuugai1.gif
1072 ms
ist_opera.gif
1074 ms
ist_opera1.gif
1056 ms
moukaru_2.gif
1084 ms
moukaru_21.gif
1056 ms
moukaru_3.gif
1068 ms
moukaru_31.gif
1073 ms
b_2.jpg
1072 ms
b_22.jpg
1042 ms
log_event
21 ms
yano6.gif
1083 ms
yano62.gif
1066 ms
marcheur02.gif
1087 ms
creative1.jpg
1246 ms
anim.gif
1248 ms
a_btn048.gif
1025 ms
b1.gif
1087 ms
company_annai.gif
1078 ms
JST_1.gif
1088 ms
line21.gif
1142 ms
image17.gif
1170 ms
13.gif
1125 ms
44.gif
1117 ms
nanodax.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.
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
Page has valid source maps
nanodax.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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: