Chwmai.com Test Results

Chwmai.com Mobile Performance: 40/100
Quick overview:
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Properly size images
Potential savings of 3,994 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.
Reduce unused JavaScript
Potential savings of 47 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.
Minimize main-thread work
7.1 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work
Avoid large layout shifts
8 layout shifts found
These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS
Largest Contentful Paint element
6,850 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Reduce unused CSS
Potential savings of 12 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.
Efficiently encode images
Potential savings of 1,412 KiB
Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.
Eliminate render-blocking resources
Potential savings of 730 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.
Defer offscreen images
Potential savings of 136 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn how to defer offscreen images.
Serve images in next-gen formats
Potential savings of 5,952 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more about modern image formats.
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`.
Does not use passive listeners to improve scrolling performance
Consider marking your touch and wheel event listeners as `passive` to improve your page's scroll performance. Learn more about adopting passive event listeners.
Avoid enormous network payloads
Total size was 8,356 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Serve static assets with an efficient cache policy
35 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
Image elements do not have explicit `width` and `height`
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions
Minify CSS
Potential savings of 3 KiB
Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.
Time to Interactive
17.6 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.
First Meaningful Paint
2.2 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric.

Chwmai.com Mobile SEO: 83/100
Quick overview:
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Image elements do not have `[alt]` attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.
Crawling and Indexing
To appear in search results, crawlers need access to your app.
robots.txt is not valid
66 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.

Chwmai.com Mobile Best Practices: 59/100
Quick overview:
Trust and Safety
Does not use HTTPS
37 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.
General
Browser errors were logged to the console
Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit
Uses deprecated APIs
1 warning found
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Chwmai.com Mobile Accessibility: 71/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.
ARIA toggle fields do not have accessible names
When a toggle field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about toggle fields.
ARIA input fields do not have accessible names
When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about input field labels.
Navigation
These are opportunities to improve keyboard navigation in your application.
Heading elements are not in a sequentially-descending order
Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.
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.
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.
Links do not have a discernible name
Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.
Image elements do not have `[alt]` attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.
Best practices
These items highlight common accessibility best practices.
`[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5.
Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
`<html>` element does not have a `[lang]` attribute
If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.
Similar sites
Similar tests
www.chwmai.com
www.chwmai.net
www.chwmai.org
www.chwmai.info
www.chwmai.biz
www.chwmai.us
www.chwmai.mobi
www.hwmai.com
www.chwmai.com
www.xhwmai.com
www.cxhwmai.com
www.xchwmai.com
www.dhwmai.com
www.cdhwmai.com
www.dchwmai.com
www.fhwmai.com
www.cfhwmai.com
www.fchwmai.com
www.vhwmai.com
www.cvhwmai.com
www.vchwmai.com
www.cwmai.com
www.cbwmai.com
www.chbwmai.com
www.cbhwmai.com
www.cgwmai.com
www.chgwmai.com
www.cghwmai.com
www.cywmai.com
www.chywmai.com
www.cyhwmai.com
www.cuwmai.com
www.chuwmai.com
www.cuhwmai.com
www.cjwmai.com
www.chjwmai.com
www.cjhwmai.com
www.cnwmai.com
www.chnwmai.com
www.cnhwmai.com
www.chmai.com
www.chqmai.com
www.chwqmai.com
www.chqwmai.com
www.chamai.com
www.chwamai.com
www.chawmai.com
www.chsmai.com
www.chwsmai.com
www.chswmai.com
www.chemai.com
www.chwemai.com
www.chewmai.com
www.chwai.com
www.chwnai.com
www.chwmnai.com
www.chwnmai.com
www.chwjai.com
www.chwmjai.com
www.chwjmai.com
www.chwkai.com
www.chwmkai.com
www.chwkmai.com
www.chwmi.com
www.chwmqi.com
www.chwmaqi.com
www.chwmqai.com
www.chwmwi.com
www.chwmawi.com
www.chwmwai.com
www.chwmsi.com
www.chwmasi.com
www.chwmsai.com
www.chwmzi.com
www.chwmazi.com
www.chwmzai.com
www.chwma.com
www.chwmau.com
www.chwmaiu.com
www.chwmaui.com
www.chwmaj.com
www.chwmaij.com
www.chwmaji.com
www.chwmak.com
www.chwmaik.com
www.chwmaki.com
www.chwmao.com
www.chwmaio.com
www.chwmaoi.com
www.chwmai.con
Last Tested: