Chwb.org Test Results
Chwb.org Mobile Performance: 98/100
Quick overview:
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Eliminate render-blocking resources
Potential savings of 580 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.
Reduce unused JavaScript
Potential savings of 20 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.
Reduce initial server response time
Root document took 640 ms
Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.
Reduce unused CSS
Potential savings of 15 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.
Serve static assets with an efficient cache policy
5 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
Chwb.org Mobile SEO: 77/100
Quick overview:
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Document does not have a meta description
Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.
Document doesn't have a `<title>` element
The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more about document titles.
Crawling and Indexing
To appear in search results, crawlers need access to your app.
robots.txt is not valid
172 errors found
If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.
Chwb.org Mobile Best Practices: 76/100
Quick overview:
Trust and Safety
Does not use HTTPS
6 insecure requests 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.
Does not redirect HTTP traffic to HTTPS
Make sure that you redirect all HTTP traffic to HTTPS in order to enable secure web features for all your users. Learn more.
User Experience
Serves images with low resolution
Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.
Chwb.org Mobile Accessibility: 83/100
Quick overview:
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.
Image elements have `[alt]` attributes that are redundant text.
Informative elements should aim for short, descriptive alternative text. Alternative text that is exactly the same as the text adjacent to the link or image is potentially confusing for screen reader users, because the text will be read twice. Learn more about the `alt` attribute.
Document doesn't have a `<title>` element
The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more about document titles.
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.
Similar sites
Similar tests
www.chwb.com
www.chwb.net
www.chwb.org
www.chwb.info
www.chwb.biz
www.chwb.us
www.chwb.mobi
www.hwb.org
www.chwb.org
www.xhwb.org
www.cxhwb.org
www.xchwb.org
www.dhwb.org
www.cdhwb.org
www.dchwb.org
www.fhwb.org
www.cfhwb.org
www.fchwb.org
www.vhwb.org
www.cvhwb.org
www.vchwb.org
www.cwb.org
www.cbwb.org
www.chbwb.org
www.cbhwb.org
www.cgwb.org
www.chgwb.org
www.cghwb.org
www.cywb.org
www.chywb.org
www.cyhwb.org
www.cuwb.org
www.chuwb.org
www.cuhwb.org
www.cjwb.org
www.chjwb.org
www.cjhwb.org
www.cnwb.org
www.chnwb.org
www.cnhwb.org
www.chb.org
www.chqb.org
www.chwqb.org
www.chqwb.org
www.chab.org
www.chwab.org
www.chawb.org
www.chsb.org
www.chwsb.org
www.chswb.org
www.cheb.org
www.chweb.org
www.chewb.org
www.chw.org
www.chwv.org
www.chwbv.org
www.chwvb.org
www.chwg.org
www.chwbg.org
www.chwgb.org
www.chwh.org
www.chwbh.org
www.chwhb.org
www.chwn.org
www.chwbn.org
www.chwnb.org
www.chwb.net
www.chwb.org
www.chwb.info
www.chwb.biz
www.chwb.us
www.chwb.mobi
www.hwb.org
www.chwb.org
www.xhwb.org
www.cxhwb.org
www.xchwb.org
www.dhwb.org
www.cdhwb.org
www.dchwb.org
www.fhwb.org
www.cfhwb.org
www.fchwb.org
www.vhwb.org
www.cvhwb.org
www.vchwb.org
www.cwb.org
www.cbwb.org
www.chbwb.org
www.cbhwb.org
www.cgwb.org
www.chgwb.org
www.cghwb.org
www.cywb.org
www.chywb.org
www.cyhwb.org
www.cuwb.org
www.chuwb.org
www.cuhwb.org
www.cjwb.org
www.chjwb.org
www.cjhwb.org
www.cnwb.org
www.chnwb.org
www.cnhwb.org
www.chb.org
www.chqb.org
www.chwqb.org
www.chqwb.org
www.chab.org
www.chwab.org
www.chawb.org
www.chsb.org
www.chwsb.org
www.chswb.org
www.cheb.org
www.chweb.org
www.chewb.org
www.chw.org
www.chwv.org
www.chwbv.org
www.chwvb.org
www.chwg.org
www.chwbg.org
www.chwgb.org
www.chwh.org
www.chwbh.org
www.chwhb.org
www.chwn.org
www.chwbn.org
www.chwnb.org