Water.blog Test Results

Water.blog Mobile Performance: 76/100
Quick overview:
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Reduce unused CSS
Potential savings of 52 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.
Reduce unused JavaScript
Potential savings of 24 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
Avoid multiple page redirects
Potential savings of 630 ms
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Largest Contentful Paint element
4,980 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Eliminate render-blocking resources
Potential savings of 1,410 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn how to eliminate render-blocking resources.
Properly size images
Potential savings of 68 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.
Ensure text remains visible during webfont load
Leverage the `font-display` CSS feature to ensure text is user-visible while webfonts are loading. Learn more about `font-display`.
Avoid serving legacy JavaScript to modern browsers
Potential savings of 11 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers. Learn how to use modern JavaScript
Serve static assets with an efficient cache policy
9 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
Time to Interactive
5.0 s
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

Water.blog Mobile SEO: 100/100
Quick overview:

Water.blog Mobile Best Practices: 83/100
Quick overview:
Trust and Safety
Does not use HTTPS
1 insecure request found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more about HTTPS.
Water.blog Mobile Accessibility: 81/100
Quick overview:
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.
Uses ARIA roles on incompatible elements
Many HTML elements can only be assigned certain ARIA roles. Using ARIA roles where they are not allowed can interfere with the accessibility of the web page. Learn more about ARIA roles.
Best practices
These items highlight common accessibility best practices.
Touch targets do not have sufficient size or spacing.
Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
List items (`<li>`) are not contained within `<ul>`, `<ol>` or `<menu>` parent elements.
Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.
Contrast
These are opportunities to improve the legibility of your content.
Background and foreground colors do not have a sufficient contrast ratio.
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Similar sites
Similar tests
www.water.com
www.water.net
www.water.org
www.water.info
www.water.biz
www.water.us
www.water.mobi
www.ater.blog
www.water.blog
www.qater.blog
www.wqater.blog
www.qwater.blog
www.aater.blog
www.waater.blog
www.awater.blog
www.sater.blog
www.wsater.blog
www.swater.blog
www.eater.blog
www.weater.blog
www.ewater.blog
www.wter.blog
www.wqter.blog
www.waqter.blog
www.wwter.blog
www.wawter.blog
www.wwater.blog
www.wster.blog
www.waster.blog
www.wzter.blog
www.wazter.blog
www.wzater.blog
www.waer.blog
www.warer.blog
www.watrer.blog
www.warter.blog
www.wafer.blog
www.watfer.blog
www.wafter.blog
www.wager.blog
www.watger.blog
www.wagter.blog
www.wayer.blog
www.watyer.blog
www.wayter.blog
www.watr.blog
www.watwr.blog
www.watewr.blog
www.watwer.blog
www.watsr.blog
www.watesr.blog
www.watser.blog
www.watdr.blog
www.watedr.blog
www.watder.blog
www.watrr.blog
www.waterr.blog
www.wate.blog
www.watee.blog
www.watere.blog
www.wateer.blog
www.wated.blog
www.waterd.blog
www.watef.blog
www.waterf.blog
www.watefr.blog
www.watet.blog
www.watert.blog
www.watetr.blog
Last Tested: