waterandpower.org Website Information

Daily Unique Visits: 3,342

Daily Page Views: 13,368

Income Per Day: $37

Estimated Value: $19,980

This website is located in United States and is using following IP address 66.175.58.9. See the complete list of popular websites hosted in United States.

waterandpower.org is registered under .ORG top-level domain. Please check other sites in .ORG zone.

Website waterandpower.org is using the following name servers:

ns1.carrierzone.com
ns4.carrierzone.com
ns3.carrierzone.com
ns2.carrierzone.com

and is probably hosted by INFB2-AS - InternetNamesForBusiness.com, US. See the full list of other websites hosted by INFB2-AS - InternetNamesForBusiness.com, US.

The highest website waterandpower.org position in Alexa rank database was 43072 and the lowest rank position was 999801. Current position of waterandpower.org in Alexa rank database is 375453.

Desktop speed score of waterandpower.org (49/100) is better than the results of 22.8% of other sites and shows that the page desktop performance can be improved.

Mobile usability score of waterandpower.org (61/100) is better than the results of 5.47% of other sites and means that the page is not mobile-friendly.

Mobile speed score of waterandpower.org (48/100) is better than the results of 30.32% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.

waterandpower.org Alexa Rank

The traffic rank is based on three months of aggregated historical traffic data from millions of Alexa Toolbar users and is a combined measure of page views and users.

waterandpower.org whois

WHOIS gives you the ability to lookup any generic domains to find out the registered domain holder. WHOIS database are provided for information purposes only. It allows the public to check whether a specific domain name is still available or not and to obtain information related to the registration records of existing domain names.

Domain Name: WATERANDPOWER.ORG
Registry Domain ID: D98242747-LROR
Registrar WHOIS Server: whois.tucows.com
Registrar URL: http://www.tucows.com
Updated Date: 2021-06-10T07:30:49Z
Creation Date: 2003-06-10T14:57:12Z
Registry Expiry Date: 2022-06-10T14:57:12Z
Registrar Registration Expiration Date:
Registrar: Tucows Domains Inc.
Registrar IANA ID: 69
Registrar Abuse Contact Email: domainabuse@tucows.com
Registrar Abuse Contact Phone: +1.4165350123
Reseller:
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
Registrant Organization: Contact Privacy Inc. Customer 0145419515
Registrant State/Province: ON
Registrant Country: CA
Name Server: DNS3.EARTHLINK.NET
Name Server: DNS2.EARTHLINK.NET
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form https://www.icann.org/wicf/)
>>> Last update of WHOIS database: 2022-01-17T20:36:49Z

waterandpower.org server information

Servers Location

waterandpower.org desktop page speed rank

Last tested: 2019-08-14

Desktop Speed Bad

49/100

waterandpower.org Desktop Speed Test Quick Summary

priority - 96Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 938.2KiB (44% reduction).

Compressing https://waterandpower.org/Index_Photo/StreamB.jpg could save 227.6KiB (49% reduction).
Compressing https://waterandpower.org/Historical_DWP_Photo_Col…ry/1st_Streetlight.jpg could save 200.2KiB (63% reduction).
Compressing https://waterandpower.org/E%20Historic%20Photos%20E/Intake.jpg could save 130.8KiB (52% reduction).
Compressing and resizing https://waterandpower.org/C%20Historic%20Photos%20C/Meeting_Clipart3.jpg could save 89.3KiB (75% reduction).
Compressing https://waterandpower.org/E%20Historic%20Photos%20…stalling_OH_Lines2.jpg could save 70.5KiB (52% reduction).
Compressing https://waterandpower.org/Historical_DWP_Photo_Col…_Aqueduct_Opening2.jpg could save 45.3KiB (23% reduction).
Compressing https://waterandpower.org/E%20Historic%20Photos%20…wer_Distribution_3.jpg could save 31.7KiB (22% reduction).
Compressing https://waterandpower.org/C%20Historic%20Photos%20C/Mission_Statement.jpg could save 24.8KiB (20% reduction).
Compressing https://waterandpower.org/C%20Historic%20Photos%20C/LA_River_Basin.jpg could save 21.9KiB (21% reduction).
Compressing https://waterandpower.org/C%20Historic%20Photos%20C/Mission2x.jpg could save 19.9KiB (29% reduction).
Compressing https://waterandpower.org/8%20Historic%20Photos%208/News.jpg could save 17.3KiB (69% reduction).
Compressing https://waterandpower.org/museum/images/mulholland.jpg could save 17.1KiB (65% reduction).
Compressing https://waterandpower.org/C%20Historic%20Photos%20C/Mission1x.jpg could save 17KiB (29% reduction).
Compressing https://waterandpower.org/C%20Historic%20Photos%20C/Mission3x.jpg could save 13.4KiB (29% reduction).
Compressing https://waterandpower.org/images/image.jpg could save 10.3KiB (37% reduction).
Compressing https://www.google.com/cse/static/css/v2/clear.png could save 898B (88% reduction).
Compressing https://waterandpower.org/images/gadget_bg.gif could save 135B (39% reduction).

priority - 10Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

https://count.carrierzone.com/app/count_server/count.js (expiration not specified)
https://waterandpower.org/8%20Historic%20Photos%208/News.jpg (expiration not specified)
https://waterandpower.org/C%20Historic%20Photos%20C/LA_River_Basin.jpg (expiration not specified)
https://waterandpower.org/C%20Historic%20Photos%20C/Meeting_Clipart3.jpg (expiration not specified)
https://waterandpower.org/C%20Historic%20Photos%20C/Mission1x.jpg (expiration not specified)
https://waterandpower.org/C%20Historic%20Photos%20C/Mission2x.jpg (expiration not specified)
https://waterandpower.org/C%20Historic%20Photos%20C/Mission3x.jpg (expiration not specified)
https://waterandpower.org/C%20Historic%20Photos%20C/Mission_Statement.jpg (expiration not specified)
https://waterandpower.org/E%20Historic%20Photos%20E/Intake.jpg (expiration not specified)
https://waterandpower.org/E%20Historic%20Photos%20…stalling_OH_Lines2.jpg (expiration not specified)
https://waterandpower.org/E%20Historic%20Photos%20…wer_Distribution_3.jpg (expiration not specified)
https://waterandpower.org/Historical_DWP_Photo_Col…ry/1st_Streetlight.jpg (expiration not specified)
https://waterandpower.org/Historical_DWP_Photo_Col…_Aqueduct_Opening2.jpg (expiration not specified)
https://waterandpower.org/Index_Photo/StreamB.jpg (expiration not specified)
https://waterandpower.org/images/gadget_bg.gif (expiration not specified)
https://waterandpower.org/images/image.jpg (expiration not specified)
https://waterandpower.org/museum/images/mulholland.jpg (expiration not specified)
https://waterandpower.org/style.css (expiration not specified)
https://www.google.com/cse/static/style/look/v3/default.css (50 minutes)
https://cse.google.com/adsense/search/async-ads.js (60 minutes)
https://ssl.google-analytics.com/ga.js (2 hours)

priority - 6Enable compression

Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.

Enable compression for the following resources to reduce their transfer size by 55.4KiB (73% reduction).

Compressing https://count.carrierzone.com/app/count_server/count.js could save 26.8KiB (76% reduction).
Compressing https://waterandpower.org/ could save 25.2KiB (71% reduction).
Compressing https://waterandpower.org/style.css could save 3.4KiB (72% reduction).

priority - 2Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 1 blocking CSS resources. This causes a delay in rendering your page.

Optimize CSS Delivery of the following:

https://waterandpower.org/style.css

priority - 1Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

Minify JavaScript for the following resources to reduce their size by 12KiB (35% reduction).

Minifying https://count.carrierzone.com/app/count_server/count.js could save 12KiB (35% reduction).

priority - 1Minify HTML

Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.

Minify HTML for the following resources to reduce their size by 5.9KiB (17% reduction).

Minifying https://waterandpower.org/ could save 5.9KiB (17% reduction).

priority - 0Minify CSS

Compacting CSS code can save many bytes of data and speed up download and parse times.

Minify CSS for the following resources to reduce their size by 4.8KiB (29% reduction).

Minifying https://www.google.com/cse/static/element/e1b7867e793369c8/default+en.css could save 3.8KiB (40% reduction) after compression.
Minifying https://www.google.com/cse/static/style/look/v3/default.css could save 512B (19% reduction) after compression.
Minifying https://waterandpower.org/style.css could save 494B (11% reduction).

waterandpower.org Desktop Resource Breakdown

Total Resources	34
Number of Hosts	8
Static Resources	26
JavaScript Resources	5
CSS Resources	3

waterandpower.org mobile page speed rank

Last tested: 2019-08-19

Mobile Speed Bad

48/100

waterandpower.org Mobile Speed Test Quick Summary

priority - 89Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 871.4KiB (41% reduction).

Compressing https://waterandpower.org/Index_Photo/StreamB.jpg could save 227.6KiB (49% reduction).
Compressing https://waterandpower.org/Historical_DWP_Photo_Col…ry/1st_Streetlight.jpg could save 200.2KiB (63% reduction).
Compressing https://waterandpower.org/E%20Historic%20Photos%20E/Intake.jpg could save 130.8KiB (52% reduction).
Compressing https://waterandpower.org/E%20Historic%20Photos%20…stalling_OH_Lines2.jpg could save 70.5KiB (52% reduction).
Compressing https://waterandpower.org/Historical_DWP_Photo_Col…_Aqueduct_Opening2.jpg could save 45.3KiB (23% reduction).
Compressing https://waterandpower.org/E%20Historic%20Photos%20…wer_Distribution_3.jpg could save 31.7KiB (22% reduction).
Compressing https://waterandpower.org/C%20Historic%20Photos%20C/Mission_Statement.jpg could save 24.8KiB (20% reduction).
Compressing https://waterandpower.org/C%20Historic%20Photos%20C/Meeting_Clipart3.jpg could save 22.5KiB (19% reduction).
Compressing https://waterandpower.org/C%20Historic%20Photos%20C/LA_River_Basin.jpg could save 21.9KiB (21% reduction).
Compressing https://waterandpower.org/C%20Historic%20Photos%20C/Mission2x.jpg could save 19.9KiB (29% reduction).
Compressing https://waterandpower.org/8%20Historic%20Photos%208/News.jpg could save 17.3KiB (69% reduction).
Compressing https://waterandpower.org/museum/images/mulholland.jpg could save 17.1KiB (65% reduction).
Compressing https://waterandpower.org/C%20Historic%20Photos%20C/Mission1x.jpg could save 17KiB (29% reduction).
Compressing https://waterandpower.org/C%20Historic%20Photos%20C/Mission3x.jpg could save 13.4KiB (29% reduction).
Compressing https://waterandpower.org/images/image.jpg could save 10.3KiB (37% reduction).
Compressing https://www.google.com/cse/static/css/v2/clear.png could save 898B (88% reduction).
Compressing https://waterandpower.org/images/gadget_bg.gif could save 135B (39% reduction).

priority - 16Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

priority - 8Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 1 blocking CSS resources. This causes a delay in rendering your page.

Optimize CSS Delivery of the following:

https://waterandpower.org/style.css

priority - 6Enable compression

Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.

Enable compression for the following resources to reduce their transfer size by 55.4KiB (73% reduction).

priority - 1Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

Minify JavaScript for the following resources to reduce their size by 12KiB (35% reduction).

Minifying https://count.carrierzone.com/app/count_server/count.js could save 12KiB (35% reduction).

priority - 1Minify HTML

Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.

Minify HTML for the following resources to reduce their size by 5.9KiB (17% reduction).

Minifying https://waterandpower.org/ could save 5.9KiB (17% reduction).

priority - 1Minify CSS

Compacting CSS code can save many bytes of data and speed up download and parse times.

Minify CSS for the following resources to reduce their size by 5KiB (28% reduction).

waterandpower.org Mobile Resource Breakdown

Total Resources	35
Number of Hosts	8
Static Resources	27
JavaScript Resources	5
CSS Resources	4

waterandpower.org mobile page usability

Last tested: 2019-08-19

Mobile Usability Bad

61/100

waterandpower.org Mobile Usability Test Quick Summary

priority - 39Use legible font sizes

The following text on your page renders in a way that may be difficult for some of your visitors to read. Use legible font sizes to provide a better user experience.

The following text fragments have a small font size. Increase the font size to make them more legible.

Informing the…and California renders only 5 pixels tall (13 CSS pixels).

State mandated…ltage support. and 56 others render only 5 pixels tall (14 CSS pixels).

Historical LAD…acts & Figures and 15 others render only 5 pixels tall (14 CSS pixels).

to see the lat…ntake Magazine and 31 others render only 5 pixels tall (12 CSS pixels).

Board Meeting…Guest Speakers and 5 others render only 5 pixels tall (14 CSS pixels).

(1940) - DWP O…Crew at work. and 1 others render only 5 pixels tall (12 CSS pixels).
Intake renders only 5 pixels tall (14 CSS pixels).
Early LA Progr…tyle Buildings and 27 others render only 5 pixels tall (12 CSS pixels).
Ensuring Grid…Energy Future and 10 others render only 6 pixels tall (16 CSS pixels).
LADWP HISTORIC…T COMING SOON! renders only 5 pixels tall (14 CSS pixels).
View of the 30…et light mast. renders only 5 pixels tall (12 CSS pixels).
Click the Dona…n California. renders only 5 pixels tall (14 CSS pixels).

Positions on O…Angeles Issues and 15 others render only 6 pixels tall (16 CSS pixels).

© Copyright Wa…wer Associates and 1 others render only 5 pixels tall (12 CSS pixels).
Website Templates renders only 5 pixels tall (12 CSS pixels).

priority - 11Size content to viewport

The page content is too wide for the viewport, forcing the user to scroll horizontally. Size the page content to the viewport to provide a better user experience.

The page content is 1,315 CSS pixels wide, but the viewport is only 980 CSS pixels wide. The following elements fall outside the viewport:

The element <img src="C Historic Pho…_Statement.jpg"> falls outside the viewport.
The element <td></td> falls outside the viewport.
The element <td></td> falls outside the viewport.
The element <td></td> falls outside the viewport.
The element <img src="C Historic Pho…/Mission3x.jpg"> falls outside the viewport.
The element <p>Our goal is t…toric records.</p> falls outside the viewport.
The element <p>Because The As…able resource.</p> falls outside the viewport.
The element <p>The best way t…terest to you.</p> falls outside the viewport.
The element <td></td> falls outside the viewport.
The element <td></td> falls outside the viewport.
The element <td></td> falls outside the viewport.
The element <td></td> falls outside the viewport.
The element <tr></tr> falls outside the viewport.
The element <tr></tr> falls outside the viewport.
The element <img src="E Historic Pho…ribution_3.jpg"> falls outside the viewport.
The element <td></td> falls outside the viewport.
The element <td>(2019) - DWP O…Crew at work.</td> falls outside the viewport.
The element <td></td> falls outside the viewport.
The element <td></td> falls outside the viewport.
The element <td></td> falls outside the viewport.
The element <tr></tr> falls outside the viewport.
The element <tr></tr> falls outside the viewport.
The element <td></td> falls outside the viewport.
The element <td></td> falls outside the viewport.
The element <td></td> falls outside the viewport.
The element <td></td> falls outside the viewport.
The element <td></td> falls outside the viewport.
The element <td></td> falls outside the viewport.
The element <td></td> falls outside the viewport.
The element <tr></tr> falls outside the viewport.
The element <tr>View of the 30…et light mast.</tr> falls outside the viewport.
The element <td></td> falls outside the viewport.
The element <td></td> falls outside the viewport.
The element <td></td> falls outside the viewport.
The element <td></td> falls outside the viewport.
The element <td></td> falls outside the viewport.

priority - 10Configure the viewport

Your page does not have a viewport specified. This causes mobile devices to render your page as it would appear on a desktop browser, scaling it down to fit on a mobile screen. Configure a viewport to allow your page to render properly on all devices.

priority - 6Size tap targets appropriately

Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.

The following tap targets are close to other nearby tap targets and may need additional spacing around them.

The tap target <a href="museum/Early_V…ls_Page_1.html">Early Views of Beverly Hills</a> and 15 others are close to other tap targets.

The tap target <a href="index.html">Home</a> and 15 others are close to other tap targets.

The tap target <button class="gsc-search-but…arch-button-v2">search</button> is close to 2 other tap targets.

waterandpower.org HTML validation

Errors

Almost standards mode doctype. Expected “<!DOCTYPE html>”.

Line: 1 Column: 1 - 121
"...<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html..."

The “width” attribute on the “table” element is obsolete. Use CSS instead.

Line: 62 Column: 11 - 40
"... <table width="628" border="0"> ..." Line: 67 Column: 11 - 40
"... <table width="618" border="0"> ..." Line: 80 Column: 11 - 40
"... <table width="624" border="2"> ..." Line: 90 Column: 11 - 40
"... <table width="632" border="2"> ..." Line: 98 Column: 11 - 40
"... <table width="600" border="0"> ..." Line: 118 Column: 11 - 40
"... <table width="632" border="2"> ..." Line: 128 Column: 11 - 40
"... <table width="648" border="0"> ..." Line: 136 Column: 11 - 40
"... <table width="648" border="2"> ..." Line: 152 Column: 11 - 40
"... <table width="657" border="2"> ..." Line: 170 Column: 11 - 40
"... <table width="648" border="2"> ..." Line: 180 Column: 1 - 30
"...tion.</p> <table width="200" border="0"> <tr..." Line: 192 Column: 1 - 30
"...nbsp;</p> <table width="648" border="2"> <tr..." Line: 208 Column: 13 - 42
"... <table width="659" border="2"> ..." Line: 227 Column: 11 - 40
"... <table width="648" border="2"> ..."

The “border” attribute on the “table” element is obsolete. Use CSS instead.

The “width” attribute on the “td” element is obsolete. Use CSS instead.

Line: 64 Column: 17 - 43
"... <tr> <td width="622" height="107"><p>Our..." Line: 69 Column: 17 - 43
"... <tr> <td width="430" height="416"><img s..." Line: 70 Column: 121 - 29
"...6" /></td> <td width="10"> ..." Line: 71 Column: 41 - 30
"...nbsp;</td> <td width="164"><p ali..." Line: 82 Column: 17 - 30
"... <tr> <td width="612"><div a..." Line: 92 Column: 17 - 30
"... <tr> <td width="620"><div a..." Line: 100 Column: 17 - 30
"... <tr> <td width="135"><img s..." Line: 101 Column: 102 - 29
"...5" /></td> <td width="10"> ..." Line: 102 Column: 41 - 30
"...nbsp;</td> <td width="441"><p><st..." Line: 120 Column: 17 - 30
"... <tr> <td width="620"><div a..." Line: 130 Column: 17 - 29
"... <tr> <td width="18"><img s..." Line: 131 Column: 155 - 30
"...1" /></td> <td width="449"> ..." Line: 132 Column: 42 - 30
"...nbsp;</td> <td width="167"><p><im..." Line: 138 Column: 17 - 30
"... <tr> <td width="636"><div a..." Line: 154 Column: 17 - 30
"... <tr> <td width="200"><div a..." Line: 155 Column: 166 - 30
".../div></td> <td width="233"><div a..." Line: 156 Column: 161 - 30
".../div></td> <td width="200"><div a..." Line: 172 Column: 17 - 30
"... <tr> <td width="636"><div a..." Line: 194 Column: 7 - 20
"...2"> <tr> <td width="636"><div a..." Line: 210 Column: 19 - 32
"... <tr> <td width="214"><div a..." Line: 211 Column: 184 - 32
".../div></td> <td width="227"><div a..." Line: 212 Column: 265 - 32
".../div></td> <td width="194"><div a..." Line: 229 Column: 17 - 30
"... <tr> <td width="636"><div a..."

The “height” attribute on the “td” element is obsolete. Use CSS instead.

Line: 64 Column: 17 - 43
"... <tr> <td width="622" height="107"><p>Our..." Line: 69 Column: 17 - 43
"... <tr> <td width="430" height="416"><img s..."

Bad value “8 Historic Photos 8/Index_Pic.jpg” for attribute “src” on element “img”: Illegal character in path segment: space is not allowed.

Line: 69 Column: 44 - 115
"...ght="416"><img src="8 Historic Photos 8/Index_Pic.jpg" width="417" height="386" /></td> ..."

An “img” element must have an “alt” attribute, except under certain conditions. For details, consult guidance on providing text alternatives for images.

Line: 69 Column: 44 - 115
"...ght="416"><img src="8 Historic Photos 8/Index_Pic.jpg" width="417" height="386" /></td> ..." Line: 100 Column: 31 - 96
"...dth="135"><img src="8 Historic Photos 8/News.jpg" width="125" height="75" /></td> ..." Line: 182 Column: 9 - 116
"...> <td><img src="Historical_DWP_Photo_Collection_LA_Public_Library/1st_Streetlight.jpg" width="643" height="820" /></td> ..."

The “align” attribute on the “p” element is obsolete. Use CSS instead.

Line: 71 Column: 31 - 49
"...dth="164"><p align="justify">The be..." Line: 72 Column: 17 - 35
"... <p align="justify"> ..." Line: 73 Column: 15 - 33
"... <p align="justify">Click ..." Line: 74 Column: 15 - 33
"... <p align="justify"> ..." Line: 88 Column: 1 - 16
"...ong></h4> <p align="left">The Ci..." Line: 89 Column: 11 - 26
"... <p align="left">Althou..."

Bad value “_new” for attribute “target” on element “a”: Reserved keyword “new” used.

Line: 73 Column: 40 - 127
"...fy">Click <a href="sitebuildercontent/sitebuilderfiles/January_2018_Newsletter.pdf" target="_new">HERE</..." Line: 82 Column: 57 - 97
"...er">Click <a href="newsletters.html" target="_new">HERE</..." Line: 110 Column: 18 - 80
"... <p>The <a href="museum/DWP_MUSEUM.html#Hammel_Building" target="_new">Hammel..." Line: 110 Column: 265 - 335
"...on of the <a href="museum/Zanja Madre (Original LA Aqueduct).html" target="_new">Zanja ..." Line: 113 Column: 173 - 235
"...it (Click <a href="museum/DWP_MUSEUM.html#Hammel_Building" target="_new">HERE</..." Line: 127 Column: 25 - 67
"...isit our <a href="museum/museum.html" target="_new">Museum..." Line: 145 Column: 40 - 85
"...addition, <a href="museum/DWP_FACTS.html" target="_new">Histor..." Line: 147 Column: 123 - 182
"...s titled: <a href="museum/Street_Name_Origins_SFV.html" target="_new">SFV St..." Line: 147 Column: 215 - 277
"...s</a> and <a href="museum/Community_Name_Origins_SFV.html" target="_new">SFV Co..." Line: 149 Column: 108 - 169
"...n titled: <a href="museum/Smog_in_Early_Los_Angeles.html" target="_new">Smog i..." Line: 154 Column: 51 - 122
"...="center"><a href="museum/Early_Views_of_Beverly_Hills_Page_1.html" target="_new">Early ..." Line: 155 Column: 51 - 116
"...="center"><a href="museum/Early_LA_Drive_In_Restaurants.html" target="_new">Early ..." Line: 156 Column: 59 - 133
"..."><strong><a href="museum/Early_Views_of_West_Hollywood_(1920_+).html" target="_new">Early ..." Line: 159 Column: 39 - 96
"...="center"><a href="museum/Early_LA_Gas_Stations.html" target="_new">Early ..." Line: 160 Column: 39 - 106
"...="center"><a href="museum/Programmatic_Style_Architecture.html" target="_new">Early ..." Line: 161 Column: 39 - 103
"...="center"><a href="museum/Early_Views_of_Cahuenga_Pass.html" target="_new">Early ..." Line: 168 Column: 21 - 64
"...<p>A new <a href="museum/A_INDEX.html" target="_new">SEARCH..." Line: 168 Column: 81 - 117
"... INDEX</a><a href="A_INDEX.html" target="_new"></a> h..." Line: 172 Column: 57 - 100
"...er">Click <a href="museum/A_INDEX.html" target="_new">HERE</..." Line: 305 Column: 17 - 60
"... <li><a href="museum/A_INDEX.html" target="_new">Search..."

The “align” attribute on the “div” element is obsolete. Use CSS instead.

Line: 79 Column: 1 - 20
"...nbsp;</p> <div align="center"></div>..." Line: 82 Column: 31 - 50
"...dth="612"><div align="center">Click ..." Line: 92 Column: 31 - 50
"...dth="620"><div align="center">Click ..." Line: 120 Column: 31 - 50
"...dth="620"><div align="center">Click ..." Line: 138 Column: 31 - 50
"...dth="636"><div align="center">Click ..." Line: 154 Column: 31 - 50
"...dth="200"><div align="center"><a hre..." Line: 155 Column: 31 - 50
"...dth="233"><div align="center"><a hre..." Line: 156 Column: 31 - 50
"...dth="200"><div align="center"><stron..." Line: 159 Column: 19 - 38
"... <td><div align="center"><a hre..." Line: 160 Column: 19 - 38
"... <td><div align="center"><a hre..." Line: 161 Column: 19 - 38
"... <td><div align="center"><a hre..." Line: 172 Column: 31 - 50
"...dth="636"><div align="center">Click ..." Line: 194 Column: 21 - 40
"...dth="636"><div align="center">Click ..." Line: 207 Column: 11 - 30
"... <div align="center"> ..." Line: 210 Column: 33 - 52
"...dth="214"><div align="center"><a hre..." Line: 211 Column: 33 - 52
"...dth="227"><div align="center"><stron..." Line: 212 Column: 33 - 52
"...dth="194"><div align="center"><stron..." Line: 215 Column: 21 - 40
"... <td><div align="center"><stron..." Line: 216 Column: 21 - 40
"... <td><div align="center"><stron..." Line: 217 Column: 21 - 40
"... <td><div align="center"><stron..." Line: 229 Column: 31 - 50
"...dth="636"><div align="center">Robert..." Line: 243 Column: 13 - 32
"... <div align="center"> ..." Line: 249 Column: 11 - 30
"... <div align="center"> ..."

Bad value “8 Historic Photos 8/News.jpg” for attribute “src” on element “img”: Illegal character in path segment: space is not allowed.

Line: 100 Column: 31 - 96
"...dth="135"><img src="8 Historic Photos 8/News.jpg" width="125" height="75" /></td> ..."

Bad value “museum/Zanja Madre (Original LA Aqueduct).html” for attribute “href” on element “a”: Illegal character in path segment: space is not allowed.

Line: 110 Column: 265 - 335
"...on of the <a href="museum/Zanja Madre (Original LA Aqueduct).html" target="_new">Zanja ..."

Bad value “museum/Historical Record Committee.html” for attribute “href” on element “a”: Illegal character in path segment: space is not allowed.

Line: 120 Column: 57 - 106
"...er">Click <a href="museum/Historical Record Committee.html">HERE</..."

Bad value “Early_City_Views (1900 - 1925)_Page_1.html” for attribute “href” on element “a”: Illegal character in path segment: space is not allowed.

Line: 211 Column: 188 - 240
"...html"></a><a href="Early_City_Views (1900 - 1925)_Page_1.html"></a></..."

Attribute “border” not allowed on element “input” at this point.

Line: 246 Column: 15 - 181
"... <input type="image" src="https://www.paypalobjects.com/en_US/i/btn/btn_donateCC_LG.gif" border="0" name="submit" alt="PayPal - The safer, easier way to pay online!" /> ..."

No “p” element in scope but a “p” end tag seen.

Line: 250 Column: 13 - 16
"... </p> ..."

Element “br” not allowed as child of element “ul” in this context. (Suppressing further errors from this subtree.)

Line: 303 Column: 59 - 64
"...s</a></li><br /> ..." Line: 308 Column: 13 - 18
"... <br /> <br /..." Line: 308 Column: 20 - 25
"... <br /> <br /> ..."

Element “gcse:searchbox-only” not allowed as child of element “ul” in this context. (Suppressing further errors from this subtree.)

Line: 320 Column: 1 - 38
"...</script> <gcse:searchbox-only newWindow="true"></gcse..."

Bad element name “gcse:searchbox-only”: Code point “U+003A” is not allowed

Line: 320 Column: 1 - 38
"...</script> <gcse:searchbox-only newWindow="true"></gcse..."

Warnings

The “name” attribute is obsolete. Consider putting an “id” attribute on the nearest container instead.

Line: 106 Column: 4 - 32
"...p></p> <p><a name="Museum" id="Museum"></a></..." Line: 199 Column: 4 - 58
"...p></p> <p><a name="Special_Collections" id="Special_Collections"></a></..."

Element name “gcse:searchbox-only” cannot be represented as XML 1.0.

Line: 320 Column: 1 - 38
"...</script> <gcse:searchbox-only newWindow="true"></gcse..."

This document appears to be written in English. Consider adding “lang="en"” (or variant) to the “html” start tag.

Line: 2 Column: 122 - 43
"...onal.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"><!-- I..."

waterandpower.org similar domains

Similar domains:

www.waterandpower.com
www.waterandpower.net
www.waterandpower.org
www.waterandpower.info
www.waterandpower.biz
www.waterandpower.us
www.waterandpower.mobi
www.aterandpower.org
www.waterandpower.org
www.qaterandpower.org
www.wqaterandpower.org
www.qwaterandpower.org
www.aaterandpower.org
www.waaterandpower.org
www.awaterandpower.org
www.saterandpower.org
www.wsaterandpower.org
www.swaterandpower.org
www.eaterandpower.org
www.weaterandpower.org
www.ewaterandpower.org
www.wterandpower.org
www.wqterandpower.org
www.waqterandpower.org
www.wwterandpower.org
www.wawterandpower.org
www.wwaterandpower.org
www.wsterandpower.org
www.wasterandpower.org
www.wzterandpower.org
www.wazterandpower.org
www.wzaterandpower.org
www.waerandpower.org
www.warerandpower.org
www.watrerandpower.org
www.warterandpower.org
www.waferandpower.org
www.watferandpower.org
www.wafterandpower.org
www.wagerandpower.org
www.watgerandpower.org
www.wagterandpower.org
www.wayerandpower.org
www.watyerandpower.org
www.wayterandpower.org
www.watrandpower.org
www.watwrandpower.org
www.watewrandpower.org
www.watwerandpower.org
www.watsrandpower.org
www.watesrandpower.org
www.watserandpower.org
www.watdrandpower.org
www.watedrandpower.org
www.watderandpower.org
www.watrrandpower.org
www.waterrandpower.org
www.wateandpower.org
www.wateeandpower.org
www.watereandpower.org
www.wateerandpower.org
www.watedandpower.org
www.waterdandpower.org
www.watefandpower.org
www.waterfandpower.org
www.watefrandpower.org
www.watetandpower.org
www.watertandpower.org
www.watetrandpower.org
www.waterndpower.org
www.waterqndpower.org
www.wateraqndpower.org
www.waterqandpower.org
www.waterwndpower.org
www.waterawndpower.org
www.waterwandpower.org
www.watersndpower.org
www.waterasndpower.org
www.watersandpower.org
www.waterzndpower.org
www.waterazndpower.org
www.waterzandpower.org
www.wateradpower.org
www.waterabdpower.org
www.wateranbdpower.org
www.waterabndpower.org
www.waterahdpower.org
www.wateranhdpower.org
www.waterahndpower.org
www.waterajdpower.org
www.wateranjdpower.org
www.waterajndpower.org
www.wateramdpower.org
www.wateranmdpower.org
www.wateramndpower.org
www.wateranpower.org
www.wateranxpower.org
www.waterandxpower.org
www.wateranxdpower.org
www.wateranspower.org
www.waterandspower.org
www.wateransdpower.org
www.wateranepower.org
www.waterandepower.org
www.wateranedpower.org
www.wateranrpower.org
www.waterandrpower.org
www.wateranrdpower.org
www.wateranfpower.org
www.waterandfpower.org
www.wateranfdpower.org
www.waterancpower.org
www.waterandcpower.org
www.waterancdpower.org
www.waterandower.org
www.waterandoower.org
www.waterandpoower.org
www.waterandopower.org
www.waterandlower.org
www.waterandplower.org
www.waterandlpower.org
www.waterandpwer.org
www.waterandpiwer.org
www.waterandpoiwer.org
www.waterandpiower.org
www.waterandpkwer.org
www.waterandpokwer.org
www.waterandpkower.org
www.waterandplwer.org
www.waterandpolwer.org
www.waterandppwer.org
www.waterandpopwer.org
www.waterandppower.org
www.waterandpoer.org
www.waterandpoqer.org
www.waterandpowqer.org
www.waterandpoqwer.org
www.waterandpoaer.org
www.waterandpowaer.org
www.waterandpoawer.org
www.waterandposer.org
www.waterandpowser.org
www.waterandposwer.org
www.waterandpoeer.org
www.waterandpoweer.org
www.waterandpoewer.org
www.waterandpowr.org
www.waterandpowwr.org
www.waterandpowewr.org
www.waterandpowwer.org
www.waterandpowsr.org
www.waterandpowesr.org
www.waterandpowdr.org
www.waterandpowedr.org
www.waterandpowder.org
www.waterandpowrr.org
www.waterandpowerr.org
www.waterandpowrer.org
www.waterandpowe.org
www.waterandpowee.org
www.waterandpowere.org
www.waterandpowed.org
www.waterandpowerd.org
www.waterandpowef.org
www.waterandpowerf.org
www.waterandpowefr.org
www.waterandpowet.org
www.waterandpowert.org
www.waterandpowetr.org

waterandpower.org Ping

Ping is a computer network administration software utility used to test the reachability of a host on an Internet Protocol (IP) network. It measures the round-trip time for messages sent from the originating host to a destination computer that are echoed back to the source.

waterandpower.org TRACEROUTE

Traceroute is a computer network diagnostic tool for displaying the route (path) and measuring transit delays of packets across an Internet Protocol (IP) network. The history of the route is recorded as the round-trip times of the packets received from each successive host (remote node) in the route (path); the sum of the mean times in each hop is a measure of the total time spent to establish the connection. Traceroute proceeds unless all (three) sent packets are lost more than twice, then the connection is lost and the route cannot be evaluated.

WATERANDPOWER.ORG Water and Power Associates

waterandpower.org Website Information

Advertisement

waterandpower.org Alexa Rank

waterandpower.org whois

waterandpower.org server information

Servers Location

waterandpower.org desktop page speed rank

waterandpower.org Desktop Speed Test Quick Summary

priority - 96Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 938.2KiB (44% reduction).

priority - 10Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

priority - 6Enable compression

Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.

Enable compression for the following resources to reduce their transfer size by 55.4KiB (73% reduction).

priority - 2Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 1 blocking CSS resources. This causes a delay in rendering your page.

Optimize CSS Delivery of the following:

priority - 1Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

Minify JavaScript for the following resources to reduce their size by 12KiB (35% reduction).

priority - 1Minify HTML

Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.

Minify HTML for the following resources to reduce their size by 5.9KiB (17% reduction).

priority - 0Minify CSS

Compacting CSS code can save many bytes of data and speed up download and parse times.

Minify CSS for the following resources to reduce their size by 4.8KiB (29% reduction).

waterandpower.org Desktop Resource Breakdown

waterandpower.org mobile page speed rank

waterandpower.org Mobile Speed Test Quick Summary

priority - 89Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 871.4KiB (41% reduction).

priority - 16Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

priority - 8Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 1 blocking CSS resources. This causes a delay in rendering your page.

Optimize CSS Delivery of the following:

priority - 6Enable compression

Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.

Enable compression for the following resources to reduce their transfer size by 55.4KiB (73% reduction).

priority - 1Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

Minify JavaScript for the following resources to reduce their size by 12KiB (35% reduction).

priority - 1Minify HTML

Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.

Minify HTML for the following resources to reduce their size by 5.9KiB (17% reduction).

priority - 1Minify CSS

Compacting CSS code can save many bytes of data and speed up download and parse times.

Minify CSS for the following resources to reduce their size by 5KiB (28% reduction).

waterandpower.org Mobile Resource Breakdown

waterandpower.org mobile page usability

waterandpower.org Mobile Usability Test Quick Summary

priority - 39Use legible font sizes

The following text on your page renders in a way that may be difficult for some of your visitors to read. Use legible font sizes to provide a better user experience.

The following text fragments have a small font size. Increase the font size to make them more legible.

priority - 11Size content to viewport

The page content is too wide for the viewport, forcing the user to scroll horizontally. Size the page content to the viewport to provide a better user experience.

The page content is 1,315 CSS pixels wide, but the viewport is only 980 CSS pixels wide. The following elements fall outside the viewport:

priority - 10Configure the viewport

Your page does not have a viewport specified. This causes mobile devices to render your page as it would appear on a desktop browser, scaling it down to fit on a mobile screen. Configure a viewport to allow your page to render properly on all devices.

priority - 6Size tap targets appropriately

Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.

The following tap targets are close to other nearby tap targets and may need additional spacing around them.

waterandpower.org HTML validation

Errors

Almost standards mode doctype. Expected “<!DOCTYPE html>”.

The “width” attribute on the “table” element is obsolete. Use CSS instead.

The “border” attribute on the “table” element is obsolete. Use CSS instead.

The “width” attribute on the “td” element is obsolete. Use CSS instead.

The “height” attribute on the “td” element is obsolete. Use CSS instead.

Bad value “8 Historic Photos 8/Index_Pic.jpg” for attribute “src” on element “img”: Illegal character in path segment: space is not allowed.

An “img” element must have an “alt” attribute, except under certain conditions. For details, consult guidance on providing text alternatives for images.

The “align” attribute on the “p” element is obsolete. Use CSS instead.

Bad value “_new” for attribute “target” on element “a”: Reserved keyword “new” used.

The “align” attribute on the “div” element is obsolete. Use CSS instead.