9.7 sec in total
2.1 sec
6.8 sec
728 ms
Visit water-server.jp now to see the best up-to-date Water Server content for Japan and also check out these interesting facts you probably never knew about water-server.jp
<2022年度>ウォーターサーバーの人気30社を徹底比較!業界歴10年以上の管理者が、本当にお徳なウォーターサーバー選びを独自の視点から徹底サポートいたします。の本当の実力をプロが徹底検証。使ってみてよい点、気になる点をまとめました! 実際に使ってみないとわからない本当の実力を比較して、あなたのオススメの1台をご紹介します!
Visit water-server.jpWe analyzed Water-server.jp page load time and found that the first response time was 2.1 sec and then it took 7.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
water-server.jp performance score
name
value
score
weighting
Value5.4 s
7/100
10%
Value6.7 s
8/100
25%
Value10.0 s
9/100
10%
Value110 ms
97/100
30%
Value0.291
41/100
15%
Value11.0 s
21/100
10%
2119 ms
344 ms
1048 ms
353 ms
358 ms
Our browser made a total of 65 requests to load all elements on the main page. We found that 94% of them (61 requests) were addressed to the original Water-server.jp, 3% (2 requests) were made to Google-analytics.com and 3% (2 requests) were made to Cdn.clicktale.net. The less responsive or slowest element that took the longest time to load (3.7 sec) belongs to the original domain Water-server.jp.
Page size can be reduced by 531.3 kB (27%)
2.0 MB
1.5 MB
In fact, the total size of Water-server.jp main page is 2.0 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.7 MB which makes up the majority of the site volume.
Potential reduce by 45.5 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 45.5 kB or 81% of the original size.
Potential reduce by 333.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. Obviously, Water Server needs image optimization as it can save up to 333.9 kB or 20% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 124.6 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 124.6 kB or 64% of the original size.
Potential reduce by 27.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. Water-server.jp needs all CSS files to be minified and compressed as it can save up to 27.4 kB or 81% of the original size.
Number of requests can be reduced by 19 (30%)
64
45
The browser has sent 64 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Water Server. 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 from 6 to 1 for CSS and as a result speed up the page load time.
water-server.jp
2119 ms
style.css
344 ms
jquery.js
1048 ms
roll_over.js
353 ms
pagelink.js
358 ms
pagenavi-css.css
363 ms
base.css
173 ms
layout.css
360 ms
page.css
543 ms
hack.css
200 ms
logo.gif
204 ms
hbtn.jpg
200 ms
gnav1_off.png
201 ms
gnav2_off.png
202 ms
gnav3_off.png
201 ms
gnav4_off.png
173 ms
gnav5_off.png
345 ms
main.jpg
874 ms
sindan_ttl.png
1056 ms
check.png
355 ms
ch1.gif
365 ms
ch2.gif
387 ms
ch3.gif
515 ms
ch4.gif
531 ms
ch5.gif
553 ms
ch6.gif
580 ms
btn_kensaku2.png
686 ms
ttl1.jpg
708 ms
sample1.jpg
734 ms
more_btn.jpg
773 ms
onewaywater_logo.jpg
855 ms
clytia_logo.jpg
884 ms
crecla_logo.jpg
912 ms
frecious_logo.jpg
969 ms
aquaclara_logo.jpg
1022 ms
alpina_logo.jpg
1042 ms
urunon_logo.jpg
1056 ms
hawaiiwater_logo.jpg
1093 ms
suntory_logo.jpg
1162 ms
ranking_btn.jpg
1533 ms
pageup.gif
1216 ms
ttl2.jpg
1222 ms
kiji114.jpg
1233 ms
kiji_list_01.jpg
1273 ms
kiji_list_02.jpg
1354 ms
kiji_list_03.jpg
1365 ms
analytics.js
5 ms
3fe9d527-94ab-4b7d-9c3f-ab86e40e0b8e.js
26 ms
collect
37 ms
WRf4.js
3 ms
kiji_list_04.jpg
1237 ms
kiji_list_05.jpg
1221 ms
ttl3.gif
1266 ms
srank.png
1360 ms
sttl1.png
1375 ms
sttl2.png
1383 ms
sttl3.png
1254 ms
flogo.png
1294 ms
header_bg.gif
1350 ms
main_bg.jpg
1366 ms
sindan_bg.png
3683 ms
sindan_bg2.png
1230 ms
icon1.gif
1222 ms
arrow1.gif
1249 ms
footer_bg.jpg
1199 ms
water-server.jp 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-hidden="true"] elements contain focusable descendents
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
No form fields have multiple labels
Image elements do not have [alt] attributes
Form elements do not have associated labels
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
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.
water-server.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
water-server.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
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 Water-server.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 Water-server.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.
water-server.jp
Open Graph data is detected on the main page of Water Server. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: