Wpxz.org Site Title

WPXZ - WordPress实用指南

Wpxz.org Meta Description

WPXZ是一个面向初学者的WordPress教程网站。网站的主要目标是提供高质量且细致的WordPress使用技巧,使WordPress初学者可以快速改进自己的网站。

Wpxz.org Test Results

Wpxz.org Mobile Performance: 54/100
Quick overview:
Opportunities
These suggestions can help your page load faster. They don't directly affect the Performance score.
Reduce server response times (TTFB). Root document took 5,230 ms
Time To First Byte identifies the time at which your server sends a response. Learn more.
Avoid multiple page redirects. Potential savings of 1,260 ms
Redirects introduce additional delays before the page can be loaded. Learn more.
Eliminate render-blocking resources. Potential savings of 660 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.
Remove unused CSS. Potential savings of 37 KB
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn more.
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Minimize main-thread work
3.5 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more
Reduce JavaScript execution time
1.6 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.
Avoid chaining critical requests
3 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.
Keep request counts low and transfer sizes small
29 requests • 363 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Wpxz.org Mobile SEO: 98/100
Quick overview:
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. Learn more.
Tap targets are not sized appropriately
83% appropriately sized tap targets
Interactive elements like buttons and links should be large enough (48x48px), and have enough space around them, to be easy enough to tap without overlapping onto other elements. Learn more.

Wpxz.org Mobile Best Practices: 85/100
Quick overview:
Does not use HTTPS
2 insecure requests found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. 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.
Includes front-end JavaScript libraries with known security vulnerabilities
2 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers. Learn more.
Wpxz.org Mobile Progressive Web App: 52/100
Quick overview:
PWA Optimized
Does not set a theme color for the address bar.
The browser address bar can be themed to match your site. Learn more. Failures: No manifest was fetched, No `<meta name="theme-color">` tag found.
Is not configured for a custom splash screen
A themed splash screen ensures a high-quality experience when users launch your app from their homescreens. Learn more. Failures: No manifest was fetched.
Fast and reliable
`start_url` does not respond with a 200 when offline
A service worker enables your web app to be reliable in unpredictable network conditions. Learn more. No usable web app manifest found on page.
Current page does not respond with a 200 when offline
If you're building a Progressive Web App, consider using a service worker so that your app can work offline. Learn more.
Installable
Does not use HTTPS
2 insecure requests found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. 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.
Web app manifest does not meet the installability requirements
Browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement. Learn more. Failures: No manifest was fetched.
Does not register a service worker that controls page and `start_url`
The service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. Learn more.
Wpxz.org Mobile Accessibility: 78/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.
Buttons do not have an accessible name
When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn more.
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 more.
Form elements do not have associated labels
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more.
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 more.
Tables and lists
These are opportunities to to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
List items (`<li>`) are not contained within `<ul>` or `<ol>` parent elements.
Screen readers require list items (`<li>`) to be contained within a parent `<ul>` or `<ol>` to be announced properly. Learn more.
Similar tests
www.wpxz.com
www.wpxz.net
www.wpxz.org
www.wpxz.info
www.wpxz.biz
www.wpxz.us
www.wpxz.mobi
www.pxz.org
www.wpxz.org
www.qpxz.org
www.wqpxz.org
www.qwpxz.org
www.apxz.org
www.wapxz.org
www.awpxz.org
www.spxz.org
www.wspxz.org
www.swpxz.org
www.epxz.org
www.wepxz.org
www.ewpxz.org
www.wxz.org
www.woxz.org
www.wpoxz.org
www.wopxz.org
www.wlxz.org
www.wplxz.org
www.wlpxz.org
www.wpz.org
www.wpzz.org
www.wpxzz.org
www.wpzxz.org
www.wpsz.org
www.wpxsz.org
www.wpsxz.org
www.wpdz.org
www.wpxdz.org
www.wpdxz.org
www.wpcz.org
www.wpxcz.org
www.wpcxz.org
www.wpx.org
www.wpxx.org
www.wpxzx.org
www.wpxxz.org
www.wpxs.org
www.wpxzs.org
www.wpxa.org
www.wpxza.org
www.wpxaz.org
Last Tested: