12 sec in total
1.5 sec
10.2 sec
338 ms
Welcome to cosmowater.com homepage info - get ready to check Cosmowater best content for Japan right away, or after learning these important things about cosmowater.com
天然水ウォーターサーバーならコスモウォーター。ランニングコストNo.1!サーバーレンタル料0円、送料0円、初期費用0円、メンテナンス不要。今なら特典付き。
Visit cosmowater.comWe analyzed Cosmowater.com page load time and found that the first response time was 1.5 sec and then it took 10.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
cosmowater.com performance score
name
value
score
weighting
Value6.5 s
2/100
10%
Value13.2 s
0/100
25%
Value24.9 s
0/100
10%
Value4,390 ms
1/100
30%
Value0.631
9/100
15%
Value31.4 s
0/100
10%
1467 ms
1293 ms
429 ms
454 ms
880 ms
Our browser made a total of 167 requests to load all elements on the main page. We found that 44% of them (73 requests) were addressed to the original Cosmowater.com, 3% (5 requests) were made to B97.yahoo.co.jp and 2% (4 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (4.4 sec) belongs to the original domain Cosmowater.com.
Page size can be reduced by 821.9 kB (37%)
2.2 MB
1.4 MB
In fact, the total size of Cosmowater.com 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 988.6 kB which makes up the majority of the site volume.
Potential reduce by 192.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 192.3 kB or 78% of the original size.
Potential reduce by 30.9 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. Cosmowater images are well optimized though.
Potential reduce by 351.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 351.3 kB or 52% of the original size.
Potential reduce by 247.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. Cosmowater.com needs all CSS files to be minified and compressed as it can save up to 247.4 kB or 83% of the original size.
Number of requests can be reduced by 98 (64%)
154
56
The browser has sent 154 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cosmowater. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 54 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
cosmowater.com
1467 ms
www.cosmowater.com
1293 ms
default.css
429 ms
uniq.css
454 ms
jquery.js
880 ms
site.js
483 ms
css_browser_selector.js
505 ms
jquery.pikachoose.js
875 ms
ga.js
827 ms
adlpo.js
913 ms
slider001.css
918 ms
jquery.min.js
43 ms
slider001.js
951 ms
jquery.easing.1.3.js
1197 ms
getseal
132 ms
xrpt.js
905 ms
adv.js
28 ms
pixel.js
469 ms
dc.js
35 ms
__utm.gif
11 ms
event.php
75 ms
header_btn_member.png
195 ms
header_logo04.png
200 ms
header_txt_tel_03.png
319 ms
header_btn_tsuika02.png
652 ms
index_slide_bnr_15.png
993 ms
index_slide_bnr_14.png
1811 ms
index_slide_bnr_94.png
1200 ms
index_slide_bnr_norikae.png
1699 ms
index_slide_bnr_cp.png
1657 ms
topBigImg_btn.png
954 ms
index_waterServer_Title.png
1600 ms
index_waterServer_img01.jpg
1760 ms
index_waterServer_img02.jpg
1812 ms
index_waterServer_img03.jpg
2425 ms
index_waterServer_img04.jpg
2484 ms
index_h2_column_01.png
2082 ms
index_btn_column_01.png
2132 ms
img31_s.jpg
2461 ms
img30_s.jpg
2230 ms
index_h2_news.png
2409 ms
index_h2_proposal_01.png
2514 ms
nav_h2_in-new_02.png
2594 ms
nav_h2_in-new_03.jpg
3134 ms
nav_h2_in-new_04.png
2807 ms
nav_h2_in-new_07.png
2793 ms
nav_h2_in-new_05.png
2863 ms
nav_h2_in-use_01.png
2889 ms
nav_txt_in-use_01.png
2913 ms
nav_txt_in-use_02.png
3134 ms
nav_h2_tvcm_01.png
3210 ms
nav_h2_media_01.png
3181 ms
nav_h2_in-new_01.jpg
3529 ms
nav_h2_business_01.png
3269 ms
nav_txt_business_01.png
3464 ms
banner_fb.jpg
3513 ms
gtm.js
62 ms
nav_banner_04.png
3500 ms
c.js
515 ms
__utm.gif
12 ms
conversion_async.js
17 ms
36 ms
43 ms
fbx_nosync.php
37 ms
cp_01.jpg
3850 ms
cp_norikae.jpg
4021 ms
sam_cap.jpg
4445 ms
xGIiqCTmFsA
119 ms
getseal
59 ms
41e714cb-5681-459e-ac31-4e62cbd45df8.js
52 ms
WRf4.js
3 ms
tag.js
18 ms
b.gif
270 ms
dg_gateway.js
7 ms
adv_inner.js
3 ms
b.gif
412 ms
sam_credit.jpg
4007 ms
www-embed-player-vflZsBgOl.css
68 ms
www-embed-player.js
90 ms
base.js
156 ms
tag
15 ms
yrK4EqpSRdoujKQmsJoZ5WaLgeULvcWnibQMQSxOOnM.js
9 ms
ad_status.js
37 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
84 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
96 ms
header_bg_nav_01.png
3012 ms
pixel
151 ms
header_bg_nav_02.png
2981 ms
pixel
69 ms
Pug
64 ms
sync.ad-stir.com
459 ms
sync
60 ms
sync
458 ms
is
459 ms
adv.aspx
430 ms
adv.aspx
600 ms
r.js
98 ms
nendRt.js
56 ms
conversion.js
1189 ms
ld.js
29 ms
sd
16 ms
header_btn_nav_02_off.png
3076 ms
395 ms
event
21 ms
Pug
17 ms
sync
18 ms
tracker.js
71 ms
uiuqpz2z28.js
373 ms
event
497 ms
dgcore.js
11 ms
adSiteVisit.js
11 ms
xrost
150 ms
adfunnel
272 ms
header_btn_nav_04_off.png
2732 ms
tr_adv.ashx
162 ms
pix.js
527 ms
img
1070 ms
pta.js
513 ms
header_btn_nav_03_off.png
2747 ms
track
822 ms
header_btn_nav_05_off.png
2846 ms
header_btn_nav_07_off.png
2912 ms
tr_adv.ashx
174 ms
header_btn_nav_06_off.png
2871 ms
contents-head_bg_vi_01.png
3007 ms
pix-cosmo_life-min.js
13 ms
pix-test_ectg-min.js
26 ms
s_retargeting.js
360 ms
pixel
18 ms
topBigImg.jpg
3750 ms
60b46132.js
497 ms
icon.png
2854 ms
nav_bg_in-new_01.png
2819 ms
conversion.js
556 ms
nav_bg_in-use_01.png
2647 ms
nav_bg_tvcm_01.png
2711 ms
nav_bg_business_01.png
2762 ms
goToTop.png
2894 ms
footer_bg_tree_01.png
2865 ms
footer_bg_tree_02.png
2824 ms
pn
528 ms
contents_pointer03.png
2666 ms
contents_pointer04.png
2779 ms
510 ms
867 ms
901 ms
999 ms
conversion_async.js
33 ms
1020 ms
16 ms
21 ms
16 ms
19 ms
insight.min.js
303 ms
bl_track.js
354 ms
tag
7 ms
ya.js
353 ms
__li.gif
153 ms
bl_track.cgi
372 ms
webantenna.js
532 ms
pb.js
549 ms
335 ms
_webantenna.png
193 ms
oct.js
60 ms
adsct
95 ms
adsct
51 ms
dis.aspx
391 ms
cosmowater.com 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.
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
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
cosmowater.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
cosmowater.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Cosmowater.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 Cosmowater.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.
cosmowater.com
Open Graph description is not detected on the main page of Cosmowater. 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: