Ioz.ac.cn Test Results

Ioz.ac.cn Mobile Performance: 56/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,850 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.
Enable text compression
Potential savings of 370 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more about text compression.
Efficiently encode images
Potential savings of 2,493 KiB
Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.
Reduce unused JavaScript
Potential savings of 135 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.
Serve images in next-gen formats
Potential savings of 4,381 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.
Reduce unused CSS
Potential savings of 179 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.
Largest Contentful Paint element
21,600 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Avoid multiple page redirects
Potential savings of 2,240 ms
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Minify CSS
Potential savings of 23 KiB
Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.
Minimize main-thread work
2.2 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 an excessive DOM size
1,519 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn how to avoid an excessive DOM size.
Serve static assets with an efficient cache policy
130 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
Defer offscreen images
Potential savings of 380 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.
Properly size images
Potential savings of 179 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.
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.
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
Avoid enormous network payloads
Total size was 6,421 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Minify JavaScript
Potential savings of 3 KiB
Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.
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().
First Meaningful Paint
5.2 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
8.1 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.

Ioz.ac.cn Mobile SEO: 75/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.
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.
Crawling and Indexing
To appear in search results, crawlers need access to your app.
robots.txt is not valid
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. Lighthouse was unable to download a robots.txt file

Ioz.ac.cn Mobile Best Practices: 52/100
Quick overview:
User Experience
Displays images with incorrect aspect ratio
Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.
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.
Trust and Safety
Does not use HTTPS
3 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.
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`
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.
Ioz.ac.cn Mobile Accessibility: 57/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.
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.
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.
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.
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.
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 tests
www.ioz.com
www.ioz.net
www.ioz.org
www.ioz.info
www.ioz.biz
www.ioz.us
www.ioz.mobi
www.oz.ac.cn
www.ioz.ac.cn
www.uoz.ac.cn
www.iuoz.ac.cn
www.uioz.ac.cn
www.joz.ac.cn
www.ijoz.ac.cn
www.jioz.ac.cn
www.koz.ac.cn
www.ikoz.ac.cn
www.kioz.ac.cn
www.ooz.ac.cn
www.iooz.ac.cn
www.oioz.ac.cn
www.iz.ac.cn
www.iiz.ac.cn
www.ioiz.ac.cn
www.iioz.ac.cn
www.ikz.ac.cn
www.iokz.ac.cn
www.ilz.ac.cn
www.iolz.ac.cn
www.iloz.ac.cn
www.ipz.ac.cn
www.iopz.ac.cn
www.ipoz.ac.cn
www.io.ac.cn
www.iox.ac.cn
www.iozx.ac.cn
www.ioxz.ac.cn
www.ios.ac.cn
www.iozs.ac.cn
www.iosz.ac.cn
www.ioa.ac.cn
www.ioza.ac.cn
www.ioaz.ac.cn
Last Tested: