Tools & Wizards About Us
alivewater.com screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

alivewater.com

Alive Water® | Vortex Water Revitalizer Official Site

Page Load Speed

4.3 sec in total

First Response

212 ms

Resources Loaded

3.8 sec

Page Rendered

368 ms

alivewater.com screenshot

About Website

Welcome to alivewater.com homepage info - get ready to check Alive Water best content for United States right away, or after learning these important things about alivewater.com

Official home of the Alive Water® Vortex Water Revitalizer. Pioneering residential and industrial water revitalization since 1996. Protected by U.S. Patent No. D1134697-S.

Visit alivewater.com

Key Findings

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

Performance Metrics

alivewater.com performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

62/100

10%

LCP (Largest Contentful Paint)

Value8.7 s

1/100

25%

SI (Speed Index)

Value8.8 s

16/100

10%

TBT (Total Blocking Time)

Value11,600 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.14

79/100

15%

TTI (Time to Interactive)

Value21.5 s

1/100

10%

Network Requests Diagram

alivewater.com

212 ms

www.alivewater.com

517 ms

gtm.js

49 ms

printfriendly.js

21 ms

core.css

134 ms

Our browser made a total of 174 requests to load all elements on the main page. We found that 80% of them (139 requests) were addressed to the original Alivewater.com, 7% (12 requests) were made to Jnn-pa.googleapis.com and 6% (10 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Alivewater.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 462.6 kB (24%)

Content Size

1.9 MB

After Optimization

1.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-75%

Potential reduce by 44.2 kB

  • Original 58.8 kB
  • After minification 53.3 kB
  • After compression 14.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 44.2 kB or 75% of the original size.

Image Optimization

-9%

Potential reduce by 94.4 kB

  • Original 1.0 MB
  • After minification 939.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. Alive Water images are well optimized though.

JavaScript Optimization

-42%

Potential reduce by 291.7 kB

  • Original 694.4 kB
  • After minification 691.2 kB
  • After compression 402.7 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 291.7 kB or 42% of the original size.

CSS Optimization

-23%

Potential reduce by 32.3 kB

  • Original 141.2 kB
  • After minification 139.8 kB
  • After compression 108.9 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. Alivewater.com needs all CSS files to be minified and compressed as it can save up to 32.3 kB or 23% of the original size.

Requests Breakdown

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

Requests Now

170

After Optimization

49

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

alivewater.com

alivewater.com

212 ms

www.alivewater.com

www.alivewater.com

517 ms

gtm.js

gtm.js

49 ms

printfriendly.js

printfriendly.js

21 ms

core.css

core.css

134 ms

controlgroup.css

controlgroup.css

196 ms

checkboxradio.css

checkboxradio.css

206 ms

resizable.css

resizable.css

219 ms

button.css

button.css

210 ms

dialog.css

dialog.css

220 ms

align.module.css

align.module.css

218 ms

fieldgroup.module.css

fieldgroup.module.css

259 ms

container-inline.module.css

container-inline.module.css

275 ms

clearfix.module.css

clearfix.module.css

274 ms

details.module.css

details.module.css

284 ms

hidden.module.css

hidden.module.css

294 ms

item-list.module.css

item-list.module.css

293 ms

js.module.css

js.module.css

326 ms

nowrap.module.css

nowrap.module.css

347 ms

position-container.module.css

position-container.module.css

349 ms

progress.module.css

progress.module.css

350 ms

reset-appearance.module.css

reset-appearance.module.css

361 ms

resize.module.css

resize.module.css

369 ms

sticky-header.module.css

sticky-header.module.css

394 ms

css_41w6dBZ448pJSogyLgoToui9MDm8KnZHhhxIUFUonds.e37FtImSYRArD-YR7xx_6NTM7t0lTnYPMiTfGJ3V9nk.css

css_41w6dBZ448pJSogyLgoToui9MDm8KnZHhhxIUFUonds.e37FtImSYRArD-YR7xx_6NTM7t0lTnYPMiTfGJ3V9nk.css

415 ms

system-status-report-counters.css

system-status-report-counters.css

421 ms

system-status-report-general-info.css

system-status-report-general-info.css

418 ms

css_PRpLCpZQr4zTfafBQvuU6Ai1fdWr3UHToA3uiawHjkM.fLPfLB0XwmNrMgpuaRfK4T-BBNy7nDIXycFgFzdHoEQ.css

css_PRpLCpZQr4zTfafBQvuU6Ai1fdWr3UHToA3uiawHjkM.fLPfLB0XwmNrMgpuaRfK4T-BBNy7nDIXycFgFzdHoEQ.css

431 ms

css_aylBIaNUjhSigWKCcIK0c-t_kOYqAOEKlb80phSXPOI.YEu5frKSRjA4c8ZWvMbXap7EDcPykNyiQnFkLNEJt20.css

css_aylBIaNUjhSigWKCcIK0c-t_kOYqAOEKlb80phSXPOI.YEu5frKSRjA4c8ZWvMbXap7EDcPykNyiQnFkLNEJt20.css

442 ms

drupal-mmenu.css

drupal-mmenu.css

468 ms

mmenu.css

mmenu.css

488 ms

ckeditor5.dialog.fix.css

ckeditor5.dialog.fix.css

488 ms

views.module.css

views.module.css

492 ms

views_slideshow_cycle.css

views_slideshow_cycle.css

503 ms

css_kJqax_RkZBAk2I3Nq_rTD9LHc0oMwWKlanYK42ORIfM.CvxpKHOIB7UdEa4opLf3Ghio9wJowht1qDeijlqMnH4.css

css_kJqax_RkZBAk2I3Nq_rTD9LHc0oMwWKlanYK42ORIfM.CvxpKHOIB7UdEa4opLf3Ghio9wJowht1qDeijlqMnH4.css

511 ms

printfriendly.css

printfriendly.css

537 ms

webform_bootstrap.css

webform_bootstrap.css

558 ms

bootstrap.css

bootstrap.css

33 ms

drupal-bootstrap.css

drupal-bootstrap.css

49 ms

css_7SAjSsQnMj7vlOjlWmjie5LXXV8lmR_h5-EhU1tOEHw.FPq2BXAlyCwIcZtZw1Tepd8UqUR-hXEnavLvyXpzZ4Y.css

css_7SAjSsQnMj7vlOjlWmjie5LXXV8lmR_h5-EhU1tOEHw.FPq2BXAlyCwIcZtZw1Tepd8UqUR-hXEnavLvyXpzZ4Y.css

641 ms

css_CsdPqmlZO9Yj3NEylJFooOuxz10nLrhlJHl1pzk_qJk.TxJQrdu3WCzdXwL2aBCY-0_h5uAKFhuH_Ou4uhP-6Uk.css

css_CsdPqmlZO9Yj3NEylJFooOuxz10nLrhlJHl1pzk_qJk.TxJQrdu3WCzdXwL2aBCY-0_h5uAKFhuH_Ou4uhP-6Uk.css

567 ms

a

a

89 ms

jquery.min.js

jquery.min.js

19 ms

jquery-ui.min.js

jquery-ui.min.js

24 ms

bootstrap.js

bootstrap.js

18 ms

css_ZSjzdXYRrGmgLpjroezomhM8OZOtZ1J8ZQw_EQ9cUSk.A7sW_EsZ2_dQRqR4RpkpeIOiJhNTcYG2CIrs-XWnhe0.css

css_ZSjzdXYRrGmgLpjroezomhM8OZOtZ1J8ZQw_EQ9cUSk.A7sW_EsZ2_dQRqR4RpkpeIOiJhNTcYG2CIrs-XWnhe0.css

514 ms

drupal-bootstrap.css

drupal-bootstrap.css

479 ms

css_57Tx8bTSRmyodmzLZ1Z9CvqZVUnoAY-mCZ-_AmAVjbM.6Us65Eg5HsbXvBS6oB0E_y1svewm9GU06O6ci5SB10g.css

css_57Tx8bTSRmyodmzLZ1Z9CvqZVUnoAY-mCZ-_AmAVjbM.6Us65Eg5HsbXvBS6oB0E_y1svewm9GU06O6ci5SB10g.css

421 ms

underscore-min.js

underscore-min.js

434 ms

element.matches.js

element.matches.js

499 ms

object.assign.js

object.assign.js

491 ms

nodelist.foreach.js

nodelist.foreach.js

491 ms

css.escape.js

css.escape.js

501 ms

es6-promise.auto.min.js

es6-promise.auto.min.js

463 ms

once.min.js

once.min.js

461 ms

jquery.once.min.js

jquery.once.min.js

460 ms

drupalSettingsLoader.js

drupalSettingsLoader.js

451 ms

drupal.js

drupal.js

456 ms

drupal.init.js

drupal.init.js

491 ms

version-min.js

version-min.js

455 ms

data-min.js

data-min.js

453 ms

disable-selection-min.js

disable-selection-min.js

457 ms

focusable-min.js

focusable-min.js

457 ms

form-min.js

form-min.js

455 ms

ie-min.js

ie-min.js

495 ms

jquery-patch-min.js

jquery-patch-min.js

595 ms

keycode-min.js

keycode-min.js

661 ms

plugin-min.js

plugin-min.js

659 ms

safe-active-element-min.js

safe-active-element-min.js

656 ms

safe-blur-min.js

safe-blur-min.js

646 ms

scroll-parent-min.js

scroll-parent-min.js

818 ms

unique-id-min.js

unique-id-min.js

830 ms

controlgroup-min.js

controlgroup-min.js

809 ms

form-reset-mixin-min.js

form-reset-mixin-min.js

810 ms

labels-min.js

labels-min.js

806 ms

mouse-min.js

mouse-min.js

796 ms

checkboxradio-min.js

checkboxradio-min.js

787 ms

draggable-min.js

draggable-min.js

819 ms

resizable-min.js

resizable-min.js

799 ms

button-min.js

button-min.js

788 ms

dialog-min.js

dialog-min.js

781 ms

index.umd.min.js

index.umd.min.js

751 ms

mmenu_fire.js

mmenu_fire.js

745 ms

mmenu.js

mmenu.js

920 ms

dc.js

dc.js

72 ms

OPPQPi_EJ_Y

OPPQPi_EJ_Y

150 ms

KmTg4gHDkGI

KmTg4gHDkGI

455 ms

tPc0zXxaFDY

tPc0zXxaFDY

495 ms

g3vKvf7NO78

g3vKvf7NO78

631 ms

Q0fomlcXwZM

Q0fomlcXwZM

555 ms

caq2albYeBk

caq2albYeBk

592 ms

drupal.bootstrap.js

drupal.bootstrap.js

848 ms

attributes.js

attributes.js

849 ms

theme.js

theme.js

849 ms

bootstrap.js

bootstrap.js

854 ms

menu-hover.js

menu-hover.js

887 ms

webform.behaviors.js

webform.behaviors.js

888 ms

jquery.once.bc.js

jquery.once.bc.js

888 ms

states.js

states.js

885 ms

__utm.gif

__utm.gif

12 ms

states.js

states.js

876 ms

webform.states.js

webform.states.js

840 ms

webform_bootstrap.states.js

webform_bootstrap.states.js

1123 ms

popover.js

popover.js

1110 ms

tooltip.js

tooltip.js

1104 ms

progress.js

progress.js

1101 ms

www-player.css

www-player.css

14 ms

www-embed-player.js

www-embed-player.js

28 ms

base.js

base.js

50 ms

progress.js

progress.js

1094 ms

loadjs.min.js

loadjs.min.js

1045 ms

ad_status.js

ad_status.js

575 ms

4-NlEi-7NY8SQPLCpX1INlyCg7Vzxjxgly2SzKIOrZg.js

4-NlEi-7NY8SQPLCpX1INlyCg7Vzxjxgly2SzKIOrZg.js

528 ms

embed.js

embed.js

288 ms

ajax.js

ajax.js

946 ms

ajax.js

ajax.js

949 ms

debounce.js

debounce.js

945 ms

displace.js

displace.js

947 ms

jquery.tabbable.shim.js

jquery.tabbable.shim.js

904 ms

position.js

position.js

727 ms

modal.js

modal.js

733 ms

dialog.js

dialog.js

731 ms

modal.jquery.ui.bridge.js

modal.jquery.ui.bridge.js

730 ms

dialog.js

dialog.js

730 ms

dialog.position.js

dialog.position.js

730 ms

ckeditor5.dialog.fix.js

ckeditor5.dialog.fix.js

673 ms

dialog.ajax.js

dialog.ajax.js

745 ms

dialog.ajax.js

dialog.ajax.js

745 ms

json2.js

json2.js

746 ms

jquery.cycle.all.js

jquery.cycle.all.js

747 ms

views_slideshow_cycle.js

views_slideshow_cycle.js

748 ms

jquery.hoverIntent.js

jquery.hoverIntent.js

748 ms

id

id

193 ms

views_slideshow.js

views_slideshow.js

627 ms

sansation_regular-webfont.woff

sansation_regular-webfont.woff

717 ms

wlws_logo.jpg

wlws_logo.jpg

716 ms

facebook.png

facebook.png

635 ms

twitter.png

twitter.png

628 ms

youtube.png

youtube.png

628 ms

Create

Create

459 ms

Create

Create

457 ms

Create

Create

460 ms

Create

Create

462 ms

Create

Create

465 ms

Create

Create

527 ms

linkedin.png

linkedin.png

653 ms

rss-feed.png

rss-feed.png

654 ms

shopping-cart.png

shopping-cart.png

653 ms

menu_bg.jpg

menu_bg.jpg

651 ms

health-benefits_0.jpg

health-benefits_0.jpg

812 ms

discover_2.png

discover_2.png

727 ms

home-benefits_0.jpg

home-benefits_0.jpg

527 ms

discover_0.png

discover_0.png

444 ms

FrontBanner3ApartmentModels.png

FrontBanner3ApartmentModels.png

884 ms

discover.png

discover.png

443 ms

The-Vortex-Water-Revitalizer-Product_0.jpg

The-Vortex-Water-Revitalizer-Product_0.jpg

525 ms

discover_1_0.png

discover_1_0.png

443 ms

Open-Vortex-Water-Revitalizer-Copper-Pipe-Standardweb1.jpg

Open-Vortex-Water-Revitalizer-Copper-Pipe-Standardweb1.jpg

530 ms

bullet.png

bullet.png

411 ms

bottom_bg.png

bottom_bg.png

527 ms

health-benefits_0.jpg

health-benefits_0.jpg

437 ms

discover_2.png

discover_2.png

364 ms

home-benefits_0.jpg

home-benefits_0.jpg

437 ms

discover_0.png

discover_0.png

365 ms

FrontBanner3ApartmentModels.png

FrontBanner3ApartmentModels.png

884 ms

discover.png

discover.png

441 ms

The-Vortex-Water-Revitalizer-Product_0.jpg

The-Vortex-Water-Revitalizer-Product_0.jpg

441 ms

discover_1_0.png

discover_1_0.png

441 ms

GenerateIT

GenerateIT

277 ms

GenerateIT

GenerateIT

276 ms

GenerateIT

GenerateIT

192 ms

GenerateIT

GenerateIT

154 ms

GenerateIT

GenerateIT

101 ms

GenerateIT

GenerateIT

28 ms

Accessibility Review

alivewater.com accessibility score

94

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

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

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

alivewater.com 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

alivewater.com 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 Alivewater.com 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 Alivewater.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.

Social Sharing Optimization

alivewater.com

Open Graph description is not detected on the main page of Alive Water. 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: