Wx.vzan.com Site Title

加载中...

Wx.vzan.com Test Results

Wx.vzan.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.
Reduce initial server response time
Root document took 740 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.
Avoid multiple page redirects
Est savings of 43,930 ms
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Minimize main-thread work
2.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
Reduce unused CSS
Est savings of 408 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.
Minify JavaScript
Est savings of 18 KiB
Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.
Enable text compression
Est savings of 24 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more about text compression.
Largest Contentful Paint element
17,190 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Avoid serving legacy JavaScript to modern browsers
Est savings of 49 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support legacy browsers. Learn why most sites can deploy ES6+ code without transpiling
Avoid large layout shifts
10 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
Reduce unused JavaScript
Est savings of 986 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.
Properly size images
Est savings of 4,506 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.
Defer offscreen images
Est savings of 2,050 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
Est savings of 1,368 KiB
Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.
Serve static assets with an efficient cache policy
88 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
Preload Largest Contentful Paint image
Est savings of -1,980 ms
If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP. Learn more about preloading LCP elements.
Serve images in next-gen formats
Est savings of 4,098 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.
Avoid enormous network payloads
Total size was 7,594 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Render blocking requests
Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.
Layout shift culprits
Layout shifts occur when elements move absent any user interaction. Investigate the causes of layout shifts, such as elements being added, removed, or their fonts changing as the page loads.
Time to Interactive
33.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.
LCP request discovery
Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading
Optimize DOM size
A large DOM can increase the duration of style calculations and layout reflows, impacting page responsiveness. A large DOM will also increase memory usage. Learn how to avoid an excessive DOM size.
Forced reflow
Many APIs, typically reading layout geometry, force the rendering engine to pause script execution in order to calculate the style and layout. Learn more about forced reflow and its mitigations.
Document request latency
Est savings of 3 KiB
Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.
Legacy JavaScript
Est savings of 187 KiB
Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling
Improve image delivery
Est savings of 5,067 KiB
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
Use efficient cache lifetimes
Est savings of 3,304 KiB
A long cache lifetime can speed up repeat visits to your page. Learn more.
Max Potential First Input Delay
170 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.

Wx.vzan.com Mobile SEO: 91/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.

Wx.vzan.com 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.
General
Missing source maps for large first-party JavaScript
Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.
Wx.vzan.com Mobile Accessibility: 83/100
Quick overview:
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.
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.
Similar sites
Similar tests
www.wx.com
www.wx.net
www.wx.org
www.wx.info
www.wx.biz
www.wx.us
www.wx.mobi
www.x.vzan.com
www.wx.vzan.com
www.qx.vzan.com
www.wqx.vzan.com
www.qwx.vzan.com
www.ax.vzan.com
www.wax.vzan.com
www.awx.vzan.com
www.sx.vzan.com
www.wsx.vzan.com
www.swx.vzan.com
www.ex.vzan.com
www.wex.vzan.com
www.ewx.vzan.com
www.w.vzan.com
www.wz.vzan.com
www.wxz.vzan.com
www.wzx.vzan.com
www.ws.vzan.com
www.wxs.vzan.com
www.wd.vzan.com
www.wxd.vzan.com
www.wdx.vzan.com
www.wc.vzan.com
www.wxc.vzan.com
www.wcx.vzan.com
Last Tested: