2.2 sec in total
85 ms
1.8 sec
322 ms
Welcome to waterheater.com homepage info - get ready to check Water Heater best content right away, or after learning these important things about waterheater.com
Rheem has nearly a century worth of manufacturing innovative, efficient, air, water, and pool solutions for your home and business.
Visit waterheater.comWe analyzed Waterheater.com page load time and found that the first response time was 85 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster. This domain responded with an error, which can significantly jeopardize Waterheater.com rating and web reputation
waterheater.com performance score
name
value
score
weighting
Value3.6 s
32/100
10%
Value10.6 s
0/100
25%
Value9.2 s
13/100
10%
Value5,200 ms
0/100
30%
Value1.314
1/100
15%
Value20.9 s
1/100
10%
85 ms
351 ms
127 ms
84 ms
83 ms
Our browser made a total of 118 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Waterheater.com, 42% (49 requests) were made to Rheem.com and 19% (23 requests) were made to Static-rheem.globalimageserver.com. The less responsive or slowest element that took the longest time to load (496 ms) relates to the external source Rheem.com.
Page size can be reduced by 598.6 kB (27%)
2.2 MB
1.6 MB
In fact, the total size of Waterheater.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. 55% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 96.2 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 96.2 kB or 76% of the original size.
Potential reduce by 113.6 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. Water Heater images are well optimized though.
Potential reduce by 297.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 297.6 kB or 61% of the original size.
Potential reduce by 91.2 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. Waterheater.com needs all CSS files to be minified and compressed as it can save up to 91.2 kB or 84% of the original size.
Number of requests can be reduced by 51 (54%)
95
44
The browser has sent 95 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Water Heater. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 27 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
waterheater.com
85 ms
www.rheem.com
351 ms
vscrollarea.js
127 ms
ie-hover-pack.js
84 ms
inputs.js
83 ms
jquery.min.js
30 ms
jquery-ui.css
152 ms
jquery-ui.js
10 ms
jquery-migrate-1.2.1.min.js
10 ms
tabs.js
83 ms
faqPopup.js
88 ms
head.css
180 ms
newAll.css
184 ms
foot.css
180 ms
faqPopup.css
181 ms
carousel.css
182 ms
stepcarousel.js
251 ms
carousel-setup.js
182 ms
effects.core.js
186 ms
effects.blind.js
185 ms
com-rheem-load.js
208 ms
WebResource.axd
301 ms
ScriptResource.axd
496 ms
ScriptResource.axd
302 ms
ScriptResource.axd
238 ms
ScriptResource.axd
268 ms
ScriptResource.axd
288 ms
addthis_widget.js
16 ms
timeline-promo.jpg
84 ms
air-and-water-anime.gif
52 ms
nest-background.jpg
51 ms
naeca2015-background.jpg
55 ms
EN_C1-background.jpg
49 ms
KC-background.jpg
59 ms
hybrid-background.jpg
60 ms
nest-midground.png
59 ms
naeca2015-midground.png
60 ms
EN_C1-midground.png
53 ms
KC-midground.png
58 ms
hybrid-midground.png
56 ms
nest-foreground.png
60 ms
naeca2015-foreground.png
61 ms
EN_C1-foreground.png
76 ms
KC-foreground.png
61 ms
hybrid-foreground.png
65 ms
bg-body.jpg
57 ms
blank.gif
47 ms
468x60_MegaMenu_Tankless.jpg
149 ms
loader.gif
85 ms
icon-service-repair-30px.png
83 ms
cancel_btn.png
88 ms
btn_updateresults_gray.png
119 ms
close-btn.png
127 ms
btn_submit_b_gray.png
134 ms
header-search-btn.png
131 ms
iui3
28 ms
appnexus
17 ms
bg-header.gif
51 ms
bg-items-icons.png
128 ms
bg-megadrop-about.png
122 ms
logo.png
119 ms
bg-megadrop-t.png
119 ms
bg-megadrop-c.png
116 ms
bg-megadrop-b.png
117 ms
separator.gif
116 ms
bg-main.gif
10 ms
btn-menu.gif
13 ms
bg-menu.png
12 ms
bg-sidebox-t.gif
13 ms
bg-sidebox-b.gif
14 ms
arrow.gif
14 ms
arrows.png
102 ms
hero-swoop.png
107 ms
gallery_curve.png
105 ms
bg-menu-container.gif
134 ms
bullet.gif
103 ms
ico-flags.gif
103 ms
quick-links-icons-2015.png
105 ms
analytics.js
82 ms
insight.min.js
85 ms
validatePostalCode.asmx
326 ms
300lo.json
46 ms
ui-bg_flat_75_ffffff_40x100.png
75 ms
ui-icons_222222_256x240.png
75 ms
ui-bg_highlight-soft_75_cccccc_1x100.png
76 ms
generic
33 ms
sh.8e5f85691f9aaa082472a194.html
53 ms
collect
41 ms
pixel
41 ms
collect
60 ms
pixel
22 ms
4 ms
generic
5 ms
bg-btn.gif
5 ms
roundtrip.js
9 ms
BOO7W7VWY5CEJOF733WTTM.js
141 ms
16 ms
l
67 ms
fbevents.hashing.js
152 ms
out
32 ms
41 ms
out
9 ms
out
27 ms
out
26 ms
out
26 ms
out
25 ms
out
31 ms
out
30 ms
u.php
48 ms
adsct
103 ms
pixel
28 ms
26 ms
sync
7 ms
377928.gif
8 ms
sd
7 ms
in
14 ms
23 ms
tap.php
140 ms
waterheater.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
Form elements do not have associated labels
waterheater.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
waterheater.com 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
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
N/A
N/A
N/A
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Waterheater.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Waterheater.com main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
waterheater.com
Open Graph description is not detected on the main page of Water Heater. 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: