Tools & Wizards About Us
hydrocare.com.ph screenshot

Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

hydrocare.com.ph

Water Refilling Station Equipment | HYDROCARE System Technology

Page Load Speed

9.6 sec in total

First Response

954 ms

Resources Loaded

7.9 sec

Page Rendered

758 ms

hydrocare.com.ph screenshot

About Website

Visit hydrocare.com.ph now to see the best up-to-date HYDROCARE content and also check out these interesting facts you probably never knew about hydrocare.com.ph

The Best Supplier of Machines & Equipment for Purified, Alkaline, Mineral Water Refilling Stations in the Philippines - Water Refilling Station Equipment

Visit hydrocare.com.ph

Key Findings

We analyzed Hydrocare.com.ph page load time and found that the first response time was 954 ms and then it took 8.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

hydrocare.com.ph performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.8 s

0/100

10%

LCP (Largest Contentful Paint)

Value21.3 s

0/100

25%

SI (Speed Index)

Value18.1 s

0/100

10%

TBT (Total Blocking Time)

Value1,590 ms

12/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value28.7 s

0/100

10%

Network Requests Diagram

www.hydrocare.com.ph

954 ms

wp-emoji-release.min.js

448 ms

style.min.css

499 ms

settings.css

505 ms

css

36 ms

Our browser made a total of 108 requests to load all elements on the main page. We found that 69% of them (75 requests) were addressed to the original Hydrocare.com.ph, 11% (12 requests) were made to Fonts.gstatic.com and 6% (7 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (2.8 sec) belongs to the original domain Hydrocare.com.ph.

Page Optimization Overview & Recommendations

Page size can be reduced by 154.7 kB (4%)

Content Size

4.4 MB

After Optimization

4.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Hydrocare.com.ph main page is 4.4 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. Only a small number of websites need less resources to load. Images take 3.4 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 102.5 kB

  • Original 120.9 kB
  • After minification 118.5 kB
  • After compression 18.4 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 102.5 kB or 85% of the original size.

Image Optimization

-0%

Potential reduce by 1.3 kB

  • Original 3.4 MB
  • After minification 3.4 MB

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. HYDROCARE images are well optimized though.

JavaScript Optimization

-7%

Potential reduce by 31.3 kB

  • Original 449.4 kB
  • After minification 449.4 kB
  • After compression 418.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. This website has mostly compressed JavaScripts.

CSS Optimization

-5%

Potential reduce by 19.6 kB

  • Original 434.1 kB
  • After minification 434.0 kB
  • After compression 414.5 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. Hydrocare.com.ph has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 59 (71%)

Requests Now

83

After Optimization

24

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 83 CSS, Javascripts, AJAX and image requests in order to completely render the main page of HYDROCARE. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 32 to 1 for JavaScripts and from 29 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

www.hydrocare.com.ph

www.hydrocare.com.ph

954 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

448 ms

style.min.css

style.min.css

499 ms

settings.css

settings.css

505 ms

css

css

36 ms

css

css

25 ms

css

css

23 ms

fontello.css

fontello.css

592 ms

elementor-icons.min.css

elementor-icons.min.css

611 ms

animations.min.css

animations.min.css

687 ms

frontend-legacy.min.css

frontend-legacy.min.css

709 ms

frontend.min.css

frontend.min.css

743 ms

frontend.min.css

frontend.min.css

755 ms

stylesheet.css

stylesheet.css

887 ms

stylesheet.css

stylesheet.css

916 ms

css

css

20 ms

fontello-embedded.css

fontello-embedded.css

1641 ms

style.css

style.css

1178 ms

__styles.css

__styles.css

984 ms

__colors.css

__colors.css

1007 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

1188 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

1221 ms

responsive.css

responsive.css

1230 ms

css

css

36 ms

fontawesome.min.css

fontawesome.min.css

1261 ms

solid.min.css

solid.min.css

1414 ms

brands.min.css

brands.min.css

1479 ms

csshero-static-style-camelia.css

csshero-static-style-camelia.css

1527 ms

md5.js

md5.js

1474 ms

util.js

util.js

1511 ms

jquery.js

jquery.js

1660 ms

__inline.css

__inline.css

1563 ms

smush-lazy-load.min.js

smush-lazy-load.min.js

1598 ms

superfish.min.js

superfish.min.js

1583 ms

__scripts.js

__scripts.js

2110 ms

mediaelement-and-player.min.js

mediaelement-and-player.min.js

1693 ms

mediaelement-migrate.min.js

mediaelement-migrate.min.js

1721 ms

wp-mediaelement.min.js

wp-mediaelement.min.js

2105 ms

wp-embed.min.js

wp-embed.min.js

2106 ms

jquery.smartmenus.min.js

jquery.smartmenus.min.js

2108 ms

imagesloaded.min.js

imagesloaded.min.js

2107 ms

slick.min.js

slick.min.js

1864 ms

frontend-modules.min.js

frontend-modules.min.js

1885 ms

jquery.sticky.min.js

jquery.sticky.min.js

1874 ms

frontend.min.js

frontend.min.js

1903 ms

position.min.js

position.min.js

1825 ms

dialog.min.js

dialog.min.js

1805 ms

waypoints.min.js

waypoints.min.js

1881 ms

swiper.min.js

swiper.min.js

1996 ms

share-link.min.js

share-link.min.js

1967 ms

frontend.min.js

frontend.min.js

1952 ms

h9dmXrGN1x4

h9dmXrGN1x4

199 ms

HYDROCARE-NEW-LOGO-LANDSCAPE.png

HYDROCARE-NEW-LOGO-LANDSCAPE.png

1424 ms

SERVICES-HEADER_NEW.jpg

SERVICES-HEADER_NEW.jpg

1485 ms

2-1.jpg

2-1.jpg

1671 ms

LOBBY_new.jpg

LOBBY_new.jpg

1610 ms

IMG_8261.jpg

IMG_8261.jpg

1481 ms

IMG_7290.jpg

IMG_7290.jpg

1482 ms

3rd-cover.png

3rd-cover.png

2759 ms

REMS-MFG-RO.jpg

REMS-MFG-RO.jpg

1896 ms

REMS-MFG-PRE-TREATMENT.jpg

REMS-MFG-PRE-TREATMENT.jpg

1484 ms

REMS-MFG-TANKS.jpg

REMS-MFG-TANKS.jpg

1881 ms

REMS-MFG-PRE-TREATMENT-1.jpg

REMS-MFG-PRE-TREATMENT-1.jpg

1653 ms

FROSTMAN-ICE-PLANT-RO.jpg

FROSTMAN-ICE-PLANT-RO.jpg

2099 ms

FROSTMAN-ICE-PLANT-PRE-TREATMENT.jpg

FROSTMAN-ICE-PLANT-PRE-TREATMENT.jpg

1893 ms

COLD-DUST-ICE-PLANT-RO.jpg

COLD-DUST-ICE-PLANT-RO.jpg

2279 ms

FROSTMAN-CONTROL-PANEL.jpg

FROSTMAN-CONTROL-PANEL.jpg

2108 ms

COLD-DUST-ICE-PLANT-PRE-TREATMENT.jpg

COLD-DUST-ICE-PLANT-PRE-TREATMENT.jpg

2078 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

39 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aX8.ttf

40 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aX8.ttf

68 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf

93 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf

93 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

92 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw3aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw3aX8.ttf

20 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf

92 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aX8.ttf

92 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aX8.ttf

88 ms

gandhiserif-regular.woff

gandhiserif-regular.woff

2069 ms

gandhiserif-bold.woff

gandhiserif-bold.woff

2247 ms

fa-solid-900.woff

fa-solid-900.woff

2258 ms

www-player.css

www-player.css

6 ms

www-embed-player.js

www-embed-player.js

36 ms

base.js

base.js

101 ms

fa-brands-400.woff

fa-brands-400.woff

2189 ms

WATER-STATION.jpg

WATER-STATION.jpg

2195 ms

ad_status.js

ad_status.js

233 ms

0o2vSHmH6ApOX27UzDeaY_GD7faOtklBjWYygVKryhI.js

0o2vSHmH6ApOX27UzDeaY_GD7faOtklBjWYygVKryhI.js

198 ms

embed.js

embed.js

91 ms

IMG_7278.jpg

IMG_7278.jpg

2002 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

46 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

45 ms

id

id

33 ms

iframe_api

iframe_api

152 ms

Create

Create

133 ms

frontend-msie.min.css

frontend-msie.min.css

1533 ms

sdk.js

sdk.js

91 ms

www-widgetapi.js

www-widgetapi.js

64 ms

eicons.woff

eicons.woff

1100 ms

HKGrotesk-Bold.woff

HKGrotesk-Bold.woff

1157 ms

HKGrotesk-SemiBold.woff

HKGrotesk-SemiBold.woff

1178 ms

HKGrotesk-Medium.woff

HKGrotesk-Medium.woff

1340 ms

HKGrotesk-Regular.woff

HKGrotesk-Regular.woff

1364 ms

HKGrotesk-Light.woff

HKGrotesk-Light.woff

1409 ms

sdk.js

sdk.js

6 ms

GenerateIT

GenerateIT

19 ms

page.php

page.php

95 ms

page.php

page.php

56 ms

Accessibility Review

hydrocare.com.ph accessibility score

87

Accessibility Issues

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

High

[aria-hidden="true"] elements contain focusable descendents

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

High

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

hydrocare.com.ph best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

hydrocare.com.ph SEO score

89

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hydrocare.com.ph can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Hydrocare.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.

Social Sharing Optimization

hydrocare.com.ph

Open Graph data is detected on the main page of HYDROCARE. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: