75j.cn Test Results
75j.cn Mobile Performance: 0/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
Est savings of 1,590 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.
Largest Contentful Paint element
3,510 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Avoid multiple page redirects
Est savings of 1,260 ms
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Remove duplicate modules in JavaScript bundles
Est savings of 13 KiB
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers
Est savings of 1 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
Reduce unused CSS
Est savings of 139 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.
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().
Reduce unused JavaScript
Est savings of 305 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.
Enable text compression
Est savings of 447 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more about text compression.
Reduce the impact of third-party code
Third-party code blocked the main thread for 760 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn how to minimize third-party impact.
Serve static assets with an efficient cache policy
4 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
Render blocking requests
Est savings of 1,450 ms
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.
Document request latency
Est savings of 2,580 ms
Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.
Network dependency tree
Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
Use efficient cache lifetimes
Est savings of 20 KiB
A long cache lifetime can speed up repeat visits to your page. Learn more.
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.
Metrics
Collects all available metrics.
75j.cn Mobile SEO: 73/100
Quick overview:
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
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.
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.
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.
75j.cn Mobile Best Practices: 59/100
Quick overview:
Trust and Safety
Does not use HTTPS
12 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.
General
Uses deprecated APIs
1 warning found
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
75j.cn Mobile Accessibility: 71/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.
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.
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.
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.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` are missing some or all of those required children.
Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.
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.
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.75j.com
www.75j.net
www.75j.org
www.75j.info
www.75j.biz
www.75j.us
www.75j.mobi
www.5j.cn
www.75j.cn
www.7j.cn
www.75.cn
www.75n.cn
www.75jn.cn
www.75nj.cn
www.75h.cn
www.75jh.cn
www.75hj.cn
www.75u.cn
www.75ju.cn
www.75uj.cn
www.75i.cn
www.75ji.cn
www.75ij.cn
www.75k.cn
www.75jk.cn
www.75kj.cn
www.75m.cn
www.75jm.cn
www.75mj.cn
www.75j.net
www.75j.org
www.75j.info
www.75j.biz
www.75j.us
www.75j.mobi
www.5j.cn
www.75j.cn
www.7j.cn
www.75.cn
www.75n.cn
www.75jn.cn
www.75nj.cn
www.75h.cn
www.75jh.cn
www.75hj.cn
www.75u.cn
www.75ju.cn
www.75uj.cn
www.75i.cn
www.75ji.cn
www.75ij.cn
www.75k.cn
www.75jk.cn
www.75kj.cn
www.75m.cn
www.75jm.cn
www.75mj.cn