4.8 sec in total
938 ms
3.6 sec
215 ms
Welcome to waters.com.ph homepage info - get ready to check Waters best content for Philippines right away, or after learning these important things about waters.com.ph
rain or shine Your water refilling station in the comfort of your home No more extra storage space for big bottles No more acidic water from water refill station No more lifetime water expense rain or...
Visit waters.com.phWe analyzed Waters.com.ph page load time and found that the first response time was 938 ms and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
waters.com.ph performance score
name
value
score
weighting
Value5.8 s
4/100
10%
Value12.2 s
0/100
25%
Value8.9 s
15/100
10%
Value1,760 ms
10/100
30%
Value0.38
27/100
15%
Value21.1 s
1/100
10%
938 ms
15 ms
29 ms
29 ms
31 ms
Our browser made a total of 91 requests to load all elements on the main page. We found that 29% of them (26 requests) were addressed to the original Waters.com.ph, 31% (28 requests) were made to Scontent.xx.fbcdn.net and 22% (20 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Scontent.xx.fbcdn.net.
Page size can be reduced by 449.9 kB (16%)
2.9 MB
2.4 MB
In fact, the total size of Waters.com.ph main page is 2.9 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. 60% of websites need less resources to load. Images take 2.3 MB which makes up the majority of the site volume.
Potential reduce by 18.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 18.5 kB or 75% of the original size.
Potential reduce by 70.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. Waters images are well optimized though.
Potential reduce by 150.1 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 150.1 kB or 62% of the original size.
Potential reduce by 211.0 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. Waters.com.ph needs all CSS files to be minified and compressed as it can save up to 211.0 kB or 83% of the original size.
Number of requests can be reduced by 35 (40%)
88
53
The browser has sent 88 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Waters. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
waters.com.ph
938 ms
swfobject.js
15 ms
styles.css
29 ms
js-image-slider.css
29 ms
js-image-slider.js
31 ms
sdk.js
197 ms
UDpeAoxNXv8
83 ms
1uaw1fc1DtU
192 ms
cbrd9mvJClM
210 ms
counter.js
20 ms
bg.jpg
29 ms
img_top.jpg
52 ms
img_bg_content.jpg
28 ms
img-bg-home.jpg
27 ms
loading.gif
42 ms
1.png
186 ms
2.png
233 ms
3.png
188 ms
4.png
186 ms
5.png
188 ms
6.png
163 ms
7.png
232 ms
8.png
230 ms
img_middle.jpg
186 ms
massager.png
229 ms
bmp.png
229 ms
noah.png
229 ms
noah-series.png
238 ms
kythe.png
313 ms
mansmith.png
238 ms
img_footer.jpg
238 ms
t.php
142 ms
www-embed-player-vflfNyN_r.css
29 ms
www-embed-player.js
58 ms
fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js
81 ms
ad_status.js
114 ms
QHD8zigcbDB8aPfIoaupKOvvDin1pK8aKteLpeZ5c0A.ttf
126 ms
RxZJdnzeo3R5zSexge8UUSZ2oysoEQEeKwjgmXLRnTc.ttf
128 ms
112 ms
xd_arbiter.php
179 ms
xd_arbiter.php
288 ms
page.php
480 ms
LUdypCgtRlc.css
179 ms
46icGyCHNkx.css
222 ms
Hy2B8ciSPhU.css
263 ms
7UFpPvIym7D.css
303 ms
q68gy-v_YMF.js
381 ms
YvxwM8R7ol8.js
404 ms
ihptErjAmMX.js
341 ms
3So47A9WcrL.js
304 ms
1BQnIVjTFoC.js
422 ms
CZfzbakm8cM.js
433 ms
cUsKAwzqrQw.js
433 ms
12541126_705475322885282_3773983016772939071_n.jpg
252 ms
safe_image.php
268 ms
12670058_711338125632335_7313518897750009669_n.jpg
313 ms
12227138_463223377210739_6166433960650362072_n.jpg
400 ms
12814388_1708630786079835_4794069787752062902_n.jpg
359 ms
12654484_1001938743219146_4319960310687318246_n.jpg
358 ms
12814775_10207523282097744_6148509366302017502_n.jpg
359 ms
9471_1035125603169435_3642769537296248750_n.jpg
507 ms
12821580_1720480341497160_593974121306477162_n.jpg
405 ms
12524265_1074259649293389_4408572337080025750_n.jpg
553 ms
12523107_1551151538544459_7661184277596120528_n.jpg
458 ms
12654207_1652182101722545_6698911209005834821_n.jpg
401 ms
11703055_829803313807761_2767157448479414317_n.jpg
487 ms
1510596_1251852854843718_133906504951440361_n.jpg
488 ms
12742780_1029975547059547_6123532502517340462_n.jpg
445 ms
1915675_135857976807107_4926108609296555646_n.jpg
487 ms
3121_74080953345_2681318_n.jpg
504 ms
1016_728331037266377_2162619558063292553_n.jpg
596 ms
12804752_728331040599710_7988821806809576417_n.jpg
566 ms
12806249_728330900599724_9126694819423450971_n.jpg
560 ms
12809518_728330993933048_7796078418185560929_n.jpg
545 ms
10850131_727960420636772_8522498528565282056_n.jpg
620 ms
12795400_727960413970106_5187812812371223741_n.jpg
616 ms
12795356_727960417303439_7027632387913896888_n.jpg
623 ms
12814666_727960633970084_3534944584998087605_n.jpg
601 ms
12803029_727511814014966_7271219172971122577_n.jpg
677 ms
942282_727511810681633_8219552010649256712_n.jpg
636 ms
12804674_727511804014967_8913323336713069946_n.jpg
1262 ms
12794535_726771000755714_6872430572745185468_n.jpg
778 ms
wL6VQj7Ab77.png
105 ms
s7jcwEQH7Sx.png
107 ms
GtIpNnEyqq_.png
107 ms
lRyN50VcaFW.js
40 ms
6GqoI2ZyIrf.png
42 ms
R9a_DtVRZgv.js
43 ms
cUDgRFxaoIk.js
42 ms
0JBr1QHp8Gi.js
43 ms
kDOzhTr2W91.js
45 ms
waters.com.ph accessibility score
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
Buttons do not have an accessible name
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
waters.com.ph 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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
waters.com.ph SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Waters.com.ph can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Waters.com.ph 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.
waters.com.ph
Open Graph description is not detected on the main page of Waters. 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: