Cshfwh.com Test Results

Cshfwh.com Mobile Performance: 65/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 1,260 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 initial server response time
Root document took 620 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.
Largest Contentful Paint element
6,450 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Serve images in next-gen formats
Potential savings of 3,969 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.
Minimize main-thread work
5.5 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
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
A `<meta name="viewport">` not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more about using the viewport meta tag. No `<meta name="viewport">` tag found
Defer offscreen images
Potential savings of 68 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.
Efficiently encode images
Potential savings of 2,743 KiB
Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.
Avoid `document.write()`
For users on slow connections, external scripts dynamically injected via `document.write()` can delay page load by tens of seconds. Learn how to avoid document.write().
Serve static assets with an efficient cache policy
132 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
Minify JavaScript
Potential savings of 6 KiB
Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.
Reduce unused JavaScript
Potential savings of 21 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.
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
Properly size images
Potential savings of 2,615 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.
Avoid serving legacy JavaScript to modern browsers
Potential savings of 9 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
Reduce JavaScript execution time
1.7 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.
Avoid enormous network payloads
Total size was 5,555 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Max Potential First Input Delay
150 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.
First Meaningful Paint
2.4 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric.
Time to Interactive
3.5 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.

Cshfwh.com Mobile SEO: 75/100
Quick overview:
Crawling and Indexing
To appear in search results, crawlers need access to your app.
robots.txt is not valid
79 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.
Links are not crawlable
Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable
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.

Cshfwh.com Mobile Best Practices: 38/100
Quick overview:
Trust and Safety
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.
Does not use HTTPS
111 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.
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
2 warnings found
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Issues were logged in the `Issues` panel in Chrome Devtools
Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.
Browser Compatibility
Page lacks the HTML doctype, thus triggering quirks-mode
Specifying a doctype prevents the browser from switching to quirks-mode. Learn more about the doctype declaration. Document contains a `doctype` that triggers `limited-quirks-mode`
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.
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
A `<meta name="viewport">` not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more about using the viewport meta tag. No `<meta name="viewport">` tag found
Displays images with incorrect aspect ratio
Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.
Document doesn't use legible font sizes
Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px. Learn more about legible font sizes. Text is illegible because there's no viewport meta tag optimized for mobile screens.
Cshfwh.com Mobile Accessibility: 30/100
Quick overview:
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.
Identical links have the same purpose.
Links with the same destination should have the same description, to help users understand the link's purpose and decide whether to follow it. Learn more about identical links.
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.
Form elements do not have associated labels
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.
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.
`<input type="image">` elements do not have `[alt]` text
When an image is being used as an `<input>` button, providing alternative text can help screen reader users understand the purpose of the button. Learn about input image alt text.
`<frame>` or `<iframe>` elements do not have a title
Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Lists do not contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.
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.
Contrast
These are opportunities to improve the legibility of your content.
Links rely on color to be distinguishable.
Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.
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 tests
www.cshfwh.com
www.cshfwh.net
www.cshfwh.org
www.cshfwh.info
www.cshfwh.biz
www.cshfwh.us
www.cshfwh.mobi
www.shfwh.com
www.cshfwh.com
www.xshfwh.com
www.cxshfwh.com
www.xcshfwh.com
www.dshfwh.com
www.cdshfwh.com
www.dcshfwh.com
www.fshfwh.com
www.cfshfwh.com
www.fcshfwh.com
www.vshfwh.com
www.cvshfwh.com
www.vcshfwh.com
www.chfwh.com
www.cwhfwh.com
www.cswhfwh.com
www.cwshfwh.com
www.cehfwh.com
www.csehfwh.com
www.ceshfwh.com
www.cdhfwh.com
www.csdhfwh.com
www.czhfwh.com
www.cszhfwh.com
www.czshfwh.com
www.cxhfwh.com
www.csxhfwh.com
www.cahfwh.com
www.csahfwh.com
www.cashfwh.com
www.csfwh.com
www.csbfwh.com
www.cshbfwh.com
www.csbhfwh.com
www.csgfwh.com
www.cshgfwh.com
www.csghfwh.com
www.csyfwh.com
www.cshyfwh.com
www.csyhfwh.com
www.csufwh.com
www.cshufwh.com
www.csuhfwh.com
www.csjfwh.com
www.cshjfwh.com
www.csjhfwh.com
www.csnfwh.com
www.cshnfwh.com
www.csnhfwh.com
www.cshwh.com
www.cshcwh.com
www.cshfcwh.com
www.cshcfwh.com
www.cshdwh.com
www.cshfdwh.com
www.cshdfwh.com
www.cshrwh.com
www.cshfrwh.com
www.cshrfwh.com
www.cshtwh.com
www.cshftwh.com
www.cshtfwh.com
www.cshgwh.com
www.cshfgwh.com
www.cshvwh.com
www.cshfvwh.com
www.cshvfwh.com
www.cshfh.com
www.cshfqh.com
www.cshfwqh.com
www.cshfqwh.com
www.cshfah.com
www.cshfwah.com
www.cshfawh.com
www.cshfsh.com
www.cshfwsh.com
www.cshfswh.com
www.cshfeh.com
www.cshfweh.com
www.cshfewh.com
www.cshfw.com
www.cshfwb.com
www.cshfwhb.com
www.cshfwbh.com
www.cshfwg.com
www.cshfwhg.com
www.cshfwgh.com
www.cshfwy.com
www.cshfwhy.com
www.cshfwyh.com
www.cshfwu.com
www.cshfwhu.com
www.cshfwuh.com
www.cshfwj.com
www.cshfwhj.com
www.cshfwjh.com
www.cshfwn.com
www.cshfwhn.com
www.cshfwnh.com
www.cshfwh.con
Last Tested: