wp-cli.org - WP-CLI

Wp-cli.org Site Title

WP-CLI | WP-CLI

Wp-cli.org Test Results

Wp-cli.org Mobile Performance: 89/100

Quick overview:

Opportunities

These suggestions can help your page load faster. They don't directly affect the Performance score.

Properly size images. Potential savings of 142 KiB

Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

Serve images in next-gen formats. Potential savings of 67 KiB

Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.

Diagnostics

More information about the performance of your application. These numbers don't directly affect the Performance score.

Avoid `document.write()`

For users on slow connections, external scripts dynamically injected via `document.write()` can delay page load by tens of seconds. Learn more.

Ensure text remains visible during webfont load

Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.

Serve static assets with an efficient cache policy

7 resources found

A long cache lifetime can speed up repeat visits to your page. Learn more.

Largest Contentful Paint element

1 element found

This is the largest contentful element painted within the viewport. Learn More

Avoid chaining critical requests

11 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.

Avoid long main-thread tasks

4 long tasks found

Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn more

Keep request counts low and transfer sizes small

24 requests • 251 KiB

To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Wp-cli.org Mobile SEO: 81/100

Quick overview:

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Document does not have a meta description

Meta descriptions may be included in search results to concisely summarize page content. Learn more. Description text is empty.

Document doesn't have a valid `hreflang`

hreflang links tell search engines what version of a page they should list in search results for a given language or region. Learn more.

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

82% 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.

Wp-cli.org Mobile Best Practices: 85/100

Quick overview:

Trust and Safety

Links to cross-origin destinations are unsafe

Add `rel="noopener"` or `rel="noreferrer"` to any external links to improve performance and prevent security vulnerabilities. Learn more.

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 servedover 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.

Wp-cli.org Mobile Progressive Web App: 46/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.

Does not provide a valid `apple-touch-icon`

For ideal appearance on iOS when users add a progressive web app to the home screen, define an `apple-touch-icon`. It must point to a non-transparent 192px (or 180px) square PNG. Learn More.

Manifest doesn't have a maskable icon

A maskable icon ensures that the image fills the entire shape without being letterboxed when installing the app on a device. Learn more. No manifest was fetched

Installable

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.

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 use HTTPS

1 insecure request found

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.

Wp-cli.org Mobile Accessibility: 0/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.

Form elements do not have associated labels

Labels ensure that form controls are announced properly by assistive technologies, like 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.

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.

Contrast

These are opportunities to improve the legibility of your content.

Background and foreground colors have a sufficient contrast ratio

Low-contrast text is difficult or impossible for many users to read. Learn more.

Similar tests

www.wp-cli.com
www.wp-cli.net
www.wp-cli.org
www.wp-cli.info
www.wp-cli.biz
www.wp-cli.us
www.wp-cli.mobi
www.p-cli.org
www.wp-cli.org
www.qp-cli.org
www.wqp-cli.org
www.qwp-cli.org
www.ap-cli.org
www.wap-cli.org
www.awp-cli.org
www.sp-cli.org
www.wsp-cli.org
www.swp-cli.org
www.ep-cli.org
www.wep-cli.org
www.ewp-cli.org
www.w-cli.org
www.wo-cli.org
www.wpo-cli.org
www.wop-cli.org
www.wl-cli.org
www.wpl-cli.org
www.wlp-cli.org
www.wpcli.org
www.wp-li.org
www.wp-xli.org
www.wp-cxli.org
www.wp-xcli.org
www.wp-dli.org
www.wp-cdli.org
www.wp-dcli.org
www.wp-fli.org
www.wp-cfli.org
www.wp-fcli.org
www.wp-vli.org
www.wp-cvli.org
www.wp-vcli.org
www.wp-ci.org
www.wp-cpi.org
www.wp-clpi.org
www.wp-cpli.org
www.wp-coi.org
www.wp-cloi.org
www.wp-coli.org
www.wp-cki.org
www.wp-clki.org
www.wp-ckli.org
www.wp-cl.org
www.wp-clu.org
www.wp-cliu.org
www.wp-clui.org
www.wp-clj.org
www.wp-clij.org
www.wp-clji.org
www.wp-clk.org
www.wp-clik.org
www.wp-clo.org
www.wp-clio.org