2.9 sec in total
603 ms
2 sec
387 ms
Welcome to brightwater.com homepage info - get ready to check Brightwater best content right away, or after learning these important things about brightwater.com
Switching your water services to Brightwater is quick, easy and free. We take care of everything, and keep you fully informed from start to finish
Visit brightwater.comWe analyzed Brightwater.com page load time and found that the first response time was 603 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
brightwater.com performance score
name
value
score
weighting
Value3.2 s
43/100
10%
Value3.9 s
51/100
25%
Value4.8 s
66/100
10%
Value1,100 ms
23/100
30%
Value0.389
26/100
15%
Value12.1 s
16/100
10%
603 ms
44 ms
46 ms
101 ms
192 ms
Our browser made a total of 59 requests to load all elements on the main page. We found that 71% of them (42 requests) were addressed to the original Brightwater.com, 7% (4 requests) were made to Fonts.gstatic.com and 5% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (674 ms) belongs to the original domain Brightwater.com.
Page size can be reduced by 72.9 kB (8%)
886.2 kB
813.2 kB
In fact, the total size of Brightwater.com main page is 886.2 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 70% of websites need less resources to load. Javascripts take 379.4 kB which makes up the majority of the site volume.
Potential reduce by 58.3 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 58.3 kB or 80% of the original size.
Potential reduce by 12.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. Brightwater images are well optimized though.
Potential reduce by 1.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. This website has mostly compressed JavaScripts.
Potential reduce by 495 B
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. Brightwater.com has all CSS files already compressed.
Number of requests can be reduced by 38 (73%)
52
14
The browser has sent 52 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Brightwater. 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 13 to 1 for CSS and as a result speed up the page load time.
www.brightwater.com
603 ms
font-awesome.min.css
44 ms
css
46 ms
style.min.css
101 ms
classic-themes.min.css
192 ms
gravity-forms-bootstrap.css
279 ms
main.css
286 ms
wpp.min.js
279 ms
jquery.min.js
305 ms
jquery-migrate.min.js
319 ms
index.js
80 ms
gravity-forms-theme-foundation.min.css
326 ms
gravity-forms-theme-reset.min.css
399 ms
gravity-forms-theme-framework.min.css
393 ms
formreset.min.css
399 ms
formsmain.min.css
417 ms
readyclass.min.css
415 ms
browsers.min.css
475 ms
api.js
98 ms
main.js
489 ms
wp-polyfill-inert.min.js
489 ms
regenerator-runtime.min.js
488 ms
wp-polyfill.min.js
510 ms
dom-ready.min.js
509 ms
hooks.min.js
622 ms
i18n.min.js
623 ms
a11y.min.js
624 ms
jquery.json.min.js
624 ms
gravityforms.min.js
625 ms
placeholders.jquery.min.js
625 ms
utils.min.js
674 ms
vendor-theme.min.js
673 ms
scripts-theme.min.js
673 ms
frontend.min.js
673 ms
masonry.pkgd.min.js
420 ms
wp-emoji-release.min.js
656 ms
gtm.js
104 ms
logo.svg
406 ms
telephone-icon.png
453 ms
email-icon.png
453 ms
Bubble-its-free-quick-easy.png
453 ms
brightwater-identity-no-strapline.png
453 ms
6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7g.ttf
53 ms
6xKydSBYKcSV-LCoeQqfX1RYOo3ik4zwlxdr.ttf
54 ms
6xKydSBYKcSV-LCoeQqfX1RYOo3i54rwlxdr.ttf
76 ms
6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwlxdr.ttf
77 ms
hands-up-v2.png
463 ms
line-drawn-tap.png
463 ms
why-switch.jpg
595 ms
how-to-save.jpg
596 ms
brightwater-pad-2.jpg
672 ms
droplets.png
493 ms
fontawesome-webfont.woff
25 ms
masonry.pkgd.min.js
67 ms
js
52 ms
recaptcha__en.js
122 ms
analytics.js
60 ms
collect
14 ms
js
46 ms
brightwater.com accessibility score
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
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
ARIA IDs are not unique
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
[id] attributes on active, focusable elements are not unique
Heading elements are not in a sequentially-descending order
brightwater.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
brightwater.com SEO score
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Brightwater.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 Brightwater.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.
brightwater.com
Open Graph data is detected on the main page of Brightwater. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: